Posted on 01-16-2008 07:27 AM
Is anyone using Casper's Adobe CS3 packaging feature to distribute keyed
copies of CS3 apps? If so, how are you doing it?
For those unfamiliar with keyed applications, I'm using Sasafrass KeyServer
to restrict the number of simultaneous launches of Acrobat, Dreamweaver and
Photoshop.
So far, it looks like I'd have to wait for Casper has to do a full CS3
un-keyed installation during startup. Then, I might use a policy to send the
keyed components. Seems like this would be more work to maintain than
building my own pre-keyed CS3 packages.
Comments anyone?
Tom Francais
OIT Software Support
Princeton University
Posted on 01-16-2008 08:00 AM
Hi Tom,
This semester will be our first run using the Adobe deployment in Casper. You are right about how you'd have to do the keyed apps though, it would have to lay the keyed applications over the top after the installer has finished at reboot.
The work is you just have to pack the applications if you patch them versus the entire suite. I still think that's easier. Unfortunately with keying you can't really take advantage of deploying patches for the applications either since you'd have to key the new application.
Instead of locking ourselves into a set number of copies available we still track usage of the suite with KeyServer, and if we do go over our number of copies we just purchase the additional overage. This allows us to not key the applications. The KeyServer client will do a catch up report to the KeyServer when it can talk to the server again, meaning that if a user goes off-site with no access to KeyServer they don't have to check out a key, and when they get back and the client can contact the server it updates the server with the usage while it was away again so we can make sure if we went over count at any time and adjust.
You have it figured out, you just need to decide what you want to do it sounds like.
Craig