Active Directory Course Prerequisites

Before starting a course on Active Directory (AD), a Windows Server administrator would benefit from having experience with the following Windows Server operating systems and related foundational tasks:

1. Windows Server 2012 or Later – Since many Active Directory concepts and features were refined in Windows Server 2012 and beyond, it’s helpful to have experience with at least Windows Server 2012, and ideally, more recent versions like Windows Server 2016, 2019, or 2022.
2. Basic Server Setup and Configuration – Experience with installing and configuring Windows Server, including setting up roles and features, configuring IP addressing, and basic security settings.
3. Understanding of Server Roles and Features – Familiarity with various server roles, particularly those related to networking and security, such as DNS, DHCP, and Group Policy Management. DNS is critical since AD heavily relies on DNS for network resource identification.
4. User and Group Management – Basic experience with managing local users and groups, as AD extends and scales user and group management to the domain level.
5. File and Folder Permissions – Familiarity with NTFS permissions and file sharing, which are essential when managing resources within an AD environment.
6. Networking Basics – Understanding TCP/IP networking, subnets, and network troubleshooting to address connectivity issues in a domain environment.

These foundational skills in Windows Server management and networking will help an administrator understand and apply Active Directory concepts more effectively. This course is intended for Active Directory Technology Specialists, Server and Enterprise Administrators who want to learn how to implement Active Directory Domain Services in Windows Server environments. Those participating in this course would be interested in learning how to secure domains by using Group Policies, restore, monitor, and troubleshoot configuration to ensure trouble-free operation of Active Directory Domain Services.

In the 1970s and 1980s, X.25 networks were some of the first widely used “cloud” services. They allowed companies to access mainframe computers remotely and are considered by some to be the starting point for the Enterprise Wide Area Network (WAN). Before that, connecting local networks (LANs) in different locations required dedicated “point-to-point leased lines,” which were direct connections between locations. These connections were typically low-speed (56 Kbps) or expensive T1/E1 lines, and because they were costly, fractional versions of T1 or T3 connections were developed to lower the cost.
At first, companies used remote bridges to connect these lines, but later, a new device called a router—made popular by Cisco—took over. In the early 1990s, Frame Relay service arrived, changing everything. With Frame Relay, businesses could connect to a “cloud” network provided by a service company, meaning they didn’t have to manage individual connections for every site they wanted to link together. Frame Relay lowered monthly WAN costs, reduced the number of physical connections needed, and allowed companies to share high-cost bandwidth more efficiently across multiple locations. It also required less expensive router hardware than previous point-to-point setups. These advantages drove companies to adopt Frame Relay quickly, cutting both operating costs (OpEx) and capital expenses (CapEx). Within just five years, even cautious businesses like banks had switched to Frame Relay, making it the fastest-adopted WAN service in history, even faster than the Internet.

• Elements of Point-to-Point Leased Lines A point-to-point leased line is the most reliable solution for the communication and connectivity that modern businesses require. Leased, since the service is paid for with a fixed fee for an agreed upon duration and service capacity. The fixed points in a private network are connected through dedicated digital circuits that vary in capacity and speeds. This allows businesses to extend the coverage of the business wide area network using secured, highly-reliable and high-speed network connections.

Network operating system is the term used to describe a networked environment in which various types of resources, such as user, group, and computer accounts, are stored in a central repository that is controlled by administrators and accessible to end users. Typically, a NOS environment is comprised of one or more servers that provide NOS services, such as authentication, authorization, and account manipulation, and multiple end users that access those services. Microsoft's first integrated NOS environment became available in 1990 with the release of Windows NT 3.0, which combined many features of the LAN Manager protocols and of the OS/2 operating system. The NT NOS slowly evolved over the next eight years until Active Directory was first released in beta form in 1997. Under Windows NT, the domain concept was introduced, providing a way to group resources based on administrative and security boundaries. NT domains were flat structures limited to about 40,000 objects (users, groups, and computers). For large organizations, this limitation imposed superficial boundaries on the design of the domain structure. Often, domains were geographically limited as well because the replication of data between domain controllers (for example, servers providing the NOS services to end users) performed poorly over high-latency or low-bandwidth links. Another significant problem with the NT NOS was delegation of administration, which typically tended to be an all-or-nothing matter at the domain level. Microsoft was well aware of these limitations and the need to rearchitect its NOS model into something that would be much more scalable and flexible. It looked to LDAP-based directory services as a possible solution. In the next lesson, you will learn what you need to take this course.

The evolution of network hardware has been pivotal in enhancing Microsoft Azure's cloud computing capabilities. Key developments include:

1. Software-Defined Networking (SDN): Azure has transitioned from traditional hardware-based networking to SDN, allowing for dynamic, scalable, and programmable network configurations. This shift enables rapid deployment and management of network resources, essential for cloud scalability. Microsoft's development of Software for Open Networking in the Cloud (SONiC) exemplifies this approach, providing a robust, open-source network switch platform that enhances flexibility and control over network operations.
2. Accelerated Networking with SmartNICs: To reduce latency and increase throughput, Azure introduced Accelerated Networking, which offloads network processing to specialized hardware known as SmartNICs. These network interface cards handle tasks traditionally managed by the CPU, resulting in lower latency, higher packets per second, reduced jitter, and decreased CPU utilization.
3. Integration of Custom Silicon: Azure has incorporated custom silicon solutions to optimize performance for specific workloads. For instance, the collaboration with Ampere Computing led to the deployment of ARM-based processors in Azure's infrastructure, offering efficient and scalable processing power tailored for cloud environments.
4. Global Network Expansion: Microsoft has significantly expanded its global network infrastructure, connecting over 60 Azure regions and more than 220 data centers worldwide. This extensive network, comprising over 165,000 miles of terrestrial and subsea fiber, ensures high availability and low-latency connectivity for Azure services globally.
5. Cloud-Native Networking Services: Azure has developed cloud-native networking services such as Azure Virtual Network and Azure Virtual WAN, enabling seamless integration of on-premises networks with Azure's cloud infrastructure. These services provide secure, scalable, and manageable networking solutions essential for modern cloud applications.

Through these advancements, Azure's network hardware has evolved to support the demands of modern cloud computing, delivering enhanced performance, scalability, and reliability to its users.