I was trying to publish Apple’s QuickTime Player into my home lab at the weekend, and decided to lock down various parts of the user interface. Everything seemed to go without a hitch – I used the Spy Tool to select the parts of the interface I wanted to disable (namely menu items), applied the Lockdown Actions to a specific group, logged off and tested. However, I was a little surprised to find that when I launched the program directly, the Lockdown actions worked – but when I double-clicked on a QuickTime movie file to open the program, they didn’t. Rather bizarre.
It turns out the reason for this is because the Spy Tool captures the Window Title as part of the Lockdown process which allows it to identify which windows it is supposed to be working on. When you open a QuickTime movie, however, QuickTime changes the Window Title to the name of the video! So AppSense Environment Manager thinks it is looking for a window that it can’t see, and the Lockdown Action fails.
There’s an easy enough way around this, though. Simply edit the Lockdown item in Environment Manager and change the Parent Text field to a wildcard (*) as shown below.
And that’s all there is to it – save and deploy your config, and you can now lock down QuickTime Player to your heart’s content.
Share
