The Problem Update: This problem is a very long running issue that I’m surprised hasn’t been resolved by Microsoft yet. The fix below does work for some people, but based on the comments on this post and those on the Microsoft Forums this solution doesn’t always work and many other fixes have been suggested (see the forum for a large number of other suggested solutions). Some folk have reported that the fix below can prevent the Mail and Calendar apps from working at all, so I’d recommend that you use this process with care and recommend strongly that you back up the comms folder before deleting the content.
After a couple of bumps upgrading my development laptop to Windows 10, I finally got to update all my Hyper-V lab VMs to the new version of Hyper-V. This included updating the Virtual Machine Configuration version and enabling virtual network adapter Device Naming - see What’s new in Hyper-V in Technical Preview for more information.
But having a number of VM’s running on this Hyper-V host I couldn’t be bothered updating them all by hand.
I have been spending a bit of time experimenting with loading Nano Server into WDS (using capture images, VHDX files and the like) and while doing this I decided to dig around inside Server Nano to see what is missing. The thing that is missing that makes me grumble the most is that lots of PowerShell modules are missing. This of course is because Server Nano doesn’t have the full .
After passing my MS 70.410 exam I had a little bit of free time on my hands, so I thought I’d clean up my WSUS servers and prepare them for Windows 10 and VS 2015. So I thought I’d force myself to do the whole thing via PowerShell. The problem is that the UpdateServices PowerShell module doesn’t have cmdlets for some things I wanted to do -force a synchronization was among them.
As part of my recent studies (and because I’m a bit OCD) I’ve been writing some notes on what how to perform various DISKPART commands in PowerShell. You might also need to do this if you’re converting old DISKPART scripts into PowerShell (for whatever reason).
In most cases it is straight forward to map DISKPART commands over to PowerShell. For example, to use DISKPART to initialize and set the partition format to GPT on disk 6 in a machine:
