VMware
1 2 3 4 5 Previous Next 64 Replies Last post: Jun 2, 2009 2:59 PM by curious2   Go to original post

Re: ESX VMWare Tools Silent Install/Upgrade ANSWER!

15. Sep 2, 2005 9:32 AM in response to: Rajeev
Click to view sbeaver's profile Guru 7,719 posts since
Nov 1, 2004
Hook me up please beavers_at_gtlaw_dot_com

Re: ESX VMWare Tools Silent Install/Upgrade ANSWER!

16. Sep 2, 2005 12:24 PM in response to: sbeaver
Click to view gul's profile Enthusiast 125 posts since
Jun 15, 2005
Add me to the list:
fixthetools@gulshome.com

Re: ESX VMWare Tools Silent Install/Upgrade ANSWER!

17. Sep 3, 2005 3:27 PM in response to: Rajeev
Click to view moenster's profile Master 956 posts since
May 19, 2004
Me to please :o)

nina_dot_henrik_at_mobilixnet_dot_dk

Thanks

Regards Henrik
Click to view Rajeev's profile Hot Shot 197 posts since
Nov 10, 2004
Sorry, just saw this thread. I've just sent out the file.

Re: ESX VMWare Tools Silent Install/Upgrade ANSWER!

19. Sep 6, 2005 11:03 PM in response to: Rajeev
Click to view TomVDB's profile Enthusiast 109 posts since
Apr 5, 2005
Rajeev could u email me the file?

Thx in advantage

tom.vandenbosch@uzleuven.be

Re: ESX VMWare Tools Silent Install/Upgrade ANSWER!

20. Sep 7, 2005 6:07 AM in response to: Rajeev
Click to view johnjore's profile Hot Shot 299 posts since
Mar 11, 2005
I would actually turn on the HW accelleration, (big boost on video performance) but too this day, I have not found a way to script it. Thanks meistermn!

I have automated it with AutoIt? but it's not a neat and clean way of doing it.

JJ

Message was edited by: johnjore

Click to view frond's profile Novice 66 posts since
Oct 6, 2003
We've used a combination of the "reg" command with a custom VBS script to script the process of enabling the video hardware acceleration. It's ugly and not very elegant, but it works. The command line is:

reg query HKLM\HARDWARE\DEVICEMAP\VIDEO | find /i "video0" | cscript enablehdwacc.vbs

All that does is change the setting in the registry so it takes effect on the next reboot.

This is the enablehdwacc.vbs:

Set WshShell = WScript.CreateObject("WScript.Shell")

' Acceleration Levels go from 0 to 5. 0=full, 5=none
intAccelLevel = 0

' Read output from the following command:
'
' reg query HKLM\HARDWARE\DEVICEMAP\VIDEO | find /i "video0"
'
' We have to do it this way because the name of the key we want
' is "\Device\Video0" (including the backslashes). The "\" character
' in the name screws up the RegRead method in VBS and there seems to be
' no way to escape it out. Hence, we have to get it from the "reg.exe"
' command line utility instead.
strInputString = WScript.StdIn.ReadLine

' Output contains "\Registry\Machine\System\CurrentControlSet\..."
' We need to replace "\Registry\Machine" with "HKLM" and add
' the Acceleration.Level value to the end
intStartLocation = instr(1, strInputString, "\System\CurrentControlSet\")
strPartKey = right(strInputString, len(strInputString) - intStartLocation +1)
strNewKey = "HKLM" & strPartKey & "\Acceleration.Level"

'Write the new key to the registry
WshShell.RegWrite strNewKey, intAccelLevel,"REG_DWORD"

Re: ESX VMWare Tools Silent Install/Upgrade ANSWER!

22. Sep 7, 2005 8:39 AM in response to: frond
Click to view Rajeev's profile Hot Shot 197 posts since
Nov 10, 2004
Awsome!!! I'm going to give this a try. I think the combination of the two solutions should help everyone out!

Re: ESX VMWare Tools Silent Install/Upgrade ANSWER!

23. Sep 7, 2005 10:54 AM in response to: quihong
Click to view Rajeev's profile Hot Shot 197 posts since
Nov 10, 2004
Just tried the vbs script posted above and it works like a charm!
Click to view Mike_Laverick's profile Virtuoso 4,064 posts since
Jan 5, 2004
Hi

I wasn't able to make it work as described above, but
the following made it work for me

SET VMTOOLPATH=
path

regedit /s
"%VMTOOLPATH%\disableDriverSigningWarning.reg"
msiexec.exe /i "%VMTOOLPATH%\VMware Tools.msi" /q
REBOOT="ReallySuppress"
regedit /s
"%VMTOOLPATH%\enableDriverSigningWarning.reg"

By editing a single value in the msi-file, using
orca, I can change the installation type.

How come the first didn't work?

This was all on windows 2000, the driver signing
stuff doesn't seem to work on server 2003.

Regards Henrik


There is a good reason why this reg method of disabling the driver pop-ups on Windows 2003.

Microsoft has removed the method!

This is because dodgy hardware vendors would use a reg file to bypass the protection to the users - to get their driver on without messages - and the switch it back on. Thus negating the whole point of Driver Signing Protection.

The reasoning behind this is documented here:

http://support.microsoft.com/kb/298503

The only way to disable the pop-ups in W2K3 is with either a transform file or using AD Policies - outlined in the document above to supress it...

Regards
Mike Laverick
RTFM Education - VMware

Re: ESX VMWare Tools Silent Install/Upgrade ANSWER!

25. Sep 20, 2005 2:38 AM in response to: Rajeev
Click to view Mike_Laverick's profile Virtuoso 4,064 posts since
Jan 5, 2004
After some messing around I FINALLY figured out how
to bypass the Hardware Acceleration check (for
Windows 2003) during the install. What you need to
do is create a transform that removes the following
lines from the InstallExecuteSequence in the MSI.

VM_CheckHWAcceleration
VM_CheckHWAcceleration_SetData

If you want the file let me know.


Hi there...

Can I have copy of the transform file - can you give me a sample of the command-line usage of msiexec so I know how to run it?

Regards
Mike Laverick
RTFM Education - VMware
Click to view Rajeev's profile Hot Shot 197 posts since
Nov 10, 2004
You have mail!

Re: ESX VMWare Tools Silent Install/Upgrade ANSWER!

27. Sep 20, 2005 6:29 AM in response to: Randy_B
Click to view Mike_Laverick's profile Virtuoso 4,064 posts since
Jan 5, 2004
I finally edited the msi with Wise and specified that
this package would upgrade the previous package (had
to give it a new product code). I first published the
msi to an administrative install share, got that from
another post:
http://www.vmware.com/community/thread.jspa?threadID=1
3440&start=15&tstart=0

For the driver signing in W2K3, I created a .inf that
sets the local security and import it with secedit.

Contents of the .inf to disable the unsigned driver
warning:

[Unicode]
Unicode=yes
[Version]
signature="$CHICAGO$"
Revision=1
[Registry Values]
MACHINE\Software\Microsoft\Driver
Signing\Policy=3,0

To reset it back to default:
[Unicode]
Unicode=yes
[Version]
signature="$CHICAGO$"
Revision=1
[Registry Values]
MACHINE\Software\Microsoft\Driver
Signing\Policy=3,1

Now that these steps all work individualy, I'm going
to wrap it all up in a vb script. I'll post the whole
thing when I'm done.

Randy


I'm interesting in this inf method of changing the setting - can you give me sample of what you would use in secedit command to do this...

Did you ever get round to writting this VBS File?

Kind Regards
Mike
Click to view doslager's profile Novice 9 posts since
Oct 7, 2005
Here's what I used to get the INF file to import:
secedit /configure /db .\blah.sdb /cfg .\enabledriversigningpolicy.inf

I then delete the blah.sdb file. I'm not sure it's function, but it's needed to complete the syntax for secedit.

One thing i did do was to reverse engineer the INF file by doing an export
secedit /export /cfg exportedsettings.inf

Then i looked in the INF file and saw the setting that needed tweaking, as below.

(You can find the limited documentation for secedit at: http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/b1007de8-a11a-4d88-9370-25e244560587.mspx)

FYI: There were some line breaks that got messed up in the above quoting/re-posting. Here is the line *between* quotes with no line breaks:
"MACHINE\Software\Microsoft\Driver Signing\Policy=3,1"
NOTE the space in "Driver Signing"
NOTE: 3,1 is "warn".....3,0 is "ignore"...and 3,2 is "block"

My method was to do this via a cmdlines.txt using sysprep. The policy is set to ignore drivers during the PnP re-discovery using the following line in my sysprep.inf [Unattended] Section. This allows the Mini Setup to re-find the NIC and install the drivers. W/o the ignore, it would not install the NIC, and thus not be able to join a domain, etc.
[Unattended]
DriverSigningPolicy = Ignore


Then it reapplys the driver signing policy at the end of MiniSetup with the above command part of the cmdlines.txt. This sets the policy back to where i want it ("warn but allow"). Otherwise sysprep/mini-setup would've set the machine policy to "ignore" and left it like that.

Hope this helps...i spent alot of time trying to figure out secedit and it's somewhat cryptic syntax. If you want the INF, and/or any of the sysprep stuff, email me at doslager (@) yahoo (dot) com, and i'll be happy to help.

Dave O.
Click to view diztorted's profile Master 733 posts since
Mar 14, 2005
We're doing something similar, and have found that this method works fantastic for pushing VMware Tools silently via a software delivery method (we use CA's SDO).. We tested it out recently when we upgraded to 2.5.2.. worked like a champ :)

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Incoming Links

Communities