•You have a basic understanding of AD concepts.
•You have an AD user account with the administrator role in the AD domain you plan to use when configuring support for AD in HCP.
•If you plan to secure communication between HCP and AD:
oThe applicable AD domain is configured with a certificate authority.
oYou have access to a Windows server running the AD certificate authority.
oYou have access to the Windows client from which you plan to access the HCP System Management Console for the purpose of configuring support for AD.
•For creating the AD group and user account, you have access to a Windows or Unix server from which you can access AD.
•The OU or CN in which you want to create the AD group already exists in the applicable domain.
•The OU or CN in which you want to create the AD user account already exists in the applicable domain. This can be, but does not have to be, the same OU or CN as the one in which you create the AD group.
•The OU or CN in which computer accounts will be created for the HCP nodes already exists in the applicable domain. This is the OU or CN you specify as the organizational unit in the HCP configuration of support for AD. The default for this in HCP is the CN Computers.
•Your DNS is configured on a Windows server.
•Your DNS contains a stub zone for HCP that’s configured for AD integration. For information on configuring the HCP stub zone, see Configuring an HCP secondary zone or stub zone in Windows.
•Your DNS contains a forward lookup zone definition for the applicable AD domain.
•You have access to a Windows server from which you can configure your DNS.
•Optionally, you have pre-populated the domain controller filter list even if HCP was not joined to Active Directory at the time. For information on adding domains and domain controllers to the domain controller filter list, see Configuring support for Active Directory.
© 2017 Hitachi Data Systems Corporation. All rights reserved.