Cannot install VMtools in XP in safe mode under fusion 3.1

[vernonspencer]

Going around in circles:

I have recently converted an existing XP Pro service pack 3, transferred across to a MAC with Fusion 3.1. So far so good.

The XP version boots to a black screen! I assume some sort of video controller issue.

I then boot XP in Fusion in Safe mode, OK. I see that Other devices has Base System Device and Video Controller (VGA Compatible) issues.

I try to install VMtools and the message  "The system administrator has set policies to prevent this installation"

So I seem to go around in a loop, cannot install VMtools to correct problem in safe mode, cannot boot to full windows to install VMtools?

I have followed all threads regards the "The system administrator has set policies to prevent this installation" message, but still cannot fix.

I also try the orginal dell drivers, however the CD does not want to auto load and also cannot see the contents in safe mode.

So stuck in "safe mode" with no network support.

Any help appreciated :smileyconfused:

[continuum]

you tried to install Dell drivers in the VM ?
the VM has no Dell-devices so that makes no sense at all

if your XP has no network drivers there seems to be something wrong with your vmx-file - usually a XP VM has network drivers for the AMD PCnet32 device.

in safe mode try to find out which driver is configured for the video card and disable them
the standard VGA-driver should work fine

in other words: you have no problem with the vmware-tools - the problem are old drivers that are still enabled in registry

[WoodyZ]

vernonspencer wrote: I also try the orginal dell drivers, however the CD does not want to auto load and also cannot see the contents in safe mode.

VMware does not support the migration of OEM versions of Windows since it violates the EULA and you cannot legally transfer it to another system physical or virtual as it lives and dies on the original system it's installed!  Additionally if you are using an OEM version that was originally install on a Dell and have violated the EULA by transferring it then that probably also violates the Community Terms of Use by seeking help with and OEM migration.

Message was edited by: WoodyZ - Reworded statement to make it informative vs accusatory as that was not my original intent, sorry.

[patrickds]

P2V of a machine with an OEM license is not necessarily a violation of the EULA.

If you have the proper license for the target hardware (OEM or not), it doesn't really matter that the machine was originally installed using a different license, on different hardware.

You're only transferring the Windows installation, not the license.

But that doesn't really help to answer the original question.

Try uninstalling graphics drivers in safe mode, that should make it start with legacy VGA driver.

[WoodyZ]

patrickds wrote:  P2V of a machine with an OEM license is not necessarily a violation of the EULA.

If you have the proper license for the target hardware (OEM or not), it doesn't really matter that the machine was originally installed using a different license, on different hardware.

You're only transferring the Windows installation, not the license.

The install of the OEM Windows Software and the accompanying OEM License are not separable and they are bound to the original system to which installed!  VMware does not support the migration of OEM version of Windows!

End of discussion on this subject!

[continuum]

We do not even know which type of license is used here ...

[WoodyZ]

Yes we do not know absolutely however the OP did state "I also try the orginal dell drivers, however the CD does not want to auto load and also cannot see the contents in safe mode." so it is a very normal and logical assumption that the source is a Dell OEM version of Windows XP however regardless it does not change the facts surrounding OEM.

[continuum]

He may also talk about a simple CD with drivers only

I'd rather go with in dubio pro res then accusing folks of foul play without proof.

This was a very normal discussion about driver issues after P2V - absolutely normal in the Converter section.
No need to turn  this into another OEM-debate without need

[WoodyZ]

I agree with what you said and note I reworded my original statement as I did not mean to be accusatory and am normally more careful of my wording until l know for sure however having spent the time I have in these forums and specifically VMware Fusion with the exception of a few where the OP stated outright it was a Retail or VLK the remaining overwhelming majority of migrations from a Dell to a Mac the OP usually when asked admitted it being OEM and this is probably why I stated it the way I did at first.  I'll have to be more careful in the future.

[continuum]

[vernonspencer]

Thanks all for your various comments.

This is not a licence issue, I have multiple licenses all fully audited and controlled for OS and Applications etc...

This is one off machine that has many applications installed, it was just a question of moving it so we have a reference machine and prevent the need to go through the laborious process of re-installing the OS and loading all the Apps back on a MAC with fusion 3.1.

So all wanted to do is try and overcome the display driver issue.

Thanks all.

[ColoradoMarmot]

In safe mode, switch to the base SVGA driver.  Then reboot, and install tools in regular mode.  Do not install hardware specific device drivers.

Migrating physical machines often results in unstable/unusable/bloated VM's.