QuestionQ167

VerifiedImplementación y administración de Active Directory Domain Services (AD DS) en entornos locales y en la nube

Overview

Company Information

ADatum Corporation is a manufacturing company with a main office in Seattle and two branch offices in Los Angeles and Montreal.

Fabrikam Partnership

ADatum recently partnered with a company named Fabrikam, Inc.

Fabrikam is a manufacturing company with a main office in Boston and a branch office in Orlando.

Both companies plan to work together on several joint projects.

Existing Environment

ADatum AD DS Environment

The on-premises network for ADatum includes an Active Directory Domain Services (AD DS) forest named adatum.com.

The forest contains two domains named adatum.com and east.adatum.com, and the domain controllers shown in the following table.

Scenario Image

Fabrikam AD DS Environment

The on-premises network for Fabrikam includes an AD DS forest named fabrikam.com.

The forest contains two domains named fabrikam.com and south.fabrikam.com.

The fabrikam.com domain contains an organizational unit (OU) named Marketing.

Server Infrastructure

The adatum.com domain contains the servers shown in the following table.

Scenario Image

HyperV1 contains the virtual machines shown in the following table.

Scenario Image

All virtual machines on HyperV1 have only the default management tools installed.

SSPace1 contains the Storage Spaces virtual disks shown in the following table.

Scenario Image

Azure Resources

ADatum has an Azure subscription that contains an Azure AD tenant. Azure AD Connect is configured to synchronize the adatum.com forest with Azure AD.

The subscription contains the virtual networks shown in the following table.

Scenario Image

The subscription contains the Azure Private DNS zones shown in the following table.

Scenario Image

The subscription contains the virtual machines shown in the following table.

Scenario Image

All the servers are in a workgroup.

The subscription contains a storage account named storage1 that has a file share named share1.

Requirements

Planned Changes

ADatum plans to implement these changes:

  • Sync Data1 to share1.
  • Configure an Azure runbook named Task1.
  • Allow Azure AD users to sign in to Server1.
  • Create an Azure DNS Private Resolver with the following settings:
    • Name: Private1
    • Region: West US
    • Virtual network: VNet1
    • Inbound endpoint: SubnetB
  • Enable users in the adatum.com domain to access resources in the south.fabrikam.com domain.

Technical Requirements

ADatum identifies these technical requirements:

  • The data on SSPace1 must always be available.
  • DC2 must become the schema master if DC1 fails.
  • VM3 must be configured to enable per-folder quotas.
  • Trusts must allow access only to the required resources.
  • Users in the Marketing OU must have access to storage1.
  • Azure Automanage must be used on all supported Azure virtual machines.
  • A direct SSH session must be used to manage all supported virtual machines on HyperV1.

You need to meet the technical requirements for the schema master.

You run ntdsutil.exe.

Which five commands should you run in sequence?

Drag & Drop
Explanation

A failed schema-master role holder requires the role to be seized by another domain controller. Ntdsutil enters FSMO role maintenance, connects to the intended new role holder, exits the connection context, and then runs the schema-master seizure command. Metadata cleanup is a separate procedure and is not part of this role-seizure sequence.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!