Information Technology Reference
In-Depth Information
7. In the Administrative Credentials for the Configuration Set window, enter administrative
credentials. If both servers are in the same domain and you're logged on to the domain as
an administrator, the currently logged-on account can be used. Click Next.
8. In the Copying Application Directory Partitions window, select which application directory
partitions you want to replicate. (The configuration and schema partitions are always repli-
cated.) Click Next.
9. In the File Locations window, specify where you want the AD LDS files to be stored. By
default, the location is C:\Program Files\Microsoft ADAM\
instance
\data (replacing
instance
with the name you specified in Step 4). Click Next.
10. In the Service Account Selection window, click Network service account (or specify a serv-
ice account), and then click Next.
11. In the AD LDS Administrators window, you can specify the users or groups with adminis-
trative permissions for the AD LDS instance. Accept the default, which is the currently
logged-on user, and then click Next.
12. In the Ready to Install window, review your selections, and then click Next. When the instal-
lation is completed, click Finish.
Like AD DS, AD LDS uses multimaster replication, and intrasite replication is configured
automatically. However, you can configure the frequency of intrasite replication in Active
Directory Sites and Services, just as you do for AD DS intersite replication. Before you can
manage AD LDS objects in Active Directory Sites and Services, you must install the necessary
schema extensions by importing the MS-ADLDS-DisplaySpecifiers.ldf file. If you know you'll be
managing AD LDS with Active Directory Sites and Services, you can import this file when
installing the AD LDS instance or later with LDIFDE.
Synchronizing AD LDS with AD DS
As you have seen, you can create user accounts
and groups for AD LDS authentication manually. Manual user creation or importing users
with LDIFDE works well when only a few users must authenticate to the AD LDS application
or if the users aren't part of a Windows domain. If the AD LDS instance is installed on a
member server, however, you can synchronize AD DS user account information with an AD
LDS instance.
Adamsync, included in AD LDS, synchronizes Active Directory information with an AD
LDS instance. Before you can run Adamsync, you must prepare the target AD LDS instance with
the necessary schema changes. The LDIF file ms-adamschemaw2k8.ldf in %windir%\Adam
must be imported during installation of the instance or with LDIFDE. Next, import the ms-
adamsyncmetadata.ldf file. Finally, you edit the ms-adamsyncconf.xml file, which provides
Adamsync with information for the synchronization. For detailed instructions on preparing for
AD DS synchronization and running Adamsync, click the Active Directory Lightweight
Directory Services node in Server Manager, click “Enable application to consolidate data by syn-
chronizing data from AD DS to AD LDS” in the Resources and Support section, and click the
“More about this recommendation” link.
12
Activity 12-4: Uninstalling AD LDS Instances
and Removing the AD LDS Role
Time Required:
20 minutes
Objective:
Uninstall the AD LDS instance and remove the AD LDS role.
Description:
The application you were using that required AD LDS has been superseded by a
new application that doesn't use AD LDS. You remove the AD LDS instance with Control Panel's
Programs and Features, and then remove the role in Server Manager.
1. Log on to
Server1XX
as Administrator, if necessary.
2. Click
Start
,
Control Panel
. In Control Panel, double-click
Programs and Features
.
Search WWH ::
Custom Search