Office 2003 (UNC path install) & Windows Installer

[bdarcyevans]

Hi everyone,

Just got a question about Microsoft office network installations. At the moment I have the office 2003 CD sitting on a network share. On my workstations I install office using the UNC path (\\server\share\msifilehere.msi) but what I’m finding is windows installer wants to configure office for each new user that logs onto a workstation.

For example. A workstation has a full install of Office 2003 installed via the UNC path. A new user logs onto the workstation and opens word. Upon the first run Windows Installer appears and configures “Microsoft Office 2003”. Once it has run for that user once, other applications such as Excel and PowerPoint can be opened without the windows installer appearing. If the user logs off and another new user logs on the same process occurs.

Is there something I can embed into the Default User profile to stop windows installer from configuring office each time a new user uses a workstation? Or perhaps there is another solution?

All feedback appreciated.

Thanks,

Brendan

[m8rk]

I have the same problem - network installation point - imaged installations tho', and Office 2K.

I read a while back - I think there's an MS KB on it - that there are permissions settings to make this go away. Just had a search but not able to find anything. Will try again.

What about setting a default profile in the GPO user [as described here: http://www.windowsdevcenter.com/pub/a/wind...1/rmng_usr.html ]. If that worked it might be useful in speeding up initial profile creation, if like me all your users need to be identical. You could log in as a test user - set up everything as you want it [configure programs as they're run 1st time], then copy that profile to the GPO default.

I realise it's just a theory but it'd be good if it worked.

[Martin Zugec]

AFAIK it is not creation, it is registration of advertised per-user feature from cached MSI...

[m8rk]

AFAIK it is not creation, it is registration of advertised per-user feature from cached MSI...

<{POST_SNAPBACK}>

So you're saying that's not possible then soulin?