Archive for 2012 R2 Essentials

Connector for Windows 10 to 2012 R2 Essentials Now Available

This information just came in today:

Windows 10 Client Connector for connecting to Windows Server 2012 R2 is now Released via Download Center

We have now officially released the Windows 10 connector for connecting to Windows Server 2012 R2 via Download Center. It is available from the following URL:

Please note: we do not have the fix for the auto-download and installation released yet. So you have to manually download and install this client connector on the Windows 10 client machine. Then you can run the client deploy to start the connecting.

For the servers in-place upgraded from Windows 7, 8.1 to 10,  you will need to manually download and install this client connector and do the connecting again.

If the machine ID is the same after the upgrade, then everything will be working automatically. However if the machine ID is somehow changed during the upgrade, then it will be treated as a new client, so you have to leave the domain and connect to the Essentials server again. The old client back up data will be in the archive folder on the Essentials server, and you can still use that to do the restore back to the upgraded Windows 10 client.

New 2012 Windows Server 2012 R2 VM Couldn’t Complete the Updates Undoing Changes

Aarrgghh – why don’t I remember these things anymore????

I was in the process of firing up a new 2012 R2 VM,  and in my rush, I  clicked to download and install all updates before heading out to do some errands. When I got back home, I was greeted with the following error message:

We couldn’t complete the updates. Undoing changes. Don’t turn off the computer.


The thing is — this was a known issue over a year ago! One that my good MVP friend Boon Tee encountered it, and wrote up a blog post at that time for the workaround.

The problem occurs if you are creating a Gen 2 virtual machine (.vhdx) and KB 2920189 is included in the list of updates you are trying to install.

The solution?

Shutdown VM –> disable Secure Boot from the VM –> Start VM  and install updates –> Shutdown VM –> re-enable Secure Boot –> Start VM

You can find the option to enable/disable Secure Boot under the Firmware section of the VM settings.


Warning — the “Undoing changes” can take quite a long time to complete. I decided to delete the VM, and start over from scratch!