Microsoft: INF200.1x Microsoft Windows Server 2012 Fundamentals: Infrastructure

What you will learn in this course:

• How to install Windows Server 2012 including upgrades, editions, roles, features, and server core.
• How to identify and use the physical and logical components of AD DS, such as forests, domains, and domain controllers.
• How to perform day to day system administrator tasks such as backup and restore, and implementing the Recycle Bin.
• How to create and configure user, group, and computer accounts.
• How to implement Group Policy Objects to enforce standard processes in your organization.

Course Prerequisites:

• Learners should have some general understanding of Windows Server and how it is used.
• Windows PowerShell will be the tool of choice when implementing the features in this course. Learners should have a good foundation in accessing and using simple Windows PowerShell commands. To help in this area the course includes an Appendix on Windows PowerShell Basics.

 There are many resources available for learning the skills necessary to be successful in this course. For example,Microsoft Virtual Academy.

Module 1 – Windows Server Basics
Module 2 – AD DS Logical Components
Module 3 – AD DS Physical Components
Module 4 - Administering AD DS
Module 5 - User Accounts
Module 6 - Group Accounts
Module 7 - Computer Accounts
Module 8 - Group Policy         

Where can you take this course?
Follow this link

Is this course for you?

This course is designed to help you understand Active Directory Domain Services in Windows Server 2012 and Windows Server 2012 R2.

You may already have some familiarity and real world experience with this technology. What follows are some sample

Questions that you would be expected to answer after completing this course. You can use these Questions to decide if the course content will be appropriate for you.  

• If you answer all of these Questions correctly, you may already know the course material.
• If you miss a few Questions, this course will fill in the gaps in your knowledge.
• If you struggle to answer the Questions, this course will definitely help you gain a better understanding of how to use these concepts and technologies.
• If you don't understand the Questions at all, you probably are not ready for this course. We suggest you review the recommended prerequisite knowledge and return to the course after additional self-study.

After completing the course, you should return to this topic and ensure you can easily answer the

Questions. Real world practice will be needed to master these skills, but this course will provide a step in the right direction.

1. What is an Organizational Unit (OU) and why would you create additional OUs?
2. What are the five flexible single master operations (FSMO) roles and where do they exist?
3. What is a trust relationship and which type of trust relationship is used to improve user logon times between two domains in a forest?
4. Which optional AD DS feature enables you to quickly restore objects that have been deleted?
5. What is Server Core and what are some advantages of using it?
6. Which feature can you use to define different password policies and account lockout settings in a domain?
7. Aziz has reported he is unable to sign in to the domain. The error message is, “The trust relationship between this workstation and the primary domain failed.” What is likely the problem and how should you fix it?
8. What is the global catalog and when is it used?
9. What is the global catalog and when is it used?
10. What is an AD DS site and when should you consider creating a site?
11. When should you use an authoritative restore?
12. How are Group Policy settings and a Group Policy preferences different?

 
Answers:

1. An OU is an object in a domain that you can use to store user objects, computer objects, group objects, and other AD DS objects. You typically create additional OUs when you want to delegate control to a specific group or link a Group Policy Object to the OU.
2. FSMO roles are special roles within a forest and domain. There are two FSMO roles at the forest level: Schema Master and Domain Naming Master. There are three FSMO roles at the domain level: RID Master, Infrastructure Master, and PDC Emulator.
3. Trust relationships are authentication pipelines between different domains. Shortcut trusts can be used to improve user logon times between two domains in an Active Directory forest.
4. The Active Directory Recycle Bin, an optional feature of AD DS, provides a simplified process for restoring deleted objects.
5. Server Core is the default Windows Server installation option. Server Core does not have a graphical user interface. Server Core installs fewer components so fewer updates are required. Server Core removes unneeded files so disk space and memory requirements are less. Lastly, fewer files and components means less opportunity for security threats.
6. Fine-grained password policies let you specify different password policies and account lockout policies for different groups of users. For example, executives, administrators, service accounts, or regular users.
7. Most likely the problem is a broken secure channel. You can use Active Directory Users and Computers or PowerShell to reset the computer account and rejoin the computer to the domain.
8. The global catalog is a central directory of every object in the forest. The global catalog is commonly used to provide Exchange email account information and a user’s Universal group memberships.
9. The global catalog is a central directory of every object in the forest. The global catalog is commonly used to provide Exchange email account information and a user’s Universal group memberships.
10. An AD DS site represents the physical structure, or topology, of your network. There are several reasons to consider creating additional sites such as: number of users at a location, slow links between locations, service localization, and AD DS database replication.
11. An authoritative restore is necessary when a known good copy of AD DS has been restored that contains objects that must override the existing state of other objects in the AD DS database.
12. Group policy settings and group policy preferences are different. Preferences are not enforced, can reapply automatically, and can use item-level targeting.