Step 3: Verify if the schema extension was successful - Amazon Directory Service
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Step 3: Verify if the schema extension was successful

After you have finished the import process, it is important to verify that schema updates were applied to your directory. This is especially critical before you migrate or update any application that relies on the schema update. You can do this using a variety of different LDAP tools or by writing a test tool that issues the appropriate LDAP commands.

This procedure uses the Active Directory Schema Snap-in and/or PowerShell to verify that the schema updates were applied. You must run these tools from a computer that is domain joined to your Amazon Managed Microsoft AD. This can be a Windows server running in your on-premises network with access to your virtual private cloud (VPC) or through a virtual private network (VPN) connection. You can also run these tools on an Amazon EC2 Windows instance (see How to launch a new EC2 instance with seamless domain join).

To verify using the Active Directory Schema Snap-in
  1. Install the Active Directory Schema Snap-In using the instructions on the TechNet website.

  2. Open the Microsoft Management Console (MMC) and expand the AD Schema tree for your directory.

  3. Navigate through the Classes and Attributes folders until you find the schema changes that you made earlier.

To verify using PowerShell
  1. Open a PowerShell window.

  2. Use the Get-ADObject cmdlet as shown below to verify the schema change. For example:

    get-adobject -Identity 'CN=Shoe-Size,CN=Schema,CN=Configuration,DC=example,DC=com' -Properties *

Optional step

Add a value to the new attribute - Optional