Upgrade Office 2003 : problem with username
Hello
I use ZENworks to distribute applications.
I must deploy Office 2003 (upgrade from Office 2000), and when i do this upgrade, i lose the username in Word, Excel, ...
Can someone help me for this issue, a want to keep the username (in Word, Tools --> Options --> User)
Thank's for your help
Johan
I use ZENworks to distribute applications.
I must deploy Office 2003 (upgrade from Office 2000), and when i do this upgrade, i lose the username in Word, Excel, ...
Can someone help me for this issue, a want to keep the username (in Word, Tools --> Options --> User)
Thank's for your help
Johan
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
MicrosoftBob
16 years ago
It looks like Office 2003 stores that information at HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\UserInfo and it stores it in REG_BINARY form for some strange reason.
I don't know where Office 2000 stores that info, but my guess would be the same path except 9.0 instead of 11.0. However it may store it as REG_SZ instead of REG_BINARY in which case it might be difficult to translate.
You would have to read or export this value from the 9.0 path and then write it back out to the 11.0 path, using the scripting language of your choice.
I don't know where Office 2000 stores that info, but my guess would be the same path except 9.0 instead of 11.0. However it may store it as REG_SZ instead of REG_BINARY in which case it might be difficult to translate.
You would have to read or export this value from the 9.0 path and then write it back out to the 11.0 path, using the scripting language of your choice.
Posted by:
anonymous_9363
16 years ago
I suspect you could this with some script using the automation objects of the Office applications. I say 'applications' plural because you'll probably want to attend to XL and PP, too.
Extract the User Info before the install and store it somehow (e.g. a temporary registry value), install the new flavour of Doofuss and then use the same object model to write it back after install.
As a starting point, I'd record changing the info in a macro. You'll end up with VBA code which can nomrally be converted very simple by removing the type declarations i.e. where VBA says 'Dim objWordApp As Word.Application' you'd edit the code to 'Dim objWordApp' and then create the Word object.
Not simple, but do-able, I think.
Extract the User Info before the install and store it somehow (e.g. a temporary registry value), install the new flavour of Doofuss and then use the same object model to write it back after install.
As a starting point, I'd record changing the info in a macro. You'll end up with VBA code which can nomrally be converted very simple by removing the type declarations i.e. where VBA says 'Dim objWordApp As Word.Application' you'd edit the code to 'Dim objWordApp' and then create the Word object.
Not simple, but do-able, I think.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.