Configuring Windows Server Mgration Tool (SMIGDeploy.exe)

Windows server Migration tool is a new offering on Microsoft servers which is further enhanced in windows Server 2012. We decided to use these for Hyper V migration from a Windows 2008 R2 server to Windows 2012 R2 server. However the migration didn’t go as Planned and we ended up doing a traditional Copy VHD migration process, But still there were quite some learning during the process on installing and configuring Windows server Migration tool, so I decided to share the same Lets start below 1) Install the Windows server migration tool on both source (win2k8R2) and destination (Win2k12R2) server This tool is not something which you need to download , rather its feature which just needs to be installed. You can either open server manager and install the same via GUI or use power shell to install it. Open Powershell with Run as admin privilege  and follow the following code Import-module Server Manager Add-WindowsFeature Migration Install this role on both Source and Destination servers,Reboot the server if needed 2) Now once the Migration Tools are installed, as we are migrating from an older OS i.e. Win 2k8R2 to WIndows 2012 R2, so we need to do couple of more steps to get Migration tools works a) Create Deployment folder for source servers on destination server Open Cmd  on destination server with Admin Rights (Run as Admin) Browse to directory where server tools are installed, default cd %Windir%\System32\ServerMigrationTools\ As my source server is WIn2k8R2 X64 bit, so the command which I am going to execute is SmigDeploy.exe /package /architecture amd64 /os WS08R2 /path <deployment folder path> (c:\ServerMigTool) PS: You can also...

HyperV Virtual Machine not able to access any network

Issue: HyperV Virtual Machine not able to access any network. Summary: Transferring HyperV Virtual Machines from old Host Server (Windows Server 2008 R2) to new Host Server (Windows Server 2012 R2) via manual process. Copied VHD to the new server, configured Virtual Machine on the new HyperV 2012 R2 Server. The VHDs were not converted to VHDx format. When all was then and we started the machine and gave it the same static IP, it failed to connect to any network. This Hyper V VM is not able to access the HOST Network, the Gateway,  and had an exclamation sign on the Network Icon in system tray. Solution: This is usually caused because of the hidden network adaptor present in the virtual machine, with the same static IP. You’ll have to remove these hidden adaptors to ensure all goes well. Here are the steps to do so: Shutdown the Virtual Machine, which has problem accessing the network Remove all Network Adaptor from the Settings of the Virtual Machine Save the configuration of the Virtual Machine and Start it Login to Windows and open command prompt At the command prompt, type the following command and hit return: (If you do not run this command, you’ll not see the required adaptor in Step 8) set devmgr_show_nonpresent_devices=1 Again within the command prompt, type the following and hit return: start devmgmt.msc Under View menu of Device Manager, click on Show hidden devices. Expand the Network Adaptors and you’ll notice some Virtual Adaptors listed and are little dimmed (Like they are inactive) as compared to others. Usually named as “Microsoft Virtual Machine Bus Network Adapter #“...

Import Hyper V Virtual Machine from 2008R2 to 2012R2

Objective: Import Hyper V Virtual Machine from windows 2008R2 to Windows 2012R2. We were trying to Export the VM’s from windows 2008R2 hyper server by following the standard procedure. Export Procedure Open Hyper V manager Shutdown the VM to be exported (Saving or Pausing the Virtual Machine will not work) Select the VM and do export and it created the exported folder for us Copy the Exported folder to the destination server   Import Procedure  Now we went to our new, shiny Windows 2012 R2 server, already configured with Hyper V Role, in-fact I have a couple of VM’s running on it. Went ahead and selected to import the Virtual Machine on Server 2012R2, browsed to the folder which I copied from Source Windows 2008R2 server   Tried a few thing, but no success, it is not willing to see my VM. Finally found out that  Windows Server 2012 R2 can only import from Windows Server 2012 and Windows Server 2012 R2. To import those VMs exported using Windows Server 2008 R2, you first need to import to a Windows Server 2012 machine, then import those files into Windows Server 2012R2 (either by exporting from Server 2012 or just directly importing the files from Server 2012). Export isn’t actually required to import with Server 2012 and later. Hope this one saves some time 🙂 Conclusion: Since, it was for only about 20 Virtual Machines, we decided to first configure the VM in the HyperV Manager without the VHD attached to it. Once the VM config is ready, we simply shutdown the server. Than, transferred the VHD to the new Server. Added the Virtual machine to...