Chat now with support
Chat with Support

Active Roles 8.1.4 - Administration Guide

Introduction Getting started with Active Roles Configuring rule-based administrative views Configuring role-based administration Rule-based autoprovisioning and deprovisioning
Provisioning Policy Objects Deprovisioning Policy Objects How Policy Objects work Policy Object management tasks Policy configuration tasks
Property Generation and Validation User Logon Name Generation Group Membership AutoProvisioning Exchange Mailbox AutoProvisioning AutoProvisioning in SaaS products OneDrive Provisioning Home Folder AutoProvisioning Script Execution Microsoft 365 and Azure Tenant Selection E-mail Alias Generation 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
Using rule-based and role-based tools for granular administration Workflows
Key workflow features and definitions About workflow processes Workflow processing overview Workflow activities overview Configuring a workflow
Creating a workflow definition for a workflow 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
Approval workflow Email-based approval Automation workflow Activity extensions
Temporal Group Memberships Group Family Dynamic groups Active Roles Reporting Management History Entitlement profile Recycle Bin AD LDS data management One Identity Starling Join and configuration through Active Roles Managing One Identity Starling Connect Configuring linked mailboxes with Exchange Resource Forest Management Configuring remote mailboxes for on-premises users Migrating Active Roles configuration with the Configuration Transfer Wizard Managing Skype for Business Server with Active Roles
About Skype for Business Server User Management Active Directory topologies supported by Skype for Business Server User Management User Management policy for Skype for Business Server User Management Master Account Management policy for Skype for Business Server User Management Access Templates for Skype for Business Server Configuring the Skype for Business Server User Management feature Managing Skype for Business Server users
Exchanging provisioning information with Active Roles SPML Provider Monitoring Active Roles with Management Pack for SCOM Configuring Active Roles for AWS Managed Microsoft AD Azure AD, Microsoft 365, and Exchange Online Management
Configuring Active Roles to manage Hybrid AD objects Unified provisioning policy for Azure M365 Tenant Selection, Microsoft 365 License Selection, Microsoft 365 Roles Selection, and OneDrive provisioning Changes to Active Roles policies for cloud-only Azure objects
Managing the configuration of Active Roles
Connecting to the Administration Service 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 Using regular expressions Administrative Template Configuring federated authentication Communication ports Active Roles and supported Azure environments Integrating Active Roles with other products and services Active Roles Language Pack Active Roles Diagnostic Tools Active Roles Add-on Manager

User Management policy for Skype for Business Server User Management

The Skype for Business - User Management built-in policy enables Active Roles to perform user management tasks on Skype for Business Server. The policy is intended for:

  • Single-forest and multi-forest environments where login-enabled accounts of Skype for Business users are defined in the Active Directory forest in which Skype for Business Server is deployed.

  • Multi-forest environments where login-enabled master accounts of Skype for Business Server users are defined in external forests with each master account being represented by a shadow account (inactive user account or contact) in the Active Directory forest in which Skype for Business Server is deployed.

The Policy Object that holds this policy is located in the following container in the Active Roles Console:

Configuration/Policies/Administration/Builtin/Built-in Policy - Skype for Business - User Management

Depending on your Active Directory topology, apply this Policy Object as follows to enable Skype for Business Server User Management in Active Roles.

Table 87: Applying the Built-in - Skype for Business - User Management Policy Object

Topology option

Where to apply the Policy Object

Single forest topology for Skype for Business Server User Management

Apply this Policy Object to Active Directory domains or containers that hold user accounts you want to administer by using Skype for Business Server User Management in Active Roles.

Resource forest topology for Skype for Business Server User Management

Apply this Policy Object to Active Directory domains or containers in the Skype for Business Server forest that hold shadow accounts (inactive user accounts) for users from external forests you want to administer by using Skype for Business Server User Management in Active Roles.

Central forest topology for Skype for Business Server User Management

Apply this Policy Object to:

  • Active Directory domains or containers in the Skype for Business Server forest that hold login-enabled user accounts you want to administer by using Skype for Business Server User Management in Active Roles

  • Active Directory domains or containers in the Skype for Business Server forest that hold shadow accounts (contacts) for users from external forests you want to administer by using Skype for Business Server User Management in Active Roles.

Skype for Business Server User Management policy settings

This section describes the policy settings available for the Skype for Business User Management built-in policy.

Connecting to Skype for Business Server

To administer Skype for Business Server users, Active Roles requires a connection to a computer running one of the following server roles in your Skype for Business Server deployment:

  • Front End Server (if using Skype for Business Server Enterprise Edition).

  • Standard Edition Server.

The computer must be from an Active Directory domain that is registered with Active Roles as a managed domain. By using the Server policy setting, you can specify how you want Active Roles to select a Skype for Business Server computer:

  • Connect to any available server: With this option, Active Roles attempts to connect to any Front End Server or Standard Edition Server that runs the Central Management Server in your Skype for Business Server deployment. If no Central Management Server role holders are available in the managed domains, then Active Roles attempts to connect to the first Front End Server or Standard Edition Server found in the managed domains.

  • Connect to these servers only: This option allows you to configure a list from which you want Active Roles to select a Skype for Business Server computer. You can:

    • Add or remove computers from the list. Active Roles searches the managed domains for computers running the appropriate Skype for Business Server role, allowing you to select the desired computers.

    • Set the default computer. Active Roles first attempts to connect to that computer.

    • Reorder the list. Active Roles first attempts to connect to computers that are higher in the list.

NOTE: At least one of your Active Directory domains that hold computers running the Front End Server or Standard Edition Server must be registered with Active Roles as a managed domain. Otherwise, Active Roles cannot discover your Skype for Business Server deployment, and the Skype for Business Server User Management feature will not work.

SIP user name generation rule

The SIP User Name policy setting allows you to configure a rule for generating the SIP user name based on other properties of the user account. When adding a new Skype for Business Server user, Active Roles uses that rule to generate the SIP user name on the Web Interface page for enabling users for Skype for Business Server. The rule has an effect if you select the SIP address option that provides for entering a SIP user name. On the page where you edit Skype for Business Server users, the rule performs a validation function, preventing changes to the SIP user name that violate the rule.

To configure a rule, set up a value that acts as a template for the SIP user name. You can add one or more entries to the value, with each entry representing one of the following:

  • Text: A text string. You can type the desired text when adding the entry.

  • User Property: A particular property of the user account. You can choose the desired property and specify whether you want the entry to include the entire property or a part of the property.

  • Parent OU Property: A particular property of the Organizational Unit that holds the user account. You can choose the desired property and specify whether you want the entry to include the entire property or a part of the property.

  • Parent Domain Property: A particular property of the Active Directory domain that holds the user account. You can choose the desired property and specify whether you want the entry to include the entire property or a part of the property.

The rule sets the SIP user name to the string value obtained by calculating each entry and then concatenating the calculation results so that they form a single string value.

By default, the policy allows the generated name to be modified. The SIP User Name policy setting provides the option to prevent changing the generated name. If you select that option, the SIP user name is read-only on the Web Interface page for enabling users for Skype for Business Server.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating