[dead2sin]

I setup a machine with 10.5.8 to mess with it. I’ll let you know what I find out.

Nate

[dead2sin]

Just as a side note, I would use the SP2 install media that you have rather then 12.1.0. the SP2 install media worked much better for me then the 12.0.0 version. I know it won’t fix this specific issue, but I’d avoid using old install media.

Also, just to be sure, you are building a 10.5 image using a 10.5 machine, correct? I know 10.5 Builds use chroot jails and the 10.6 builds do not, so that is most likely the difference in behavior that you are seeing.

I wonder if anyone else with 10.5 can confirm this.

Nate

[dead2sin]

[QUOTE][u]Quote by: Brigandy[/u][p][QUOTE][u]Quote by: dead2sin[/u][p][QUOTE][u]Quote by: Brigandy[/u][p]I am running Instaup2date r353 from a Mac Pro (OS: Mac OS X 10.5.8) and am trying to create a 10.5.8 image.

I am able to install “Office 2008 for Mac v12.0.0 (AKA: Office Installer.mkpg) with no problems.

Note: I am using a volume license version of “Office 2008 for Mac v12.0.0”.

The problem is:

I am unable to install “Office 2008 for Mac” [u]updates[/u]. When I try to install updates I receive the following error in my debug log:

[b]” The install failed (The following install step failed: run preflight script for Quit Microsoft Applications. Contact the software manufacturer for assistance.)”[/b]

I have successfully used Mosen’s patch (to patch my “Office 2008 for Mac” updates), but I still receive the error (above).

Note:The Mosen patch can be found at the following location: https://www.afp548.com/forum/viewtopic.php?forum=45&showtopic=26882

What am I doing wrong?

PS:
I have also tried the latest volume license version of “Office 2008 for Mac v12.2.x”. Updates just do not work. I keep getting the error outlined in bold (above).[/p][/QUOTE]

Try using this for the Office updates:

[url]https://www.afp548.com/filemgmt/index.php?id=84&comments=1[/url]

I use that on all mine before putting them in InstaDMG and they work great.

Nate[/p][/QUOTE]

Nate:

That is what i’m using. I’m using the patch in the Office 2008 tutorial link (above). I guess I shouldn’t of referred to Mosen. I should of called it the dead2sin patch. This patch that you referred me to does not work. I’ve tried using the following updates: 12.1.0 12.2.0, etc…all the way up to 12.2.6. The patch does patch the update (I have verified this) but the end result is the following error occurs when it goes to install ANY Office 2008 update:

” The install failed (The following install step failed: run preflight script for Quit Microsoft Applications. Contact the software manufacturer for assistance.)”
[/p][/QUOTE]

No, it is Mosen’s patch, you were correct 🙂 I just missed that part. That guide is mainly for 10.6 (I didn’t test it on 10.5), so perhaps there is a difference. If I get some time, I might go back and test it out on 10.5.

Nate

[dead2sin]

[QUOTE][u]Quote by: Brigandy[/u][p]I am running Instaup2date r353 from a Mac Pro (OS: Mac OS X 10.5.8) and am trying to create a 10.5.8 image.

I am able to install “Office 2008 for Mac v12.0.0 (AKA: Office Installer.mkpg) with no problems.

Note: I am using a volume license version of “Office 2008 for Mac v12.0.0”.

The problem is:

I am unable to install “Office 2008 for Mac” [u]updates[/u]. When I try to install updates I receive the following error in my debug log:

[b]” The install failed (The following install step failed: run preflight script for Quit Microsoft Applications. Contact the software manufacturer for assistance.)”[/b]

I have successfully used Mosen’s patch (to patch my “Office 2008 for Mac” updates), but I still receive the error (above).

Note:The Mosen patch can be found at the following location: https://www.afp548.com/forum/viewtopic.php?forum=45&showtopic=26882

What am I doing wrong?

PS:
I have also tried the latest volume license version of “Office 2008 for Mac v12.2.x”. Updates just do not work. I keep getting the error outlined in bold (above).[/p][/QUOTE]

Try using this for the Office updates:

[url]https://www.afp548.com/filemgmt/index.php?id=84&comments=1[/url]

I use that on all mine before putting them in InstaDMG and they work great.

Nate

[dead2sin]

[QUOTE][u]Quote by: imonkey[/u][p]Thanks Nate, should have looked there first.[/p][/QUOTE]

No worries, I constantly forget it is there.

Nate

[dead2sin]

[QUOTE][u]Quote by: imonkey[/u][p]Hi All,
Is there a full listing of all InstaDMG switches? I was trying to specify the location of the base image [which I found from these forums was -I]. The latest manual I have InstalDMG Guide 1-6 doesn’t list it and he previous guide lists -I as specifying the log folder.

Any help appreciated.

[/p][/QUOTE]

In the InstaDMG folder I believe there is a readme that contains them all iirc. You can also do ./instadmg –help and it should list them.

Nate

[dead2sin]

[QUOTE][u]Quote by: Brigandy[/u][p]Hi Guys,

I am installing Microsoft Office 2008 and receiving the following error:

Working on folder 2 Microsoft Office 2008 for Mac (14:32:57)
Copying folder /Volumes/Mac/instadmg/InstallerFiles/InstaUp2DatePackages/Office Installer.mpkg into the target at /private/tmp/mount_point.1otqIy/private/tmp/package.F5LDm1
Installing Office Installer.mpkg inside a chroot jail
PFPkg: No file found at path: /private/tmp/package.F5LDm1/Office Installer.mpkg
PFPackage::packageWithURL – can’t instantiate package: /private/tmp/package.F5LDm1/Office Installer.mpkg
Error the package path specified was invalid: ‘/private/tmp/package.F5LDm1/Office Installer.mpkg’.
Removing the copied folder: /private/tmp/mount_point.1otqIy/private/tmp/package.F5LDm1
Folder 2 Microsoft Office 2008 for Mac done (14:34:23)

I have mounted the Microsoft Office 2008 ISO and dragged “Office Installer.mpkg” to the “InstaUp2DatePackages” directory.

This is the original Microsoft Office 2008 (with no Service Packs included). This is a volume license version of Microsoft Office 2008 (from Microsoft’s MSDN site).

What usually causes this error? I just want to get Microsoft Office 2008 installed. I’ll deal with the “Microsoft Office 2008 Service Packs and Updates” later.

NOTE: MANY OTHER PACKAGES INSTALL FROM THE “InstaUp2DatePackages” DIRECTORY. I’M JUST HAVING PROBLEMS INSTALLING MICROSOFT OFFICE 2008. I AM RUNNING INSTADMG FROM A MAC OS X 10.5.8 MACHINE AND AM TRYING TO CREATE A 10.5.8 IMAGE.[/p][/QUOTE]

I would highly suggest getting the SP2 media from MSDN. It seems to work a lot better with InstaDMG for me.

Nate

[dead2sin]

[QUOTE][u]Quote by: Brigandy[/u][p]I have InstaDMG (rev 339) and I noticed the “10.5_vanilla.catalog” file has the folowing:

Mac OS X 10.5.8 Combo Update
QuickTime 7.6.6 for Leopard
AirPort Utility 5.3.2 Leopard
AirPort Utility Software Update 5.4.2
AirPort Base Station Update 2010-001 5.5.1
Security Update 2010-004
Front Row Update 2.1.7
Java For MacOS X 10.5 Update 5
Remote Desktop Client 3.3.2
Java For MacOS X 10.5 Update 7
Security Update 2010-005

My question is this:

Why do we need the “Security Update 2010-004” if the “Security Update 2010-005” supercedes it?

BTW: I have found that if I remove the “Security Update 2010-004” and only install the “Security Update 2010-005”, “Software Update” is fine with it.

Why do we have both of these entries? Is there a reason for it?[/p][/QUOTE]

No, it is probably just something that got overlooked. You should be fine to just do the 005 one and leave out the 004 one, especially since SWU doesn’t prompt for it. Typically the security updates are cumulative.

Nate

[dead2sin]

[QUOTE][u]Quote by: bosemachine[/u][p]Good to know! Luckily we deal with predominantly HP printers here so it’s relatively harmless…relatively.

Anyway, I did in fact get it to work thanks to dead2sin’s help…the only thing that kept screwing me up was setting the actual “duplex” option. For reasons that are beyond me, ‘lpoptions -l’ listed the duplexer line as “HPOptions_Duplexer/Duplex Unit: True *False” so I assumed I’d be using [code]lpoptions -p “PrinterX” -o “HPOptions_Duplexer/Duplex Unit”=true[/code]

but for whatever reason, I wasn’t getting the change the show up in lpoptions -l.

After some looking around at the actual PPD file, I found that the actual duplex option was “HPOption_Duplexer”.

So problem solved thanks to you guys! :)[/p][/QUOTE]

No problem! I’m glad you got it all running smoothly. Don’t forget to check out ##osx-server on irc.freenode.net (Some work, some play, great bunch of guys).

Nate

[dead2sin]

[QUOTE][u]Quote by: bosemachine[/u][p]I know Workgroup Manager allows you to pass printing info to other machines but for whatever reason, it doesn’t install the necessary drivers (uses Generic Drivers) which is fine for most but not for some of the administrative types who want their fancy ‘duplex’ and what not ;).

Anyway, so I tried using Composer to snapshot the process from beginning to end of installing drivers and setting up printers on a local account, cleaned it up and copied User Library stuff to the User Template and finally wrapped it all into a nice package. However, install this package on a machine dumps the files there but the printer list doesn’t populate and none of the programs can see the printers.

Does anyone know either A) how to get WGM to pass actual printer drivers or B) what i have to do to get the printer list to populate with the packaged printers?

Thanks!
B[/p][/QUOTE]

I handle this problem by installing the required drivers in my InstaDMG workflow and then setting up the actual printer by using a firstboot script with an lpadmin command to actually setup the printer such as this:

[code]lpadmin -p “Printer Name” -L “Printer Location” -D “Printer Description” -E -v lpd://server/printqueue -P $genericppd -o printer-is-shared=false[/code]

This way, I get a clean print driver install as well as a clean printer setup. Another method I’ve started using is installing printers using Munki. You make a package that delivers a command to setup the printer as well as an uninstall.sh script for each printer. You then set the print driver for that printer as a prerequisite so it installs before the setup command is run.

I find that both these methods work exceedingly well.

Nate

[dead2sin]

[QUOTE][u]Quote by: nobrainer[/u][p]Yeah, I saw the perl script, fought with it for about 2 weeks before I realized the encrypted PW was being sent as clear text (first 8 characters of the output of that file) rather than converting back to the actual PW.
wasn’t sure if I tried a different encryption method if it would work…
[/p][/QUOTE]

Now when you say VNC, are you using the compatibility mode VNC so non-Macs can connect to the screen, or will it be mac to mac, just no ARD?

Nate

[dead2sin]

[QUOTE][u]Quote by: Nihilator[/u][p]To Larkost:

Why are you “deliberately” ignoring this problem with Mac OS X 10.5.x?

Problem: No outputfile.

Error: ###### There were no items to install in: /private/tmp/InstaDMG_temp_folder.agg2Vy/mount_point.CFjHDl/private/tmp/mount_point.oXxnM4 ######

Solution:

Comment out lines 573-575

Insert the following on line 576: HOST_MOUNT_FOLDER=”/tmp”

FIX IT IN YOUR NEXT RELEASE “LARKOST”. FIX YOUR “$MOUNT_FOLDER_TEMPLATE”![/p][/QUOTE]

From what I gather his main focus is 10.6. Honestly, if you want something that works epically well with 10.5, use an older version of InstaDMG. Also, Larkost does this for free. He doesn’t get paid…so try to show a little more patience and respect for his work. He has a regular job just like all of us.

Nate

[dead2sin]

[QUOTE][u]Quote by: nobrainer[/u][p][QUOTE][u]Quote by: dead2sin[/u][p][QUOTE][u]Quote by: nobrainer[/u][p]Okay, so I followed precisely the instructions ([url]http://www.osxdeployment.info/wiki/InstaUp2Date_Guide[/url]) (and created the 3 catalog files), and I don’t think the firstboot ran. It didn’t enable the remote desktop (ARD / VNC), time server wasn’t set (because we ship all over, I left the timezone out), IPV6 is still enabled, etc.

I added it to instadmg, which said the pkg was loaded successfully, and there was no errors in the build logs or anything that I could tell…

What am I missing? I’m so close I can taste it! Oh wait… that was leftover from lunch.

[/p][/QUOTE]

Check your system.log for errors. If any of the commands didn’t work, many times you can find a hint of what went wrong there. It sounds to me like the firstboot files didn’t get put there at all, or perhaps the permissions on the launchd item were incorrect and it didn’t run.

Nate[/p][/QUOTE]

Permissions? I didn’t change any, I set the scripts to +x but didn’t change anything else…

I looked through any log I thought might have something to do with it, and all I could find was was that the pkg was installed… nothing (successful or unsuccessful) about actually running the firstboot or scripts or anything. I did find the time server was off, but that was supposed to be taken care of via the script….
[/p][/QUOTE]

Permissions are set per item within packagemaker. You can decide what permissions the file will have once they are delivered. It looks like I might of messed up the permissions on the launchd item itself (com.company.firstboot.plist). In PackageMaker, under Contents, try changing the permissions for the item to owner Root group Wheel and make sure it has RW, R, R permissions at the bottom (Read, Write for owner, Read for Groups and Read for Others.).

I’ll fix it and repost a fixed version in a bit, but go ahead and try that and see if it helps. As far as system.log is concerned, once you’ve applied the image, it should show on the system you’ve deployed it to in the system.log file if it did run or if there was an error that prevented it from running.

Nate

[dead2sin]

[QUOTE][u]Quote by: nobrainer[/u][p]Okay, so I followed precisely the instructions ([url]http://www.osxdeployment.info/wiki/InstaUp2Date_Guide[/url]) (and created the 3 catalog files), and I don’t think the firstboot ran. It didn’t enable the remote desktop (ARD / VNC), time server wasn’t set (because we ship all over, I left the timezone out), IPV6 is still enabled, etc.

I added it to instadmg, which said the pkg was loaded successfully, and there was no errors in the build logs or anything that I could tell…

What am I missing? I’m so close I can taste it! Oh wait… that was leftover from lunch.

[/p][/QUOTE]

Check your system.log for errors. If any of the commands didn’t work, many times you can find a hint of what went wrong there. It sounds to me like the firstboot files didn’t get put there at all, or perhaps the permissions on the launchd item were incorrect and it didn’t run.

Nate

[dead2sin]

[QUOTE][u]Quote by: golbiga[/u][p]Thanks! I thought I was going crazy for a minute there. Is it recommended to use the newest hardware anyways? I’m waiting on a new iMac so it shouldn’t be a problem soon enough. Thanks again.[/p][/QUOTE]

You can build the image on any machine really. For Snow Leopard Images, the only things you need to keep in mind are that the build box #1 is Running Snow Leopard (I tend to keep it as up to date as possible) and of course #2 it has to be intel, which is really a requirement of Snow Leopard.

Nate

[Author]

Posts