[dead2sin]

cygnus in ##osx-server on irc.freenode.net updated the patcher. Here is a link to it: [url]http://dl.dropbox.com/u/429559/patchOffice2011_1410Update_v041.dmg [/url](he posted it to the instadmg-dev google group)

Hop on irc if you have any questions or email the instadmg-dev google group.

Nate

[dead2sin]

Very Nice! Its always a pain to put stuff into existing user’s folders, but that looks like it’ll do the trick 🙂

Nate

[dead2sin]

I distribute it with Munki now, which is why I’ve not spent much time on getting this updated 🙁 Sorry. Work has me doing lots of Windows stuff, so I have not had time for much other stuff.

Nate

[dead2sin]

If you dig in the patcher.app you can find the script. Here are the contents of the script:

[url]http://pastebin.com/XCG11QsK[/url]

I’ll update the patcher itself in a bit.

Nate

[dead2sin]

Yes. I created one for use as a NetBoot set and it works perfectly fine for imaging purposes (DeployStudio Netboot set).

Nate

[dead2sin]

[QUOTE][u]Quote by: cyberatz[/u][p]No special patcher is required to fix this 😯

Basically, download the update file (see links above) from MS. Kill any running instances of Communicator. Move the file from your Applications folder to trash. Run the updater. The updater will basically reinstall communicator with the correct 13.1.0 version.

None of this patcher stuff.

Enjoy.

[/p][/QUOTE]

This is specifically for building images using InstaDMG. Communicator shouldn’t be installed on your build system to begin with, so I assume you are referring to installing the update on a standard client system?

Nate

[dead2sin]

You only need the latest patcher version. The versions are simply improvements to the patcher that make it work with newer versions of updates/office versions, etc.

Its strange you cannot download those files from dropbox…it must be some sort of network issue or perhaps a content filter (I just tested the links again and they work).

I’ll send both to you.

Nate

[dead2sin]

Interesting. I could of sworn I did it from pre-installed software. Either way, Composer is up to the task.

Nate

[dead2sin]

[QUOTE][u]Quote by: bango[/u][p]hi
i would like to use a loginhook that runs when the local admin logs in the first time (after the image has been deployed). the reason why i would want to use a loginhook is because in the .sh script i have has a line to call oascript (applescipt) to prompt the tech to assign a computer name, before the machine is bound to AD. if i use this .sh file as a firstboot script it fails to prompt the tech to assign a computer name because in the Console log is says that “untrusted apps are not allowed to connect to or launch windows server before login”.
my question is – how do i go about setting up this loginhook (that only runs once). i understand i need to put it in the loginwindow.plist – with the key called LoginHook. i just dont know how i would implement this in the image build process?
i dont want to place the .sh file somewhere on the image or or have run it from a network share – stopping the tech from viewing the “code”
any ideas would be great.
thanks[/p][/QUOTE]

Just curious, what are you deploying your images with?

Nate

[dead2sin]

[QUOTE][u]Quote by: dknisely[/u][p]I think I must be an idiot, but I can’t seem to get the patcher to do anything. Is it supposed to work on the “Communicator13.1_ALL.dmg” file? I still get the same error when I try to run the updated version. Am I supposed to drop the dmg file on the patcher or the extracted mpkg file? Neither has any effect.

Any help would be appreciated as the repeated requests by Microsoft Office Autoupdater are very annoying and it appears there are new features in 13.1.[/p][/QUOTE]

For Communicator, you’ll want the Office Update Patcher: [url]http://dl.dropbox.com/u/11466/InstaDMG%20PatchOfficeUpdate%200.4.dmg[/url]

The Update patcher will patch 2008, 2011 and Communicator updates.

The Office 2011 Installer patcher is strictly for the Office 2011 installer.

Basically, you need to drag the .pkg/.mpkg to your desktop or any other folder that isn’t a read-only DMG. Then, drop the .mpkg on the patcher and it will make the changes necessary for it to work with InstaDMG.

If you mount the .dmg from Microsoft and try to just drag the .mpkg onto the patcher directly, it won’t do anything because the .dmg is read only.

Let me know if you run into any other issues.

Nate

[dead2sin]

[QUOTE][u]Quote by: Turtle[/u][p]Does anyone have personal experience creating a Tiger 10.4.x Golden Master image via InstaDMG? If so, please are you willing to give any advice. Are there any PowerPC vs Intel issues that one should be careful of? Is the best course two DMGs, one for PPC and one for Intel?

If you are willing to share a Catalog File for InstaUp2Date, for Tiger, with updates, that would be wonderful.

I’ve been using NetInstall and Deploy Studio, but I’m a newbe for instaDMG, and feel a bit lost. And I need to jump in quickly and come up with a working Tiger GM.

Thanks in advanced for any help.[/p][/QUOTE]

I’m honestly not sure InstaDMG will do 10.4. I know its been tested and supported for 10.5 and 10.6, but I’ve never touched it for 10.4. If you want to mess with it and hope it works, you could easily make your own 10.4_vanilla catalog by just installing to a base system, running system update and writing down which updates it asks for. Then, go to support.apple.com/updates and get the sha1 hashes and download links and dump them in a 10.4_vanilla catalog.

Not sure it’ll work, but if you want to try it, you could 🙂

Nate

[dead2sin]

Nope. You must have iLife 2011 installed before it will show up in pre-installed software. You can’t package something using diffs thats not installed yet.

Nate

[dead2sin]

I repacked iLife ’11 using the Composer Pre-installed software preset and it worked great. I know not everyone has Composer, but I wanted to throw it out there that it handles it out of the box, as well as CS5.

Nate

[dead2sin]

[QUOTE][u]Quote by: tristan_mason[/u][p]Hi Nate

I am indeed. Somewhere in the scheme of things I missed this whole step when I started this whole instaDMG thing so i’m coming at this having done most everything else. DERP! Anyhow do I just put the xml file in the folder and run the workflow as normal or do I have to run the xml from the terminal and then run the workflow?

Cheers

Tristan[/p][/QUOTE]

What you do for installerchoices is place it in any folder within InstallerFiles and then run ./checksum.py on it. It’ll spit out the full path to the InstallerChoices file as well as a checksum. You include this on the vanilla catalog using this format:

[code]Installer Choices File: tab [/code]

Note its only the full path to XML + Checksum, rather then description, path and checksum.

Then, once you run your instaup2date build, it’ll use this installer choices.

Nate

[dead2sin]

Are you running it as sudo?

Nate

[Author]

Posts