Further Configuration

6 min

now we have done a basic configuration and created our first new user, it's time to dig deeper and understand how activate's configuration works to further extend the configuration and align with your organisation's standards user type templates activate user type xml templates are used to define how usernames and email addresses are generated define the attributes in ad to be updated enable/disable functions such as home drive creation and mailboxes specify password rules templates are defined in an xml format and can be reviewed on each user type under roles > user types this is the default user type template any user type without a custom template, such as employee, will inherit it the following sections show you how to adjust the configuration to align with your organisation’s standards \<template> \<data> \<userou>=/data/roles/location/userou/ou\</userou> \<loginname>#data/prefix|data/firstname 1|data/lastname|{#}\</loginname> \<cn protected="1">#data/attribute/displayname|{#}\</cn> \<prefix>=/data/roles/type/accountprefix\</prefix> \<password mustchange="1"> \</password> \<passwordrules> \<type>keyword\</type> \<prefix>a!1234\</prefix> \</passwordrules> \<attribute> \<scriptpath>=/data/roles/department/loginscript\</scriptpath> \<axfirstname>=/data/firstname\</axfirstname> \<axlastname>=/data/lastname\</axlastname> \<initials>=/data/initials\</initials> \<displayname>%=/data/firstname% %=/data/lastname%\</displayname> \</attribute> \<mail> \<enable default="1">false\</enable> \<email>#data/firstname|" "|data/lastname|{#}|"@%=//resources/configuration/defaultemaildomain%"\</email> \<exchangeserver>=//resources/exchange servers/office365\</exchangeserver> \</mail> \<directory>=//resources/activedirectory/external directories/azure\</directory> \</data> \<directories> \<home> \<enable>false\</enable> \<homedrive protected="1">h \</homedrive> \<homedirectory>auto\</homedirectory> \<source>=/user/homedirectory\</source> \<create> \<ifexists>rename\</ifexists> \<path>\\\\%=/data/roles/location/userhomeserver%\users\\%=/data/loginname%\</path> \<share>%=/data/loginname%\</share> \<template> \</template> \<acl>%=/data/sid%\ c\</acl> \</create> \</home> \<profile> \<enable>false\</enable> \<profiledirectory>auto\</profiledirectory> \<source>=/user/profilepath\</source> \<create> \<ifexists>rename\</ifexists> \<acl>%=/data/sid%\ c\</acl> \<path>\\\\%=/data/roles/location/userprofileserver%\profile\\%=/data/loginname%\</path> \<template> \</template> \</create> \</profile> \<tsprofile> \<enable>false\</enable> \</tsprofile> \<tshome> \<enable>false\</enable> \</tshome> \</directories> \</template> define username and email address generation activate provides an expression language that makes it simple to customise the rules for generating usernames and email addresses this gives implementers the flexibility to define patterns that suit their organisation’s requirements by default, for the employee user type, activate uses the first initial of the first name followed by the full last name (e g , wevans for wendy evans) for more details on defining appropriate name generation and email generation expressions, refer to the docid\ jsab9ccywamim5yjrrrjd guide to configure a user type template with the name generation expression open the template parameter of the desired user type set the value of data/loginname to the expression, e g #data/prefix|data/firstname 1|data/lastname|{#} set the value of data/mail/email to the expression e g #data/firstname|" "|data/lastname|{#}|"@%=//resources/configuration/defaultemaildomain%" save the template parameter disabling email address creation some user types may not require the creation of a mailbox to disable the email address creation, set the mail/enable value to false directories configuration depending on your organisation’s requirements, home drives and profile directories may or may not be necessary when creating a user by default, the create user task will not create any directories to enable the creation of home drives and profile directories follow these steps double click the template parameter to enable home drive creation, scroll to directories/home and change the enable tag from false to true to enable profile directory creation, scroll to directories/profile and change the enable tag from false to true configure userhomeserver and userprofileserver parameters as required on the location roles these can be just set on roles > locations and inherited down if there is only one server when new home drive or profile directory is created, if a directory with the same name already exists, activate will rename the existing one by appending “ x” followed by a timestamp to the folder name (e g , \\\servername\users\loginname x23112020151715) if you prefer not to have directories renamed, you can configure activate to either throw an error or reuse the existing directory to do this, update the create/ifexists tag with one of the following options error – activate will throw an exception if the directory already exists allow – activate will assign the existing directory to the new user active directory attributes updated during user creation during the create user process, activate updates specific directory (e g ad, azure) attributes these attributes can be provided through the create user task form or defined (generated or hardcoded) within the user type template here are some examples of the attributes in the default employee {{user type}} template true 220,220,221left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type