How to Configure Atria to Set Users' Proxy Addresses Attribute in AD

How to Configure Atria to Set Users' Proxy Addresses Attribute in AD

Objective

This article provides a guide on how to configure Atria to Set Users' Proxy Addresses Attribute in AD during provisioning

Considerations

  1. This configuration is OPTIONAL to be implemented and is dependent on your requirement.
  2. Once the configuration is implemented, the option to set Proxy Addresses can be toggled per customer (default value is FALSE).
  3. The end result of this configuration if enabled - it will allow the setting of Proxy Addresses in AD even if a user is not a mail-enabled object.

Configuration Steps

Make sure that you are able to navigate to "Customers > Configuration > Customer List > Display Properties"
 

If not available, enable this page for Service Provider Administrator role.

1. Using a service provider administrator account, in Atria Home Page, navigate to Display Properties (as shown above), then filter the list to "Customers" Type


2. On the left pane, under Management, select "New Property" and create a property with the following details and SAVE it.


3. After saving the new property, you will notice that when creating a new customer or editing an existing customer, the property added is now present with a default value that is not ticked meaning it is set to "FALSE"

Only enable this property to customers that are expected to "Set Users Proxy Addresses in AD" by default

4. Now that the property is created, let's create the rules associated to this configuration. Login in to your Provisioning Server and open the Provisioning Manager.
Then enable "Advanced" under Options menu
Located in "C:\Program Files (x86)\Automate101\Atria\Provisioning Engine\ProvisioningManager.exe"

5. On the provisioning manager, setup the rules with the following details
      a. Under "Default Rule Store > Events > User > PreProvision > After" -- Add a New Rule -- "Get SetUserProxyAddresses Setting" -- then hit SAVE after creating the rule
            - General Tab:
                  - Tick "Rule enabled"           
            - Action Tab:
                  - Action: "SQL Command"  with (4) parameters
                  - Description: Get SetUserProxyAddresses Setting
                  - Property: setUserProxyAddresses
                  - ConnectionString: {ConnectionString}
                  - Command: Select Value from vw_PropertyValues where objectid = {CustomerObjectID} and property = 'setUserProxyAddresses'
                  - Expand: True
                  - Timeout: 0
            

      b. Under "Default Rule Store > Events > User > Provision > After" -- Add a New Rule -- "If ProxyAddresses to be set Then" -- then hit SAVE after creating the rule
             - General Tab:
                  - Tick "Rule enabled"
            - Condition Tab:
                  - Condition: {setUserProxyAddresses} = "True"
                  - Description: ProxyAddresses to be set
                  - Tick "Condition Enabled"           
            - Action Tab:
                  - Action: "Call"  with (1) parameter
                  - Description: Set Users Email Addresses
                  - Name: $CustomEmailAddressesSet
            

      c. Under "Default Rule Store > Events > User > Provision > After > If ProxyAddresses to be set Then" -- Add a New Rule -- "clear ProxyAddresses" -- then hit SAVE after creating the rule
             - General Tab:
                  - Tick "Rule enabled"           
            - Action Tab:
                  - Action: "Directory Attribute Set Object"  with (2) parameters
                  - Description: clear ProxyAddresses
                  - sAmAccountName: {Username}
                  - Attribute: proxyAddresses
                  - Value:
                  - DCServer: {DCServer}
            

      d. Under "Default Rule Store > Events > User > Provision > After > If ProxyAddresses to be set Then" -- Add a New Rule -- "For Each Email Address" -- then hit SAVE after creating the rule
             - General Tab:
                  - Tick "Rule enabled"           
            - Action Tab:
                  - Action: "For Each"
                  - Description: For Each Email Address
                  - Optional Parameter: 1
                  - Item: Address
                  - Array: EmailAddresses
                  - Filename:
                  - Classname: OleDbActions
                  - Parms: $CustomAddEmailAddressToProxyAddresses
            

      e. Under "Default Rule Store > Events > User > Provision > After > If Proxy Addresses to be set Then > For Each Email Address" -- Add a New Rule -- "Add Email Address" -- then hit SAVE after creating the rule
             - General Tab:
                  - Tick "Rule enabled"           
            - Action Tab:
                  - Action: "Directory Attribute Array Add" with (3) parameters
                  - Description: Add Email Address
                  - Path: {UserFullPath}
                  - Name: {Username}
                  Attribute: proxyAddresses
                  Value: {Address}
                  - DCServer: {DCServer}
            
Make sure all rules are properly set with the right values and hierarchy as shown on the screenshots

5. Restart the AtriaQueueMonitor both on your Primary Location and Remote Location for these rules to take effect.

Validation

You may want to test this first before implementing this on a live customer
1. On a customer, tick the "Set Users ProxyAddresses Attribute" -- this will set it to TRUE

2. Provision the customer
3. Navigate to a user (currently not mail-enabled), add e-mail aliases or if there are present aliases already that is fine. 
(Sample Screenshot Only)

4. Provision the user
5. Validate in AD that the ProxyAddresses of that user has been added and reflected properly
  1. Via DSA.
      
  1. Via Powershell command.  (Get-ADUser -Identity <username> -Properties ProxyAddresses)
      

For any other inquiries or concerns with regard to this article. Please contact support@automate101.com
    • Related Articles

    • Atria v12.11+ System Requirements

      Overview  The following article provides the prerequisites necessary for the deployment of Atria v12.11+ into your environment.  System Requirements   Environment  Core servers for the platform should be domain joined. Before you can deploy Atria ...
    • How to configure Azure AD Custom Tenant Configuration Scripts

      Overview As part of the Atria Azure AD Service Sync Policies, you can assign custom configuration scripts that will be run each time the service is provisioned.  This is useful to ensure your customer's tenants are always configured with your ...
    • Atria v12.11+ Deployment Guide

      Overview  This article outlines the deployment procedure of Atria v12.11+.  This article will also refer to other articles that may assist with your installation or upgrade. Alert:  In-place migration from any version of CloudPortal Services Manager ...
    • Atria with Citrix Cloud

      Overview This article provides a guide on how to set up Atria with Citrix Cloud. Where required details and links provided in this article have been extracted from Citrix documentation. Related Links Citrix Cloud Documentation System Requirements ...
    • Atria v12.13+ Portal Branding

      Objective Atria allows service providers, resellers, and customers to create their own brand so that the web portal interface (control panel) displays their own logo, color scheme, fonts, and messages when their users log on to the portal. Overview ...