How to properly connect network users to a completely clean domain controller?

D

danykeep2015-12-30 10:01:12

Active Directory

danykeep, 2015-12-30 10:01:12

Challenge:
There were users connected to a domain controller running WS2003 that
also hosted DNS and DHCP.
There is no more domain controller, no more backups. There is only a list of users on paper.
A new domain controller running WS2012R2 with the same forest name and name is raised.
DHCP and DNS are still on the default settings (perhaps something needs to be corrected).
Question:
How to correctly drag users to the new AD?
At the moment, workstations are entered into AD according to a new one, but they don’t even take an IP address from DHCP, accepting 169.254 .....
If you force the address to be assigned, everything is OK.
Windows XP and Windows 7 workstations.

Reply

Answer the question

In order to leave comments, you need to log in

4 answer(s)

O

other_letter, 2015-12-30
@other_letter

No way. If you have already decided to reset the CD - change the domain completely.
Also what means "if to assign compulsorily - everything is OK"? What is OK? Is the domain working? Goes to the Internet?

A

Alexey, 2015-12-31
@skazi_premiere

The task is strange and incomprehensible in its form, because it was possible to raise another controller in a pair of 2003, transfer FSMO Roles to it, lower the old one, and then raise the level of the forest.
But if so, then:
1. Display and start stations in a new domain. (Specify the DNS of the new CD with handles)
2. Migration of users between domains of the same name is impossible, since it is unlikely to be able to set up trust (and there is no live controller), therefore:
In the new domain, the user's SID will be new, you can create a user and then manually fix it through the registry on the workstation at the old SID account to a new one (passwords will naturally need to be reset). Look for user migration utilities, but honestly both ways will bring only hemera.
As for DNS and DHCP, it is difficult to answer, you need to understand what settings are made. 169.254 is the default subnet when no DHCP server is found, so it's ok. But as I assume, the machines are trying to contact the old domain controller.

I

Ivan Bazaichenko, 2016-01-11
@Banzaii

The machines that are driven into the domain have their own password, under which it is authorized in AD. Therefore, all attempts to use machines in the new domain with the old name will fail. Not to mention timestamps and USN. Machines must be expelled from the domain to a workgroup and brought into a new one, albeit with the old name. With DHCP, they may have forgotten to authorize the server in AD. Therefore, he does not distribute anything. The first commentator Sergey suggested the right program for transferring profiles, and use it when you find yourself in a new domain. Import to AD users can be done with powershell. A combination of import-csv and new-aduser commands.