Active Directory Provider::Create Object

autoGenerateEmailAddresses

Description:
Specifies whether Microsoft Exchange Server 2000 is allowed to automatically generate e-mail addresses in the format "alias@domain" for new Active Directory objects that are mail-enabled. Such objects include users, groups, contacts, public folders, stores, and system attendants.

In MPF installations running Exchange 2000 Server, the default policy is to automatically generate addresses for new mail-enabled objects. When Exchange generates an address, it sets the new object's proxyAddresses property to "alias@domain". This is a problem if the object should have a different address. To override this default behavior and preserve a manually-defined value for proxyAddresses, include an autoGenerateEmailAddresses node with a value of "0" in the request to Create Object. For example:

<autoGenerateEmailAddresses>0</autoGenerateEmailAddresses>

Note

To use the autoGenerateEmailAddresses option, the computer that runs the Active Directory Provider must have Collaboration Data Objects (CDO) installed.

Parent:
executeData

container

Description:
Lightweight directory access protocol (LDAP) path of the new object's container object. For example:

<container>LDAP://CN=Users,DC=myDomain,DC=com</container>

If possible, allow Active Directory to dynamically assign a domain controller to the object. If you specify the domain controller in the container path, you must later use the Active Directory Provider::Make Path Domain Specific [HMC SDK1] procedure to modify the path so it points to the Active Directory domain instead of to the domain controller. This extra step is necessary to ensure that other domain controllers can support the object if the original controller is unavailable.

Parent:
executeData

flagIgnoreAlreadyExistsError

Description:
Determines whether the procedure can succeed even if the object already exists. If this element is specified, the procedure ignores any errors stating that the object already exists and prevents rollback from accidentally deleting the object.

Now that MPF supports try/catch error handling (through Provisioning Schema::try and Provisioning Schema::catch elements), there is little need to specify flagIgnoreAlreadyExistsError. This node was originally introduced to support error handling. For example, a Create Object call ordinarily fails if the user already exists. To override this behavior, the request can include a flagIgnoreAlreadyExistsError node, which instructs Create Object to return the flagSkipAction node. Subsequent calls pass this node to prevent further operations on the object. For example, if the next call is to , the presence of flagSkipAction prevents accidental resets of the user's password.

Parent:
executeData

flagSkipAction

Description:
Empty element returned if the object already exists and the input XML includes the flagIgnoreAlreadyExistsError element.

Parent:
executeData

path

Description:
LDAP path returned for the new object. Consists of the object name and the container path. For example, inputs

<name>CN=myUser1</name>

and

<container>LDAP://CN=Users,DC=myDomain,DC=com</container>

result in

<path>LDAP://CN=myUser1,CN=Users,DC=myDomain,DC=com</path>

path is saved in the rollback log, so it can be deleted after rollback.

property

Description:
Name of an Active Directory property for the new object. For example:

<properties> 
  <property name='sAMAccountName'>myUser1</property> 
  <property name='otherHomePhone'> 
    <value>425-555-1212</value> 
    <value>206-555-1212</value> 
  </property> 
</properties>

Parent:
properties

Child:
value (minOccurs="0" maxOccurs="*", input only)

Attributes: