Software Deployment

If you turn on verbose logging and push it via GPO, you should have more data to work with in troubleshooting your issue. Are you assigning the MST in the GPO, and/or did you specify it when creating your adminstrative installation?

Many thanks for your reply. I am specifying my MST file through the GPO. I didn't actually see an option to do it during the install, unless you can specify a transform on the command line when initiating the Admin install . . . in any case, I'd rather specify it in the GPO anyway.

I will try switching on Verbose logging and see what comes out, thanks. I will post the results.

Thanks again,

Simon

If you are upgrading from a previous version of Office, you may be migrating the previous installation state. When you do that, if the feature wasn't installed in the previous version, the 2003 version won't install either no matter what you specify.

In the Office 2003 Custom Installation Wizard, page 7 (Set Feature Installation States), look at the properties section in the upper right corner for the "Do Not Migrate Previous Installation State" check box. Note that these properties are not general properties, they are for what is highlighted in the tree on the left. If you want to install what you specified in the tree to the left no matter what was previously installed in older Office versions, then highlight the root of the tree, check "Do Not Migrate Previous Installation State" and click the Apply To Branch button.

Hope that helps!

Absolutely Spot On !!

That seems to have done the trick ! I'm about to try on a clean unattended install just to make sure, but I think that's done it. I remember seeing the option, but I never even gave it a second thought.
It actually makes perfect sense, as it was just upgrading the Office 97 installation, which I only used to install Access 97. It didn't upgrade Access because I told it not to install the new version, and it installed InfoPath and Publisher because they were never included as part of the original Office 97 package ! I can't beleive it wa so simple . . .after days of trying to work it out [:)]

I love it when a plan comes together !!

Thank you, thank you, and . . . ummmm . . .thank you !!

Simon

We had a similar issue with the same resolution:

We installed

-Office 2003 with Word, Excel and PowerPoint
-Added a package containing publisher and the shortcut and exe would not appear, but the file structure would.

In that scenario, we had to turn off Migration on both the base office package and the separate publisher install.

Nice one VikingLoki....why don't you submit this on the Tips page. I think alot of the users will find this tip very helpful as Office 2003 is becoming the "next must have" rollout most companies are going into.

You can do it here.

http://www.appdeploy.com/tips/submit.asp

That was upsetting me with my FrontPage 2002. Thanks for the FIX VikingLoki. Worked perfectly.

Matt