Office 2003 install headache

[pooley]

Ok have installed Office 2k3 on Various Networked xp workstations.

The only problem is that every time a new user logs onto one of these machines the office application (work/excel etc) goes through an install process before they can use it.

Eventvwr give me

Detection of product '{90110409-6000-11D3-8CFE-0150048383C9}', feature 'ExcelUserData', component '{8ADD2C96-C8B7-11D1-9C67-0000F81F1B38}' failed. The resource 'HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\ Excel\UserData' does not exist.

And its quite correct it doesnt exist. lol

Any help ?

[Ric_]

Run Office and set it up like you want and then copy the local profile of that user to your 'Default User' profile.

[pooley]

Naah doesnt work.

If I logon to pc as admin and then open word it goes through install process, I then close word and immediatly open it again and it again goes through the install process.

Must be something to do with having installed it while logged onto network as apposed to local admin of the pc - 1 test box I installed office on (local admin) i dont get the problems.

Ahh well back to drawing board.

thanks anyway

**edit**

Only way it works without the install bit comming up is to install office before making the pc part of the domain.

Too late for the 40 or so ive allready joined

[Dos_Box]

Do you have mandatory profiles?

[Ric_]

You need to make sure that you clear the locally stored profiles first otherwise a new one won't be created.

If you are using roaming/mandatory profiles, you will need to update those rather than the Default User profile.

[alan-d]

when you do the install - don't delete the setup files - leave them.

I found that once users let it do the install it stopped after a while

No logic to it - it just did

[mark]

Interesting [as i've only just started rolling this monster out]. I'll give that a try too.

[tarquel]

This - as I understand it [and it works for me] - is the normal way of doing it I think:

- set up a adminisrative share of Office 2k3 that your users can see...
[I've found that \\servername\mso2k3 isnt a good place to install from as it takes longer than a mapped share i.e. i:\Apps\MSO2K3 [which is a share on a network drive naturally lol]

- customise how you want the install to run with the resource tools for Office 2k3 - Cant remember the names offhand but I'll update this post a bit later on It's on the whole not that important though as you can lock it down pretty tightly via the Office 2k3 GP's anyhow

- As a administrator, install Office 2k3 from that share using any transforms/settings that you may have steup up for the install [I think you need to keep the transforms in a location that the users can see also - but not 100% on this one - I just stick them in the same dir of the administrative install]

Thats it really - well, for me, I use roaming profiles and each user gets the initial install window appear when they first start it - but once they have done it once, it doesnt ask them again - as its stored in their roaming profile naturally lol

pooley - You might find that something in your GP is preventing the install from completing [but it does sound very odd that you get it again after closing word and starting again]. By not using roaming/manditory profiles or configuring the local default user profile, your users will keep getting the "Install/Setup" window when they log on as it seems there is no way for it to hold the information anywhere.

Sorry if this is a trifle like rambling - i'm tired and ill lol

Have a chat on MSN if you care to

Cheers
N.

[pooley]

Cheers m8, will take alook at my GP and see what ive enabled.