.WINNT profiles on Windows 2000 clients in Windows Server 2003 AD

  • Thread starter Thread starter Stefan Holland
  • Start date Start date
S

Stefan Holland

Hello,

on all newly installed Windows 2000 Pro clients we found for all locally
stored user profile an additional profile directory with the user name
and appended .WINNT. Even the "default user" profile exists in a copy
with the .WINNT ending.

We have not seen these profiles before and would like to know for what
these profiles are.

We use Windows 2000 clients in a Windows Server 2003 active directory,
which is operated in mixed-mode. We do not have any Windows NT machine
in this AD.

Logging on a Windows Server 2003 and Windows 2000 clients seems to
damage the quick launch bar. The quick launch bars multiply endlessly in
some profiles.

Do Windows 2000 profiles differ from Windows Server 2003 profiles ?
 
Profiles are not compatible between OSes - don't use roaming profiles to log
onto your server (and users shouldn't be logging on to it, and admin
accounts shouldn't have roaming profiles. Don't roam between W2k/XP/NT with
roaming profiles, either.

You'r seeing the .WINNT profile thingy because the local user name had its
own profile, and then you logged in and it created a domain profile, I
suspect. Is there any need to have local logins?
 
Lanwench said:
Profiles are not compatible between OSes - don't use roaming profiles to log
onto your server (and users shouldn't be logging on to it, and admin
accounts shouldn't have roaming profiles. Don't roam between W2k/XP/NT with
roaming profiles, either.
We have been using roaming profiles between Windows 2000 clients and
Windows Server 2003 machines for about year and the problems just
started some weeks ago.
You'r seeing the .WINNT profile thingy because the local user name had its
own profile, and then you logged in and it created a domain profile, I
suspect. Is there any need to have local logins?

No, there are no local accounts with the same name.

If this is the case the global domain account gets the ending
..DomainName to distinguish it from the local account.
 
Back
Top