- This topic has 7 replies, 4 voices, and was last updated 14 years, 5 months ago by
purpanther.
-
AuthorPosts
-
October 28, 2010 at 4:12 pm #379720
purpanther
ParticipantHey folks, been a lurker here for a long time 😀
I watched the recent Mac sys admin videos on InstaDMG and was fired up to go and try the current system with instaup2date. I think it’s fantastic and I am on board with the idea!
I have my vanilla build working, and a 6.4 build with my custom user packages, config packages, etc. working.
When I add iLife ’09 to the mix, it installs on the local machine and not the DMG except for iconless placeholders in the Applications folder. When I add iWork to the build I see iWork 09 in the Applications folder but it cannot launch. the local machine gets all of the actual install files.
For Office 2011 I had to change the licensing files to add “$3” before /Library…etc.etc… Is there something like that necessary for iWork and iLife ’09?
Thanks in advance!
Sable
October 28, 2010 at 10:14 pm #379722tristan_mason
ParticipantHi There
I just copied the iLife pkg from the DVD (actually i had made a dmg of the install DVD and copied it from that but same diff), generated a checksum and dropped it into my catalogue file, popped the pkg in the instaUp2DatePackages folder, put the updates after it and presto…
Regards
Tristan
October 28, 2010 at 10:27 pm #379723purpanther
ParticipantThat’s exactly what I did in both cases too.
October 28, 2010 at 10:33 pm #379724Allister Banks
ParticipantHey purpanther,
I posted a package to ‘fix’ iWork, but that’s for after it successfully installs – it sounds like your svn checkout may be borked. I can run a test this weekend, but you shouldn’t have to modify anything, including Office 2011 AFAIK. Please post the relevant parts of your debug log, and which svn version of both instaUp2Date and InstaDMG you have.
That iWork fixer pkg:
https://www.afp548.com/filemgmt/index.php?id=107Let us know when you get a chance,
Allister
October 29, 2010 at 12:07 am #379725dead2sin
ParticipantOffice 2011 requires you to change the postflight script on the licensing package for it to be licensed properly.
iLife 09 I can confirm works perfectly as is without modificaiton. I believe I use a .dmg copy of the iLife 09 installer disc. I’ve never messed with iWork, but it sounds like Allister has you covered on that. Make sure you update to latest SVN, then report back your findings and maybe we can figure out what is causing the issues.
Nate
October 29, 2010 at 11:29 am #379728dead2sin
ParticipantI was mistaken about iLife 09. I just grabbed the 4.74gb iLife ’09.mpkg from the DVD and put that into InstaDMG without modification.
Nate
October 29, 2010 at 6:50 pm #379730purpanther
Participant[QUOTE][u]Quote by: Allister[/u][p]Hey purpanther,
I posted a package to ‘fix’ iWork, but that’s for after it successfully installs – it sounds like your svn checkout may be borked. I can run a test this weekend, but you shouldn’t have to modify anything, including Office 2011 AFAIK. Please post the relevant parts of your debug log, and which svn version of both instaUp2Date and InstaDMG you have.
That iWork fixer pkg:
https://www.afp548.com/filemgmt/index.php?id=107Let us know when you get a chance,
Allister[/p][/QUOTE]
Thanks. I’ll give this a shot. I had to modify the office 2011 files in order for my site license to install correctly. I have the 10/11 svn version on the machine, 387 I think. If it fails with the fixit package I will post the logs.
Sable
October 29, 2010 at 6:51 pm #379731purpanther
Participant[QUOTE][u]Quote by: dead2sin[/u][p]I was mistaken about iLife 09. I just grabbed the 4.74gb iLife ’09.mpkg from the DVD and put that into InstaDMG without modification.
Nate[/p][/QUOTE]
I’ll try popping in the AELP dvd and dragging the mpkg off of the disk. I’m sure that’s how I got the file in the first place but I don’t mind trying again. I will report back.
Thanks for your help.
[EDIT] This worked this time. The checksum for the fresh copy from dvd was different than before .. hrmmm….
Sable
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed