Multiuser Office XP Deployment- First Run- Name and Initials Promp

[Jeff Hanchey]

Hi,

I have different users that use the same workstation with Office XP
installed. Office has been deployed from an administrative share with a
transform created from the ORK applied. Everytime a new user logs on to a
workstation and when they start an Office app for the first time, it goes
through a setup process and then prompts the user for a name and their
initials. I do not want this to happen. I have already populated the
userinfo key for the current user with a utility that runs at login and pulls
the user name and initials from AD. I have verified the utility is working
correctly and populating the userinfo keys correctly. However, when the user
starts an office app for the first time, the setup process clears the
userinfo registry keys and then proceeds to prompt the user for a name and
initials. How can I keep Office from prompting the end user for name and
initials on its first run? I have tried just about everything I can think of
and just can't get it to stop prompting the end user. Please advise.

 

[Craig Sanders]

I have the same problem with a deployment of Office 2003 in a Multiuser
Office Deployment. I tried using the Office Profile Wizard from the Office
2003 Resource Kit to get around the problem but no luck. If anyone can give
me some references for eliminating the "mini-setup" I would appreciate it.

On Office 2000 I was able to work around the problem by writing a script
that copied a set of registry keys but that doesn't seem to work in Office
2003.

 

[Craig Sanders]

I have the same problem with a deployment of Office 2003 in a Multiuser
Office Deployment. I tried using the Office Profile Wizard from the Office
2003 Resource Kit to get around the problem but no luck. If anyone can give
me some references for eliminating the "mini-setup" I would appreciate it.

On Office 2000 I was able to work around the problem by writing a script
that copied a set of registry keys but that doesn't seem to work in Office
2003.

 

[Craig Sanders]

I have the same problem with a deployment of Office 2003 in a Multiuser
Office Deployment. I tried using the Office Profile Wizard from the Office
2003 Resource Kit to get around the problem but no luck. If anyone can give
me some references for eliminating the "mini-setup" I would appreciate it.

On Office 2000 I was able to work around the problem by writing a script
that copied a set of registry keys but that doesn't seem to work in Office
2003.

 

[Craig Sanders]

I have the same problem with a deployment of Office 2003 in a Multiuser
Office Deployment. I tried using the Office Profile Wizard from the Office
2003 Resource Kit to get around the problem but no luck. If anyone can give
me some references for eliminating the "mini-setup" I would appreciate it.

On Office 2000 I was able to work around the problem by writing a script
that copied a set of registry keys but that doesn't seem to work in Office
2003.

 

[Craig Sanders]

I have the same problem with a deployment of Office 2003 in a Multiuser
Office Deployment. I tried using the Office Profile Wizard from the Office
2003 Resource Kit to get around the problem but no luck. If anyone can give
me some references for eliminating the "mini-setup" I would appreciate it.

On Office 2000 I was able to work around the problem by writing a script
that copied a set of registry keys but that doesn't seem to work in Office
2003.

 

[Craig Sanders]

I have the same problem with a deployment of Office 2003 in a Multiuser
Office Deployment. I tried using the Office Profile Wizard from the Office
2003 Resource Kit to get around the problem but no luck. If anyone can give
me some references for eliminating the "mini-setup" I would appreciate it.

On Office 2000 I was able to work around the problem by writing a script
that copied a set of registry keys but that doesn't seem to work in Office
2003.

 

[Craig Sanders]

I have the same problem with a deployment of Office 2003 in a Multiuser
Office Deployment. I tried using the Office Profile Wizard from the Office
2003 Resource Kit to get around the problem but no luck. If anyone can give
me some references for eliminating the "mini-setup" I would appreciate it.

On Office 2000 I was able to work around the problem by writing a script
that copied a set of registry keys but that doesn't seem to work in Office
2003.

 

[Craig Sanders]

I have the same problem with a deployment of Office 2003 in a Multiuser
Office Deployment. I tried using the Office Profile Wizard from the Office
2003 Resource Kit to get around the problem but no luck. If anyone can give
me some references for eliminating the "mini-setup" I would appreciate it.

On Office 2000 I was able to work around the problem by writing a script
that copied a set of registry keys but that doesn't seem to work in Office
2003.

 

[Craig Sanders]

I have the same problem with a deployment of Office 2003 in a Multiuser
Office Deployment. I tried using the Office Profile Wizard from the Office
2003 Resource Kit to get around the problem but no luck. If anyone can give
me some references for eliminating the "mini-setup" I would appreciate it.

On Office 2000 I was able to work around the problem by writing a script
that copied a set of registry keys but that doesn't seem to work in Office
2003.