Same SID
Tech-Archive recommends: Fix windows errors by optimizing your registry
Hi
One of my clients have a NT domain with mostly XP clients (some 2000 and
NT4). The clients are cloned from a few different images so many of them
have the same SID. This havent been a problem in the NT4 domain.
Now we are about to migrate to 2003 AD.
Are we facing big trouble here??
or..
Can we migrate to 2003 without changing the SID?
or
Do we have to change SIDs before migration or after?
Tomppa
.
Relevant Pages
- Re: Anmeldevorgang in einer Misch Umgebung (inplace Upgrade NT4 --> W2003)
... WOHER zum teufel erfahren die Clients in der Zweigstellt und wie vro allen ... es wird ja NT4 PDC emuliert. ... Die melden sich gegen den BDC an ... Der PDC in der Zentrale ist niemals abgeschottet. ...
(microsoft.public.de.german.win2000.active_directory) - Re: Fallback to NT4 - Clients wont talk to Domain
... >> We have been experimenting in the lab with the UPGRADE ... >> route for converting our NT4 domain to Active Directory. ... >> an easy way to move all the clients back to the NT4 ...
(microsoft.public.win2000.active_directory) - Re: Fallback to NT4 - Clients wont talk to Domain
... The registry entry is the one he mentioned and is apparently ... >>> We have been experimenting in the lab with the UPGRADE ... >>> route for converting our NT4 domain to Active Directory. ... and it's a "feature" because this lets the news> clients get ...
(microsoft.public.win2000.active_directory) - Unable to Logon with UPN
... We have just upgraded our domain from NT4 to W2K3 AD and are having problems ... UPN details. ... WinXP clients are still authenticating with one of our NT4 BDC's, ...
(microsoft.public.windows.server.active_directory) - Re: ** Please Advise ** NT4 -> 2003 Upgrade Plan !!
... NT4 domain. ... > 1) Install new nt4 BDC and promote to PDC. ... 2k/XP/2003 clients from immediately swamping the new DC. ... even though they will NOT be using AD dns servers? ...
(microsoft.public.windows.server.active_directory) |
|
