Discussion:
New local profile is created
(too old to reply)
Gerko
2005-09-15 09:08:04 UTC
Permalink
Hello,

On our Windows 2000 Terminal Server, the users have a local profile.
Yesterday the following happend, user JeanB started a session (he had an
existing profile with the name JeanB), and a new profile was created with the
name JeanB.DOMAIN. If I delete this profile it is created again be starting a
new session.
I am not aware that there where changes on our network, and the user logged
on as usual. I did have a look a the Documents and Settings folder and find
out that some foldernames are just the username and others have username and
domainname. What is happening here, and is it possible that the user can use
its old profile again?

The eventlog on the terminal server reported:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 14-9-2005
Time: 16:36:51
User: DOMAIN\JeanB
Computer: TERMINALSERVER
Description:
Windows cannot copy file M:\Documents and Settings\Default User\NTUSER.DAT
to location M:\Documents and Settings\JeanB.DOMAIN\NTUSER.DAT. Contact your
network administrator.

DETAIL - The process cannot access the file because it is being used by
another process.
Patrick Rouse
2005-09-15 21:37:17 UTC
Permalink
The original profile is probably locked in memory or corrupted, so until you
delete it (or try rebooting first) this will happen.
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
Post by Gerko
Hello,
On our Windows 2000 Terminal Server, the users have a local profile.
Yesterday the following happend, user JeanB started a session (he had an
existing profile with the name JeanB), and a new profile was created with the
name JeanB.DOMAIN. If I delete this profile it is created again be starting a
new session.
I am not aware that there where changes on our network, and the user logged
on as usual. I did have a look a the Documents and Settings folder and find
out that some foldernames are just the username and others have username and
domainname. What is happening here, and is it possible that the user can use
its old profile again?
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 14-9-2005
Time: 16:36:51
User: DOMAIN\JeanB
Computer: TERMINALSERVER
Windows cannot copy file M:\Documents and Settings\Default User\NTUSER.DAT
to location M:\Documents and Settings\JeanB.DOMAIN\NTUSER.DAT. Contact your
network administrator.
DETAIL - The process cannot access the file because it is being used by
another process.
Gerko
2005-09-16 07:03:01 UTC
Permalink
Thank you Patrick for your reply, I tried a reboot but then still the new
created profile is used. After that I deleted the new profile (System
Properties - User Profiles), but when logged-on a new profile is created
again. Is there a way to force Windows to use the old profile, or is it just
so corrupted that Windows can not use it anymore? Is there a way to see the
condition of a profile?

Gerko
Post by Patrick Rouse
The original profile is probably locked in memory or corrupted, so until you
delete it (or try rebooting first) this will happen.
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
Post by Gerko
Hello,
On our Windows 2000 Terminal Server, the users have a local profile.
Yesterday the following happend, user JeanB started a session (he had an
existing profile with the name JeanB), and a new profile was created with the
name JeanB.DOMAIN. If I delete this profile it is created again be starting a
new session.
I am not aware that there where changes on our network, and the user logged
on as usual. I did have a look a the Documents and Settings folder and find
out that some foldernames are just the username and others have username and
domainname. What is happening here, and is it possible that the user can use
its old profile again?
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 14-9-2005
Time: 16:36:51
User: DOMAIN\JeanB
Computer: TERMINALSERVER
Windows cannot copy file M:\Documents and Settings\Default User\NTUSER.DAT
to location M:\Documents and Settings\JeanB.DOMAIN\NTUSER.DAT. Contact your
network administrator.
DETAIL - The process cannot access the file because it is being used by
another process.
Patrick Rouse
2005-09-16 13:56:04 UTC
Permalink
Not that I know of, that what backups are for, so you can restore things when
they get messed-up. I store roaming profiles on a volume with Shadow Copies
of Shared Folders enabled, so I don't even need to go to tape if a profile
gets corrupted.
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
Post by Gerko
Thank you Patrick for your reply, I tried a reboot but then still the new
created profile is used. After that I deleted the new profile (System
Properties - User Profiles), but when logged-on a new profile is created
again. Is there a way to force Windows to use the old profile, or is it just
so corrupted that Windows can not use it anymore? Is there a way to see the
condition of a profile?
Gerko
Post by Patrick Rouse
The original profile is probably locked in memory or corrupted, so until you
delete it (or try rebooting first) this will happen.
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
Post by Gerko
Hello,
On our Windows 2000 Terminal Server, the users have a local profile.
Yesterday the following happend, user JeanB started a session (he had an
existing profile with the name JeanB), and a new profile was created with the
name JeanB.DOMAIN. If I delete this profile it is created again be starting a
new session.
I am not aware that there where changes on our network, and the user logged
on as usual. I did have a look a the Documents and Settings folder and find
out that some foldernames are just the username and others have username and
domainname. What is happening here, and is it possible that the user can use
its old profile again?
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 14-9-2005
Time: 16:36:51
User: DOMAIN\JeanB
Computer: TERMINALSERVER
Windows cannot copy file M:\Documents and Settings\Default User\NTUSER.DAT
to location M:\Documents and Settings\JeanB.DOMAIN\NTUSER.DAT. Contact your
network administrator.
DETAIL - The process cannot access the file because it is being used by
another process.
Gerko
2005-09-21 13:34:08 UTC
Permalink
Thanks Patrick,

Backup is a good one. What is the procedure to backup profiles? Will it be
sufficient to backup all folders in the documents and setting folder?

Gerko
Post by Patrick Rouse
Not that I know of, that what backups are for, so you can restore things when
they get messed-up. I store roaming profiles on a volume with Shadow Copies
of Shared Folders enabled, so I don't even need to go to tape if a profile
gets corrupted.
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
Post by Gerko
Thank you Patrick for your reply, I tried a reboot but then still the new
created profile is used. After that I deleted the new profile (System
Properties - User Profiles), but when logged-on a new profile is created
again. Is there a way to force Windows to use the old profile, or is it just
so corrupted that Windows can not use it anymore? Is there a way to see the
condition of a profile?
Gerko
Post by Patrick Rouse
The original profile is probably locked in memory or corrupted, so until you
delete it (or try rebooting first) this will happen.
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
Post by Gerko
Hello,
On our Windows 2000 Terminal Server, the users have a local profile.
Yesterday the following happend, user JeanB started a session (he had an
existing profile with the name JeanB), and a new profile was created with the
name JeanB.DOMAIN. If I delete this profile it is created again be starting a
new session.
I am not aware that there where changes on our network, and the user logged
on as usual. I did have a look a the Documents and Settings folder and find
out that some foldernames are just the username and others have username and
domainname. What is happening here, and is it possible that the user can use
its old profile again?
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 14-9-2005
Time: 16:36:51
User: DOMAIN\JeanB
Computer: TERMINALSERVER
Windows cannot copy file M:\Documents and Settings\Default User\NTUSER.DAT
to location M:\Documents and Settings\JeanB.DOMAIN\NTUSER.DAT. Contact your
network administrator.
DETAIL - The process cannot access the file because it is being used by
another process.
Patrick Rouse
2005-09-21 13:41:06 UTC
Permalink
Yes. (as long as they aren't in use)
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
Post by Gerko
Thanks Patrick,
Backup is a good one. What is the procedure to backup profiles? Will it be
sufficient to backup all folders in the documents and setting folder?
Gerko
Post by Patrick Rouse
Not that I know of, that what backups are for, so you can restore things when
they get messed-up. I store roaming profiles on a volume with Shadow Copies
of Shared Folders enabled, so I don't even need to go to tape if a profile
gets corrupted.
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
Post by Gerko
Thank you Patrick for your reply, I tried a reboot but then still the new
created profile is used. After that I deleted the new profile (System
Properties - User Profiles), but when logged-on a new profile is created
again. Is there a way to force Windows to use the old profile, or is it just
so corrupted that Windows can not use it anymore? Is there a way to see the
condition of a profile?
Gerko
Post by Patrick Rouse
The original profile is probably locked in memory or corrupted, so until you
delete it (or try rebooting first) this will happen.
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
Post by Gerko
Hello,
On our Windows 2000 Terminal Server, the users have a local profile.
Yesterday the following happend, user JeanB started a session (he had an
existing profile with the name JeanB), and a new profile was created with the
name JeanB.DOMAIN. If I delete this profile it is created again be starting a
new session.
I am not aware that there where changes on our network, and the user logged
on as usual. I did have a look a the Documents and Settings folder and find
out that some foldernames are just the username and others have username and
domainname. What is happening here, and is it possible that the user can use
its old profile again?
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 14-9-2005
Time: 16:36:51
User: DOMAIN\JeanB
Computer: TERMINALSERVER
Windows cannot copy file M:\Documents and Settings\Default User\NTUSER.DAT
to location M:\Documents and Settings\JeanB.DOMAIN\NTUSER.DAT. Contact your
network administrator.
DETAIL - The process cannot access the file because it is being used by
another process.
Loading...