Hi All,
I have been trying several times, and with different CS3 configurations to build a package. I know I in another thread earlier pointed to FileWave.org for their whitepaper on how to build the package, but whatever I do, licensing is complained about when I launch any Adobe application from my package.
This was my FileWave link:
[url]http://www.filewave.org/viewtopic.php?t=643[/url]
Have anybody gotten this to work with Iceberg, or something similar, and how is it done?
Thanks,
Søren
We have use a key-served site-license for Adobe CS3, so this may be different from your setup, but here’s how I got it working:
A combination of logGen, pkgGen, and IceBerg based on this workflow: [url]http://blog.irisink.com/?p=106[/url] This article from irisink explains how to use logGen and pkgGen to capture changes to the system, but I found that Leopard PackageMaker (and InstallEase) both screwed up while packaging CS3. So, instead, I used IceBerg to package everything in the “fauxroot” folder created by pkgGen.
This may be obvious, but I ran logGen to make a before capture of the system before installing, ran another after installing Adobe Design Premium and entering the SN. Then I ran pkgGen on the difference and used that to create an IceBerg package project.
I made a second package for Adobe Web Standard using the same method. With this setup, you MUST install the Design Premium package first or neither will work properly.
I’m in the process now of packaging updates & our key-server app. The un-keyed, site-licensed projects are working well.
Also, IceBerg lets you choose to make your package contents “Project Relative” or “Absolute Path.” I chose to make them all Project Relative, and this worked for me. Also, in the Settings area, I checked “Follow Symbolic Links” and chose “Root Authorization.”
[QUOTE][u]Quote by: Theilgaard[/u][p]########
[snip]
Have anybody gotten this to work with Iceberg, or something similar, and how is it done?
Thanks,
Søren
########[/p][/QUOTE]We’ve gotten it work, but we are FileWave.customers. Are you using corporate serialized/site licensed Adobe software, or individual needs-to-be-activated licenses? Individual licenses would be a huge PITA.
My notes list that at least the following files are the locations of the serial numbers:
/Library/Application Support/Adobe/Adobe PCD/cache/cache.db
– This appears to be the new “Adobe Registration Database”, where all licenses for all installed Adobe software lives.
/Library/Preferences/FLEXnet Publisher/FLEXnet/adobe_00080000_tsf.data
– The “Trusted Storage File” appears to be a file related to activation of products in the Adobe CS3.
Check that you’re distributing those. I’m sure that there are other things that will cause CS3 to throw up a licensing request, but it’s a starting point.
– Patrick
When I followed the FileWave description, these files is part of their description. I build my installer with LANrev InstallEase manually by draggin the folders in as described in the document, and then I build an Icaberg project, and then the package.
The empty folder mentioned in the document was in the Iceberg project, but I did not put empty files into those folders, as I do not think that empty folder should be a problem for Iceberg.
What puzzled me was the file in /Library/Caches which was not present on the CS3 Design Premium installation, as it is on the CS3 Standard installation. And not all the empty folders mentioned in the description was present in the Standard installation.
I will try using ewhite’s suggestion, and also LANrev in snapshot mode.
/Søren
Part of the assumption made by Adobe is that whoever is running the suite is an admin, and will have the ability to create those folders (or do other administrative/management tasks like install plugins at the request of Acrobat). Adding those folders allows the CS apps to launch without complaining.
Did you run all the applications before attempting to assemble your package? Some of the various required folders only appear upon first launch of the various applications.
FWIW, the reason that FileWave requires you to create folders and place a file in those folders is that the folders are required for CS3 to run, but FileWave can’t distribute empty folders (it distributes everything as a file–paths are created as needed). Can Apple’s installer create empty folders?
– Patrick
[QUOTE][u]Quote by: Patrick+Fergus[/u][p]Part of the assumption made by Adobe is that whoever is running the suite is an admin, and will have the ability to create those folders (or do other administrative/management tasks like install plugins at the request of Acrobat). Adding those folders allows the CS apps to launch without complaining.
Did you run all the applications before attempting to assemble your package? Some of the various required folders only appear upon first launch of the various applications.
FWIW, the reason that FileWave requires you to create folders and place a file in those folders is that the folders are required for CS3 to run, but FileWave can’t distribute empty folders (it distributes everything as a file–paths are created as needed). Can Apple’s installer create empty folders?
– Patrick[/p][/QUOTE]
Iceberg packages can, so I assume Packagemaker can as well.
I can’t believe we bought a 45 user volume license and no way to push to our computers. When will Adobe learn?
Don
what i did for CS3 install with LANrev.
I packaged up the CS3 Design Premium install Directory, the 2.6GB beast that contains the Setup.app and the deployment, payload and resources directories, and the bootstrapper.dmg.
I install this into /Users/Shared/AdobeCS3DP/
then when the system comes up, and LANrev is controlling it, it will then push an installer package(could be done by a onetime startup item too), that I included all of the updates in as well. This package writes the application.xml.override file to the proper location, then runs the installer, then it runs each patch separately. at the end of that I added the icons to the dock of any existing users, and the user templates.
Why did I do it this way, i wanted to be able to add more patches easily and not have to recreate the package from scratch each time. and Adobe in their lack of wisdom has not included $3 in their install scripts so things happen at /, and instead of trying to work around that I decided to just let it install after the system comes up.
The last thing I added was the things that get changed when acrobat pro starts up.
I used the installease tool to find out what changed so that I would not need the admin password the first time it starts.
*Note only run the snapshot before and after you start acrobat pro. if you do it prior to launching any of the other applications as is required by acrobat pro for licensing purposes, and you capture that, it seems to break the licensing pretty badly.
*Second Note: all adobe updates are not created equal, some of them have the AdobePatcher.app that you can just get and run. some of them have different formats and you have to mount some silly dmg before you actually find the patch, (inDesign was this way) and some of them are simple file replacements, camera raw, flash…