• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Windows Server domain controller...

I

Izza

Gawd
Joined
Mar 23, 2004
Messages
753
There are two domain controllers on a network. One is the 'current' domain (Server 2008), and there are several machines (plus old domain server running 2003).

I've managed to migrate a few machines over to the new domain, remapped drives, etc, with no problems.

The issue I'm having is that when the old domain controller is powered on (so some folks have access to certain resources on the network), it 'pulls' members of the new domain (including those who were never part of the old one) into the old domain.

Everything *looks* fine, until you see that the network they're connected to is 'olddomain.loc', and not 'newdomain.com'. Resources on the network cease to be available, etc.

Is there a... I don't know... elegant way of bringing the old domain controller, and all members of that old domain, over to the new domain, without a lot of grief?

I'm new to this, so apologies if I'm being somewhat vague. :(
 
Izza said:
Is there a... I don't know... elegant way of bringing the old domain controller, and all members of that old domain, over to the new domain, without a lot of grief?
Click to expand...

You passed the point of no return to do the standard approach....a "migration".
Install new server into existing SBS domain....
Promote to a DC
Transfer services and data "off" of the old SBS box
Transfer AD roles over to new server
power off old server....test for a bit...if all good, power up...properly remove from AD, power down for the last time.

There are more steps involved of course...but in a nutshell..those are it.

Since your new server is already up and running and assuming that you've flipped over some of the workstations into the new domain..may as well just move the rest of the data off. But as to describe the behavior you are seeing....as the person above posted....most likely DHCP is still running on the SBS box and causing clients to see it's DNS and stuff. Workstations catch it before it can detect the new server and its DHCP and shut itself off (because two Windows DHCP services don't get along and one will typically shut down because it detects another).
 
You must log in or register to reply here.
Back
Top