Export (0) Print
Expand All
Expand Minimize

Grant-CsSetupPermission

 

Topic Last Modified: 2013-02-21

Grants Lync Server setup permissions on an Active Directory organizational unit (OU). This cmdlet was introduced in Lync Server 2010.

Grant-CsSetupPermission -ComputerOU <String> [-Confirm [<SwitchParameter>]] [-Domain <Fqdn>] [-DomainController <Fqdn>] [-Force <SwitchParameter>] [-GlobalCatalog <Fqdn>] [-Report <String>] [-WhatIf [<SwitchParameter>]]

The command shown in Example 1 grants setup permissions for the CsServers OU in the domain litwareinc.com.

Grant-CsSetupPermission -ComputerOU "ou=CsServers,dc=litwareinc,dc=com"

The domain preparation that takes place when you install Lync Server does not automatically add the permissions that enable members of the RTCUniversalServerAdmins group to run the Enable-CsTopology cmdlet. That means that, by default, you must be a domain administrator in order to enable a topology. To give members of the RTCUniversalServerAdmins group the right to enable a topology you must run the Grant-CsSetupPermissions cmdlet. In addition, you will need to run this cmdlet against each Active Directory container that houses computers running Lync Server.

Keep in mind that this cmdlet only grants permissions to the RTCUniversalServerAdmins group; the cmdlet cannot be used to grant permissions to other security groups or to individual users.

Who can run this cmdlet: You must be a domain administrator in order to run the Grant-CsSetupPermission cmdlet locally. 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 "Grant-CsSetupPermission"}

 

Parameter Required Type Description

ComputerOU

Required

System.String

Distinguished name of the OU containing the accounts for the computers where Lync Server will be (or has been) installed. For example: "ou=CsServers,dc=litwareinc,dc=com".

If you prefer you can leave off the domain portion of the distinguished name when specifying the OU. For example:

-ComputerOU "ou=CsServers"

Confirm

Optional

System.Management.Automation.SwitchParameter

Prompts you for confirmation before executing the command.

Domain

Optional

Microsoft.Rtc.Management.Deploy.Fqdn

Name of the domain where the OU is located. If this parameter is not included, then the Grant-CsSetupPermission cmdlet will look for the OU in the current domain.

DomainController

Optional

Microsoft.Rtc.Management.Deploy.Fqdn

Fully qualified name of the domain controller to be contacted when assigning the policy. For example: -DomainController atl-dc-001.litwareinc.com.

If not specified, the Grant-CsSetupPermission cmdlet will contact the nearest available domain controller when assigning the policy.

Force

Optional

System.Management.Automation.SwitchParameter

Suppresses the display of any non-fatal error message that might occur when running the command.

GlobalCatalog

Optional

Microsoft.Rtc.Management.Deploy.Fqdn

Fully qualified name of the global catalog server to be contacted when assigning the policy. For example: -GlobalCatalog atl-dc-001.litwareinc.com.

If not specified, the Grant-CsSetupPermission cmdlet will contact the nearest available global catalog server when assigning the policy.

Report

Optional

System.String

Enables you to specify a file path for the log file created when the cmdlet runs. For example: -Report "C:\Logs\SetupPermissions.html"

WhatIf

Optional

System.Management.Automation.SwitchParameter

Describes what would happen if you executed the command without actually executing the command.

None. The Grant-CsSetupPermission cmdlet does not accept pipelined input.

None. The Grant-CsSetupPermission cmdlet does not return any objects or values.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft