How to Install Your First Windows Server 2022 Active Directory Domain Controller

Subscribe to this channel
/ @itgeared
Find more related videos in this playlist
• Windows Server 2022
Video Description
In this video, we demonstrate the process of establishing our first root domain controller in a new Active Directory Forest.

[@supriyochatterjee4095]

Excellent videos, please kindly make videos on all kinds of technical troubleshooting scenarios for Windows Server and Active Directory

[@itgeared]

Thanks! Yes that is the plan. I’ve been away for a while, but back and working on new videos. Stay tuned…

[@agronzenko4010]

Great video. Thanks for making it for us. I have question. The Server2022 (Dell EMC PowerEdge T350)that I am configuring has 2 NIC Cards and 2 HD. What static IPs should assign to each embedded NIC card? Thnx

[@JorgeMederos]

Thank you for the feedback and question. For a domain controller, one NIC is typically sufficient. Unless you have a need to have this server participate on multiple subnets OR if you have drivers/software to add to the system to treat both NICs as a single NIC for fault tolerance, I would suggest you simply disable one NIC. For the remaining NIC, you would configure it with a static IP address that is usable within the subnet where this server will be placed. If you are at the very beginning of building your network, determining the IP space and structure is your first step so you can then configure not only this server with the proper configuration but any other server, clients, and other devices you intend to join on this network.

[@agronzenko4010]

Thank you so much@@JorgeMederos

[@itgeared]

@@agronzenko4010 👍

[@evelyndai8200]

hi, how do i choose a suitable fixed ipv4 for my server if the internet network has dhcp enabled. I have tried multiple ipv4 but it I set it to anything other than obtain ip automatically the network access is shut off, do you have any video to refer to

[@itgeared]

Interesting situation. If you do not have control over the network, this does create a challenge. Another option would be to build your own network that you can control. If you install your own network router and connect the WAN interface to this network, it can get an IP address via DHCP. Then, you can do anything you want on the private side of this network. Of course, it would be easier if you just work with whoever is controlling this network to allow you to have one or more static IP addresses.

[@itgeared]

You could also leave your server obtaining a DHCP address if the configuration of that DHCP service will ensure that your DHCP address will absolutely not change. When you install roles on your server, the wizard may warn you of using a dynamic but you could technically have a dynamic IP address configured. It will work fine unless your IP changes. If this happens, you will likely encounter network issues.

[@apexedition1494]

My server with active directory/domain controller crashed .. And I have to format it... Although all PC connected to the domain is working fine and both the administrator user name and password is also working fine... But am afraid so how do I remove the domain from each users PC and not loose their profile and software installed

[@itgeared]

You really should try to get the server operational again, then add a secondary domain controller to have your directory services availalbe to not impact your clients. Once you have a secondary server, you can then safely demote the crashed system from Active Directory. If you are not able to bring up this crashed system to allow you to bring up a secondary, then you can proceed with unjoining the users' PCs. You wont loose software applications that are installed but you are correct that the profile is tied to the domain membership. Once you bring up a new domain and rejoin the users' PCs, even if the name of the domain is the same, the PCs will recognize this as a different domain and when you users sign in, they will get a new profile. However, you can do some manual work (or script it) to copy over the previous profiles to the new profiles that may be created once the users sign in to the new domain. Keep in mind that you will also have to create the new user accounts and any group policy that you have lost. This is why i encourage you to try to recovery the crashed domain controller for the purpose of bringing up a secondary domain controller. If you are succesful in doing that you will not have this impact to your users. Always include in your design at least 2 domain controllers for each domain in your forest.

[@itgeared]

unjoining the PCs from the domain is the reverse process of joining... go to control panel, system properties, computer name tab and join a workgroup. make sure that you have a local account for the users to log in with while the pc is a member of a workgroup.

[@itgeared]

Or... if you build your new domain now while your users can still log in with these cached credentials... rather than unjoining, just have the computers join the new domain. then just copy the profile after the user sucessfully signs into the new domain.

[@Kreemerz]

This is not really an explanation. Just a regurgitation of what is written on the Microsoft site.

[@itgeared]

I’ll be more than happy to elaborate on clarifying what it is that you expected to have a better understanding on. Explaining a process by me or anyone else of course is going to mimic what you find on the vendor’s site. What information are you looking for?

[@Kreemerz]

@@itgeared focus on the IP addresses and where to get them from. That's a vital piece of information. If it's wrong, it won't work. You won't be able to join the PC to the domain. So you really have discuss that in the same video.

[@itgeared]

Thanks for the comments.