Office 2003: Custom Installation Wizard Settings Will Not Apply

I have a couple of Windows server 2003 Service Pack 2, Terminal
Services servers that I using the Office 2003 Resource Kit's Custom
Installation Wizard tool to customize an Admin Install. When choosing
Office components, I click on Publisher, InfoPath and SharePoint and
select "Not Available, Locked, Hidden."
After I run the installation, using the MST created by the CIW, all
three of those components are still fully installed and operational on
my server.
I ran the installation package in Terminal Services Install mode,
changed to Execute mode and rebooted the server afterwards. Anyone
have any ideas why the CIW didn't work?

Thanks.

Hi Robert,

You didn't mention Applications Server mode for Terminal Services
http://office.microsoft.com/en-us/or...402071033.aspx
and I'm assuming that Office 2003 was not previously installed?
Also check your Office CIW settings for Migration State
http://support.microsoft.com/kb/311241
What was the command line you used for running Office 2003 Setup with the MST?

==================
wrote in message ...
I have a couple of Windows server 2003 Service Pack 2, Terminal
Services servers that I using the Office 2003 Resource Kit's Custom
Installation Wizard tool to customize an Admin Install. When choosing
Office components, I click on Publisher, InfoPath and SharePoint and
select "Not Available, Locked, Hidden."
After I run the installation, using the MST created by the CIW, all
three of those components are still fully installed and operational on
my server.
I ran the installation package in Terminal Services Install mode,
changed to Execute mode and rebooted the server afterwards. Anyone
have any ideas why the CIW didn't work?

Thanks.
--

Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

On Feb 15, 9:59*pm, "Bob Buckland ?:-\)" 75214.226(At Beautiful
Downtown)compuserve.com wrote:
Hi Robert,

You didn't mention Applications Server mode for Terminal Services
*http://office.microsoft.com/en-us/or...402071033.aspx
and I'm assuming that Office 2003 was not previously installed?
Also check your Office CIW settings for Migration State
*http://support.microsoft.com/kb/311241
What was the command line you used for running Office 2003 Setup with the MST?

wrote in ...

I have a couple of Windows server 2003 Service Pack 2, Terminal
Services servers that I using the Office 2003 Resource Kit's Custom
Installation Wizard tool to customize an Admin Install. When choosing
Office components, I click on Publisher, InfoPath and SharePoint and
select "Not Available, Locked, Hidden."
After I run the installation, using the MST created by the CIW, all
three of those components are still fully installed and operational on
my server.
I ran the installation package in Terminal Services Install mode,
changed to Execute mode and rebooted the server afterwards. Anyone
have any ideas why the CIW didn't work?

Thanks.
--

Bob *Buckland *?:-)
MS Office System Products MVP

* *Courtesy is not expensive and can pay big dividends*

Hi Bob,

Thanks for looking at my post and replying. I may have missed some
details in my post, due to my frustrations in not being able to put
together a relatively simple package.
Yes, Terminal Services was installed in Applications Server mode -
these servers are going to be part of a Citrix 4.5 farm. Citrix 4.5
has also been installed. My machines are newly built Dell 1955 blade
servers. I followed KB311241 closely. This was a fresh install of
Office 2003. Again, I chose 'Not Installed, Locked and Hidden' for
the components I did not wish to install. I also chose 'Do not migrate
previous installation,' even though this was a squeaky clean
installation.
The command line I used to install the package was:

msiexec.exe /i "Z:\OFF11\pro11.msi" /t "Z:
\OFF11\CtxOfficeTrans.MST" /qb-

BTW, after this installation, if I run the Custom Maintenance Wizard,
I can un-install the components that I don't want. However, I would
prefer a clean server, hosting cleanly installed apps and no leftover
crumbs from un-installed applications.

Thanks again,

Bob W.