---
title: "VMware Tools and Hardware Version upgrade on Windows Server Core Domain Controller"
date: "2013-03-26T22:29:36Z"
tags: ["Active Directory", "Upgrade", "VMware Tools", "Virtual Hardware", "Windows Server", "Windows Server 2008 R2 Core"]
categories: ["Microsoft", "VMware"]
---

![Apple Core][1]

Recently I was "playing" a bit with Windows Server 2008 R2 Core VMware Tools and Virtual Hardware upgrade from version 3.5 to 4.1. Migration went fine from one environment to another, but the rest went totally wrong. I got immediately **BSOD - Blue Screen Of Death**.

My patient was Windows Server 2008 R2 Core Active Directory domain controller with database on separate disk.
<!--more-->
<!--adsense-->
I was following solution described here <a title="Windows 2008 Server Core ESX Guest Virtual Hardware Upgrade ? BSOD on boot" href="http://www.totalnetsolutions.net/2010/09/19/windows-2008-server-core-esx-guest-virtual-hardware-upgrade-%E2%80%93-bsod-on-boot/" target="_blank">http://www.totalnetsolutions.net/</a>, but there is other way to do this.

The main problem is that, after virtual hardware upgrade from version 4 to 7 Windows doesn't recognize disks where Active Directory database is located. In order to fix this issue you need to change SAN policy in diskpart.

Here are steps how you can do it:

* Login to your server
* Start diskpart
* Type **SAN **to check what policy is set
* If your policy is **OfflineAll** or **OfflineShared**- change it to **OnlineAll** by typing **SAN POLICY=OnlineAll**

Also to summarize I would like to guide you how you should perform VMware Tools and Virtual Hardware upgrade.

1. Perform backup of server
2. Migrate Virtual Machine to "new" environment
3. Perform upgrade of VMware Tools
4. Take a snapshot of VM
5. Check current VMware tools version - go to VMware Tools directory and execute command **vmware-toolbox-cmd -v**. Then compare version to other VM's in your new environment to check if upgrade was really done.
6. Change SAN policy
7. Power off Virtual Machine
8. Upgrade Virtual Hardware
9. Start Virtual Machine
10. Reconfigure IP setting if they are missing
11. **SUCCESS!**
12. Change policy to original one + reboot

[1]: /images/uploads/2013/03/Apple-Core.webp