[dead2sin]

See if this works for you:

Version 0.4

[url]http://dl.dropbox.com/u/11466/InstaDMG%20PatchOfficeUpdate%200.4.dmg[/url]

Its very similar to the other updates, just required one edit to the .dist file.

Let me know if that works or not. I don’t have time to do a test build with it atm.

Nate

[dead2sin]

I bet the patcher for communicator is more similar to the Office installer then the office patches.

I’ll download it and take a look.

Nate

[dead2sin]

[QUOTE][u]Quote by: bw38[/u][p]This patcher works with Update 14.0.2. Wish I could find a direct link to Communicator Update 13.1.0 to test that out as well. It seems it’s only available through Microsoft AutoUpdate.[/p][/QUOTE]

That is driving me crazy too. If you figure out a good way of getting your hands on it, let me know.

Nate

[dead2sin]

Curious. If you run them manually, do they work?

Nate

[dead2sin]

[QUOTE][u]Quote by: bw38[/u][p]So you’re saying I should install the software, run updates, then create the package from the Pre-Installed package? That sounds like it saves a lot of work from the guide that’s currently up! Awesome. I take it I still have to make the changes to Adobe Acrobat and Distiller so they don’t break and try to self-heal afterwards.

On another note, how do I go about getting the upgrade? I didn’t know I could do that. Would certainly be nice to take advantage of![/p][/QUOTE]

Just email their support and let them know that you own 7.21 and would like to get the latest update.

The guide is useful for non-composer users, but dang has composer got it nailed 🙂 Its only useful if you don’t need Acrobat.

Nate

[dead2sin]

[QUOTE][u]Quote by: bw38[/u][p][QUOTE][u]Quote by: dead2sin[/u][p][QUOTE][u]Quote by: bw38[/u][p]I have packaged the entire Adobe CS5 suite using the guide available. I packaged it with Composer and got it working pretty well except for one application: Media Encoder CS5 crashes every time I quit the program. It makes very little sense and I’m not sure what could be causing it. Now just to make sure, this only happens when I use a different account from the one I used to package the software originally. So for example, I make all my packages under the “administrator” account and Media Encoder seems to work fine (no crashing). However when I create another user account with admin rights, it suddenly starts crashing on me me. I’d post the log from Apple but it’s too long: however here’s a similar issue here that never got resolved it seems: http://forums.adobe.com/thread/756797%5B/p%5D%5B/QUOTE%5D

Did you use the Casper Preset for CS5 or did you do it yourself?

Nate[/p][/QUOTE]
I did it myself. What do you mean Casper Preset for CS5? I have Composer 7.2 only, not the Casper Suite. Are you referring to the Pre-Installed software package that Composer offers when deciding how to create a package?[/p][/QUOTE]

Yea, sorry. I was thinking Composer and said Casper. Upgrading to 7.31 and 8.0 is free btw if you own 7.x.

Either, way, Download the Latest diffs from the context menu at the top and then create a new package from Pre-installed software. That is how I did it and I am not experiencing the Media Encoder crashing issue.

Nate

[dead2sin]

[QUOTE][u]Quote by: bw38[/u][p]I have packaged the entire Adobe CS5 suite using the guide available. I packaged it with Composer and got it working pretty well except for one application: Media Encoder CS5 crashes every time I quit the program. It makes very little sense and I’m not sure what could be causing it. Now just to make sure, this only happens when I use a different account from the one I used to package the software originally. So for example, I make all my packages under the “administrator” account and Media Encoder seems to work fine (no crashing). However when I create another user account with admin rights, it suddenly starts crashing on me me. I’d post the log from Apple but it’s too long: however here’s a similar issue here that never got resolved it seems: http://forums.adobe.com/thread/756797%5B/p%5D%5B/QUOTE%5D

Did you use the Casper Preset for CS5 or did you do it yourself?

Nate

[dead2sin]

Fixed. Thanks 🙂

[dead2sin]

It will show a list of users by default. You must change it to do names and passwords. As far as hiding the admin account, I believe you can hide it from the login window if it is above a specific UID. I think the createUser documentation might have more on that. I would look into that and just remove anything from firstboot that has to do with loginwindow and see what happens.

Nate

[dead2sin]

Is this for a 10.6 image, or another version of OS X? I assume OS X client as well? Also, is the machine you are building the image on the same as the version of the image you are building?

Nate

[dead2sin]

I’ll fix it 🙂 I changed it to 644 after someone said what I had was wrong. If 775 works, then we’ll go with that.

Nate

[dead2sin]

Time to suck it up. I just ran a new build with 10.6.5 and iLife 9.0.4 shows up in Software Updates (DOH!). I hadn’t run a build since 10.6.4, but I thought I had…soooooooooo….yea. Sorry guys 🙁 Thankfully, munki can install this at first boot for me, So that is what I plan on doing.

Nate

[dead2sin]

Yep. A bare .app gets copied to /Applications by default. If its a .pkg in a dmg, it installs the pkg.

Nate

[dead2sin]

While not exhaustive, there is a list of common things that people change here:

They are split up by firstboot script and postflight:

[url]http://osxdeployment.com/wiki/Firstboot_Postflight_Commands
[/url]
[url]http://osxdeployment.com/wiki/Firstboot_Script_Commands[/url]

If you need any specific settings beyond that, let me know and I can tell you how to wrangle them 🙂

Nate

[dead2sin]

There is a bug that prevents it from using the latest version at the moment. I don’t know of a way to pick a specific Install Disc to use when issuing the command. I’d imagine if you had different models, the easiest way about it would just be to copy vanilla and delete out the builds you don’t need. Yes, a bit tedious, but it would get the job done.

Nate

[Author]

Posts