I have been struggling a bit with adding .NET Framework 3.5 on a few systems (and reference image for MDT). The posts on MSDN and TechNet are good, but not always crystal clear.

Here is how I solved the issues we were experiencing…

Recently the Helpdesk have been getting cases about slow delivery times due to Office 365 ATP Safe Attachments. We have created a script to retrieve the data from Exchange Online, and then used Power BI to visualize it.

I finally I got some time to play with the new Azure Active Directory Sync tool and its configuration.

The installation was very straight forward. The step-by-step instruction are provided on MSDN. The administration tools and scripts are located in difference places compared to DirSync which was little confusing in the beginning.

A customer of mine recently started deploying Windows 8 in their environment. MDT was set up and the deployment was working fine, but after deployment the Windows 8 machines wouldn’t connect to the WSUS server.

When trying to connect to the WSUS-server through the Control Panel I got an error message.

My customer has bought a Hewlett-Packard server with a Windows Server 2012 ROK (Reseller Option Kit) license.
However this customer had some issues with the installation of the license on the Hyper-V guest server. Since the Windows server does not recognize the ‘hardware’ as a Proliant server, licensing will not succeed.

However there is a simple solution…