Hey all,
One of our customers is running Parallels (Windows XP) in a networked home folder environment. They have Tiger Server and log into their networked homes from various other workstations.
Each workstation's Parallels installation is configured to keep vm's in /Users/Shared/Parallels. That way, the vm can be shared by any account logged into the computer.
I've been aware that the vm needs to have its permissions set so that all users can access it, and have made this change. However, one user is still receiving the error,
"Unable to get the geometry of the virtual hard disk. Perhaps file /Network/Servers/server.companyserver.com/Users/Shared/Parallels/winxp/winxp.hdd is not a valid virtual hard disk image file."
He only gets this when logging into a computer that he doesn't normally use. Perhaps not coincidentally, this user usually works on the server itself (not my recommendation!). If you're familiar with OS X Server, you'll notice that the path given in the error message is to a standard mountpoint.
Any clues as to why this is happening and how to fix it?
Thanks!
One of our customers is running Parallels (Windows XP) in a networked home folder environment. They have Tiger Server and log into their networked homes from various other workstations.
Each workstation's Parallels installation is configured to keep vm's in /Users/Shared/Parallels. That way, the vm can be shared by any account logged into the computer.
I've been aware that the vm needs to have its permissions set so that all users can access it, and have made this change. However, one user is still receiving the error,
"Unable to get the geometry of the virtual hard disk. Perhaps file /Network/Servers/server.companyserver.com/Users/Shared/Parallels/winxp/winxp.hdd is not a valid virtual hard disk image file."
He only gets this when logging into a computer that he doesn't normally use. Perhaps not coincidentally, this user usually works on the server itself (not my recommendation!). If you're familiar with OS X Server, you'll notice that the path given in the error message is to a standard mountpoint.
Any clues as to why this is happening and how to fix it?
Thanks!