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…

Get Alerts for Low UPD and FSLogix disk space

One of the hurdles of UPDs and FSLogix is that they cause issues if they run out of space, and they don't alert users when they are out of space. In some cases you will waste time troubleshooting when you could have resolved it in a minute by just cleaning up the disk.

I created the script below to address this issue. You can run it against your RDS servers and gateway, and you will not need to modify anything beyond the SMTP settings, thresholds, and exclusions.

The script will do the following:
Exit if it is not run on a server (you can comment this out if you use UPDs on Desktops)Query all collections on the RDG and scan all UPD paths*Must be run on the Gateway for this to workQuery FSL Profile and ODFC paths*Must be run on computers with FSL enabledIf low space disks are found the script will send you an email with a table of all the pathsIf nothing is found the script will exit. Known limitations: The script might report false positives/negatives if you modified your max UPD/FS…

Script to Logout all Users Before Restarting RDS Servers

Multiple vendors have recommended logging out all users before restarting our RDS servers. Sadly I was never able to find a script that could do everything I wanted.

I created the script below for Server 2012 + servers. The script will do the following: Logout all active users (even console users)Write errors and information into the Application event log You can find the script here:

The script will not reboot the server, but you can always add a shutdown -r -t 0 at the end, or schedule your reboot script to run right after this one.

Enforce Office Add-ins

This guide will show you how to force add-ins to load in Office every single time. We will also prevent users and office from disabling/enabling add-ins*.

*Outlook 2016* will sometimes disable add-ins any way, but we will apply a workaround for this.

At the end of the guide, the add-ins you configure will look like this:
Getting the ClassID of an add-in Find the ClassID of the Add-in. This is found in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\AddinsHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\AddinsHKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\Office\application name\AddinsHKEY_CURRENT_USER\Software\WOW6432Node\Microsoft\Office\application name\Addins
It is usually in a format similar to Application.OutAddin
Enforcing add-ins  We will now create a GPO that will enable or disable the add-ins that we configure. Create a GPO called Office Enforced Add-ins*Depending on the importance(compliance, auditing, etc) of this Add-in it might be a good idea to Enforce the GPO(…