Import Oracle Data Create AD Users with Remote Linked Mailbox
Rule description
This rule queries the specified Oracle data source and creates Active Directory users with remote linked mailbox accounts according to the Action section settings.
For more details please see the Provisioning Linked Mailboxes in Cayosoft Administrator article.
When to use this rule
Use this rule to when you need to perform bulk provisioning of Active Directory user accounts with remote linked mailboxes.
Rule settings
Query section
| Setting name | Description |
|---|---|
Hostname |
Specify Oracle server hostname (or its IP address) to which Cayosoft Administrator will connect. NOTE: For more information, review the Connecting to Oracle database article. |
Service name |
Specify the Oracle database service name. |
Port |
Specify Oracle SQL*Net Listener port number; the default is 1521. |
Table |
Specify Table or View from the selected database. Click the Selector button to display a list of tables from which to choose. |
Credentials |
Specify Oracle user account name and password. |
Data Source Filter |
You can use the point-and-click filter builder for the specified data source. NOTE: If the Where clause is also specified, it will be applied and DataSource Filter will be ignored. |
More options | |
|
Return these SQL columns
|
Specify columns returned by the data source. |
Where clause |
Define a WHERE statement in the SQL query sent to the data source to limit the rows returned by an Oracle Server. |
Properties to display |
Select properties to display for each object found by the query. |
|
Filter data
|
Set the filtering conditions to hide unwanted data based on criteria not supported in the Query criteria setting. Example: filter by the found object Distinguished Name. TIP: For optimal performance, use the Query criteria setting above to filter objects whenever possible. |
Skip user if anchor attribute already exists |
The anchor attribute must be unique in the Data Source. Using the defined Anchor attribute, the rule checks to see if the anchor is already present in Active Directory. If the anchor is present, then this user was previously created, and the row in the Data Source is skipped. |
Data source anchor attribute |
Select a column in the data source that contains the attribute value for identifying and mapping a computer. |
Active directory anchor attribute |
Defines the attribute in the Active Directory to which the Data Source anchor attribute is to be compared. When a new user is created this value also specifies the Active Directory attribute into which the Data Source anchor is written for comparison the next time the rule is executed. |
Action section
Setting name |
Description |
|---|---|
Create master account in |
Specify OU for master accounts creation. |
Create mailbox account in |
Specify OU for mailbox accounts creation. |
Mailbox Account Naming Properties | |
|
Logon name (SamAccountName)
|
By default, SamAccountName is automatically generated from the data source, provided it contains correctly named fields. If the field names differ from those required for the selected format, contact Cayosoft to configure an override format. Additionally, the SamAccountName must be unique within the target domain. |
|
UPNSuffix (@domain.com)
|
Define the domain name component of the new user UserPrincipalName (UPN). The default UPN suffix is defined in the Default domain setting within the AD Users web query. If you are using Microsoft 365, ensure this value is set to a domain registered in Microsoft 365/Entra ID. |
|
UserPrincipalName
|
By default, UserPrincipalName (UPN) is automatically generated from the data source, provided it contains correctly named fields. If the field names differ from those required for the selected UPN format, contact Cayosoft to configure an override format. The UPN value must be unique. |
FirstName (GivenName) |
If the Data Source contains a field named FirstName, ignore this setting. Otherwise, use the Selector button to choose a field from the Data Source.
|
Initials | |
Last/SurName (sn) | |
|
Name (cn)
|
If the Data Source contains fields named FirstName and LastName, choose the desired format or ignore this setting. |
|
Display Name
| |
|
Description
|
If the Data Source contains a field name Description, ignore this setting. Otherwise, manually enter a static text value or use the Selector button to choose a field from the Data Source. |
Mailbox Account Alternate Name Generation | |
Name conflict resolution |
This option determines how the system should react when the name of a user being created already exists. |
|
The behavior of this attribute is the same as in the Contact Info section.
|
Counter format |
This setting specifies the number of fixed symbols the counter should have. |
Add counter when |
Specifies if a counter should always be added to the username, or only when name conflicts occur. |
Mailbox Account Organization Properties | |
|
If the Data Source contains one of these field names, ignore this setting. Otherwise, manually enter a static text value or use the Selector button to choose a field from the Data Source. |
Manager identifier |
Use the Selector button to choose a field from the Data Source that is a unique identifier for the user’s manager. Typically this will be the Managers EmployeeNumber or EmployeeID. |
AD attribute for manager lookup |
Select an Active Directory attribute that is used to search for the value of the Manager Identifier specified in the field above. |
Mailbox Account Contact Properties | |
Country |
Specify the user country. By default, the value is taken from the Active Directory extension settings. |
Email address |
Specify the format for email address. NOTE: If alternative SMTP addresses are needed, the AD Users | Set Proxy Addresses rule can be run after this rule. |
|
If the Data Source contains a field with one of these names, ignore this setting. Otherwise manually enter a static text value or use the Selector button to choose a field from the Data Source.
|
Mailbox Account Other Properties | |
Other Properties |
Data mapping also can be set by the script. If you want every provisioned user to have extension attribute 1 populated with some string value then use this
Copy
If you want every provisioned user to have extension attribute 2 populated with the corresponding value from the column in your data source file, then use this:
Copy
since NOTE: If you set mapping for the same properties both in Other properties and Other properties script, attribute values will be updated by the script. |
Master Account Naming Properties | |
|
Master account UPNSuffix (@domain.com)
|
By default, the first value is taken from the Trusted Domains table in the Active Directory extension settings. |
|
Specify master account naming properties. By default, they are taken from mailbox account. |
Default Password |
This setting defines the password for the new account. This value can be static text, a field from the Data Source chosen using the Selection button, or set to Generate Random Password. NOTE: Static passwords or passwords from the Data Source must meet the Active Directory Password Complexity Policy of the target container, or the account will be created in a disabled state. Randomly Generated Passwords will be generated to match both the Active Directory Password Complexity Policy and additional complexity requirements defined in the Cayosoft Administrator Password Complexity Policy. |
|
These settings enable/disable the standard Active Directory user object settings. |
Account Expiration Date |
This setting defines the Account Expiration attribute in Active Directory. In addition to populating this field from the Data Source, a text string can also be manually entered into the field in the format MM/DD/YYYY or YYYY-MM-DD. |
Master Account Other Properties | |
Other Properties |
Data mapping also can be set by the script. If you want every provisioned user to have extension attribute 1 populated with some string value then use this
Copy
If you want every provisioned user to have extension attribute 2 populated with the corresponding value from the column in your data source file, then use this:
Copy
since NOTE: If you set mapping for the same properties both in Other properties and Other properties script, attribute values will be updated by the script. |
Remote Mailbox Settings | |
Remote Routing Address |
Specify the format for remote routing address. |
Enable automatic email address updates by address policy |
By default, Exchange contains an email address policy for every mail-enabled object. For more information, please see this article Email address policies in Exchange Server. If the Exchange address policy is applied, it generates email addresses automatically. By default, this policy is not enabled, Cayosoft Administrator generates the email address by itself. |
Enable in-place archive |
Select Yes to create an in-place archive mailbox. |
Notify Manager | |
Notify Manager |
Specify whether you want to notify the manager when the user is created. You can also select send email for each created user or send one email for all created users. |
Additional to |
Additional email can be sent to Default Notify & Alert Email Address - usually, this is the administrator's email address. |
CC, BCC |
Email address where the copy will be sent. |
From |
Users can receive emails from default SMTP from address. |
Subject |
Email subject. TIP: It is possible to customize email subjects by using different tokens, see Customizing an automation rule or web action output email. |
Message |
Message text. TIP: It is possible to customize email messages by using different tokens, see Customizing an automation rule or web action output email. |
Limit the number of emails sent per minute |
An integer value that represents the number of emails sent per minute by this rule. To change the default value, navigate to Configuration > Settings > Email Settings (SMTP). The default limit for Microsoft 365 SMTP gate is 30 emails per minute. |
Output Section
This section defines the output format of this rule.
To get more information about this section, please see the Rule Output section article.
Enforce/Schedule Section
This section defines the schedule for how often to run the rule.
To get more information about this section, please see the Rule Enforce/Schedule section article.
Comments
0 comments
Please sign in to leave a comment.