Windows Server

**This article describes the licensing options you have when you want to deploy Windows Server Virtual Machines in Azure. It’s getting complicated when you start using the Hybrid Use Benefit solution, so always contact Microsoft or your licensing supplier. **Please note that I will not answer any licensing questions. Built-in Licensing for Windows Server This type of licensing is by-far the most easy to use but it can be an expensive solution. You deploy an Azure Virtual Machine from the Portal or PowerShell and the licensing costs are automatically included with the Virtual Machine costs. But what if you want to use your existing KMS licenses which you’ve bought with your Enterprise Agreement? Or you want to use Windows Server Standard licenses instead of Datacenter licenses? ...

This video, presented by Mark Russinovich and Matt McSpirit, gives you a great overview about the design and architecture of containers. Mark will show you how to create and use the containers. Don’t forget to subscribe to the Microsoft Mechanics YouTube Channel.

Today I created a user policy in an OU where Loopback Processing was applied and where Security Filtering was set to my account to test the policy. The policy didn’t show up in the RSOP data (gpresult /h report1.html) and the policy was not getting applied. Solution: Give the Domain Computers (or the group with the computer accounts from the OU) permission to read the GPO. Because of Loopback Processing, the computer account will be used to read the GPO, instead of the user account. You can still give the Domain Computers permission to read the GPO only, and add a user or group to the Security Filtering section to make sure that the GPO will be applied to that group or users. Cheers!