Hi all,

Just a quick query. I'm working up .mst's for an upcoming deployment of XP/Office 2003 to our org (our management is very slow to agree to updates [:@] ) and I've hit a bit of a stop.

We don't want to deploy Publisher/Access in the initial roll out of O2k3, rather have them available as tier 2 apps available on demand.

The idea that creating a new transform that included the components and then rolling over the existing install, predictably, failed to make a difference.

I've considered using GPO's, perhaps creating the additional components as a .msp file etc. I'm sure I'm overlooking something dreadfully obvious but the ORK and various web sources information on this type of deployment seem woefully inadequate (or just well hidden beyond my ability to find).

Any help would be appreciated,
Cheers,
G

edit: /facepalm, should have looked up the KB first...


"I first packaged Word, Excel, Outlook and PowerPoint with an MST and put Access, InfoPath and Publisher on 'not installed' (I also moved the shortcuts to another location in the start menu and deleted the shortcuts which I didn't need).

After that I needed another MST to add only Access. With ADDLOCAL=ACCESSFiles, that wasn't a problem, but I had no shortcut in my start menu. I found out that I shouldn't have deleted the shortcuts in my first MST, so I had to rebuild that. After that, all worked fine!"


I'll follow up this but if anyone still has some wisdom to offer ; )
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
You may be able to use the ADDLOCAL=<feature> command line along with the existing transform. I have never tried it but ADDLOCAL by itself will install only certain features like word, access, excel etc. Use the REMOVE=<feature> to uninstall a feature.

Here is a quick blurb about it. Scroll down a bit to see it. http://service1.symantec.com/SUPPORT/ent-security.nsf/0/daec50033554fec188256fda00651cf4?OpenDocument
Answered 02/20/2007 by: yarborg
Blue Belt

Please log in to comment
0
Cheers for the extra info, I'm test toasting the command line and will post what I find.

Edit: Can confirm that the command works well. Examples are for Office 2003 SP2 on Win XP SP2. /qb- switch was used for testing.

For example, assume you have a default.mst which has Access and Publisher selected as Not Installed.

\\installation path\SETUP.EXE TRANSFORMS=\\installation path\default.mst /qb- ADDLOCAL=ACCESSFiles

This will add Access to the PC without altering any of the current installed components. Note that it adds the sub components of Access in the default manner specified in the Pro11.msi ie. some components will be "Install on first run", "Not Installed" etc.

If you want to add Publisher and keep Access:

\\installation path\SETUP.EXE TRANSFORMS=\\installation path\default.mst /qb- ADDLOCAL=PubPrimary

The information for features can be pulled from the MSI's database using Wise or something similar.

To remove a component, use:

\\installation path\SETUP.EXE TRANSFORMS=\\installation path\default.mst /qb- REMOVE=PubPrimary

This will remove Publisher but not affect Access.

Finally, running a detect and repair will not remove extra components added by the "ADDLOCAL" command line. It seems to consider them part of the package until explicitly defined for removal. I have yet to test if the command line would override the "Hidden and not available" option when defining the original transform but I suspect it would not.

Anyhoo, hope this helps =)

Edit: Err, last edit, I can confirm that the command line will add an icon to the start menu under the "\Start Menu\Programs\Microsoft Office" folder, but not to the Desktop. I can't see a way to get the command line to add an icon but I'm not really fussed about it, the start menu is fine.
Answered 02/20/2007 by: Asmo
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity