You can use the DesktopOwner feature of the FileWave Client. Place the VM Ware files in /Users/DesktopUser in your Fileset.
Then each client has a preference for which local account should be used to activate user specific files. If you've configured your clients this way, you'd be able to make the delivery.
If you've not specified a DesktopUser in each client pref, then the best solution would be to use the copyToAllUsesrs script and rather than copying the disk image, you might try activating the disk image to /Users/shared/Documents, then copy symlinks to the VMWare folder containing the files to each users Documents folder.
[url=http:///download.php?file=copyFileToAllUsers.sh.zip]Download the Copy to All Users Script[/url]
You will need to edit the script to fit your needs.
In looking into this case, I found that you can have the Virtual Disk in any location on the hard drive.
I would recommend the following
- Move the folder Virtual Machines from you user's Documents folder to /Library
- Launch VMWare by double clicking on your XP Image in the /Library/Virtual Machines folder
- Move the file com.vmware.fusion.plist from your user's Library/Preferences folder to /Library/Preferences
- Copy the Virtual Machine directory from /Library into a Fileset in the same location
- Copy com.vmware.fusion.plist from /Library/Preferences into a Fileset in the same location
- Update model and when download is complete, you should be able to launch VMWare from the Applications folder and you should see you Windows XP disk as a selection.
Almost there... I was able to get the program running and the XP .vmwarevm file moved over to the client machines. However, when I run the program, I get an error that says:
Failed to connect to peer process
The console comes up with:
VMware Fusion Error:
VMware Fusion unrecoverable error: (vmx)
Please request support.
To collect files to submit to VMware support, run "/Library/Application Support/VMware Fusion/vm-support.tool".
We will respond on the basis of your support entitlement.
The message boards for VMWare says to reinstall ([url=http://http://communities.vmware.com/thread/109272?tstart=0]http://communities.vmware.com/thread/109272?tstart=0[/url]). This is something I would not like to do. For the time being I set the VMWare install I have on my test machine to "Left Behind" and ran an update. The update could not be run. There was an error that I posted below...
The kext error is generally due to problems with permissions. All files and folders within the Kext need to be owned by root, group wheel. Files need to be 644 and folders need to be 755. Please have a look at your Fileset and verify/change the permissions and ownership on the kexts as needed.
I checked the permissions and even went so far as to set everything in the set to 777. Unfortunately, same problem coming up. I tried to use FileWave Magic to recreate the set and could not get it to work.
Any other ideas to try and get this working? In the meantime, I have deleted the set and am installing VMWare Fusion on the machines that require it.
You should be able to deploy Fusion as a pkg. Coupled with your deployed license files, it may very well work the first time. Keep your current fileset self-healing and send out the pkg -- that pkg should have the necessary pre and postflight scripts.
In the long term, we'll work on making a vmware fileset and post a whitepaper on the subject.