I use a Microsoft Office 2000 package to deploy Office 2000 Pro along with an MST created with Install Tailor.

I have written a script to turn off Office Assistant and fill in the User Info with their AD full name and Initials. I set the "FirstRun" flag to 0 so Word wont prompt for User Info.

However, when Word, Excel, etc is run for the first time, the initial user setup portion of the package runs (as normal) and it resets the FirstRun flag, so it ends up prompting the user for their name anyway.

My Question:

Is there a way I can force Word, Excel, etc to run the user portion of the package, but to not actually run the application itself??? This way it can touch what it needs to touch in the user's profile, and then my script can set the FirstRun flag to 0 and set everything it needs to set.

Hopefully this made sense.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Use ORCA to look at the Office MSI. If the 'First Run' entry is there, you can create another transorm to modify the initial value.
Answered 11/26/2005 by: abritton
Senior Yellow Belt

Please log in to comment
I did a similar thing with Office 2003. In my case, i created a vbscript file to register the key for the current user logged in. That script file was fetching information within Active Directory to register the name in Office with the name associated with the logged user in the Active Directory. For the initials, we used the current logged on username.

You can also apply the registry file containing that info in the HKCU to apply in the default user HKCU.

Need help, i might can.

Hope this help!
Answered 12/03/2005 by: wd40
Orange Senior Belt

Please log in to comment