Recipe 4.19. Refreshing a Dynamic Object

4.19.1. Problem

You want to refresh a dynamic object to keep it from expiring and getting deleted from Active Directory.

4.19.2. Solution

In each solution below, an example of adding a user object is used. Modify the examples as needed to refresh whatever object is needed.

4.19.2.1. Using a graphical user interface

4.19.2.2. Using a command-line interface

Create an LDIF file called refresh_dynamic_object.ldf with the following contents:

dn: cn=jsmith,cn=users,dc=adatum,dc=com
changetype: modify
replace: entryTTL
entryTTL: 1800
-

Then run the following command:

> ldifde -v -i -f refresh_dynamic_object.ldf

You can also use AdMod with the following syntax:

> admod -b <ObjectDN> entryTTL::<TTL in Seconds>

4.19.2.3. Using VBScript

set objUser = GetObject("LDAP://cn=jsmith,cn=users,dc=adatum,dc=com")
objUser.Put "entryTTL", "1800"
objUser.SetInfo

4.19.2.4. Using PowerShell

To refresh a dynamic object using the Quest AD cmdlets, use the following syntax:

set-QADObject -Identity <ObjectDN> @{entryTTL=1800}

To modify an object using ADSI, use the following:

$objDyn = [System.DirectoryServices.DirectoryEntry] "LDAP://<ObjectDN>"
$objDyn.put("entryTTL","1800")
$objDyn.SetInfo()

4.19.3. Discussion

Dynamic objects expire after their TTL becomes 0. You can determine when a dynamic object will expire by looking at the current value of an object’s entryTTL attribute or by querying msDS-Entry-Time-To-Die, which contains the seconds remaining until expiration. If you’ve created a dynamic object and need to refresh it so that it will not get deleted, you must reset the entryTTL attribute to a new value. There is no limit to the number of times you can refresh a dynamic object. As long as the entryTTL value does not reach 0, the object will remain in Active Directory.

4.19.4. See Also

Section 4.15 for modifying an object and Section 4.18 for creating a dynamic object