Chat now with support
Chat with Support

Active Roles 7.4.1 - Administration Guide

Introduction About Active Roles Getting Started Rule-based Administrative Views Role-based Administration
Access Templates as administrative roles Access Template management tasks Examples of use Deployment considerations Windows claims-based Access Rules
Rule-based AutoProvisioning and Deprovisioning
About Policy Objects Policy Object management tasks Policy configuration tasks
Property Generation and Validation User Logon Name Generation Group Membership AutoProvisioning E-mail Alias Generation Exchange Mailbox AutoProvisioning AutoProvisioning for SaaS products OneDrive Provisioning Home Folder AutoProvisioning Script Execution Office 365 License Management Office 365 Roles Management User Account Deprovisioning Office 365 Licenses Retention Group Membership Removal Exchange Mailbox Deprovisioning Home Folder Deprovisioning User Account Relocation User Account Permanent Deletion Group Object Deprovisioning Group Object Relocation Group Object Permanent Deletion Notification Distribution Report Distribution
Deployment considerations Checking for policy compliance Deprovisioning users or groups Restoring deprovisioned users or groups Container Deletion Prevention policy Picture management rules Policy extensions
Workflows
Understanding workflow Workflow activities overview Configuring a workflow
Creating a workflow definition Configuring workflow start conditions Configuring workflow parameters Adding activities to a workflow Configuring an Approval activity Configuring a Notification activity Configuring a Script activity Configuring an If-Else activity Configuring a Stop/Break activity Configuring an Add Report Section activity Configuring a Search activity Configuring CRUD activities Configuring a Save Object Properties activity Configuring a Modify Requested Changes activity Enabling or disabling an activity Enabling or disabling a workflow Using the initialization script
Example: Approval workflow E-mail based approval Automation workflow Activity extensions
Temporal Group Memberships Group Family Dynamic Groups Active Roles Reporting Management History
Understanding Management History Management History configuration Viewing change history
Workflow activity report sections Policy report items Active Roles internal policy report items
Examining user activity
Entitlement Profile Recycle Bin AD LDS Data Management One Identity Starling Management One Identity Starling Two-factor Authentication for Active Roles Managing One Identity Starling Connect Azure_Overview
Config ARS to Manage Hybrid AD Objects Managing Hybrid AD Users Office 365 roles management for hybrid environment users Managing Office 365 Contacts Managing Hybrid AD Groups Managing Azure O365 or Unified Groups
Managing Configuration of Active Roles
Connecting to the Administration Service Adding and removing managed domains Using unmanaged domains Evaluating product usage Creating and using virtual attributes Examining client sessions Monitoring performance Customizing the console Using Configuration Center Changing the Active Roles Admin account Enabling or disabling diagnostic logs Active Roles Log Viewer
SQL Server Replication Appendix A: Using regular expressions Appendix B: Administrative Template Appendix C: Communication ports Appendix D: Active Roles and supported Azure environments Appendix E: Enabling delegation for Federated Authentication

Connect <Drive Letter> To <Network Path>

Connect <Drive Letter> To <Network Path>

Upon creation or renaming of a user account, the policy can configure the user account in Active Directory to connect the home folder to the specified network path. From the Connect list, select the drive letter to which you want the policy to map the home folder. In the To box, specify a network path to the home folder. Ensure that the path meets the following requirements:

  • A valid network path must begin with the UNC name of a network file share, such as \\Server\Share\, and should normally include the %username% notation. For example, with the Connect: Z: To: \\Server\Share\%username% option, the policy can configure a user account in Active Directory so that the Home Drive property of the user account is set to Z: and the Home Directory property of the user account is set to \\Server\Share\LogonName where LogonName stands for the pre-Windows 2000 logon name of the user account.
  • The path must include a common share at one level above the home folders. For example, if you type \\Comp\Home\%username%, the policy creates home folders on the share Home on the server Comp, with the name of the folder being the same as the user logon name (pre-Windows 2000). The path \\Comp\%username% would be invalid.
  • The folder on the network file share in which you want the policy to create home folders must be listed in the Home Folder Location Restriction policy. For instructions on how to view or modify the list see Configuring the Home Folder Location Restriction policy later in this section.
  • If you want the policy to create home shares (see information about the Home Share Management page later in this section), you should not specify an administrative share, such as C$, as the common share in the To box. Otherwise, the policy may be unable to create home shares when creating home folders. Thus, if you specify \\Comp\C$\%username%, the policy can successfully create home folders in the folder C:\ on the computer Comp, but it may fail to create home shares.

Enforce this home folder setting in Active Directory

Use this option to have Active Roles verify whether the Home Drive and Home Directory properties on user accounts in Active Directory are in compliance with the Connect: <drive letter> To: <network path> setting specified by this policy.

For example, with the Connect: Z: To: \\Server\Share\%username% policy setting, this option causes a policy violation condition in Active Roles upon an attempt to modify a user account so that the Home Drive property is assigned a drive letter other than Z: or the Home Directory property is assigned a network path other than \\Server\Share\LogonName where LogonName stands for the pre-Windows 2000 logon name of the user account.

When this option is turned off, the policy allows a home folder path and name that differs from the path and name prescribed by this policy. A Property Generation and Validation policy can be configured to generate the Home Drive and Home Directory properties on user accounts, or those properties can be specified manually. In either case, Active Roles updates the user account so that the folder with the specified path and name is set as the user home folder. If necessary, Active Roles creates the folder.

When this option is turned on, the policy behaves as follows:

  • It ensures that the path and name of the home folder is in compliance the policy settings. If a different path or name is specified upon creation or modification of a user account, the policy does not allow the changes to the home folder path and name to be committed to the directory.
  • The Check Policy command causes the policy to verify the existing home folder settings. The policy check results inform about policy violations, if any, and provide the ability to fix the home folder path and name settings on user accounts so as to bring them into compliance with the policy settings.

By selecting the Enforce this home folder setting in Active Directory check box, you ensure that the home folders on user accounts are set in compliance with this policy.

By clearing the check box, you get the option of applying a Property Generation and Validation policy in order to generate and validate the Home Drive and Home Directory properties, and thus have Active Roles create and assign home folders in accordance with the flexible, highly customizable rules provided by a Property Generation and Validation policy.

IMPORTANT: When setting the Home Drive and Home Directory properties, Active Roles does not create the home folder if the network path of the folder to hold the home folder is not listed in the Home Folder Location Restriction policy. The policy defines a list of the folders on network file shares in which creation of home folders is allowed, and prevents Active Roles from creating home folders in other network locations. For instructions on how to view or modify the policy settings, see Configuring the Home Folder Location Restriction policy later in this section.

Apply this home folder setting when user account is created

Upon creation of a user account, this option causes Active Roles to configure the user account in Active Directory in accord with the Connect: <drive letter> To: <network path> setting specified by this policy.

For example, with the Connect: Z: To: \\Server\Share\%username% policy setting, selecting this check box ensures that a newly created user account has the Home Drive property set to Z: and the Home Directory property set to \\Server\Share\LogonName where LogonName stands for the pre-Windows 2000 logon name of the user account.

Apply this home folder setting when user account is renamed

Upon renaming a user account, this option causes Active Roles to configure the user account in Active Directory in accord with the Connect: <drive letter> To: <network path> setting specified by this policy.

For example, with the Connect: Z: To: \\Server\Share\%username% policy setting, renaming a user account causes the policy to set the Home Directory property to \\Server\Share\NewLogonName where NewLogonName stands for the pre-Windows 2000 logon name that is assigned to the user account by the rename operation.

Related Documents