So now that our ADAM schema is ready, we can go ahead and start configuring ADAMSync.
We need to do three things to get ADAMSync running at this point:
1) Modify the XML file. The XML file is used as the configuration point for ADAMSync, so we’ll tweak this file to have the settings we desire.
2) Install the XML file in to ADAM.
3) Run ADAMSync to perform the synchronization itself.
Step 1: Modifying the XML file
Let’s try and keep it simple to start. The easiest way to get off of the ground is just to pick the proper target, do the fewest modifications required and then run with it.
ADAMSync ships with a sample XML file which has many of the commonly used tags. I typically work from this as my starting point.
I started off by making a quick copy of the default ADAMSync config to use.
C:\WINDOWS\ADAM>copy MS-AdamSyncConf.XML ADAMSyncDemo.XMLNow with that in hand, we can start making some changes for our first run of the tool.
1 file(s) copied.
To get things started, I’d suggest we first make the absolute bare minimum in terms of # of changes. We can explore different parts of the configuration file as we move forward, but it helps to first have a working configuration to work from.
Here’s what my config file looks like (with section I modified from the default in red):
<description>sample Adamsync configuration file</description>
Step 2: Installing the XML file
With our XML file in hand, installing it in to the ADAM environment is a piece of cake.
It’s worth noting that the configuration itself is stored in the target environment (ADAM), not in the source. So we’ll focus the install command against our ADAM environment.
C:\WINDOWS\ADAM>adamsync /install localhost:50000 ADAMSyncDemo.XMLAfter installing it, I usually ask ADAMSync to list all of the configuration files once so that I can confirm it made it there.
C:\WINDOWS\ADAM>adamsync /list localhost:50000Looks good!
Listing configuration files:
|-> “OU=SyncTarget”: sample Adamsync configuration file
Step 3: Running ADAMSync for the first time
Our first run….let’s see what happens!
C:\WINDOWS\ADAM>adamsync /sync localhost:50000 dc=synctargetdcADAMSync just returned without error. This is the real measure of success. 🙂 If there was a problem, we would have received some verbiage.
At this point we should be able to look at the target NC and the data should be there.
Did you get an error? If so, hang tight, tomorrow we’ll take a look at some of the logging available and look at one such log.