[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 301
  • Last Modified:

Force remove MS Virtual Machine Addittions after moved to hardware

Hi I have a 2003 server which started its life in a ms virtual server environment, it was migrated out to hardware and now cannot remove the MS virtual server addittions, this means it wont reboot completely without a hard reset. I know that I need to edit the virtual server addittions MSI to disable the 'Inside a MS Virtual Machine Check' I have seen discussion on someone who has solved this and I think I am close. any chance someone can give a little more detail on how to disable the VM check. I have tried editing the msi file with orca and set sequence to 0 and 9999 and completely removed the lines referring to CheckForRunningInsideAVirtualMachine
but still no luck, anyone had success removing this outside of ms virtual server?
Appreciate any help... i know that I can remove it my migrating back to virtual server and removing it that way, but the image is huuge and this will take an eternity.
0
slicktech007
Asked:
slicktech007
1 Solution
 
oBdACommented:
Just had look at it (it's been two years since I did this myself).
If I remember correctly, it was sufficient to drop two rows in the table "InstallExecuteSequence":
* CA_CheckForRunningInsideAVirtualMachine
* Error_CheckForRunningInsideAVirtualMachine
Save it as VMUninstall, start it by running
msiexec /x "VMUninstall.msi"

If this doesn't work, I think (it's slowly coming back) there was another catch. Look into %Systemroot%\Installer, and check the properties (not the names) of the msi files there. One is probably for the VMAdditions. Add a "-backup" to the name, copy your changed msi file in this folder, and rename it to the name the VM msi file in this folder had. Then try again.
0
 
slicktech007Author Commented:
Bingo! Thanks oBdA. I found after testing this on a coule of machines that the second part (replacing and renaming the appropriate .msi in c:\windows\installer) is only needed if you have tried to uninstall this before from the standard .msi. must get cached in that installer folder. anyway after removing those 2 lines in the .msi and replacing the file as described, the uninstaller went through without a hitch!  Thanks very much ;-)
0

Featured Post

Microsoft Certification Exam 74-409

VeeamĀ® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now