Windows Server 2012 Domain Controller & RemoteApps, No More

I recently migrated a client from Windows Server 2003 to 2012. Knowing what I know about Windows Server 2008 RDS and RemoteApps I thought I’d take the same approach. Microsoft has made many improvements to Remote Desktop Services in Windows 2012 but with that, I soon discovered, they dropped the ability to host RemoteApps in environments with single server running Active Directory Domain Services Role.

Basically, small business organizations with single server wanting to take advantage of Active Directory authentication and RemoteApps are out of luck.

Though, all is not lost. If you forgo RemoteApps you may install Remote Desktop Licensing and Remote Desktop Session Host roles on a Domain Controller, which will allow you to provide Remote Desktop Services in the environment, minus RemoteApps.

So if you find yourself in my situation check-out the following Microsoft KB article on how to deploy Windows Server 2012 RDS on servers running Active Directory Domain Services


How to Forcibly Remove DHCP Failover Partner in Windows Server 2012

Hello folks,

Ivailo here to talk about the new DHCP failover feature in Windows Server 2012. A real failover is finally possible. Split scopes are things of the past. Now it’s possible to configure DHCP partners in “Hot Standby” and “Load Balance” mode. Configuring DHCP failover is outside of the scope of this blog.

I would like to show you haw to forcibly remove a failed failover partner. I recently had to do this for a customer. The primary DHCP server was for some reason configured with invalid IP address ( as a partner. That was not my install so I don’t have an explanation as to how this happened. In order to remove a partner in the DHCP manager the two servers have to be able to talk to each other. If one of the servers is unavailable the removal will fail. The following command can be used to force the removal of the partner:

Remove-DhcpServerv4Failover -ComputerName <server name> -Name <name of the failover partnership> -force


Ivailo Mitkov

How to configure an authoritative time server in Windows Server 2012

Hello folks,

Ivailo here to talk about setting up an NTP on a PDCe. Remember this The MS tool on the page used to work like a charm. Unfortunately even though according to the “Applies to” it should work on Windows Server 2012 – it doesn’t. Of course one can follow the instructions how to configure NTP manually but I am doing this way too often for my customers so I decided to save few minutes the next time I need to configure NTP on a PDCe. This is why I created the following registry hack that can be applied simply by double clicking on it. Of course you can also apply the settings using the following command…

w32tm /config /syncfromflags:manual /manualpeerlist:”<Server1>,0x1 <Server2>,0x1 <Server3>,0x1″ /update /reliable:yes

…but it will only change the AnnounceFlags, Type, and the source and leave all intervals intact which is not a best practice.

Copy the text bellow including “Windows Registry Editor Version 5.00” and paste in your favorite text editor (notepad will work)! Change the time sources depending on the server physical location (in my case US). Append 0x1 to each server and separate multiple servers with space! Save the file (for example NTPConfiguration.reg)!

Windows Registry Editor Version 5.00






Restart the time service:

net stop w32time && net start w32time


Ivailo Mitkov