スキーマ拡張を開始すると、マネージド Microsoft AD はスキーマの変更を適用する前にスキーマ拡張バックアップを自動的に作成します。スキーマ拡張後に問題が発生した場合は、このバックアップを使用してドメインを復元できます。スキーマ拡張機能のバックアップを特定するには、ドメイン用に作成されたバックアップを一覧表示します。
OPERATION_ID は、スキーマ拡張のオペレーション ID に置き換えます。例: operation-1234567890-98765a1b2c3d4e5-e6f7g8-9h0i1j2。
スキーマ拡張を確認する
マネージド Microsoft AD インスタンスのスキーマを拡張したら、アプリケーションを Active Directory と統合する前に、スキーマの変更を確認することが重要です。スキーマの変更は、さまざまなツールと方法で確認できます。以下の各セクションでは、これらのいずれかの方法を使用してスキーマの変更を確認する方法について説明します。
Active Directory スキーマ スナップイン
Windows PowerShell
Active Directory スキーマ スナップイン
Active Directory スキーマ スナップインを使用してスキーマの変更を確認する手順は次のとおりです。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2024-12-21 UTC。"],[],[],null,["# Extend schema\n\nThis document explains how to extend the schema in a Managed Service for Microsoft Active Directory instance.\n\nBefore you begin\n----------------\n\nBefore you begin, do the following:\n\n1. [Create a Managed Microsoft AD domain](/managed-microsoft-ad/docs/create-domain).\n2. [Create and join a Windows VM to the domain](/managed-microsoft-ad/docs/quickstart-domain-join-windows).\n3. Make sure that you read [About schema extension](/managed-microsoft-ad/docs/schema-extension) and understand these [considerations](/managed-microsoft-ad/docs/schema-extension#considerations).\n4. Prepare the LDIF file with the schema changes. For more information, see [How to prepare your LDIF file](/managed-microsoft-ad/docs/schema-extension#prepare-ldif).\n5. Make sure that you have any one of the following Identity and Access Management (IAM) user roles:\n\n - Google Cloud Managed Identities Domain Admin (`roles/managedidentities.domainAdmin`)\n - Google Cloud Managed Identities Admin (`roles/managedidentities.admin`)\n\n For more information, see [Cloud Managed Identities roles](/iam/docs/understanding-roles#cloud-managed-identities-roles).\n\nExtend the schema\n-----------------\n\nWhen you initiate schema extension, Managed Microsoft AD creates a [schema extension backup](/managed-microsoft-ad/docs/backup-restore#overview) automatically before applying the schema changes. You can use this backup to [restore the domain](/managed-microsoft-ad/docs/backup-restore#restore-backup) if you encounter any problems after schema extension. To identify the schema extension backup, you can [list the backups](/managed-microsoft-ad/docs/backup-restore#list-backup) created for your domain.\n\nTo extend the schema, run the following gcloud CLI command: \n\n```\ngcloud active-directory domains extend-schema DOMAIN_NAME --ldif-file=LDIF_FILE_PATH \\\n --description=SCHEMA_EXTENSION_DESCRIPTION --project=DOMAIN_RESOURCE_PROJECT_ID --async\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eDOMAIN_NAME\u003c/var\u003e: The name of your Managed Microsoft AD domain. For example, `my-domain.example.com`.\n- \u003cvar translate=\"no\"\u003eLDIF_FILE_PATH\u003c/var\u003e: The path of the LDIF file with the schema changes. The maximum file size is limited to 1 MB.\n- \u003cvar translate=\"no\"\u003eSCHEMA_EXTENSION_DESCRIPTION\u003c/var\u003e: The description of the schema changes.\n- \u003cvar translate=\"no\"\u003eDOMAIN_RESOURCE_PROJECT_ID\u003c/var\u003e: The project ID of the domain resource project. For example, `my-project`.\n\nManaged Microsoft AD initiates schema extension and responds with an operation ID which you can use to track the completion of schema extension.\n\nTo check the status of your schema extension, run the following gcloud CLI command: \n\n```\ngcloud active-directory operations describe OPERATION_ID\n```\n\nReplace \u003cvar translate=\"no\"\u003eOPERATION_ID\u003c/var\u003e with the operation ID of your schema extension. For example, `operation-1234567890-98765a1b2c3d4e5-e6f7g8-9h0i1j2`.\n\nVerify the schema extension\n---------------------------\n\nAfter you extend the schema of your Managed Microsoft AD instance, it's important you verify the schema changes before integrating your applications with Active Directory. You can verify the schema changes using different tools and approaches. In the following sections, we explain how you can verify the schema changes using any one of these approaches:\n\n1. Active Directory Schema Snap-In\n2. Windows PowerShell\n\n### Active Directory Schema Snap-In\n\nTo verify the schema changes using Active Directory Schema Snap-In, do the following:\n\n1. Login to your domain-joined VM as a delegated administrator.\n2. [Install the **Active Directory Schema Snap-In**](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732110(v=ws.11)?redirectedfrom=MSDN).\n3. Open the **Microsoft Management Console (MMC)**.\n4. Expand the **Active Directory Schema** tree for your directory.\n5. Verify if you can see the changes in classes and attributes of the schema.\n\n### Windows PowerShell\n\nTo verify the schema changes using Windows PowerShell, use `Get-ADObject` cmdlet. Run the following command in Windows PowerShell: \n\n```\nget-adobject -Identity 'cn=ATTRIBUTE,cn=Schema,cn=Configuration,dc=ROOT_DOMAIN,dc=TOP_LEVEL_DOMAIN' -Properties *\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eATTRIBUTE\u003c/var\u003e: The name of an attribute in your schema. For example, `example-attribute`.\n- \u003cvar translate=\"no\"\u003eROOT_DOMAIN\u003c/var\u003e: The root domain of your domain name. For example, if your domain name is `example.com`, enter `example`.\n- \u003cvar translate=\"no\"\u003eTOP_LEVEL_DOMAIN\u003c/var\u003e: The top-level domain of your domain name. For example, if your domain name is `example.com`, enter `com`.\n\nIn the response, verify if you can see the changes in classes and attributes of the schema.\n\nWhat's next\n-----------\n\n- [Back up and restore a domain](/managed-microsoft-ad/docs/backup-restore)"]]