Office XP User / registration information incorrect on Citrix XP server

Hi,

I have a bit of a weird problem. We have a Windows 2000 / Citrix XP
based domain, where users run terminal sessions on W2k servers in the
farm. When users log in to their Citrix sessions and work with Office
XP, the Office should say it is licensed to "IT Services" and the user
information should display their own personal information. This is how
it is for users who log on, except for those who are directed to server
9 in the farm. When their sessions run on this the user information and
registration information both display my own domain administrator
account. This might not seem a big deal, but when users who have a
session on this server the document looks like it is created by me, and
all the associated information also points to me! Worse, when they make
edits to shared documents, the changes are attributed to me, when I
have never touched the document in my life. I am completely baffled why
this should happen. It was working fine first thing in the morning, and
then this started happening a couple of hours later, when I had not
worked on the server the whole day. I am interested to know how this
situation might have come about, but I am far more anxious to get this
sorted. I want users to have their user information integrated with
their logon when they access Office applications. Does anyone have any
ideas?

Thanks.

QH

I had a similar problem and here is what I did to fix it...
First of all, you have to delete the profile of the users that are
affected..Once its written to their ntuser.dat file then you cant really do
anything about it but delete it and start from scratch...

After doing this apply the following reg hacks to the server that is running
the TS..
(the assumption here is you are using Office 2003)

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal
Server\Install\Software\Microsoft\Office\11.0\Common\UserInfo]
"UserName"=hex:00,00
"UserInitials"=hex:00,00

and this one...

Windows Registry Editor Version 5.00
[HKEY_USERS\.DEFAULT\Software\Microsoft\Office\11.0\Common\UserInfo]
"UserName"=hex:00,00
"UserInitials"=hex:00,00

I reboot the server after applying these and then it works...I think Office
XP would be 10.0. SO I would look for 10.0 in the registry...But the process
should be the same...

As always..TEST, TEST, TEST before rolling into production....


"QH" wrote:

> Hi,
>
> I have a bit of a weird problem. We have a Windows 2000 / Citrix XP
> based domain, where users run terminal sessions on W2k servers in the
> farm. When users log in to their Citrix sessions and work with Office
> XP, the Office should say it is licensed to "IT Services" and the user
> information should display their own personal information. This is how
> it is for users who log on, except for those who are directed to server
> 9 in the farm. When their sessions run on this the user information and
> registration information both display my own domain administrator
> account. This might not seem a big deal, but when users who have a
> session on this server the document looks like it is created by me, and
> all the associated information also points to me! Worse, when they make
> edits to shared documents, the changes are attributed to me, when I
> have never touched the document in my life. I am completely baffled why
> this should happen. It was working fine first thing in the morning, and
> then this started happening a couple of hours later, when I had not
> worked on the server the whole day. I am interested to know how this
> situation might have come about, but I am far more anxious to get this
> sorted. I want users to have their user information integrated with
> their logon when they access Office applications. Does anyone have any
> ideas?
>
> Thanks.
>
> QH
>
>

Thanks plsntn_rules

Actually, we have found if the affected user goes in to
Word\tools\options\user information, deletes the incorrect infomation,
and then logs off, this is set back to nothing the next time they
logon. They can then input their own details. What I really want to
know is though - how on Earth did this happen in the first place. I was
completely stunned when it did.

Any thoughts?

plsntn_rules wrote:
> I had a similar problem and here is what I did to fix it...
> First of all, you have to delete the profile of the users that are
> affected..Once its written to their ntuser.dat file then you cant really do
> anything about it but delete it and start from scratch...
>
> After doing this apply the following reg hacks to the server that is running
> the TS..
> (the assumption here is you are using Office 2003)
>
> Windows Registry Editor Version 5.00
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal
> Server\Install\Software\Microsoft\Office\11.0\Common\UserInfo]
> "UserName"=hex:00,00
> "UserInitials"=hex:00,00
>
> and this one...
>
> Windows Registry Editor Version 5.00
> [HKEY_USERS\.DEFAULT\Software\Microsoft\Office\11.0\Common\UserInfo]
> "UserName"=hex:00,00
> "UserInitials"=hex:00,00
>
> I reboot the server after applying these and then it works...I think Office
> XP would be 10.0. SO I would look for 10.0 in the registry...But the process
> should be the same...
>
> As always..TEST, TEST, TEST before rolling into production....
>
>
> "QH" wrote:
>
> > Hi,
> >
> > I have a bit of a weird problem. We have a Windows 2000 / Citrix XP
> > based domain, where users run terminal sessions on W2k servers in the
> > farm. When users log in to their Citrix sessions and work with Office
> > XP, the Office should say it is licensed to "IT Services" and the user
> > information should display their own personal information. This is how
> > it is for users who log on, except for those who are directed to server
> > 9 in the farm. When their sessions run on this the user information and
> > registration information both display my own domain administrator
> > account. This might not seem a big deal, but when users who have a
> > session on this server the document looks like it is created by me, and
> > all the associated information also points to me! Worse, when they make
> > edits to shared documents, the changes are attributed to me, when I
> > have never touched the document in my life. I am completely baffled why
> > this should happen. It was working fine first thing in the morning, and
> > then this started happening a couple of hours later, when I had not
> > worked on the server the whole day. I am interested to know how this
> > situation might have come about, but I am far more anxious to get this
> > sorted. I want users to have their user information integrated with
> > their logon when they access Office applications. Does anyone have any
> > ideas?
> >
> > Thanks.
> >
> > QH
> >
> >

It typically happens because the admin who installed office went in and
started an office app while still in install mode.

Jeff Pitsch
http://www.sbcgatekeeper.com
Your Terminal Services Security Website

<quentinhudson@hotmail.com> wrote in message
news:1134487291.730891.97040@g43g2000cwa.googlegroups.com...
> Thanks plsntn_rules
>
> Actually, we have found if the affected user goes in to
> Word\tools\options\user information, deletes the incorrect infomation,
> and then logs off, this is set back to nothing the next time they
> logon. They can then input their own details. What I really want to
> know is though - how on Earth did this happen in the first place. I was
> completely stunned when it did.
>
> Any thoughts?
>
> plsntn_rules wrote:
>> I had a similar problem and here is what I did to fix it...
>> First of all, you have to delete the profile of the users that are
>> affected..Once its written to their ntuser.dat file then you cant really
>> do
>> anything about it but delete it and start from scratch...
>>
>> After doing this apply the following reg hacks to the server that is
>> running
>> the TS..
>> (the assumption here is you are using Office 2003)
>>
>> Windows Registry Editor Version 5.00
>> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal
>> Server\Install\Software\Microsoft\Office\11.0\Common\UserInfo]
>> "UserName"=hex:00,00
>> "UserInitials"=hex:00,00
>>
>> and this one...
>>
>> Windows Registry Editor Version 5.00
>> [HKEY_USERS\.DEFAULT\Software\Microsoft\Office\11.0\Common\UserInfo]
>> "UserName"=hex:00,00
>> "UserInitials"=hex:00,00
>>
>> I reboot the server after applying these and then it works...I think
>> Office
>> XP would be 10.0. SO I would look for 10.0 in the registry...But the
>> process
>> should be the same...
>>
>> As always..TEST, TEST, TEST before rolling into production....
>>
>>
>> "QH" wrote:
>>
>> > Hi,
>> >
>> > I have a bit of a weird problem. We have a Windows 2000 / Citrix XP
>> > based domain, where users run terminal sessions on W2k servers in the
>> > farm. When users log in to their Citrix sessions and work with Office
>> > XP, the Office should say it is licensed to "IT Services" and the user
>> > information should display their own personal information. This is how
>> > it is for users who log on, except for those who are directed to server
>> > 9 in the farm. When their sessions run on this the user information and
>> > registration information both display my own domain administrator
>> > account. This might not seem a big deal, but when users who have a
>> > session on this server the document looks like it is created by me, and
>> > all the associated information also points to me! Worse, when they make
>> > edits to shared documents, the changes are attributed to me, when I
>> > have never touched the document in my life. I am completely baffled why
>> > this should happen. It was working fine first thing in the morning, and
>> > then this started happening a couple of hours later, when I had not
>> > worked on the server the whole day. I am interested to know how this
>> > situation might have come about, but I am far more anxious to get this
>> > sorted. I want users to have their user information integrated with
>> > their logon when they access Office applications. Does anyone have any
>> > ideas?
>> >
>> > Thanks.
>> >
>> > QH
>> >
>> >
>

What do you mean by 'install mode'. Is that just the 'Add new program'
option in Control panel\add remove programs?

Thanks.

You can also do it at the command line but yes. installing an application
from add/remove programs puts the server into install mode as well.

Jeff Pitsch
http://www.sbcgatekeeper.com
Your Terminal Services Security Website

<quentinhudson@hotmail.com> wrote in message
news:1134551505.318337.304140@o13g2000cwo.googlegroups.com...
> What do you mean by 'install mode'. Is that just the 'Add new program'
> option in Control panel\add remove programs?
>
> Thanks.
>