Repost - Administrative installation problems (Programs missing)

[Jens-Peter Vraa Jensen]

Hi again. Nobody had any input on my last post, so I will try again...

We recently moved all clients from an older Win2000 DC to a new Win2003 DC.

From the old server Windows 2000 was rolled out using MSI+MST from a GP. No
problems here.

Office 2000 works fine on the new server, and I did start testing the
upgrade to Office 2003 Pro. I created the MST file and selected all program
as "Run from this computer" all other settings are (almost) left untouched.

The installation seemed to work fine, except some programs are missing:

On one computer Access 2003 was missing.
On another computer (that had been running Office 2003 beta) Outlook and
Access was missing. If went to Add/remove programs and made add remove
components, I could see that Outlook and Access was not marked as beeing
installed. Selecting "Modify" and adding Outlook and Access worked fine.

Both test computers are running Windows XP SP1.

All other applications was installed "100%" meaning all parts of these
applications was installed according the the selection made in the Custom
Installation Wizard.

For clean windows installations (no previous office version), the
installations is perfect.

Anyone has a clue why all applications are not installed?

Thanks in advance for any clues!

Best regards,

Jens-Peter

 

[marcus]

were they there before the upgrade?

 

[Arie Heinrich]

Hi Jens,

As marcus pointed out, on those computers
an early version or beta version of Office existed.

On the one with no Access, it either had Office standard installed (which
doesnt include Access) or Professional version with Access set to not
install.

The setup mechanism of Office not only detects what office versions were
installed but what was the setup state, ie: Run from my computer, run from
network, Not availabe etc...
It then goes on to install Office 2003 in those settings as well.
If you set a user to not get Access on his machine, office 2003 will not
install it.

If you want the setup process to install a Full version without detecting
the setup states of earlier components, you need to use a setup parmeter,
either on the setup command line or via the MST you created.

Please read the following page for nore info:

http://www.microsoft.com/office/ork/2003/two/ch4/DepB04.htm
- specifically look for the 'Modify intelligent setup behavior' section

Take care,

Arie H.
MS MVP