Deployment Question - Reserialize CS3 Suite on OS X

Question

Hello,
We want to build a package installer for our technicians to be able to go out and install Creative Suite CS3 that contains all of the updates. To build the package, we install, which requires a serial number, and then perform all of the updates. After that, we need to unserialize so that we can make a package installer. We have been able to figure out that deleting the Library/Application Support/Adobe/Adobe PCD/cache/ will unserialize the app, prompting us to serialize on next boot, but Acrobat no longer works after this process. Has anyone come up with a workable way to unserialize CS3 suite so it can be serialized?
Thanks

Answer 1

Thank you for the suggestion try67, I'll attempt to be a little more clear. For many of our customers, we get the volume license of CS3 and we are able to build drive images for them with CS3 and all the updates. The process I am talking about is the ability to create a package installer, which we can do with many other applications. For most applications, it goes like this..
1. Take a snapshot of the machine.
2. Install the application
3. Install all updates
4. De-serialize the software (most applications automatically do this when they notice they're on another system)
4. Take another snapshot of the machine.
5. Create a package installer of the CS3 installation with all the current updates.
Why do this? We service 1000's of systems over 100's of customers and have many technicians that have to install the CS3 suite. We don't want to spend more time on this task then is necessary. Additionally, it saves the customer money because the package installer is significantly faster than the CD/DVD install and the technician doesn't have to sit there repetitively installing Adobe updates. The other option is for us to take those site licenses, put them on machines and build package installers of those every time there is an Adobe update, not a very realistic option. Plus, that doesn't help us with the small installations that don't have site licensing.
The ability to build a package installer is useful regardless as to if you are a single person shop or you have lots of technicians. The only people who don't like package installers or disk images are those that like to overcharge the customer
As far as conforming to the EULA, some of our customers are large Adobe customers and they build these package installers all the time (on Windows and Mac). Their lawyers have already vetted the process through the EULA. To be clear, the installer is not serialized, so once it is installed, the serial number must be added to make the software active.
If you look at CS3 suite, you can easily make a package installer based upon my initial post, but the reserialization routine in CS3 does not reserialize Acrobat. All we're asking is that the routine handle all the applications that came with the suite or some method of calling the proper routine that will reserialize Acrobat.
I hope I cleared up the request.
Thanks -- Nick