No word on a packager, I have been told advancedinstaller is pretty decent.
For a GP deployment. Create an MST file, by using the Office 2003 ORK Kit with all your preferences. GPO, Link your created GPO to computers or users and point to a distribution point for the 2003Std or 2003pro MSI file and use the transform advanced section to point to the created mst. You can also just script the install by running the msi file and adding an argument to run the msi file. setup.exe TRANSFORMS="\\uncpath\transformname.MST" /qb- **Hint** Don't forget to add the Outlook Address Book in the additional addons. Otherwise no user contact folders... Greg -----Original Message----- From: Kurt Buff [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 12, 2008 7:56 PM To: NT System Admin Issues Subject: MSI packagers? I note a discussion from March of last year about MSI packagers, but want to revisit the issue. We had a fellow (who no longer works here, though not because of this issue) using the WinInstall LE package try to build an MSI for MSOffice 2003, and it was a miserable failure on the one desktop in production he tried it on - the Controller's PC. Ouch. And it took him a couple of weeks, if not longer, to actually produce this package. Double ouch. Now my IT Director is a bit gun-shy on my asking to get one of my juniors involved in building an MSI package for MSOffice 2003 - he's afraid that it will take forever and not work well. I'm fairly certain it can't be *that* hard, if the proper tools are used. Can anyone point me in a good direction for the proper software and decent directions on how to do this? Bonus points if it includes directions on how to deploy via GPO, but I'll take a file that the end-user can click on and have it install. Kurt ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
