In Part 1 we ran through some of prerequisites and readiness for this lab and migration

In Part 2 I’ll run through the system readiness to migrate the existing deployment shares from MDT01.

Build Virtual machines

In Hyper V complete the following generation 2 virtual machines

  • Install Windows Server 2019 and join to the Domain
  • Install Windows 10 and join to the Domain
  • Install Windows Admin Center on Windows 10.
  • Ensure Windows 10 has an internet connection so it can update any extensions required. There may be newer extensions for the Storage Migration Service (SMS)
  • Ensure all virtual machines are connected to the same internal switch on Hyper V

Firewall Ports

As mentioned in Part 1 you will need to open particular Firewall Ports so the WAC can manage them

I’d advise creating a Domain Group Policy and targeting them to the servers or for a lab scenario just add the incoming rules below

  • File and Printer Sharing (SMB-In)
  • Netlogon Service (NP-In)
  • Windows Management Instrumentation (DCOM-In)
  • Windows Management Instrumentation (WMI-In)

PS Remoting

Enable PSRemoting on the source and destination servers to allow connections for the migration process

  • Open PowerShell as an Admin
  • Run Enable-PSRemoting -Force

Windows Admin Center (WAC)

The windows Admin Center runs on a common URL and port once installed:


I also found initially the page would not load from MS Edge browser

  • Open the following location

C:\Program Files\Windows Admin Center\SmeDesktop

  • Run SmeDesktop as Admin. This will appear in the taskbar and will now load in the browser

Add Servers

  • Add a connection and use the server option
  • Add in both MDT Servers (MDT01 and DF7-MDT01)

NOTE: When you are prompted for Credentials use the Domain credentials in this format Domain\Username. If this format is not used you will receive CIM errors when trying to connect to the servers during the migration process

Server Roles

On the Windows Server 2019 Install the following Roles using either Server Manager, PowerShell or WAC from Windows 10

Storage Migration Service
Storage Migration Service Proxy

This completes Part 2 and we’ll move on to setting up the Migration Tasks in Part 3