What is the network impact between the ADAM instance and the AD domain?
What is the network impact between the Encryption Anywhere ADAM instance and the Active Directory domain?
Overview of the communication between an ADAM instance and AD. ========================================================
An ADAM instance checks and updates its SCP (Service Connection Point), if necessary, when the ADAM instance starts. At startup, the ADAM instance searches the global catalog for its own GUID and retrieves the distinguished name of the SCP object. The ADAM instance then binds to that distinguished name and updates the SCP object as necessary. In addition, the ADAM instance reviews the SCP object on an hourly basis by default to confirm its validity, particularly regarding any directory partitions that have been added to or removed from the ADAM instance since the SCP object was last updated.
You can modify the default time interval at which ADAM reviews the SCP object by adding a Server information update interval (mins) value to the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\instancename\Parameters and setting this value to the time interval (in minutes) that you want to use.
After the installation and authentication of the Encryption Anywhere ADAM instance there is no further communication between ADAM and AD. During the authentication of the client to ADAM there is a request from ADAM to AD to authorize the access.
The impact to the network between the Encryption Anywhere ADAM instance and AD is negligble.
Rate this Article
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.