We're paying rather a lot of money for an annual subscription to Parallels Desktop, which we haven't been able to use as of yet because Parallels won't play nice within our managed environment. I was wondering whether anyone else has had greater success than us in "allowing" network users to open Parallels Desktop on a managed client using Workgroup Manager?
Basic specs: OS X 10.6.8, locally-configured MCX preferences, using Workgroup Manager as part of Server Tools 10.6.8. We've so far tried, with the latest version 7:
* Adding Parallels Desktop to the allowed list of Applications (logging in as a network user: "You don't have permission to open the application 'Parallels Desktop'.")
* Adding individual apps within the Parallels Desktop.app bundle (same result)
And with the latest version 8:
* Adding Parallels Desktop to the allowed list (logging in as a network user: "You don't have permission to open the application 'launcher'.")
* Adding "launcher" specifically ("You don't have permission to open the application 'inittool'.")
* Adding all other binaries to the list (back to "You don't have permission to open the application 'launcher'.")
In each case, I see some variation of the following message from parentalcontrolsd in the logs:
setup.local parentalcontrolsd[1193]: -[ActivityTracker checkApp:csFlags:] [1036:user] -- *** Incoming app appears to be masquerading as white listed app and failed signature validation: /Applications/Parallels Desktop.app/Contents/MacOS/launcher. Note: This may be a valid app of a different version than what was whitelisted (on a different volume?)
After trying many more permission combinations besides, I gave up and raised a support ticket which led to an internal developer ticket PDFM-36862. Is it really just a case of the developers fixing Parallels Desktop, or has anyone else had success letting it through the gates?
Basic specs: OS X 10.6.8, locally-configured MCX preferences, using Workgroup Manager as part of Server Tools 10.6.8. We've so far tried, with the latest version 7:
* Adding Parallels Desktop to the allowed list of Applications (logging in as a network user: "You don't have permission to open the application 'Parallels Desktop'.")
* Adding individual apps within the Parallels Desktop.app bundle (same result)
And with the latest version 8:
* Adding Parallels Desktop to the allowed list (logging in as a network user: "You don't have permission to open the application 'launcher'.")
* Adding "launcher" specifically ("You don't have permission to open the application 'inittool'.")
* Adding all other binaries to the list (back to "You don't have permission to open the application 'launcher'.")
In each case, I see some variation of the following message from parentalcontrolsd in the logs:
setup.local parentalcontrolsd[1193]: -[ActivityTracker checkApp:csFlags:] [1036:user] -- *** Incoming app appears to be masquerading as white listed app and failed signature validation: /Applications/Parallels Desktop.app/Contents/MacOS/launcher. Note: This may be a valid app of a different version than what was whitelisted (on a different volume?)
After trying many more permission combinations besides, I gave up and raised a support ticket which led to an internal developer ticket PDFM-36862. Is it really just a case of the developers fixing Parallels Desktop, or has anyone else had success letting it through the gates?