The Cloud is a neighborhood

My 3 session from Microsoft Partner Boot Camp 2013 are now finished. Lots of great questions and had a great time. Unified Client Management http://www.slideshare.net/TVEDTnet/unified-client-management-session-from-microsoft-partner-boot-camp Win 8.1 Os Deployment http://www.slideshare.net/TVEDTnet/os-deployment-session-from-microsoft-partner-boot-camp-win-81 Mdop intro http://www.slideshare.net/TVEDTnet/mdop

One of the most annoying thing is sitting with a problem you know that you have solved before but you do not remember the solution too anymore. That is just what I now have spent the last 2 hours doing. I am sitting and testing out Windows Server 2012 R2 and DirectAccess feature, and suddenly my domain controller are not reachable from any other computers on the network. I only have one domain controller since I am using Microsoft Lab guide setup, so this means nothing works. All other server and computer can communicate. Some testing shows me that I can ping the server name but with IPv6 address only, no response on IPv4. Checking out the network settings shows that the «Network Location Awareness» service reports the network on the domain controller as an «unidentified network» and automatically sets it up with a «Public network» profile.  

If you are using KMS server or stuff like creating templates without using you licens key you can use KMS setup keys. This keys cannot be activated but works for deployment scenarios where you have to type in a key under installation. For instance Windows Server 2012 and 2012 R2 ask for a key if deploy With MDT, then you can use the keys.