Installing Active Directory Domain Services in Windows Server 2022, along with DNS and DHCP
ฝัง
- เผยแพร่เมื่อ 7 ก.ค. 2024
- In this video, I perform a complete installation of Active Directory Domain Services in a Windows Server 2022 virtual machine. I promote the server to a Domain Controller and verify the corresponding Domain Name System (DNS). I also deploy the DHCP server role to provide dynamic IPv4 addressing to a Windows 10 Professional host, which I then add to the Active Directory Domain. I finally create a small set of nested Organizational Units along with an domain admin user and a regular user, which I verify using the Windows 10 PC.
Time Stamps
==================================================
00:00 Introduction
01:09 Infrastructure Overview
02:53 Installation of AD DS Server Role
05:28 Promotion of Server to Domain Controller
06:13 Domain Name Best Practices
12:27 Server Manager Tour of New Domain Controller
13:16 DNS Verification
16:54 Installation of DHCP Server Role
20:23 Joining a Client to the Domain
24:16 Tour of Active Directory Users and Computers
25:40 Creation of Organizational Units
26:58 Creation of Active Directory Users
30:30 Logging in as an AD User
32:48 Summary
==================================================
Links Mentioned in the Video
==================================================
Naming conventions in Active Directory for computers, domains, sites, and OUs - Microsoft Official Documentation
docs.microsoft.com/en-us/trou...
Active Directory: Best Practices for Internal Domain and Network Names
social.technet.microsoft.com/...
Active Directory: Design Considerations and Best Practices
social.technet.microsoft.com/...
Split Brain DNS -- Use DNS Policy for Split-Brain DNS Deployment
docs.microsoft.com/en-us/wind...
==================================================
Errata:
I realized after posting that I accidentally created a domain called Int.Acme.Com instead of the domain stated in my topology, which was Corp.Acme.Com. Sorry for the confusion. - วิทยาศาสตร์และเทคโนโลยี
![[TH] VCT Pacific Stage 2 - Week 4 Day 3 // GEN vs TS | PRX vs ZETA](http://i.ytimg.com/vi/nspkjQuZve0/mqdefault.jpg)
![ตีสิบเดย์ [FULL] | ครอบครัวสะท้านทุ่ง "นางบี & อ้ายสติ๊ก"](http://i.ytimg.com/vi/A1rhYcxxNtA/mqdefault.jpg)
Fabulous teaching skills, 100% worth spending 30 minutes watching this video
This is by far the easiest and best video to follow to configure Server and ADUC functions.
You're my Master I am your Student , THank you master for sharing your Knowledge. I am a beginer in Windows Server But i was able to create a ACtive Directory like i have been doing this for 5 years
This is, by far, one of the best videos I've ever seen about IT. You're well organized in your videos and the tie stamps really helps out. Thank you and good luck with your channel.
Thanks Joseph. I appreciate the kind comments and support. Lots more in the works!
Instant Like for the talking dog! Love it!
What an amazing straightforward and easily understandable video. Great educator!
You're the best Troy. You make a relatively complicated task seem effortless. Thank you.
wow . i have never seen someone who is gifted when it comes to explaining , looking forwards to see all your videos .
You are insane, thanks a lot for this video!
Started new, did it for the first time and worked perfectly fine, you are the GOAT
This guy's good. Just taught me everything I needed to know in such a simiple and concise way with examples and easy to navigate bookmarks / logic in this video walkthrough. One of the best lab setups I've been through while learning how to set up my own Active Directory lab to learn.
The way you explain is great, not only do we achieve what we want but we also understand how it works. Thank you. You have earned yourself a subscriber! I'm sure your channel will skyrocket soon and I will be proud that I subscribed to you early in your journey!
Thank you so much for the clear and concise explanation. I have to learn this for my upcoming QA interview. Cheers
Well this is the first video of yours which came up on my list, I had to watch it and found it to be very clear and concise, for that reason I just had to subscribe. Best of luck with your channel I hope it goes a long way 👍
Thanks for you tutorials. Helped me prepare for a job interview.
Thank you so much for explaining the Reverse-Lookup Zone!
Thank you for creating such great videos!
Dude you're a legend at teaching. Love your style. You're worth many more subscribers!
Awesome video! Keep it up!
Your tuts have helped me immensely!! Thanks for this very SIMPLIFIED approach.
Thanks!
Fantastic help, greatly appreciated.
You explain very well without being boring , Thank You
The Best so Far!!!
Hey, Troy. Amazing tutorial. You are such a great teacher so I have no questions about it. Greetings from Colombia!😎
oh man! you saved my day. I love you ;) greetings from Colombia.
Very helpful. Great presenting format.
Excellent teaching on AD Config. good job.
Awesome tutorial for the beginners! Keep it up Sir!
Thanks a lot, Marcelo! I appreciate the comment!
Amazing lab. Thanks Prof. Troy
Excellent teaching on AD config.
Thank you for this video. Very well done
Sir Troy Berg explains and demonstrates the concept of ADDS, DHCP and adding/joining computers into domains. I have done this on hyper visor after learning from him as well how virtual switches work in hypervisor. i love the way you explain the concepts. Super Awesome and Wonderful
Excelente video.
Great video and eduative
Fantastic tutorial clearly explained congratulations! Helped me to install and configure the server properly under the Vmware system.
Will be great also if you can someday explain how to get to work properly Deployment Service too. Thank you very much Troy.
Your dog is so cute and your video is very informative thanks for uploading.
the best videos I've ever seen thx🤩
New subscriber, Thank you for videos appreciate you hard work. Thank you Troy.
This guy is really good.
Great vid thanks for your help
Thank you. New student here
sir layshl 3likk !!
Thanks for your Very good tutorial
You're welcome Marc. Glad you found it helpful!
You are the best
very well explained tq sir.
Thanks for information
awesome, thanks
Thanku soo much,, best explanation, ❤❤❤❤❤ it worked 🎉🎉🎉🎉
nice video to watch. with a bonus of cute dog. thank you very much for your effort sir.
Good explanation video about ad dc
Thanks Premchand!
Thanks for your help
Glad you found it helpful!
Well-defined
thank you very much
Thanks
lol greatttttt
Thank you! Very informative.
I opened up the server manager but I don’t see the local server, did I miss anything? It’s like that both on Hyper V VM and local hosting machine. Windows 10 11 pro respectively.
You should make an Exchange 2019 full install and config video and possibly exchange clustering as well as second part.
Great teaching. Thanks for making it simple. But, I have an issue after setting up mine in a live environment. Everything was fine except that joining the client PC to the domain takes a very long time and I could not log in with my AD user account after the joining is done. I was getting an error of "The security database on the server does not have a computer account for this workstation trust relationship". Please anyone with what could cause these?
Great video, just lacks the part where you're setting the domain admin credentials.
Question. I have set up DNS and DHCP on Win Server 2022. Im currently trying to configure a seperate laptop to use the Server to gain a DHCP server address. Trouble is when i set the DHCP to Automatic, it looks at my home router for an address. Ive modified the DNS server settings but unsure where im going wrong with DHCP
I'm having trouble connecting my DC01 to the internet so i can try to access azure portal. I have the VM set for external switch. But no luck at all. Any advice is appreciated.
Any chance you can throw pfsense into the config? As well as setup for multiple subnets
he is it necesari to have dhcp handle by windows server ? i have my router setup to give all the machines the DNS from the windows server and the router manage the DHCP ... thanks for the video really helpful and well explained
The domain administrator at 12'08"; when was that created? Is it the Administrator account set when installing Windows Server? The local account? Tnx
In the enterprise IT practice, due to a large number of computers need to join the domain, then for security, can we frist to do create a computer name in DC, and then can use admin rights to make this one computer to join the domain successfully? On the contrary, if there is no first created name in the DC computer , is not able to join, this process so that the DC client computer name and the user side of the computer can be the same, only match the computer can make the computer successfully into the domain, which is also for security purposes of a method!
Great, I need some guidance.
How to add a system in domain. The system is not on local network, it's using different internet and it's located at field.
Curious, I have done everything as you stated. However users are seeing SYSVOL and NETLOGON folders in the Network Shares. Now I have logged into AD DS before at a company I worked at and those file where not present if I went into Network. Actually Network was blank and you had to know the location of the Shared folder and manually map the Shared folder. So what gives here? How do I make the SYSVOL and NETLOGON not visible to users when they click on Network?
I have a question I am building a home lab for learning purposes and I would like the VM to communicate with my regular PC clients as well. Question is can I use my existing DHCP server on the VM and allow the PCs to be joined into the test domain? If the DC server does need its own DHCP server how do I make both networks talk together?
I am just an enthusiast and in to IT, and I hate reading lol. I have setup a home ad network . And I wish I found your video sooner 😆🤙. Now I will go through and clean up a bit. And I was able to get roaming profiles working. 😮. Wish there was away to keep the domain user names saved on the log in screen for win 11 when you restart, I’ve tried a few things but only last user stays there any ideas 💡 😊
Hi try, but when i try to connect i get login window and i get feedback domain not exist, work also for domain like home.local ?
Very good tutorial, but how can I get internet on
PC01
I was hoping if someone could help me out. I have a server that does NOT have a cd-rom and I am trying to install Windows Server 2022 Essentials. However MS no longer has an iso image for W2022E for download. Does anyone know how someone can get the media for this?
Troy - as you showed in this video and as I did in my Hyper V lab along side..... around 20:00 PC-1 (not on the domain yet) gets a IP address via DHCP. So Microsoft Server 2022 AD/DHCP will give out IP address to any node that ask for a DHCP regardless if they are on the domain or not? I realize a rougue computer wont be able to join a domain just because it gets a IP address from the server but still.... isnt that kind of a security flaw for a Domain controller to dish out IP addresses to any node that ask. I guess it does need to be on the network to communicate back to the server in order to start the process of joinging the domain.....
Great question, Jason. You are correct -- the DHCP server will indeed hand out an address to any workstation that requests one, regardless if that machine is domain-joined or not. And you're right, simply having an IP address on the same network as the domain controller does not by default grant the machine any access to the domain environment.
That said, we generally want to leave as little to chance as possible, and having rogue devices connect to our network and challenge our admin passwords isn't the optimum scenario. The way we handle this in a production environment is:
1) we control physical access to the network switches;
2) we control (or do our best to control) physical access to the public-facing Ethernet ports that are in offices, at desks, etc. that lead to the switch;
3) we add MAC-based port security to the switchports to which the endpoints connect (e.g. if an unrecognized device connects the switch, we can instruct the switch to disable the port in milliseconds), or we add 802.1x port authentication (if the switch supports it) which also restricts unauthorized clients from accessing the LAN;
4) we deploy a public key infrastructure (PKI) that issues digital certificates to authenticate the identity of users and devices on the network.
We always strive for a layered approach (effectively known as defense in depth). Usually we end up with a combination of all of these things.
Hope that helps. Again, great question.
I can not seem to get my windows 10 workstation on the DNS. My workstation is not utilizing Hyper-V it is utilizing Intel(R) 82574jL Gigabit Network Connection. I am unsure how to get it on the domain utilizing this connection. Do you have any insight how to fix this issue?
Great video
Can you please tell me how can we get internet access.
I'm using vmware to build up this lab.
Hi,
Can you do all of this only using Server 2022 core?
Crucially, you set a static IP first thing. Do you have a video on how to do this? I'm absolutely unable to join the user PC to the domain.
You bet.
th-cam.com/video/aZ18I4tIQvU/w-d-xo.htmlsi=Jt1AQ_qG9AvJZKjF
I do that at around the 16:49 mark.
Hope that helps!
I have an issue my server and client have the same IP address. Not sure if it makes a difference but my client's PC's network icon is working and my server is not, both can still access the internet. I noticed yours both are shown as not working. Do you need to add the client to the server before Joining the Client to the Domain?
Resolved I changed Settings>Network>Internal Network on server and workstation
thank you sir, very helpful. It would be more complete if Group Policy Management was added, considering that GPOs are installed with Active Directory
What network mode are you using in virtual box?
Internal Network
I came across quite an interesting scenario when installing DNS and I'm curious if there's a solution or advice on how to understand this or how to proceed.
I tried following the steps mentioned in this video using *External* switch but received a warning message saying _"No static IP addresses were found on this computer."_ I know what you're thinking, _"It says it right there, you didn't set a static IP."_ However, I know that I did but, just to be sure, I went and confirmed that I, in fact, did set a static IP address on the server and the host PC, for that matter.
The interesting part is that *if I change the switch* that the VM is using from *External* to Default, the problem goes away. Then, if I set the VM back to use *External* switch and try installing DNS role again, the warning popped up. It looks like there's something about *External* switch that DNS looks at and says _"I see that DHCP on this server is disabled and an IP has been statically assigned. I see that DHCP on host PC has been disabled and the host PC's IP address has been statically assigned. Yet, I still will tell you that you didn't set a static IP address."_ I'm not sure how I can make a static IP more static. This makes me think that I must be missing something.
For reference and added context, I've uploaded screenshots of both host PC configuration and VM configuration here:
imgur.com/a/89YoXX4
Again, this comes up only when I try to install DNS on a VM that is using *External* switch. Is there an explanation behind what is going on there or a solution to the warning message? If I see this in a real, corporate environment, what should I do?
Hi Mikhail,
Thanks for being so thorough in your description. Interesting troubleshooting challenge.
I quickly spun up a VM with an external switch (shared with my host operating system) in the configuration you described and as soon as I started the "Add Roles and Features Wizard" to add the DNS role, I was able to emulate the same error you got stating there is no static IP assigned to the VM, even though there very much is.
Please don't roll your eyes when I suggest this, but once you assign the static IP to your virtual machine, reboot the VM.
Countless times I've seen Windows Client Hyper-V read the NIC settings incorrectly, and a reboot of the virtual machine tends to clear that right up, especially if you've made multiple changes to the TCP/IP settings on the VM.
In my case, I tried exactly that. I rebooted the VM then restarted the installation wizard for the DNS server role and the error disappeared.
So based on your screenshots and my attempt to recreate your issue, your other settings look okay, so I hope you get the same successful result that I got.
A quick heads up though -- remember that under this configuration your virtual machine is effectively part of your home LAN. If you add the DNS role as well as roles like DHCP, you're introducing new servers and services into your home environment that other devices will be able to communicate with. If you're just building this server for experimental and learning purposes, you'll want to ensure that you're careful not to disrupt your home network. :)
Hope that helps!
Hello sir! Thank you for quick reply and for the caution about introducing VMs with DNS/DHCP roles to my home LAN! I didn't think about that. I'll have to see what the impact of adding a DNS server to my LAN will be.
Regarding the _"No static IP address"_ issues, I tried restarting the VM but, unfortunately that didn't resolve the issue. The warning message keeps popping up. It's so strange, and quite ironic (because IP address of Default Gateway and DNS on Default switch changes with each host PC reboot), that the warning message about lack of static IP is *not* coming up when *Default* switch is used but does show up when *External* switch is used.
I'll keep looking for an answer and will appreciate any additional thoughts or insights that you can provide or if there's anything that you can suggest I would try.
@@mikhailbespartochnyy2555
Thanks for the update! I know I might have sounded like I was ducking the problem by suggesting a simple reboot of the VM, but when I was able to recreate the error you described, that was the fix that honestly worked for me. I'm a huge fan of trying the simplest solutions first.
Since that didn't work, the next thing to try is to start with the foundational elements. Here's what I'd try next:
1) You mentioned that you've been experimentng with static IP assignments as well as the preferred DNS setting on your host machine. When I tried to emulate your network to recreate the error, I didn't change any settings on my host machine. Let's go back to leaving your host with a dynamically assigned address from your home LAN. That'll ensure the machine is connected based on the TCP/IP settings received from your network's router/DHCP server, and after that you should be able to leave your host machine alone.
2) Second, let's temporarily allow your VM to receive a DHCP from your home LAN via your external switch by setting the adapter to received addressing information automatically. Once that's done, use the "ipconfig /all" command to retrieve the leased address. Once you know that address, let's use THAT address as your static IP assignment. That's what I chose to do in my experiment to ensure I'm not accidentally using a currently leased address in my home network.
3) Third, when you apply that new static IP address to your VM, use TWO preferred DNS servers. From your screenshots, it looks like your LAN default DNS server is 192.168.1.254. Make that your primary preferred DNS server when you assign your addressing, but then also add the IP of your VM, as it will in fact become a DNS resource for the VM as well. For example, if your VM has the address of 192.168.1.20, add that address as your second preferred DNS server. During the installation of the role, the server will be adding this address anyway (in the form of the localhost 127.0.0.1 address). No harm in applying it beforehand, and that's another thing that I did. Verify again with ipconfig /all that the changes are accepted.
4) After those changes are made, reboot the VM.
5) When the VM turns back on, in your Hyper-V manager window there's a pane near the bottom that displays the summary settings for the virtual machine. This lower window has three tabs -- Summary, Memory, and Networking. Click on the networking tab, and verify that Hyper-V is seeing the correct IPv4 address that you statically assigned. If you see don't see the correct address displayed, we know we're chasing a different problem.
6) Lastly -- just to double-check, when you apply your static IP address to your VM, you're changing it via the control panel of your VM (specifically, the Network and Sharing Settings management window or via server manager INSIDE the virtual machine), correct? I ask this because it's possible to statically apply an address directly on the vEthernet adapter on your host machine, and that will result in inconsistent results.
Finally, are you building this VM for strictly experimental and learning purposes, or do you ultimately want this machine to be part of your home LAN environment?
I ask because if you're just building this machine to experiment with and learn some of the functionalities of Server 2022, then you might want to consider using a private switch for the VM. By default a private switch will not grant any Internet access to your VM, but for learning purposes this generally doesn't matter. When I'm teaching virtualization and LAN administration, I use private-switched VM networks as my mainstay environment. They are safe, isolated from your home LAN, and incredibly flexible. If the above ideas don't help, try assigning a private switch and a static IP on your VM. It'll be interesting to see if you get the same error.
Let me know if any of these ideas help!
Thanks again.
Hello, sir! Thanks again for the reply! Unfortunately, these steps didn't solve the issue.
For what it's worth, the warning did go away when I used a *Private* switch but that won't work for me as I do need the VM to have access to the internet.
For point 5), when I first went to the Networking tab, the IP address was blank but the IP address did show up and it did match the static IP that I set after I clicked the Refresh button in Hyper-V Manager.
As for point 6), yes that's correct, I have been setting static IP for the VM from inside the VM, more specifically from the Server Manager > Local Server > Ethernet which opens up the *Control Panel\Network and Internet\Network Connections* window and shows the Ethernet adapter that the VM is using.
I even went the extreme route, reformatted my host PC's hard drive and reinstalled Windows 10 OS on it and I am still receiving the warning message.
I'll keep looking and will share a solution if I'll find one. Thank you again for your help and your time! I truly appreciate it!
No talking dogs
Bro i say thanks to god for your existence!! 🫡
Glad to help! Thanks for commenting!