Not sure about the reason (forgot) but MS no longer suggests to pre-patch the admin install point. I think the explanation is on the ORK page that details how to do the GPO deployment.
As an additional vote, *do not* rebuild that MSI, I am not surprised that didn't yield good results :) You surely can do all you need in a simpler supported fashion. jlc -----Original Message----- From: Ben Scott [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 12, 2008 7:31 PM To: NT System Admin Issues Subject: Re: MSI packagers? On Feb 12, 2008 7:56 PM, Kurt Buff <[EMAIL PROTECTED]> wrote: > ... try to build an MSI for MSOffice 2003 ... Do you have a Volume License for Microsoft Office 2003? As I recall, you can only do a supported automated deployment of MS Office 2003 using Volume License Media. (Somebody correct me if you know otherwise.) So we went that route. According to my notes... I did an "administrative install" of Office, by running "SETUP.EXE /a" and pointing it to a network folder. I used a UNC path to a DFS share to make the path name as portable and resilient as possible. I used the "Office Resource Kit"(ORK) (free download) to create an MST (transform) with our desired configuration and customization. I put the MST on the same share. Then it was just a matter of using a GPO to deploy the MSI created in the administrative install, modified by the MST. There was some more junk in-between, that involved pre-patching the admin install to include Service Pack 2, but that's the gist of it. -- Ben ~ 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> ~
