Virtual installation?

[cicero]

Hi there,

a simple question, but i hardly found anything about:

- is it possible to install Veeam Backup in a virtual W2k3 machine
on a ESX and then do the backup, even the Veeam Guest itself
where vbk-files are stored of course on a remote share...

- an will it be possible, in a desaster recovery,
to restore simply from an .vbk-File.
(of course i've found the import-function, but
have ever been littly bit skeptical

Want to avoid another physical Windowsserver in
a fully virtualized environment.

Thank in advance,
David

[Gostev]

David,

Yes, we have some customers who are running Veeam Backup inside VM.

You need Veeam Backup to restore anything from VBK (yes, you do "Import Backup" first, and then you restore). Veeam Backup takes minutes to install, and license is not checked during restore operations, so you can restore your VBK at any time.

Thanks!

[cicero]

Gostev, thanks a lot!
Your support is outstanding ... !

David

[cicero]

HI,

having troubels with file level restore of a linux guest ,
since it is not possible to install the necessary vmware player
inside a vm.

How do you handle is scenario?

David

[Gostev]

Hello David,

To be able to install and run VMware Player inside VM, you need to do the following. Please note that this workaround requires that VMware Tools are disabled, meaning that some VMware management tools will not be able to work with such VM correctly. So, this workaround is only good for actual restores – as soon as you are done with restore, you should roll it back. You can have 2 VMX files, and register one or another as necessary.

Add these lines to the .VMX file of your Veeam Backup VM:

Code: Select all

isolation.tools.getPtrLocation.disable = "TRUE"
isolation.tools.setPtrLocation.disable = "TRUE"
isolation.tools.setVersion.disable = "TRUE"
isolation.tools.getVersion.disable = "TRUE"
monitor_control.disable_directexec = "TRUE"
monitor_control.disable_chksimd = "TRUE"
monitor_control.disable_ntreloc = "TRUE"
monitor_control.disable_selfmod = "TRUE"
monitor_control.disable_reloc = "TRUE"
monitor_control.disable_btinout = "TRUE"
monitor_control.disable_btmemspace = "TRUE"
monitor_control.disable_btpriv = "TRUE"
monitor_control.disable_btseg = "TRUE"

Also, change tools.upgrade.policy = "useGlobal" to

Code: Select all

tools.upgrade.policy = "manual"

That should do the trick. Please note that this workaround is not officially supported though.

[cicero]

took me 30 Minutes installing the player without the tools *g*
so there are reasons why veeam is recommended outside a vm

Thanks for the workaround!

David

[stevenfoo]

Do you have the full steps on how to installed VMWare player in a VM ?

Appreciate if someone could share it.

[Gostev]

Steven, sorry but I don't understand your question?

[stevenfoo]

Steven, sorry but I don't understand your question?

Do you have the steps in full to installed the VMplayer in a VM ?

Our Veeam is running on a VM.

We need to VMplayer so that it could restore File level for our linux system.

[Gostev]

Steven, no other steps are needed besides editing VMX file as outlined above.

[stevenfoo]

Gostev,

This VMX file is the VM vmx file where the VM is installed ? I am a little confuse.

When I installed VMplayer in the VM where Veeam 3.1 reside it gives me the error saying

"Sorry this product cannot be installed inside a virtual machine"

[stevenfoo]

I have stop all the VMtools, add the parameter and start the installation.

The message is the same:

"Sorry this product cannot be installed inside a virtual machine"

[Gostev]

Have you restarted the Veeam Backup VM so it can boot with changed VMX file configuration parameters?

[stevenfoo]

Gostev, I have restarted the Veeam Backup VM. The installation still does not work.

Pls help.

[stevenfoo]

Gostev,

I already get the VMplayer installed by using the following link http://communities.vmware.com/thread/61041

However I get the message now "You may not power on a Virtual Machine in a virtual machine"

Any further help to get us up and enable us to restore our Linux VM files.

Regards
Steven

[Vitaliy S.]

Hello Steven,

Could you specify whether you have tried to edit VMX file as it is described above or not?

[stevenfoo]

I have already edit the VMX file with the above parameter. Then I restarted the Veeam Backuup VM.

It still does not work until I did http://communities.vmware.com/thread/61041

The I started the File Level Restore Wizard. It can startup, however when I choose the Linux VM backup to restore
error message "You may not power on a Virtual Machine in a virtual machine"

Thanks
Steven

[Gostev]

Steven, please verify carefully that you did not miss any settings, this workaround is reported to work for 100% of customers who were requesting it - without requiring to perform actions from the above-mentioned VMware Communities thread. If you apply modifications correctly, you will be able to install VMware Player without having to modify its MSI package. If you are unable to install without MSI mod, it means you likely did not apply the VMX file mod correctly. What the mod does is it makes it impossible for any application (including setup and VMware PLayer itself) to detect that they are running inside VM.

Unfortunately, we are unable to provide official technical support for this workaround, because it involves modifying behavior of 3rd party products (VMware), which we do not have source code code and so unable to debug.

If you cannot make this working, I suggest re-installing Veeam Backup on physical computer instead. Please note that we do not officially support using Linux FLR module in a VM, so even with this workaround working, you will be using it at your own risk.

[stevenfoo]

Gostev,

I have verify all the steps. In fact I am able to installed the VMplayer now.

The method you mention is for installing the VMplayer with the parameter.

I mention for the 4th time here again is that, when I started the File Level Restore Wizard, it can startup. Previously it can startup.
However when I choose the Linux VM backup to restore error message "You may not power on a Virtual Machine in a virtual machine"

You don't tell your customer to purchase another hardware plus windows license just for this dummy backup purpose only.
This is not acceptable solution and answer to your customer.

What Veeam required is to assist customer to resolve it. Would appreciate you could escalate this issue further.

[Gostev]

Steven, we do plan to change Linux FLR implementation in the way so it will not require using VMware Player in future versions, but unfortunately right now it does require VMware Player and this is stated in the System Requirements for the product. And VMware Player cannot run in VM (not our restriction). So, we provide this workaround for the testing/evaluation purposes only, and as explained on the previous page, it is NOT officially supported.

Most likely the workaround does not work for you because your VMware ESX or VMware Player version does not support this "hack". Again, unfortunately we are not in position to troubelshoot or support this modification, because we do not own the VMware ESX / Player source code and are unable to troubleshoot their behavior with these VMX file modifications in place.

As a workaround, I suggest that you install Veeam Backup on your physical desktop/laptop, perform "Import Backup" operation to connect to the existing backup file (it will NOT be "pulled down" during this operation, it stays remote - but will appear in the Veeam Backup user interface), and perform the Linux file level recoveries this way. This workaround will not require neither extra physical server, nor extra Windows license.

[stevenfoo]

Gostev,

Thanks very much for explaination. This is a better clearer picture. My management will greatly appreciate such answers.

When do you see that we could get the Linux FLR without VMware Player? Q3 or Q4 2009 ?

Thanks
Steven

[stevenfoo]

Gostev,

This is not working for us for far.

If we installed the Veeam Backup on our laptop or PC, when the installation ask to where to installed the Veeam Database, could we choose the existing one ? Will it overwrite the existing database already available ?

Thanks
Steven

[Gostev]

Steven,

Re: no VMware Player requirement. VMware has just released the API/capabilities that would allow us to drop VMware Player requirements, and we are looking at this. Depending on the results of our research, we will be able to estimate some timelines and then we will decide which version we will add this capability to.

Re: installing Veeam Backup on laptop. No, please do not select the existing database, as only one Veeam Backup installation can work with the same database at one time. I would suggest to simply setup the Veeam Backup with local SQL Express (default option).

Thanks!

[Gostev]

Steven, I have also discussed this with support - if you'd like, please contact our support to setup webex with our support specialist who have tested this workaround initially. Just to double check that you've done everything right, and that the VMX modification is applied correctly. Unfortunately there is little we could do beyond that - but at least we will know for sure that the reason is specific ESX version and not some mistake.

I just re-read all your messages and there is one comment I am specifically worried about, where you said "I have stop all the VMtools". May be it worth re-enabling the tools, and applying the workaround without touching VMware Tools. Despite VMware Tools get disabled by this modification, may be they still play some role. This is the only thing that catched my eye.

[stevenfoo]

Actually I have enabled backup the VMtools after I installed the VMplayer. What I did was restart the whole VM.

Regards

[Gostev]

Actually I have enabled backup the VMtools after I installed the VMplayer.

Then may be this is what prevents virtual appliance from running? You were able to install VMware Player when Tools where disabled. Now, with Tools enabled, VMware Player probably detects the presence of running Tools and realizes it is installed on VM (just guessing)? Could you try to roll back all changes you made, and then perform the modification procedure from scratch, without touching VMware Tools at any point (either before or after applying modification).

[stevenfoo]

Do you mean NOT to disabled the VMTools ? As you mention in your parameter to stop all vmware stuff before installing the VMplayer, does this apply?

Thanks
steven

[Gostev]

Steven, no - you only need to apply VMX file modifications, without touching VMware Tools at any point. The VMX mod itself WILL affect VMware Tools and render them not working "correctly", but you should not touch them during this process.

I've re-read my instructions above, and I do see my remark about VMware Tools that got you confused.
What I really tried to say, is that this workaround is dangerous because it will "brake" VMware Tools, which in turn may affect many other VM management tools when dealing with the Veeam Backup VM. I did not mean VMware Tools must be disabled manually.

[stevenfoo]

Ok I will tried to revert everything into original and try for the last time.

[stevenfoo]

Gostev,

1) I have uninstalled the VMplayer

2) Add the parameter into the VMX of the Veeam Backup VM

config.version = "8"
virtualHW.version = "4"
floppy0.present = "true"
nvram = "XXX.nvram"
deploymentPlatform = "windows"
virtualHW.productCompatibility = "hosted"
#tools.upgrade.policy = "useGlobal"
tools.upgrade.policy = "manual"
powerType.powerOff = "default"
powerType.powerOn = "default"
powerType.suspend = "default"
powerType.reset = "default"

displayName = "XXX"
extendedConfigFile = "XXX.vmxf"

scsi0.present = "true"
scsi0.sharedBus = "none"
scsi0.virtualDev = "lsilogic"
memsize = "1024"
scsi0:0.present = "true"
scsi0:0.fileName = "XXX.vmdk"
scsi0:0.deviceType = "scsi-hardDisk"
ide0:0.present = "true"
ide0:0.clientDevice = "TRUE"
ide0:0.deviceType = "cdrom-raw"
ide0:0.startConnected = "FALSE"
floppy0.startConnected = "false"
floppy0.clientDevice = "true"
ethernet0.present = "true"
ethernet0.networkName = "VM Network"
ethernet0.addressType = "generated"
guestOSAltName = "Microsoft Windows Server 2003, Standard Edition (32-bit)"
guestOS = "winnetstandard"
uuid.location = "56 4d 65 59 18 ef 6a 8b-3f f9 77 3e fd dd ff d3"
uuid.bios = "56 4d 65 59 18 ef 6a 8b-3f f9 77 3e fd dd ff d3"
toolScripts.afterPowerOn = "true"
toolScripts.afterResume = "true"
toolScripts.beforeSuspend = "true"
toolScripts.beforePowerOff = "true"

scsi0:1.present = "true"
scsi0:1.fileName = "/vmfs/volumes/48b64b06-c7c4c8b2-8ce3-0015177d3078/PENTACLE/P
scsi0:1.deviceType = "scsi-hardDisk"
floppy0.fileName = "/dev/fd0"
scsi0:0.redo = ""
scsi0:1.redo = ""
ethernet0.generatedAddress = "00:0c:29:dd:ff:d3"
tools.syncTime = "FALSE"
sched.swap.derivedName = "/vmfs/volumes/48b2dcbb-d5e0932e-e706-001ec9e565f3/PENT
ethernet0.generatedAddressOffset = "0"
hostCPUID.0 = "0000000a756e65476c65746e49656e69"
guestCPUID.0 = "0000000a756e65476c65746e49656e69"
userCPUID.0 = "0000000a756e65476c65746e49656e69"
hostCPUID.1 = "0001067600040800000ce33dbfebfbff"
guestCPUID.1 = "0001067800010800000822010febbbff"
userCPUID.1 = "0001067600040800000822010febbbff"
hostCPUID.80000001 = "00000000000000000000000120100000"
guestCPUID.80000001 = "00000000000000000000000120100000"
userCPUID.80000001 = "00000000000000000000000120100000"
evcCompatibilityMode = "FALSE"

ethernet0.startConnected = "TRUE"
ide0:0.fileName = "/usr/lib/vmware/isoimages/windows.iso"

solation.tools.getPtrLocation.disable = "TRUE"
isolation.tools.setPtrLocation.disable = "TRUE"
isolation.tools.setVersion.disable = "TRUE"
isolation.tools.getVersion.disable = "TRUE"
monitor_control.disable_directexec = "TRUE"
monitor_control.disable_chksimd = "TRUE"
monitor_control.disable_ntreloc = "TRUE"
monitor_control.disable_selfmod = "TRUE"
monitor_control.disable_reloc = "TRUE"
monitor_control.disable_btinout = "TRUE"
monitor_control.disable_btmemspace = "TRUE"
monitor_control.disable_btpriv = "TRUE"
monitor_control.disable_btseg = "TRUE"

3) Restarted the Veeam Backup VM

4) Installed the VMplayer 2.5.2.

I still get the error message Sorry, this product cannot be installed inside a virtual machine.

Below is the log:
BootStrapper-build-156735: 07/28/09 22:36:29 Begin Logging
BootStrapper-build-156735: 07/28/09 22:36:29 [Info] Command Line =
BootStrapper-build-156735: 07/28/09 22:36:29 [Info] Admin = TRUE
BootStrapper-build-156735: 07/28/09 22:36:29 [Info] OS Major Version = 5
BootStrapper-build-156735: 07/28/09 22:36:29 [Info] OS Minor Version = 2
BootStrapper-build-156735: 07/28/09 22:36:29 [Info] OS Build Number = 3790
BootStrapper-build-156735: 07/28/09 22:36:29 [Info] OS Bitness = 32-bit
BootStrapper-build-156735: 07/28/09 22:36:29 [Info] OS Platform = NT
BootStrapper-build-156735: 07/28/09 22:36:29 [Info] OS Service Pack = 2
BootStrapper-build-156735: 07/28/09 22:36:29 [Info] running from --> C:\VMware-player-2.5.2-156735.exe
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = BLOCK_HYPERV, lpBuf = one
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = SKIPADMINCHECK NOT FOUND
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = MINORUPGRADE NOT FOUND
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = OPERATION, lpBuf = INSTALLUPD
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = PRODUCTNAME, lpBuf = VMware Player
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = PRODUCTCODE, lpBuf = {A53A11EA-0095-493F-86FA-A15E8A86A405}
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = LANGUAGES, lpBuf = 1033 1041
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = VM_DATABASE, lpBuf = VMware Player.msi
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = SFXINSERT, lpBuf = 1093632
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = VMIOPTION, lpBuf =
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = MINIMUM_9X_MSI, lpBuf = 200
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = MINIMUM_NT_MSI, lpBuf = 300
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = INSTMSIW, lpBuf = instmsiw.exe
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = PROPERTIES NOT FOUND
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = OLDCODES, lpBuf = {31799B14-B3E7-4522-B393-6206C03EC5D3};{A53A11EA-0095-493F-86FA-A15E8A86A405}
BootStrapper-build-156735: 07/28/09 22:36:29 [Resource] lpName = HELPER_UI NOT FOUND
BootStrapper-build-156735: 07/28/09 22:36:29 Not running under Microsoft's Hyper-V.
BootStrapper-build-156735: 07/28/09 22:36:29 [Info] Microsoft Hypervisor = NO
BootStrapper-build-156735: 07/28/09 22:36:29 [Info] UI thread started successfully
BootStrapper-build-156735: 07/28/09 22:36:29 [Info] Total unpacked size will be 49986837
BootStrapper-build-156735: 07/28/09 22:36:29 [Info] Total space required to unpack is 59984204
BootStrapper-build-156735: 07/28/09 22:36:29 [Info] attempting to find best unpack location for temporary installation files
BootStrapper-build-156735: 07/28/09 22:36:29 C:\ has 16714153984 free
BootStrapper-build-156735: 07/28/09 22:36:29 C:\ has 16714153984 free
BootStrapper-build-156735: 07/28/09 22:36:29 Local fixed drive C has 16714153984
BootStrapper-build-156735: 07/28/09 22:36:29 D:\ has 16608698368 free
BootStrapper-build-156735: 07/28/09 22:36:29 Local fixed drive D has 16608698368
BootStrapper-build-156735: 07/28/09 22:36:29 N:\ has 248623509504 free
BootStrapper-build-156735: 07/28/09 22:36:29 Local fixed drive N has 248623509504
BootStrapper-build-156735: 07/28/09 22:36:29 Not a directory: 2 - C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\
BootStrapper-build-156735: 07/28/09 22:36:29 Creating directory 'C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\'
BootStrapper-build-156735: 07/28/09 22:36:29 C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\ has been selected as the unpack location
BootStrapper-build-156735: 07/28/09 22:36:29 [Info] Extracting setup files to "C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\"
BootStrapper-build-156735: 07/28/09 22:36:29 --> instmsiw.exe [2585872]
BootStrapper-build-156735: 07/28/09 22:36:29 --> VMware Player.msi [5421568]
BootStrapper-build-156735: 07/28/09 22:36:30 --> Authd.cab [44329]
BootStrapper-build-156735: 07/28/09 22:36:30 --> codec.cab [89154]
BootStrapper-build-156735: 07/28/09 22:36:30 --> Core.cab [3370025]
BootStrapper-build-156735: 07/28/09 22:36:30 --> Devices.cab [642120]
BootStrapper-build-156735: 07/28/09 22:36:30 --> DHCP.cab [129286]
BootStrapper-build-156735: 07/28/09 22:36:30 --> Docs.cab [50357]
BootStrapper-build-156735: 07/28/09 22:36:30 --> hqtray.cab [21407]
BootStrapper-build-156735: 07/28/09 22:36:30 --> ImageC~1.cab [1190927]
BootStrapper-build-156735: 07/28/09 22:36:31 --> Japane~1.cab [25138]
BootStrapper-build-156735: 07/28/09 22:36:31 --> Japane~2.cab [1531025]
BootStrapper-build-156735: 07/28/09 22:36:31 --> Keyboard.cab [22195]
BootStrapper-build-156735: 07/28/09 22:36:31 --> mfc_x64.cab [1014637]
BootStrapper-build-156735: 07/28/09 22:36:31 --> micros~1.cab [872824]
BootStrapper-build-156735: 07/28/09 22:36:31 --> micros~2.cab [871077]
BootStrapper-build-156735: 07/28/09 22:36:32 --> NAT.cab [170324]
BootStrapper-build-156735: 07/28/09 22:36:32 --> net32.cab [88241]
BootStrapper-build-156735: 07/28/09 22:36:32 --> net64.cab [86414]
BootStrapper-build-156735: 07/28/09 22:36:32 --> Network.cab [193122]
BootStrapper-build-156735: 07/28/09 22:36:32 --> P2V.cab [13487114]
BootStrapper-build-156735: 07/28/09 22:36:33 --> ParPort.cab [12887]
BootStrapper-build-156735: 07/28/09 22:36:33 --> Perfmon.cab [127331]
BootStrapper-build-156735: 07/28/09 22:36:33 --> PlayerUI.cab [4723593]
BootStrapper-build-156735: 07/28/09 22:36:33 --> Player~1.cab [162600]
BootStrapper-build-156735: 07/28/09 22:36:34 --> PlyrJa~1.cab [179988]
BootStrapper-build-156735: 07/28/09 22:36:36 --> ThinPr~1.cab [449071]
BootStrapper-build-156735: 07/28/09 22:36:36 --> UI.cab [5844941]
BootStrapper-build-156735: 07/28/09 22:36:37 --> USB.cab [63168]
BootStrapper-build-156735: 07/28/09 22:36:37 --> VMCIDe~1.cab [297066]
BootStrapper-build-156735: 07/28/09 22:36:37 --> VMX_Re~1.cab [6216839]
BootStrapper-build-156735: 07/28/09 22:36:37 --> VSockLib.cab [2197]
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] No upgrade is necessary. System version meets minimum requirements
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Windows Installer is already correct version
BootStrapper-build-156735: 07/28/09 22:36:37 Did not find file/directory: "C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\vcredist_x86.exe"
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Verify: Call WinVerifyTrust on C:\VMware-player-2.5.2-156735.exe: 4
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Verify: C:\VMware-player-2.5.2-156735.exe - Trusted
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Verify: Verifying C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\\VMware Player.msi
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Retrieving C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\\VMware Player.msi's vendor information using Version Info
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Cannot get vendor name - no file ver info size (1812:The specified image file did not contain a resource section.)
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Get vendor name found from Summary Info
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Verify: C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\\VMware Player.msi is VMware's App - continue verification
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Verify: Call WinVerifyTrust on C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\\VMware Player.msi: 4
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Verify: C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\\VMware Player.msi - Trusted
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Verify: Verifying C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\VMware Player.msi
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Retrieving C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\VMware Player.msi's vendor information using Version Info
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Cannot get vendor name - no file ver info size (1812:The specified image file did not contain a resource section.)
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Get vendor name found from Summary Info
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Verify: C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\VMware Player.msi is VMware's App - continue verification
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Verify: Call WinVerifyTrust on C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\VMware Player.msi: 4
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Verify: C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\VMware Player.msi - Trusted
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Checking the package Signatures: Res: 0
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Setting Internal UI level
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Calling MsiInstallProduct with szInstallPath = C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\VMware Player.msi
BootStrapper-build-156735: 07/28/09 22:36:37 and szCommandLine = {null}
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Checking for existing product {A53A11EA-0095-493F-86FA-A15E8A86A405}
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Checking for existing product {31799B14-B3E7-4522-B393-6206C03EC5D3}
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Checking for existing product {A53A11EA-0095-493F-86FA-A15E8A86A405}
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] No existing products found
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] The product code '{A53A11EA-0095-493F-86FA-A15E8A86A405}' is unknown. Use first time install logic.
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] MSI logging to "C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\vmmsi.log"
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] Properties passed to msiexec is TRANSFORMS=:1033
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] CWD = [C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\]
BootStrapper-build-156735: 07/28/09 22:36:37 Failed to open key SOFTWARE\VMware, Inc.\NeedReboot
BootStrapper-build-156735: 07/28/09 22:36:37 Warning: Deleting a key that isn't empty: "HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\NeedReboot"
BootStrapper-build-156735: 07/28/09 22:36:37 [Info] InstallProduct([C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\VMware Player.msi], [ TRANSFORMS=:1033])
VMInst: 07/28/09 22:36:38 Begin Logging
VMInst: 07/28/09 22:36:38 Getting Property Installed =
VMInst: 07/28/09 22:36:38 Getting Property ProductName = VMware Player
VMInst: 07/28/09 22:36:38 Starting VMware Player installation: Releasebuild-156735
VMInst: 07/28/09 22:36:38 End Logging
instUtils-build-156735: 07/28/09 22:36:38 Begin Logging
instUtils-build-156735: 07/28/09 22:36:38 Checking System Version
instUtils-build-156735: 07/28/09 22:36:38 Setting property VMSYSVER = :WIN2003:WINDOWS SERVER 2003:STANDARD EDITION:SPMAJ=2:SPMIN=0:BUILD=3790:
instUtils-build-156735: 07/28/09 22:36:38 Done System Version
instUtils-build-156735: 07/28/09 22:36:38 End Logging
instUtils-build-156735: 07/28/09 22:36:39 Begin Logging
instUtils-build-156735: 07/28/09 22:36:39 Reading in properties
instUtils-build-156735: 07/28/09 22:36:39 Getting Property OriginalDatabase = C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\VMware Player.msi
instUtils-build-156735: 07/28/09 22:36:39 Did not find file/directory: "C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\VMware Player.txt"
instUtils-build-156735: 07/28/09 22:36:39 End Logging
instUtils-build-156735: 07/28/09 22:36:39 Begin Logging
instUtils-build-156735: 07/28/09 22:36:39 VMAppSearch running
instUtils-build-156735: 07/28/09 22:36:39 Loaded library Kernel32.dll(2011430912)
instUtils-build-156735: 07/28/09 22:36:39 Freeing library: 2011430912
instUtils-build-156735: 07/28/09 22:36:39 Loaded library Kernel32.dll(2011430912)
instUtils-build-156735: 07/28/09 22:36:39 Freeing library: 2011430912
instUtils-build-156735: 07/28/09 22:36:39 VMAppSearch ended
instUtils-build-156735: 07/28/09 22:36:39 End Logging
VMInst: 07/28/09 22:36:40 Begin Logging
VMInst: 07/28/09 22:36:40 Checking for VM.
VMInst: 07/28/09 22:36:40 Inside a VM.
VMInst: 07/28/09 22:36:40 Getting Property ProductName = VMware Player
VMInst: 07/28/09 22:36:40 Cannot query key value HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\Wnd: 2
VMInst: 07/28/09 22:36:40 Attaching to window with title "VMware Player"
VMInst: 07/28/09 22:36:45 End Logging
BootStrapper-build-156735: 07/28/09 22:36:47 [Info] MsiInstallProduct returned 1602
BootStrapper-build-156735: 07/28/09 22:36:47 Checking if we need reboot
BootStrapper-build-156735: 07/28/09 22:36:47 Cannot retrieve reboot component(s) from registry. Trying from files
BootStrapper-build-156735: 07/28/09 22:36:47 Did not find file/directory: "C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\\vmreboot.tmp"
BootStrapper-build-156735: 07/28/09 22:36:47 The reboot file does not exist
BootStrapper-build-156735: 07/28/09 22:36:47 Reboot(0) []
BootStrapper-build-156735: 07/28/09 22:36:47 [Info] Returned to [C:\]
BootStrapper-build-156735: 07/28/09 22:36:47 [Info] Cleaning up temp dir [C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\]
BootStrapper-build-156735: 07/28/09 22:36:47 Deleting [C:\DOCUME~1\ADMINI~1.IDT\LOCALS~1\Temp\{A53A11EA-0095-493F-86FA-A15E8A86A405}~setup\]
BootStrapper-build-156735: 07/28/09 22:36:47 [Info] Setup exit code is 1602
BootStrapper-build-156735: 07/28/09 22:36:47 End Logging