[sketch]

Could you please me more detailed as to the edits you made to the application.xml file?
Thanks

[QUOTE][u]Quote by: bskinner[/u][p]I am trying to do a similar deployment and I’m running into the same issues; Adobe has made this far from simple. So far we have managed to avoid building a package and simply modified the disk image. I have found two approaches that work most of the time.

[b][u]Adding application.xml.override[/u][/b]
This worked the best initially but ran into issues fairly quickly. In order to preserialize Acrobat, I created the “Contents/Resources/AMT/application.xml.override” directly in the application on the Acrobat 9 disk image but after version 9.0 this stopped working. After setting up a couple of DTrace triggers it looked like the AdobeSelfHealing.framework was to blame. In the initial 9.0 release, it would properly look for the override file in the AMT resources and preserialize Acrobat. In the later versions, however, it completely ignored the file (didn’t even TRY to stat(2) it). I ended up replacing the newer AdobeSelfHealing.framework with the original framework and things started working again. Replacing the framework introduces the chance for some pretty horrible breakage down the line, though.

[b][u]Editing application.xml[/u][/b]
Another approach I tried was adding the Serial, Registration, and other elements to the “application.xml” file. This worked for preserialization but, IIRC, it did not suppress the updates. There were also reports from several people that Acrobat reported errors with the licensing system but they were few and far between and we were unable to definitively point the finger at the application.xml edits as the root cause. Given that the file is signed, I would assume that there is a good chance the edits were causing at least some of the errors.[/p][/QUOTE]

[sketch]

[QUOTE][u]Quote by: dead2sin[/u][p]Also, just curious…are you running the installer command using a 10.6 machine, or is it running another version of OS X?[/p][/QUOTE]
10.6.3 machine

[sketch]

[QUOTE][u]Quote by: Allister[/u][p]Hey sketch,

This is 10.6 client, right ? What is the build number of the OS on the disc?

Allister[/p][/QUOTE]

Mac OS 10.6.2
build 10C2234

[sketch]

[QUOTE][u]Quote by: dead2sin[/u][p][QUOTE][u]Quote by: sketch[/u][p][QUOTE][u]Quote by: Allister[/u][p]Hey sketch,

The -target flag and path after it is unnecessary.

Allister[/p][/QUOTE]

No difference[/p][/QUOTE]

Try just this:

[code]sudo installer -showChoicesXML -pkg /Volumes/Mac\ OS\ X\ Install\ DVD/System/Installation/Packages/OSInstall.mpkg[/code]

Does that give you any output whatsoever?[/p][/QUOTE]

Negative. Same error.

[sketch]

[QUOTE][u]Quote by: Allister[/u][p]Hey sketch,

The -target flag and path after it is unnecessary.

Allister[/p][/QUOTE]

No difference

[sketch]

I ran:

sudo installer -showChoicesXML -pkg /Volumes/Mac\ OS\ X\ Install\ DVD/System/Installation/Packages/OSInstall.mpkg -target /Volumes/Test > ~/Desktop/OSInstall_default.xml

but I get “installer: Error – ” and no output :\

[sketch]

just talked to my Apple rep and he says yes

[sketch]

Yeah. Leopard and server 2008 definitely seem to have problems with each other. We’re working on this in our environment right now. It seems to be Kerberos and name-resolution related.
When I have more I’ll post (of course if someone has already found solutions I’d love to know)

[sketch]

[QUOTE][u]Quote by: Geno[/u][p]I am well behind both of you guys. I really don’t care what method I use, I just can’t get a working package for CS4. Right now I am just trying Photoshop, and can’t get a working pkg.

I have tried both of your methods. With the loggen route I got licensing errors I could not recover from. Tried again, and got the same problems. Today I tried the lanrev method, and it encounters errors when I tried to install the straight .pkg, and also when I used the iceberg route. I did not do any updates just used the lanrev snapshot method.

Any replies, private messages, or e-mails would be greatly appreciated.

sincerely,
adobe cs confused ;[/p][/QUOTE]

When you push your created package out to a test system is there already an Adobe product installed?

[sketch]

No the launchagent does not run automatically after enabling mobile accounts.

[sketch]

“Dear Apple…”

[sketch]

did you include the column headings?
if so did you leave the “dsAttrTypeStandard:” at the beginning of each?

[sketch]

Is there a command-line equivalent to what happens when you select a directory printer in the Add Printer app? That autodetection of printer driver would make scripting a ton easier

[sketch]

[QUOTE][u]Quote by: knowmad[/u][p]the plugin will ‘auto heal’ when next the program is run

[/p][/QUOTE]

But that would require the program to be run first. 😕

Not exactly “works right out of the box”

[sketch]

So you don’t do the plugin?

[Author]

Posts