Dashboard

Active Directory & Identity with Windows Server

0%

0/1 Lessons

Course Introduction

• 1min

0 / 1 lessons complete

Getting Started with Active Directory Domain Services

• 52min

0 / 6 lessons complete

Introduction to Active Directory Users & Computers

• 1hr 27min

0 / 10 lessons complete

Adding a Second Domain Controller

• 1hr 31min

0 / 7 lessons complete

Active Directory Backups

• 1hr 24min

0 / 5 lessons complete

How to Administrate Active Directory with Windows PowerShell

• 1hr 58min

0 / 7 lessons complete

Administrating AD SS (Active Directory Sites and Services)

• 1hr 3min

0 / 5 lessons complete

Active Directory Trusts

• 54min

0 / 5 lessons complete

Modifying the Active Directory Schema

• 43min

0 / 3 lessons complete

Course Conclusion

• 2min

0 / 1 lessons complete

Windows Domain Quiz

Instructions

Q&A (0)

Resources (0)

Saving Progress...

Resources

There are no resources for this lesson.

The topics learned in this module will apply to Windows Server 2012 - 2019. Probably over 90% of the course also applies to older versions of Active Directory (2003 - 2008) also.

In this course you are going to learn and get hands on experience on the following topics:

  • Getting Started with Active Directory Domain Services
  • Introduction to Active Directory Users and Computers
  • Adding a Second Domain Controller
  • Active Directory Backups
  • AD Administration with PowerShell
  • Active Directory Sites and Services
  • Windows Trusts
  • Modifying the Active Directory Schema
  • ...And more!

If you have any questions please post them on the forums here.

Click the continue button below to get started!

5 1 vote
Lesson Rating
Subscribe
Notify of
5 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments

profile avatar
Barry Free(@otis-free)
#75318
Member
1 year ago

You should not have to configure if PC is pulling IP Address from DHCP. Your answer is correct if you needed to configure workstations manually. In an enterprise corporate environment DHCP sets this up for you.

1
profile avatar
Paul Hill(@paulh)
Author
#75319
Reply to  Barry Free
1 year ago

I am not sure which question you’re referring to but you are right in most scenarios. Usually static IP addresses are reserved for servers or if DHCP is not configured.

0
profile avatar
IT Mike(@mikew)
Member
#76457
Reply to  Paul Hill
9 months ago

It is the default gateway question and I have to agree with Barry on this one that the DHCP would provide this information. Typically no one is going to manually setup all of the TCP/IP on all client pc’s – even if ultimately they are being pointed towards the Windows Domain. It’s not really a wrong answer per se but it’s all in the wording.

1
profile avatar
jamesd2(@jamesd2)
#76878
Member
4 months ago

What are the best practices for naming root domain?
Why is it not best practice to use .local?
How do we link our DC to a website we may be hosting on Godaddy?
Thank you.

0
profile avatar
Ricardo P(@ricardop)
Admin
#76880
Reply to  jamesd2
4 months ago

Hi profile avatar James Daly

You can use your internet domain name like domain.com for naming the root domain.

Using “.local” as your Active Directory domain can lead to challenges with name resolution and is a reserved domain name for Multicast DNS plus other issues.

You can add a DNS entry for the website to DNS Console. If it is the opposite way, to resolve your DC you add the entry of the Public IP to Godaddy of your DC and a port forward on the firewall to the DC depending on the service you want to use like RDP (not recommended).

Ricardo

Last edited 4 months ago by Ricardo P
1