Comments on: vSphere Virtual Machine Upgrade Process http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/ The weblog of an IT pro specializing in virtualization, storage, and servers Wed, 08 Feb 2012 17:13:47 +0000 hourly 1 http://wordpress.org/?v= By: Ravi Shanghavi http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/comment-page-1/#comment-51445 Ravi Shanghavi Tue, 30 Aug 2011 20:17:28 +0000 http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/#comment-51445 A script would be very welcome for this task. Thanks! A script would be very welcome for this task. Thanks!

]]> By: JohnR http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/comment-page-1/#comment-51038 JohnR Fri, 08 Jul 2011 15:51:42 +0000 http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/#comment-51038 Craig, Any chance you still have that script handy? Craig,

Any chance you still have that script handy?

]]> By: slowe http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/comment-page-1/#comment-50293 slowe Thu, 17 Feb 2011 19:33:44 +0000 http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/#comment-50293 Osman, the drivers that you need to remove should be hidden drivers, which is why you need to show the hidden devices feature within Device Manager. It should be fairly clear which devices are active and which ones can be removed. Good luck! Osman, the drivers that you need to remove should be hidden drivers, which is why you need to show the hidden devices feature within Device Manager. It should be fairly clear which devices are active and which ones can be removed.

Good luck!

]]> By: Osman Nuri http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/comment-page-1/#comment-50287 Osman Nuri Thu, 17 Feb 2011 14:49:49 +0000 http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/#comment-50287 Hi Scott, Really great guide. Thanks for sharing this. The only thing is not clear on my mind is "Remove the drivers for the old network adapter and old SCSI adapter. " When i try to remove hidden files it says "Failed to uninstall the device. The device may be required to boot up the computer." for all old devices. How to understand which devices should be uninstalled? Hi Scott,
Really great guide. Thanks for sharing this. The only thing is not clear on my mind is “Remove the drivers for the old network adapter and old SCSI adapter. ” When i try to remove hidden files it says “Failed to uninstall the device. The device may be required to boot up the computer.” for all old devices. How to understand which devices should be uninstalled?

]]> By: Balu http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/comment-page-1/#comment-50132 Balu Thu, 27 Jan 2011 12:17:24 +0000 http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/#comment-50132 Another update: i did vm upgrade on ISA 2006 and it was tricky.The static routes configured on RRAS disappeared during upgrade.In one of the interface, i was able to give old mac but didnt work on other. But that doesn't seem to cause any issues now.Added the static routes and working fine now. Also, for configuring vmxnet3 adaptors, i need to delete 4 old from Hidden adaptor list.( 2 old+2 new created during vm hardware change). So normally, when you want to add one vmxnet3 adaptor, you need to delete 2 old adaptors. Another update: i did vm upgrade on ISA 2006 and it was tricky.The static routes configured on RRAS disappeared during upgrade.In one of the interface, i was able to give old mac but didnt work on other. But that doesn’t seem to cause any issues now.Added the static routes and working fine now. Also, for configuring vmxnet3 adaptors, i need to delete 4 old from Hidden adaptor list.( 2 old+2 new created during vm hardware change).
So normally, when you want to add one vmxnet3 adaptor, you need to delete 2 old adaptors.

]]> By: slowe http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/comment-page-1/#comment-49884 slowe Fri, 31 Dec 2010 02:13:04 +0000 http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/#comment-49884 Balu, that's great information---thank you for sharing it with everyone! Balu, that’s great information—thank you for sharing it with everyone!

]]> By: Balu http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/comment-page-1/#comment-49874 Balu Thu, 30 Dec 2010 14:37:41 +0000 http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/#comment-49874 Hi, I haven't come across this page before i started the work of upgrading the Live vm's.I've followed vsphere upgrade guide and continuing with the project now but we have met different issues.One similar issue as Austin has pointed out is with upgrading servers with SQL which has vm tools 3.5 installed. refer this kb and make sure to backup the mentioned dll file. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012259 Also snapshot should be taken prior to any change. Hi, I haven’t come across this page before i started the
work of upgrading the Live vm’s.I’ve followed vsphere upgrade guide
and continuing with the project now but we have met different
issues.One similar issue as Austin has pointed out is with
upgrading servers with SQL which has vm tools 3.5 installed. refer
this kb and make sure to backup the mentioned dll file.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012259
Also snapshot should be taken prior to any change.

]]> By: Jose http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/comment-page-1/#comment-49645 Jose Tue, 14 Dec 2010 19:37:22 +0000 http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/#comment-49645 Hi all, I couldn't get the AMD PCnet adapter (vmnet.sys) removed from our W2K3 R2 Std. Server even while I did the SET DEVMGR.... thig before on the command prompt. The device manager does not show up this adpater any more so I did a search-n-del trough the registry and removed all vmxnet.sys from all ControlSets and also the driver file intself in ...\system32\drivers\. The system seams to run ok with this and I also set a Snapshot before doing all this. I did not change the SCSI adapter type as it is only a domain controller with not much disk activity. Anyhow I wonder why we delete the AMD PCnet adapter before adding the new one. Why don't have two installed for a short while? I also found this KB article related to ESX 3.5 (I know this is out of focus): http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007195 Why does VMware change the Windows 2K3 R2 Std to Enterprise for doing this? Does VMware Tools change behave on an Enterprise OS?? If you have a comment please let me know. I'll give it a try now and see what VMwaretools does when I change the OS to W2K3 EE. BTW: The initial reason while I came along was that VMware ESX 4.1 complains while changing the host of a running VM with DRS, HA or vMotion while HW version was still 4. The vSphere event log will show "insufficient video ram" and no chance is give to set the video memory to"auto-detect" as recommended from another KB article for fixing this. Now that I have HW vers. 7 and set video ram to "auto-detect" vMotion is running fine without any complains. Hi all,

I couldn’t get the AMD PCnet adapter (vmnet.sys) removed from our W2K3 R2 Std. Server even while I did the SET DEVMGR…. thig before on the command prompt. The device manager does not show up this adpater any more so I did a search-n-del trough the registry and removed all vmxnet.sys from all ControlSets and also the driver file intself in …\system32\drivers\.

The system seams to run ok with this and I also set a Snapshot before doing all this. I did not change the SCSI adapter type as it is only a domain controller with not much disk activity.

Anyhow I wonder why we delete the AMD PCnet adapter before adding the new one. Why don’t have two installed for a short while?

I also found this KB article related to ESX 3.5 (I know this is out of focus):
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007195

Why does VMware change the Windows 2K3 R2 Std to Enterprise for doing this? Does VMware Tools change behave on an Enterprise OS??

If you have a comment please let me know. I’ll give it a try now and see what VMwaretools does when I change the OS to W2K3 EE.

BTW: The initial reason while I came along was that VMware ESX 4.1 complains while changing the host of a running VM with DRS, HA or vMotion while HW version was still 4. The vSphere event log will show “insufficient video ram” and no chance is give to set the video memory to”auto-detect” as recommended from another KB article for fixing this.

Now that I have HW vers. 7 and set video ram to “auto-detect” vMotion is running fine without any complains.

]]> By: edgar http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/comment-page-1/#comment-49510 edgar Fri, 12 Nov 2010 23:33:18 +0000 http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/#comment-49510 hi, i have a question it is normal for the upgrade hw 7, the network card is configured as a removable device like a usb, in the S.O. Windows server 2003.? tnks. hi,

i have a question

it is normal for the upgrade hw 7, the network card is configured as a removable device like a usb, in the S.O. Windows server 2003.?

tnks.

]]> By: Henk http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/comment-page-1/#comment-49075 Henk Fri, 03 Sep 2010 09:07:27 +0000 http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/#comment-49075 Did it on VMWare 4.1, works fine so far, even on boot volume of W2K3ENT Did it on VMWare 4.1, works fine so far, even on boot volume of W2K3ENT

]]>