Enable-CsUser

Syntax

Enable-CsUser
      [-Identity] <UserIdParameter>
      [-RegistrarPool <Fqdn>]
      [-SipAddressType <AddressType>]
      [-SipDomain <Fqdn>]
      [-SipAddress <String>]
      [-HostingProviderProxyFqdn <Fqdn>]
      [-ProxyPool <Fqdn>]
      [-DomainController <Fqdn>]
      [-PassThru]
      [-WhatIf]
      [-Confirm]
      [<CommonParameters>]

Description

Before a user can log on to Skype for Business Server, that user must meet two requirements: he or she must have a valid Active Directory account, and that account must be enabled for Skype for Business Server. One way to enable a user account for Skype for Business Server is to use the Enable-CsUser cmdlet. To use this cmdlet to enable an account for Skype for Business Server, you must: 1) Select the account (or accounts) to be enabled; 2) Select a Registrar pool for the account; and 3) Assign the account a SIP address. Skype for Business Server gives administrators the option of assigning the user a specific SIP address or having Skype for Business Server create a SIP address for you.

By default, members of the following groups are authorized to run the Enable-CsUser cmdlet locally: RTCUniversalUserAdmins. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets -match "Enable-CsUser"}

Examples

-------------------------- Example 1 --------------------------

Enable-CsUser -Identity "Pilar Ackerman" -RegistrarPool "atl-cs-001.litwareinc.com" -SipAddressType SamAccountName -SipDomain litwareinc.com

In Example 1, the Enable-CsUser cmdlet enables the user account with the display name Pilar Ackerman. In this example, the user is assigned to the Registrar pool atl-cs-001.litwareinc.com, and Skype for Business Server auto-generates the SIP address by using the user's SamAccountName (pilar) followed by the SIP domain litwareinc.com.

-------------------------- Example 2 --------------------------

Enable-CsUser -Identity "Pilar Ackerman" -RegistrarPool "atl-cs-001.litwareinc.com" -SipAddress "sip:pilar@litwareinc.com"

In Example 2, the Active Directory user account belonging to Pilar Ackerman is enabled for use with Skype for Business Server. In order to configure the account for Skype for Business Server the following parameters are used along with the Enable-CsUser cmdlet: Identity, which identifies the account to be enabled; RegistrarPool, which indicates the Standard Edition server or Enterprise Edition Front End pool on which the user is to be homed; and SipAddress, which specifies the SIP address for the new user. In this case, the SIP address is explicitly assigned instead of using Skype for Business Server to auto-generate the address.

-------------------------- Example 3 --------------------------

Get-CsAdUser -LdapFilter "department=Finance" | Enable-CsUser -RegistrarPool "atl-cs-001.litwareinc.com" -SipAddressType SamAccountName -SipDomain litwareinc.com

In Example 3, all the users who work for the Finance department have their accounts enabled for Skype for Business Server. To carry out this task, the Get-CsAdUser cmdlet is used, along with the LdapFilter parameter, to return a collection of all the users who work for the Finance department. That information is then piped to the Enable-CsUser cmdlet, which enables each account in the collection for Skype for Business Server.

In order to enable an account, you must specify the user's Registrar pool and the user's SIP address. In this example, the Registrar pool is specified by using the RegistrarPool parameter. The SIP address is not directly assigned, however. Instead, two parameters, SipAddressType and SipDomain, are added to the command. That means that a new SIP address consisting of the user's SamAccountName and the SIP domain name will automatically be generated for each account. For example, a user with the SamAccountName kenmyer will be given the SIP address sip:kenmyer@litwareinc.com.

-------------------------- Example 4 --------------------------

Get-CsAdUser -Filter {Enabled -ne $True} | Enable-CsUser -RegistrarPool "atl-cs-001.litwareinc.com" -SipAddressType SamAccountName -SipDomain litwareinc.com

Example 4 enables all the Active Directory users who have not yet been enabled for Skype for Business Server. To do this, the Get-CsAdUser cmdlet is invoked, along with the Filter parameter. The filter {Enabled -ne $True} returns a collection of all the users who have not been enabled for Skype for Business Server. That collection is then piped to the Enable-CsUser cmdlet, which enables each account, assigning the user to the Registrar pool atl-cs-001.litwareinc.com and auto-generating a SIP address for each user.

-------------------------- Example 5 --------------------------

Enable-CsUser -Identity user@litwareinc.com -HostingProvider sipfed.online.lync.com -SipAddressType UserPrincipalName

Example 5 populates an existing Active Directory user in on-premises Skype for Business server who has been enabled for Skype for Business Online, or Microsoft Teams. The parameter -HostingProvider sipfed.online.lync.com specifies that the user is homed online, not on premises.

Parameters

-Confirm

-DomainController

-HostingProviderProxyFqdn

-Identity

-PassThru

-ProxyPool

-RegistrarPool

-SipAddress

-SipAddressType

-SipDomain

-WhatIf

Inputs

String or Microsoft.Rtc.Management.ADConnect.Schema.ADUser

The Enable-CsUser cmdlet accepts a pipelined string value representing the Identity of a user account that has been enabled for Skype for Business Server. The cmdlet also accepts pipelined instances of the Active Directory user object.

Outputs

None

The Enable-CsUser cmdlet does not return a value or object. Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.ADConnect.Schema.ADUser object.

Related Links

• Disable-CsUser
• Get-CsUser