Interesting, so if I replace that registration DB with an unmodified one I could effectively make a registered install an unregistered one, causing the user to be prompted to enter a serial on first use? That would be absolutely ideal.
Olly -----Original Message----- From: Peter van Houten [mailto:[EMAIL PROTECTED] Sent: 24 June 2008 12:51 To: NT System Admin Issues Subject: Re: Adobe CS Suite roll out and Windows networks OK ~ I'll dig it out and send it to you. If the 50 systems are presently disparate in their content, I would go the single image route if possible. Believe me when I say it took *weeks* to get my client up and running because each system had to be installed separately due to the differing mix of software on each. CS3 products maintain a SQLite "registration" database at: c:\program files\common files\adobe\adobe pcd\cache\cache.db If you replace that file with the original, unmodified version (before registration), it will redo the registration procedure. The unadulterated file is 10,240 bytes. Be mindful that *all* installed CS3 products will be affected by this procedure. If you are in any doubt as to how problematic this software can be, Google "adobe cs3 installation problems"... On the 24/06/2008 13:22, Oliver Marshall wrote the following: > Peter, > > Any help would be a good thing :) > > I've thought about installing them all on one and then imaging the > machine and applying the image across the board (its quicker to apply > the entire image than to install the Suite itself). However I can't find > a way to get Adobe products to ask for a key when the user firsts loads > them, which means all the machines would have to go out with the same > key. I'm not sure what that would do to the updates and so I haven't > even looked any further. > > Olly > > -----Original Message----- > From: Peter van Houten [mailto:[EMAIL PROTECTED] > Sent: 24 June 2008 11:48 > To: NT System Admin Issues > Subject: Re: Adobe CS Suite roll out and Windows networks > > Oliver, my sympathies are with you. I haven't done any GPO rollouts but > installing CS3 products onto XP platforms was a real challenge. So much > so, that the systems (XP Pro SP2) that are installed and working (about > 15 as I remember) have been imaged and have strict instructions to be > left completely alone (no updates, service packs, nothing without > consulting us first). Some of the programs (especially Photoshop and > Premiere) in the Adobe CS3 suite are *extremely* finicky during the > install process. Suffice to say, short of an install to a freshly > formatted system, it was a real mission. I have a short list of > pointers that I can send you off list if you like. > > On the 24/06/2008 12:24, Oliver Marshall wrote the following: >> Anyone had any experience of rolling out Adobe CS3 suite across 50 or >> so machines ? If so, did you find any documents on how to automate it >> using any of the features in Windows (ie creating a premade package >> and rolling it out via GPO) ? We've got to get 50 copies of Office >> 2007 and Adobe CS3 installed and while Office is clearly fairly easy >> Adobe is proving harder due to a lack of decent info from Adobe. >> >> Olly ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
