If you have installed VMware player, then you have a few new services. Now, I don’t like new services, and I really don’t like services that start automatically EVERYTIME I turn on my computer, but the kicker is, VMWare player isn’t smart enough to start them itself if they are stopped. So I’m stuck, do I let them run in the background constantly or do I start them up in the service manger every time. Nope, I, like any good sysadmin, wrote a batch file.
I have 2 batch files, Service start, and Service stop:
startVMPlayer.bat
sc start vmount2
sc start “VMware NAT Service”
sc start “VMnetDHCP”
sc start “VMAuthdService”
stopVMPlayer.bat
sc stop vmount2
sc stop “VMware NAT Service”
sc stop “VMnetDHCP”
sc stop “VMAuthdService”
Pretty simple, just open notepad, paste the 4 lines of code into each file, and save onto your desktop or quick launch bar. I find this very helpful for dealing with poorly written software which doesn’t include it’s own service control functions. The other problem with VMware Player, if the services aren’t running, you don’t even get an error message. Causes some strange issues on reloading a paused image, where the networking was enabled the first time. So, VMware please add some better service support for your player software.
No related posts
March 19th, 2007 at 7:52 am
I guess you could even append commands to start and exit VMware itself at the end of these batch files to reduce clicking.
Anyway, these 4 VMware services together don’t consume more than 2MB of RAM, so I think for know it’s better to avoid the hassle of using this barch and let them running along.
March 28th, 2007 at 12:13 am
yeah i recommend the same (for workstation)
for player i recommend change associasions for .vmx to one batch file accepting one parameter (vmx conf file). It will run services… run vwmare player and then it (automatically) waits until vmware player ends…. then it will “shoot” those stupid services
September 19th, 2008 at 5:12 pm
hi…i’m having the same situation. However, currently using server version 2.0 and the batch file commnands do not seem to work.