Setting an object’s manager

To update the manager attribute you just set it to the distinguished name of the existing user you require. A distinguished name is of the form: CN=John Smith,CN=Users,DC=test,DC=com.

So to set Jane Active’s manager to the existing user “John Smith” you would use a message like this:

<ActiveDirectoryUpdate>

<Directives WhereToBind=”LDAP://CN=Users,DC=test,DC=com” SearchScope=”onelevel” ObjectTypeFilter=”(objectClass=user)” MaxObjects=”1″/>

<Target PropertyName=”cn” EqualToValue=”Jane Active” />

<Change PropertyName=”manager” ChangeToValue=”CN=John Smith,CN=Users,DC=test,DC=com” ChangeType=”update” />

</ActiveDirectoryUpdate>

FAQs
My Solicit-Response Send Port Query Is Only Returning 1000 Results

Try adding the setting PageSize="1000" to your query parameters. For example:

<ActiveDirectoryQuery><Directives WhereToBind="LDAP://CN=Users, DC=test, DC=com" Filter="(objectCategory=user)" SearchScope="onelevel" PropertiesToReturn="cn" PageSize="1000"/></ActiveDirectoryQuery>

By default Active Directory only allows for a single page of 1000 results. By explicitly setting this value multiple pages (and hence all results) are returned.

See the entire answer

What is ActiveADAPTER?

ActiveADAPTER is a set of BizTalk adapters for working with Active Directory from BizTalk Server. We offer you:

  • A BizTalk Send Adapter that you can use to:
    • Create, move and delete Active Directory objects
    • Change object properties such as email addresses, office locations, home folder locations...
    • Set user passwords and add objects to security groups
  • A BizTalk Receive Adapter that you can use to query Active Directory and receive the results in an XML message into BizTalk Server
  • The input and output schemas for all ActiveADAPTER operations
  • Sample orchestrations and example XML input
  • Complete documentation

See the entire answer

What transactional strategy does the ActiveADAPTER Send Adapter use?

The Send Adapter commits changes per message and per object. This means commits cannot span messages. Within a message, changes to an object are all committed together. To ensure changes are all or nothing, therefore, the strategy you need to use is one message per object.

See the entire answer