Word, Excel, and RDP Crashing Due to Printer Issue

KB4541329 Appears to be the cause of this issue. Uninstalling it should permanently fix the issue.

Just ran into an issue where a user kept getting a "COM Surrogate has stopped working" every time they tried to print from Windows Photo Viewer. They also kept running into an issue where Excel, Word, and RDP connections would crash when launched.

Analyzing the crash dump that was generated (dllhost.exe) revealed the issue.
The application was not able to find the default printer. Trying to set the default through Devices and Printers in control panel resulted in another crash.
The fix was to run the command below:
(New-Object -ComObject WScript.Network).SetDefaultPrinter('PRINTER NAME')
The crashes went away once the default printer was set.

Windows Deployment Services Encountered an Error 0xc0000225

After a bad activation of BitLocker a Dell computer started giving a "no boot device found" error. I tried to re-image the computer but kept getting the error below:

Windows Deployment Services Encountered an Error 0xc0000225

Resetting all BIOS settings and clearing the TPM didn't do anything. Eventually I found that Dell computers have an option to wipe all drives. After enabling the option and wiping the drive the laptop was able to boot into WDS again.

Excel and Word Close When Opening And Saving Documents in OneDrive Folder

Just ran into an issue where Office apps would not open any documents saved in my OneDrive folder.  I would get the "Starting..." screen and then it would just close. Opening those same files from other locations like the desktop worked fine.
The event log had some errors, but they didn't really point to a specific item:
SettingSyncHost (14848) An attempt to open the file "C:\windows\system32\edbtmp.log" for read / write access failed with system error 5 (0x00000005): "Access is denied. ".  The open file operation will fail with error -1032 (0xfffffbf8).

SettingSyncHost (14848) {9842A2DC-6CA6-48E2-924F-3ECFD7461AD8}: Database recovery/restore failed with unexpected error -1216.

SettingSyncHost (14848) Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -1032.

Running ProcMon revealed that Excel and Word did not have access to %localappdata%\Mi…

Can't Delete Organizational Unit Even when Protect Object From Accidental Deletion is Disabled

I recently ran into an issue where I did not have the option to delete an Organizational unit. I made sure to uncheck "Protect Object From Accidental Deletion", and I had the appropriate permissions on the security tab.
Attempting to delete from ADSI edit resulted in the error below:

Operation failed. Error code: 0x20ce
The requested delete operation could not be performed. 
000020CW: SvcErrL DSID-0315370F, problem 5003 (WILL_NOT_PERFORM), data 0

The solution was to use redircmp to redirect new PCs to a different OU.
redircmp "OU=Servers,OU=Computers,DC=example,DC=com"

Restart Active Directory Users and Computers, and the delete option should be available for the OU.

Deploying FSLogix Profile Containers

This is an extension of my FSLogix Office 365 container guide. All of the steps in that guide should be followed before continuing onto this one.
OverviewFSLogix profile containers allow you to easily roam user files and settings across multiple machines. A VHDX file will be created and it will store all user settings. This is similar to roaming profiles, but you do not have to deal with any login delays while files copy. Instead, the VHDX file is attached to the RDS server and the user's profile loads immediately.
FSL profiles vs UPDsWindows has a native solution called User Profile Disks, but it has some big limitations. With UPDs some applications will detect that data is being stored in a UNC path and malfunction. The best example of this is the inability to install Google Chrome extensions on UPDs. FSLogix drivers trick the OS into thinking that the VHDX data is local to the machine so applications never know that the data is in a network path.

If there is a brief network loss U…

"Something went wrong" when configuring Outlook

Just had an issue where new Outlook profile creation would fail on a machine.

Autodiscover was configured correctly and working, but new profile creations would fail. The error below would show up every time.

Something went wrong.

Something went wrong and Outlook couldn't setup your account. Please try again. If the problem continues, contact your email administrator.
Eventually I noticed that the login prompt window was appearing for a fraction of a second and then disappearing.

I set the registry key below, restarted Outlook and I was able to get the auth prompt which allowed the profile to get created.

DisableADALatopWAMOverride = dword:00000001

One the profile is created you can delete the reg key since the account is already authenticated. I have also used this reg key to activate office when it shows similar symptoms (login prompt appears for a split second then disappears). Enabling this key may or may not break…

VMware ESX Install iDRAC Service Module

I'm creating this guide because the instructions on the Dell website did not work for me.
Download FilesGot to the iDRAC service Module files that apply to the ESX host (should look like the item below) Copy Files to ESXExtract the ZIP you just downloaded and copy the .VIB and (not sure if this one is actually required) file to anywhere on the datastore InstallationShutdown all VMs and put the ESX host in maintenance modeSSH into the ESX hostRun the commands belowcd /vmfs/volumes/%datastoreName%we do this to easily get the GUID of the datastoreesxcli software vib install -v /vmfs/volumes/%DataStoreGUID%/ISO/iDRAC/%iDRACFile%.vib -fMine looked like this: esxcli software vib install -v /vmfs/volumes/54311fd8-70c2redc-78546-44398f869345/ISO/iDRAC/cross_oem-dell-dcism-esxi_3.4.0.1.ESX6i-live.vib -fIf the install completes correctly you should see:  VIBs Installed: Dell_bootbank_dcism_3.4.0.1.ESXi6-1000 Reboot the ESX serverGo to the iDR…