Creating multipe Profiles? why?

[Guest]

We have recently became a MS shop ...so I'm new to domain and AD's.

I joined a domain about 3 months ago and I just looked at my C:\document and
settings\ folder and noticed 4 different local profiles.

dmadilicutty.001
dmadilicutty.002
dmadilicutty.003
dmadilicutty.DOM (DOM equals domain name)

Why are so many profiles being created? We are not doing roaming profiles
(should I)?

 

[Jerold Schulman]

We have recently became a MS shop ...so I'm new to domain and AD's.

I joined a domain about 3 months ago and I just looked at my C:\document and
settings\ folder and noticed 4 different local profiles.

dmadilicutty.001
dmadilicutty.002
dmadilicutty.003
dmadilicutty.DOM (DOM equals domain name)

Why are so many profiles being created? We are not doing roaming profiles
(should I)?

If configuration problems makes Windows think you are logging on for the first
time, it will create a new profile.

To determine you profile path:

Use the Registry Editor to navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

Inpect each SID sub-keys ProfileImagePath Value Name for <Drive:>\Documents and
Settings\UserName.



Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com

 

[Guest]

Don, you might want to take a look at the creation dates for each folder and
see if that sheds any light to the situation.
My guess would be that the 00# were all created before joining the domain.
When a new profile is created and one with the same name exists we create a
new folder user00#
When you join a domain and the name is already used you see the user.domain

 

[good things]

This could also be caused by profile corruption or permissions. If Windows
tries to create a folder called "dmadilicutty.001" and it exists and cannot
be written to, it will increment the extension and create a folder of that
name. You might want to check to see whether, with only one user logged in,
you have more that 2 hives in HKU (.default should stay). Check the
permissions on those hives. If you have broken sids, this would cause a
problem.

--


gt
Server Based Computing Evangelist

Don, you might want to take a look at the creation dates for each folder and
see if that sheds any light to the situation.
My guess would be that the 00# were all created before joining the domain.
When a new profile is created and one with the same name exists we create a
new folder user00#
When you join a domain and the name is already used you see the user.domain

--
James Brandt [MSFT]

If configuration problems makes Windows think you are logging on for the
first
time, it will create a new profile.

To determine you profile path:

Use the Registry Editor to navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList

Inpect each SID sub-keys ProfileImagePath Value Name for
<Drive:>\Documents and
Settings\UserName.



Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com

 

[Guest]

Thank you for all the advice...

I checked the reg for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList

and there is not a "profilelist" key located here.... should I add one?

Also you asked to Inpect each SID sub-keys ProfileImagePath Value Name for
<Drive:>\Documents and Settings\UserName. - How is this exactly done?

Laslty, If you have broken sids, this would cause a the problem...how do I
verify broken sids?

This could also be caused by profile corruption or permissions. If Windows
tries to create a folder called "dmadilicutty.001" and it exists and cannot
be written to, it will increment the extension and create a folder of that
name. You might want to check to see whether, with only one user logged in,
you have more that 2 hives in HKU (.default should stay). Check the
permissions on those hives. If you have broken sids, this would cause a
problem.

--


gt
Server Based Computing Evangelist

Don, you might want to take a look at the creation dates for each folder and
see if that sheds any light to the situation.
My guess would be that the 00# were all created before joining the domain.
When a new profile is created and one with the same name exists we create a
new folder user00#
When you join a domain and the name is already used you see the user.domain

--
James Brandt [MSFT]

On Mon, 9 Aug 2004 10:39:02 -0700, Don Madilicutty

We have recently became a MS shop ...so I'm new to domain and AD's.

I joined a domain about 3 months ago and I just looked at my C:\document
and
settings\ folder and noticed 4 different local profiles.

dmadilicutty.001
dmadilicutty.002
dmadilicutty.003
dmadilicutty.DOM (DOM equals domain name)

Why are so many profiles being created? We are not doing roaming profiles
(should I)?


If configuration problems makes Windows think you are logging on for the
first
time, it will create a new profile.

To determine you profile path:

Use the Registry Editor to navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList

Inpect each SID sub-keys ProfileImagePath Value Name for
<Drive:>\Documents and
Settings\UserName.



Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com

 

[Guest]

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\

My sid's are
S-1-5-21-2802022764-3685698554-67682327-1008
S-1-5-21-2802022764-3685698554-67682327-500
S-1-5-21-2441414376-2870739180-2552766755-1142
S-1-5-21-2441414376-2870739180-2552766755-1142.bak

So, in short...if there are different permissions or the profile become
corrupt....these new SIDs are created and hence a new profile is created? So
If I was changed from a "domain user" to a "domain admin" a new profile would
be created? I'm all over the place...but I do not like all these profiles
being created...my users will get totaly confused... (heck I'm confused)

 

[Guest]

A local user account and a domain account will have seperate profiles. So
if you logon locally to the computer with the same name that you use when
logging onto the domain the system will create sepearte profiles for each.

When you compare the SIDs you can see that the first 2 and last 2 were from
the same domain or computer.

Are you just wanting to get rid of the unused profils or determine where
they came from?
Depending on your goal you might want to look into using Sid2name from the
Windows 2000 resource kit to resolve the SID to a username.
A sid is the Security ID of a user account and is never changed. The only
correlation it has to profiles is a more consisten way of matching them
rather than a username that could be modified.