User Management Resource Administrator

Online Manual: "User Management Resource Adminstrator"
Go to: User Management Resource Administrator homepage

Script Action: Create contact (AD)

Function

Creates an Active Directory contact. A contact is an active directory object which contains contact information.

Deployment

This action is typically used as a part of a script designed to create contacts in Active Directory domains.Contacts are most often used to make communicatie between different active directories possible. When you create a contact, the contact can not login on the network. The setting of the contact can be used by users of the network to contact other users or entities that are not connected to the network.

Properties

Property Name	Description	Typical setting	Remarks
Domain	The domain in which to create the user domain account.	%Domain%	Often the domain name is used in many different actions, and is determined and stored in a variable previous to the action ( e.g. %Domain%). The name of the domain can be either in DNS or NETBIOS style. (e.g. Tools4ever.com or TOOLS4EVER). For more information on how to specify the domain/OU/container in which the user account is created, see the Remarks section below.
Organizational Unit-Container	The name of the Active Directory Organizational unit or other container in which to create the account.	Users	Specify the path of the organizational unit (OU) or container relative to the domain. To specify OU's in OU's, use the full path relative to the domain, separated by slashes: OU/ChildOU/GrandChildOU. Examples: students or students/group1. For more information on how to specify the domain/OU/container in which the user account is created, see the Remarks section below.
LDAP container	Optional: The LDAP name of the container in which to create the account.		Optionally specifies name of the Active Directory container in which the user is created directly by means of its LDAP name (Example: CN=users, DC=tools4ever,DC=com Example: OU=Group1, OU=Students, DC=tools4ever, DC=com) This specification can be used instead of the Domain and Organizational Unit-Container properties of this action. If specified, the specified LDAP Container takes precedence, and the Domain And Organization Unit-Container properties are ignored. For more information on how to specify the domain/OU/container in which the user account is created, see the Remarks section below.
Domain (controller)	Optional: The name of the domain controller or domain used to access the domain.		If this value is not specified, the application creates the account on a domain controller that is determined by Active Directory (serverless binding). If a domain controller is specified, the account is explicitly created on the specified controller (server binding). In both cases, Active Directory itself will replicate the account information to all domain controllers in the forest automatically as required. Depending on the actual User Management Resource Administrator Script used, it may be necessary to specify a domain controller here. If an subsequent script action does an Active Directory query to obtain information of the newly created user, this query may occur before Active Directory has replicated the new information to other Domain Controllers. As a consequence, the query may fail to find the newly created user. When both actions however specify the same domain controller, the newly created user can be found. Often a requery of Active Directory by subsequent actions for the newly created user can be prevented by using the User Object that is created by this action in subsequent actions, instead of the name of the user.
Name generation algorithm	Specifies the name of the algorithm used to generate user names	Default	The main purpose of the Name Generation algorithm is to create unique names that adhere to your company's syntax requirements. A common implementation of the algorithm will take as input the three variables %FirstName%, %MiddleName% and %LastName%, and generate from these the variables %FullName% and %UserName%. Here %FullName% contains the complete name of the user formatted for display purposes, and %UserName% the name formatted for use as the name of the account. These resulting variables can then be used as input for the other properties of this action For a thorough discussion, please see Name Generation Algorithms
CommonName	The CommonName is the full name of the user. This name is most commonly used in user interfaces.	%FullName%	Typically the name contained in %FullName% is generated by the name generation algorithm.
DisplayName	This is the Display name attribute of the account. It usually contains the full name of the user.	%FullName%	Typically the name contained in %FullName% is generated by the name generation algorithm.
Given-Name	Optional. The given name corresponds usually with the first name of the user.	%FirstName%	Typically the variable %FirstName% is directly read from the a import file specifying the users to create.
Initials	Optional. The initials of the user. It has a maximum length of six characters.	%MiddleName%	Typically the variable %MiddleName% is directly read from the a import file specifying the users to create.
SurName	Optional. The surname of the user.	%LastName%	Typically the variable %LastName% is directly read from the a import file specifying the users to create.
Description	A text string, that will be shown in the Description field of the user account in windows. The string can have any length.
General - Office	The users's office location This is the person's office location, including the building and office address or number.
General - TelephoneNumber	The user's phone number
General - E-mail	The user's e-mail address. The e-mail address appears with the universal principal name suffix (for example, someone@microsoft.com).
General - Web-Page	The user's home page URL, either on the Internet or in the local intranet site.
Address - Street	The user's street address
Address - P.O. Box	The user's post office box number
Address - City	The city where the user is located
Address - State/province	The state or province where the user is located
Address - Zip/Postal Code	The zip or postal code applicable for the user
Address -Country/region	The user's country or region		The country can be either explicitly chosen from a drop down list, or be specified as text. In the latter case it can also be read from a variable, for instance created by a column from the list of users.
Telephones - Home	The user's home telephone number
Telephones - Pager	The user's page number
Telephones - Mobil	The user's mobil telephone number
Telephones - Fax	The user's fax number
Telephones - IP phone	The users IP telephone number
Telephones - Notes	Descriptive information and any comments for this user.
Organization - Title	The user's title
Organization - Department	The user's department
Organization - Company	The users's company

Output Properties

When the action is run, the actual value of the properties are determined at run time, and the action is executed using these values. Generally these values are not stored for later usage. However, it may be that the actual value of a specific property is required for an successive action in the User Management Resource Administrator script. To facilitate this need, any property can be explicitly configured to be saved in a variable when the action has been performed. For example, when the password of a user is created with the password generator, the resulting password value may be stored in a variable, so it can be exported to a file by an other action in the script.

By default the following properties are saved in a variable for usage in other scripts. Properties that are exported are shown with an image with a green arrow in the properties list.

Property	Description	Default variable name	Remarks
Common name	The CommonName is the full name of the user. This name is most commonly used in user interfaces.	%FullName%	If more names have been tried as a consequence of the user name generation algorithm, this contains the last name tried.
Contact object	This Internal application object representing the just created contact object.	%ContactObject%	The Contact Object is main purpose is to ease subsequent operations on the same object by actions that follow in the script. For several actions this object can be used as input to specify the object the actions work on.

Remarks

Domain / OU / Container / LDAP -specification

User Management Resource Administrator supports several methods to specify the entity (domain, OU or container) in which the user account will be created. These methods differ in the way the property values are specified. The properties involved are: Domain, Organizational Unit-Container, LDAP container. Depending on your network environment and input data, you should choose the method that fits best:

Properties specified	Properties not specified	Example	Description
Domain Organizational Unit-Container	LDAP container	Domain: TOOLS4EVER or tools4ever.com Organizational Unit-Container: STUDENTS/GROUP1	This is most easy method to create user accounts in OU's. To create the account, User Management Resource Administrator will automatically compose the LDAP name of the container to create the user account.
Domain	LDAP container Organizational Unit-Container	TOOLS4EVER or tools4ever.com	Use this method only, to create user accounts in the domain root. No OU is involved.
LDAP container	Domain Organizational Unit-Container	OU=Group1, OU=Students, DC=tools4ever, DC=com	Use this method if you want to specify the OU directory using the LDAP format. If this property is specified, the Domain and Organizational Unit-Container properties are ignored.