You probably want to try out Shared VMs, which will allow the virtual machine to be managed by a service which is always running – even when no-one is logged in to the host OS console. You should be able to move your existing VM to a Shared VM. Then you can set up AutoStart for the VM to automatically power-on the VMs when the host OS starts up.
Hope this helps!
dariusd I don't need to access the VMs remotely. I only need to be able to access the processes remotely. I'm not understanding that KB. How do I get the VM to autostart and run in the background without being logged in on the host system.
You configure the VM to be a shared one.
Well I was able to figure out how to share however now I can't connect to sharepoint server which is the reason why I converted it. I am receiving the error Cannot connect to the configuration database. It was working before the share. I removed the sharing and disabled server sharing and I am still getting that error message. I even tried locally on the VM and I am still getting that error message. Any ideas what the sharing would have changed?
I remembered that I almost deleted a couple of the folders for sharepoint and sql server earlier today while clearing off space. Apparently I did delete most of the contents so I'm going to have to convert the hard drive again.
Oops! Hopefully you can repeat the hard drive conversion without too much hassle.
Regarding the use of Shared VMs: Think of it more as "VMs which are not associated with a particular user logged-in at the console"... Such VMs have two interesting properties... One is that they run – and can provide their own network services – when no-one is logged in (which is what you want), and the other is that the VMs can be managed (power-on/power-off, access to console, either locally or remote over the network) by users with appropriate credentials (which gives the feature the name "shared VMs"... "VMs which are not associated with a particular user" is not a good marketing name ).
If you don't need remote access to the VM, you can try configuring a host firewall to block access to the remote VM service on port 443, but make sure that your own workstation can still access the shared VM service on port 443 or Workstation will not be able to manage that VM.
It's working however I'm noticing that I can't compact the drive, use shared folders, or even paste in from clipboard on the shared VM. Is this normal and is there a way around that?
There are a few limitations to Shared VMs. I don't know them off the top of my head (and I can't immediately locate the relevant documentation either!), but your list all seems like the sort of stuff that could end up limited in a Shared VM setup.
You may be able to work around some of the limitations: Windows File and Print sharing between the guest and the host can substitute for Shared Folders, and I would expect that the Remote Desktop service built into Windows would be able to supply clipboard sync and drag-and-drop. Compacting the virtual disk will probably need to be performed manually from the command-line while the VM is powered down.
Limitations of Shared VMs are here:
When you share a virtual machine, you lose these features:
- Shared Folders
- drag and drop
- copy and paste
- Thin Print
- Ability to connect/redirect USB devices from the host to the virtual machine not available with Workstation 8.x
- 3D Acceleration
Not being able to compact the disk surprises me. Do you mean that it is not enabled in the UI?
Perhaps the vmware tools option still works?
Wil| Author of Vimalin. The virtual machine Backup app for VMware Desktop Products
| Vimalin : Automated backups for VMware Fusion and VMware Workstation Professional
| More info at https://www.vimalin.com
| Twitter @wilva
| VMware Wiki at http://www.vi-toolkit.com