| Instance Name |
used primarily to identify the Windows Service name and display name |
| Ports |
sets the port numbers to be used for LDAP and
LDAPS Listeners. The default LDAP port is 389,
LDAPS is 636. If these ports are in use on the
server, the setup wizard selects new ports. Work
with your network administrator to determine the
best ports to use |
| Application Directory Partition |
creates an application directory partition.
Not needed at this step, we recommend creating the
new partition now. A good practice is to use the
same distinguished name as your forest or domain,
but replace the highest level domain with adam
instead of com or local. For example, if your
forest partition is
dc=myCompany,dc=com, you
could create the ADAM partition as
dc=myCompany,dc=adam |
| File Locations |
selects the location(s) for the ADAM
partition data. |
| Service Account Selection |
selects a service account that the instance
runs as. For stand-alone services, you can use the
default network service account. If you plan on
using replicas, you need to use an account that
has access to all ADAM instances. |
| ADAM Administrators |
the delegation on the ADAM directory that
leverages Windows integrated authentication. This
is how the initial access is granted for
administration. Once the initial account is
granted rights, this user or group delegates
rights to other Windows users or ADAM users. You
can select the default to only grant admin access
to the current user, or grant access to a
different user or group based on your
needs. |
| Import LDIF Files |
the files to import. MS-UserProxy is the most
important file to import, but it’s worth adding
all available files since there is little overhead
to the schema and you won’t have to worry about
extending it later if your needs expand. Confirm
the details and the wizard complete the
configuration. |