Category Archives : Uncategorized

Getting Outlook to Autodiscover Office 365

http://www.mcbsys.com/blog/2011/08/using-office-365-in-an-sbs-2008-environment-take-2/

While editing the Service Connection Point in Active Directory Sites and Services does work, it’s probably not the “approved” way to do things.

The support manager recommended that I instead use the Exchange Management Shell to entirely remove the Autodiscover Virtual Directory using Remove-AutodiscoverVirtualDirectory. Here’s how I did that:

1. Open an elevated command prompt and back up the IIS configuration (explained here):

%windir%\system32\inetsrv\appcmd.exe add backup "Before Removing Autodiscover"

2. Open an elevated Exchange Management Shell and retrieve the current autodiscover virtual directory:

Get-AutodiscoverVirtualDirectory | fl Name, Server, InternalUrl, ExternalUrl, Identity

Save the results to a text file in case you need them to re-set the virtual directory later (see Schyler Jones’ comment below on December 2, 2015). Copy the Identity value to the clipboard.

3. In the Exchange Management Shell, remove the autodiscover virtual directory:

Remove-AutodiscoverVirtualDirectory –Identity "<identity value retrieved above>"

You will have to confirm by typing a “Y”.

4. Check that the autodiscover virtual directory is gone:

Get-AutodiscoverVirtualDirectory | fl Name, Server, InternalUrl, Identity

This should now return nothing.

5. Now, with Outlook running on a desktop, hold the Ctrl button, right-click on the Outlook icon in the system tray, and select Test E-mail AutoConfiguration. Enter your email address and password and click the Test button. The results should come from the Office 365 server.

Office 365 Powershell Login

Set-ExecutionPolicy Unrestricted -Force
$O365CREDS = Get-Credential
$SESSION = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell/ -Credential $O365CREDS -Authentication Basic -AllowRedirection
Import-PSSession $SESSION
Connect-MsolService -Credential $O365CREDS

 

Remove-PSSession $Session

OS X El Capitan: Start up in single-user mode

https://support.apple.com/kb/PH21893?viewlocale=en_US&locale=en_US

To troubleshoot your computer’s startup sequence using only UNIX commands, start up in single-user mode. You should do this only if you’re comfortable with UNIX.

  1. Choose Apple menu > Restart, or press the power button if your Mac is turned off.

  2. Press Command-S as your Mac starts up.

    The screen is black with standard white text. You can now run the UNIX commands that you want.

In single-user mode, not all OS X functions are available. To use the standard OS X interface or other high-level aspects of OS X, you need to start up in the standard mode.

To switch back to the standard OS X interface, type reboot, then press Return.

Delete CBS Logs

As for the logs not properly creating the cabinet files they should be, try the following:

1. Disable the trusted installer service (Windows Modules Installer)

2. Delete/move all of the current CBS log files from the \Windows\CBS\Logs directory

3. Restart the Windows Modules Installer service

4. Wait for log size to be large enough to compress properly into cabinet files

Surface Pro Two-Button Shutdown

Solution 3: Two-button shutdown (Surface Pro models only)

Important

Don’t use this process on Surface RT, Surface 2, or Surface 3.

Use this two-button shutdown process to ensure that your Surface is turned off completely. Here’s how:

Step 1:
Press and hold the power button on your Surface for 30 seconds and then release it.

Step 2:
Press and hold the volume-up button and the power button at the same time for at least 15 seconds and then release both.
The screen may flash the Surface logo, but continue holding the buttons down for at least 15 seconds.

Step 3:
After you release the buttons, wait 10 seconds.

Step 4:
Press and release the power button to turn your Surface back on.

Sorry, something went wrong and Word was unable to start. (24)

Started getting errors when previewing Office documents in Explorer preview pane.  When selecting a Word document and waiting for the preview to appear, we’d get this:

Sorry, something went wrong and Word was unable to start. (24)

Excel docs also had an error but it consisted of a dialog with a red exclamation point.

All of the machines this happened on all originally had 64-bit Office 2013 before it was uninstalled and replaced with 32-bit Office 2013 because of compatibility issues with a required plug-in.

In trying to figure this out, various uninstall/reinstall methods were used but nothing made a difference until I fired up procmon and used it to make comparisons with a working machine.

On a system that only ever had 32-bit Office 2013, the following key existed:

HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{84F66100-FF7C-4fb4-B0C0-02CD7FB668FE}

On a system with 64-bit Office this key also existed

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{84F66100-FF7C-4fb4-B0C0-02CD7FB668FE}

The 32-bit key contained information while the 64-bit key was empty.

As soon as that HKLM key was renamed(eventually deleted), everything worked again – didn’t even need to restart or log out.

It seems like the Office uninstaller might be forgetting this key when it does its thing.

Hope this helps some people

More:

http://www.cyann.net/2015/07/10/solved-not-enough-memory-or-system-resources-to-start-office-preview/

To fix these errors and repair the preview pane, run Regedit as administrator and delete these registry keys:

Microsoft Excel previewer:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{00020827-0000-0000-C000-000000000046}

Microsoft PowerPoint previewer:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{65235197-874B-4A07-BDC5-E65EA825B718}

Microsoft Word previewer:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{84F66100-FF7C-4fb4-B0C0-02CD7FB668FE}

Microsoft Visio previewer:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{21E17C2F-AD3A-4b89-841F-09CFE02D16B7}

Office 2013 Change Product Key

https://community.spiceworks.com/how_to/48973-remove-and-re-add-license-key-for-office-2013-on-office-365

 

Open a Command Prompt window, and then take one of the following actions:

• If you installed the 64-bit version of Office 2013, move to the following folder: C:\Program Files\Microsoft Office\Office15
• If you installed the 32-bit version of Office 2013, move to the following folder: C:\Program Files (x86)\Microsoft Office\Office15

 

cscript ospp.vbs /dstatus

 

cscript ospp.vbs /unpkey:<last five characters of product key>

 

Restart

« Previous PageNext Page »
Back to Top