The "fellow" should have been taken out back and thwapped. Office 2003 is made to be installed by GPO, without repackaging. Never mind that you don't "test" a deployment using the Controller's computer...
http://office.microsoft.com/en-us/ork2003/HA011402011033.aspx should be pretty much all you need to learn. Get the Custom Installation Wizard and Custom Wizard from the Office Resource Kit and you're golden. On 2/12/08 4:56 PM, "Kurt Buff" <[EMAIL PROTECTED]> wrote: > 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 > ----- Salvador Manzo [ 620 W. 35th St - Los Angeles, CA 90089 e. [EMAIL PROTECTED] ] Auxiliary Services IT, Datacenter University of Southern California 818-612-5112 "Progress is made by lazy men looking for easier ways to do things." - Robert A. Heinlein ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
