The Cloud is a neighborhood

Then the slide deck from my second session from NIC 2014 are ready for download You find it here http://www.slideshare.net/TVEDTnet/nic-going-totally-cloud

Now you can download my slides from the InTune InAction session her at NIC 2014 http://www.slideshare.net/TVEDTnet/in-tune-inaction

Every now and then, you have to run older software that do not comply to newer ways of doing stuff. One of the problem you might run into is the “Data Execution Prevention” feature in short just called DEP. To learn more about the DEP feature you can go here: http://support.microsoft.com/kb/875352 it is an old article for Windows XP and Server 2003, but still explains it right. The way that the software behaves are often that it does not start and gives you a “Software” has stopped working error message. However, in some cases the software works until you call up features that crashes with DEP. This is what happened to me to day.

Upgrading to Windows 8.1 for Enterprise version users are not as simple as other versions. You cannot upgrade from the Windows Store and it will not be available as a old time "Windows Update" option. It is intendent that this is a task for the IT Department, that will do this using tools like "System Center Configuration Manager" or "MDT". If you have access to the Windows 8.1 Enterprise ISO file you can do this directly from the CD of course. But beware that you need an Windows 8.1 Enterprise key or update on your KMS

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.