Skip to main content

End of support announcement of DirSync and Azure AD Sync


Microsoft announced the deprecation schedule of Windows Azure Active Directory Sync (“DirSync”) and Microsoft Azure Active Directory Sync (“Azure AD Sync”) on April 13. 

This means that all support will end on April 13 2017 for DirSync and Azure AD Sync.
The tools will of course continue to work after this date, but you will not get any updates or support from Microsoft after April 13, 2017.


The Azure AD Connector for FIM/MIM has not yet been announced as deprecated. It is at feature freeze; no new functionality is added and it receives no bug fixes. But it’s end of support will be announced at some time so it might be smart to start to plan for it.

Microsoft has provided great guides to help getting up and running on Azure AD Connect:
Upgrade Windows Azure Active Directory sync (DirSync): 

Upgrade from a previous version to the latest:

There is also a quick video on Channel 9:

Azure Active Directory Connect: in-place upgrade from legacy tools:


And if you want to stay in sync with development you can follow the Active Directory team’s blog here: 

Popular posts from this blog

Changing Windows product key (license) for a MDT OS deployment task

Creating a new OS deployment task in MDT you will be asked to specify product key


That’s easy enough, but what if you type in the wrong key or just want to change it (add it) later? You might even have gotten a new MAK.

That is not as easy, you cannot do it from the graphical interface, you have to do it from one of the configuration files. Well you might to it from graphical interface by typing it in every time deploying a computer gets deployed but that is not a great solution.

MDT - The task sequence has been suspended. LiteTouch is trying to install applications

Every now and then I get this error message when fuelling a computer with MDT:
"The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."

How to get and use the Windows key from UEFI/BIOS

I found myself in the situation that I needed to get the Windows key out from the ACPI in the UEFI bios and preferable get to use it in a task sequence in MDT.

There are different ways of doing this, but I wanted to do this with little code and easy to understand.
There is a nice tool created to get the key on github, created by Christian Korneck, called get_win81key. This tool gives you the key in plane text. You can get it
HERE: https://github.com/christian-korneck/get_win8key


If I were supposed to do this manually, I now would just take that key and type it in with slmgr command or in the GUI. But I want to do this within a task in MDT.
Testing a couple of solutions without using the get_win8key with my great scripting guru colleague HÃ¥vard ( www.grondal.me) and figuring out that it cannot be done with default powershell stuff, it needs more code. Therefore, we quickly figured out that some use of the “get_win8key” files is the easiest way, but we need a way of setting the output fro…