Win2k Pro stations on Windows 2003 Server creating new profiles at boot

compSAM

We use to be a Novell network for years and years. For the past 5
years we were running 70 stations on Windows 2000 Pro with no issues.
In March we switched over to a Windows 2003 server network. Our main
DC we installed 64bit Windows 2003 SP2. All the stations stayed
unchanged other than we had to create new profiles on the domain. All
the stations ran fine for weeks then about a month after the switch
over we had a handful of stations when the user's logged on a new
profile was automatically created for them. When the server switch-
over was done the new user profiles were all "U_Username", they did
not show up as the usual "U_Username.domainname". When the new user
profiles get created they then show up as U_Username.domainname but
this is only a handful, the remaining 60 some stations are still fine
running profiles that are just U_Username. Once the new profile is
created the machine runs fine again for about a month then some again
create a new profile once again and the profile then becomes
"U_Username.domainname.001". Only a couple stations repeat and get
new profile after new profile. We do get 1 or 2 new stations every
month - that get new profiles created. So some machines have run fine
for almost 4 months without any issues then one day kaaboom it gets a
new profile. We thought it was related to the Novell - Windows switch-
over and maybe some registry residue or something then I created a new
machine from a Dell we got and this machine never had the Novell
client on it and nothing from the old system. This new system ran
fine for 2 months then it created a new profile one morning. We had
Microsoft support through HP and they worked on it for a month and
could offer no help and knew of no similar issues reported anywhere.
We are not and have never user Roaming profiles. These are simple
profiles on the stations running on the domain.

Anyone else know, seen or can help with this issue??????????

Thanks

Dave Patrick

More than likely incorrect file system and or registry permissions on the
profile and or the \default user profile.

These two may help.
http://support.microsoft.com/kb/266118
http://support.microsoft.com/kb/244600


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"compSAM" wrote:
> We use to be a Novell network for years and years. For the past 5
> years we were running 70 stations on Windows 2000 Pro with no issues.
> In March we switched over to a Windows 2003 server network. Our main
> DC we installed 64bit Windows 2003 SP2. All the stations stayed
> unchanged other than we had to create new profiles on the domain. All
> the stations ran fine for weeks then about a month after the switch
> over we had a handful of stations when the user's logged on a new
> profile was automatically created for them. When the server switch-
> over was done the new user profiles were all "U_Username", they did
> not show up as the usual "U_Username.domainname". When the new user
> profiles get created they then show up as U_Username.domainname but
> this is only a handful, the remaining 60 some stations are still fine
> running profiles that are just U_Username. Once the new profile is
> created the machine runs fine again for about a month then some again
> create a new profile once again and the profile then becomes
> "U_Username.domainname.001". Only a couple stations repeat and get
> new profile after new profile. We do get 1 or 2 new stations every
> month - that get new profiles created. So some machines have run fine
> for almost 4 months without any issues then one day kaaboom it gets a
> new profile. We thought it was related to the Novell - Windows switch-
> over and maybe some registry residue or something then I created a new
> machine from a Dell we got and this machine never had the Novell
> client on it and nothing from the old system. This new system ran
> fine for 2 months then it created a new profile one morning. We had
> Microsoft support through HP and they worked on it for a month and
> could offer no help and knew of no similar issues reported anywhere.
> We are not and have never user Roaming profiles. These are simple
> profiles on the stations running on the domain.
>
> Anyone else know, seen or can help with this issue??????????
>
> Thanks
>