I believe this is highly dependant on a couple of factors:
- Whether the user is a high enough level user on the machine (thus having the ability to actually start services in the first place). UAC may block anyone except "fully fledged" administrators.
- Whether the program itself was written to detect the status of the service and, if need be, be able to start it.
I'm believe that being an administrator on the machine is necessary to start services as it is making potentially harmful changes to the computer. Think about if a normal user (or program belonging to them) could stop and start the "Network" service without any control whatsoever. It could quickly render your computer unusable or unstable or worse.
As that is the case it is possible that any program belonging to that user is not able to start a service even if it was so programmed to do, unless it has been started with administrator privileges as it will immediately be blocked by UAC.
What you as a user could do though is to use the net start command.
You could simply write a simple batch file that runs the commands necessary to start or stop the VMWare services, then right click that batch file and select "Run as Administrator":
net start "VMware DHCP"
net start "VMware authorization"
net start "VMware NAT"
and so on. Then with another script, also using the "Run as Administrator":
net stop "VMware DHCP"
net stop "VMware authorization"
net stop "VMware NAT"
Assuming you have administrator rights, or at least the administrator password in which case the "Run as Administrator" will pop up a password prompt.
As a side note, there are many, many ways to have a program run as administrator, most of which will pop up a UAC prompt.