If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Office 2003, Custom Installation Wizard, MST
I am attempting to use the Custom Installation Wizard that came with
the Office 2003 Resource Kit, to create an .MST file which ONLY installs Publisher 2003 and none of the other Office 2003 components. So far this does not seem to be possible. I have created the .MST, and selected 'Do not install' for all items except Publisher 2003, and yet when I run setup and apply the .MST file Excel, Word, Powerpoint and Access are all installed. The command line I am using at the client to install Office with the transform is: [path to install point]\setup.exe TRANSFORMS=[path to .MST]\[name of transform] /qb- The install runs, but when it's finished I have a number of applications that I specifically told the MST NOT to install including Word, Excel, Powerpoint and Access. I have created a number of MST files to be sure that the file wasn't corrupted. The client that I am attempting to install on is running Windows XP SP2 and an existing copy of Office 2000 Standard. Has anyone had any success deploying selected components of Office 2003 Professional with an MST from a network distribution point? Thanks, Troy. |
#2
|
|||
|
|||
Office 2003, Custom Installation Wizard, MST
On Screen 6, what do you have as the behavior for each of those apps?
If the client already has office apps installed, then you will need to set it to remove them in the MST. And screen 7 has them all "Do not install" except for Publisher? "Troy F." wrote in message oups.com... I am attempting to use the Custom Installation Wizard that came with the Office 2003 Resource Kit, to create an .MST file which ONLY installs Publisher 2003 and none of the other Office 2003 components. So far this does not seem to be possible. I have created the .MST, and selected 'Do not install' for all items except Publisher 2003, and yet when I run setup and apply the .MST file Excel, Word, Powerpoint and Access are all installed. The command line I am using at the client to install Office with the transform is: [path to install point]\setup.exe TRANSFORMS=[path to .MST]\[name of transform] /qb- The install runs, but when it's finished I have a number of applications that I specifically told the MST NOT to install including Word, Excel, Powerpoint and Access. I have created a number of MST files to be sure that the file wasn't corrupted. The client that I am attempting to install on is running Windows XP SP2 and an existing copy of Office 2000 Standard. Has anyone had any success deploying selected components of Office 2003 Professional with an MST from a network distribution point? Thanks, Troy. |
#3
|
|||
|
|||
Office 2003, Custom Installation Wizard, MST
Tom,
Thanks for taking the time to reply. A little more information for you. On Screen 6 (Remove Previous Versions) I have tried both the Default Setup behaviour, and I have also have gone through all apps and unchecked them so that they are NOT removed. I want to leave any existing Office applications installed, I am just running this particular install to add Publisher 2003. You see, I've got some users who are using Office XP, and as you probably know XP didn't come with a Publisher package so I'm just wanting to supplement their install of Office XP Pro, with only the Publisher 2003 component (and perhaps the Office Shared Features, and Office Tools) from the Office 2003 Pro. install. As far as screen 7 (Set Feature Installation States), you are correct I have set everything except Publisher, Office Shared Features and Office Tools to 'Not Available'. Interestingly if I apply this install and transform to a computer without any office apps already installed it works as expected, and only installs Publisher. But if I install it on a machine with existing apps as I am going to want to do in production, it seems to ignore my 'Not Available' settings in the MST and rather installs the 2003 versions of any existing Office components. I've seen other posts from people about this problem, but no solutions yet. Any ideas? Thanks, Troy. |
#4
|
|||
|
|||
Office 2003, Custom Installation Wizard, MST
That is weird. I have a similar job to upgrade Outlook XP to Outlook 2003,
and it works fine. Have you tried using a Custom Maintenance Wizard job? Set everything to "Leave Unchanged" except Publisher, which would be set to install? "Troy F." wrote in message oups.com... Tom, Thanks for taking the time to reply. A little more information for you. On Screen 6 (Remove Previous Versions) I have tried both the Default Setup behaviour, and I have also have gone through all apps and unchecked them so that they are NOT removed. I want to leave any existing Office applications installed, I am just running this particular install to add Publisher 2003. You see, I've got some users who are using Office XP, and as you probably know XP didn't come with a Publisher package so I'm just wanting to supplement their install of Office XP Pro, with only the Publisher 2003 component (and perhaps the Office Shared Features, and Office Tools) from the Office 2003 Pro. install. As far as screen 7 (Set Feature Installation States), you are correct I have set everything except Publisher, Office Shared Features and Office Tools to 'Not Available'. Interestingly if I apply this install and transform to a computer without any office apps already installed it works as expected, and only installs Publisher. But if I install it on a machine with existing apps as I am going to want to do in production, it seems to ignore my 'Not Available' settings in the MST and rather installs the 2003 versions of any existing Office components. I've seen other posts from people about this problem, but no solutions yet. Any ideas? Thanks, Troy. |
#5
|
|||
|
|||
Office 2003, Custom Installation Wizard, MST
Tom,
I haven't tried the Custom Maintenance Wizard, but from looking at it, it would seem that it would defeat the purpose of me deploying the install through Group Policy because I would then need to visit the stations to run the Maintenance file. I think I might contact Microsoft directly and have them explain to me why the .MST file is being ignored. If I get anywhere, I will certainly post an answer to this thread for others. Thanks for your time, Troy. |
#6
|
|||
|
|||
Office 2003, Custom Installation Wizard, MST
Update: Microsoft wants $350.00 to troubleshoot the problem which seems
rather like extortion to me. In any case, after paying for the Office licenses and associated Software Assurance, there is no way I'll be spending an additional $350.00 to troubleshoot the issue. If I ever find the solution on my own I will post it here so that others don't get suckered for a $350.00 charge. Troy. "Troy F." wrote: Tom, I haven't tried the Custom Maintenance Wizard, but from looking at it, it would seem that it would defeat the purpose of me deploying the install through Group Policy because I would then need to visit the stations to run the Maintenance file. I think I might contact Microsoft directly and have them explain to me why the .MST file is being ignored. If I get anywhere, I will certainly post an answer to this thread for others. Thanks for your time, Troy. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Problems with Office 2003 Deployment and Custom Installation | linked2you | Setup, Installing & Configuration | 2 | June 1st, 2005 11:43 PM |
Office 2003 Custom Installation Wizard | Ryan | Installation & Setup | 4 | January 19th, 2005 05:19 AM |
Four KBs to address problems epidemic, ubiquitous and replete | Rick | General Discussions | 1 | August 19th, 2004 05:14 AM |
Office 2003 / Office XP Shortcut Bar | Marc Bressman | General Discussions | 6 | June 26th, 2004 08:42 AM |
Office 2003 custom installation wizard | James T | Setup, Installing & Configuration | 0 | June 3rd, 2004 06:13 PM |