Verifies that the required permissions needed to install Microsoft Communications Server or one of its components have been configured on the specified Active Directory container.
Syntax
Test-CsSetupPermission -ComputerOu <String> [-Domain <Fqdn>] [-DomainController <Fqdn>] [-Force <SwitchParameter>] [-GlobalCatalog <Fqdn>] [-Report <String>] |
Parameters
Parameter | Required | Type | Description |
---|---|---|---|
Domain |
Optional |
String |
Name of the domain where the OU to be checked is located. If this parameter is not included, then Test-CsSetupPermission will look for the OU on the current domain. |
ComputerOU |
Required |
Active Directory distinguished name |
Distinguished name of the OU which contains the accounts for the computers where Microsoft Communications Server will be installed. For example: "ou=CsServers,dc=litwareinc,dc=com". |
DomainController |
Optional |
String |
Fully qualified domain name of a domain controller in your domain. This parameter is not required if you are running Test-CsSetupPermission on a computer with an account in your domain. |
GlobalCatalog |
Optional |
String |
Fully qualified domain name of a global catalog server in your domain. This parameter is not required if you are running Test-CsSetupPermission on a computer with an account in your domain. |
Report |
Optional |
String |
Reports detailed activity to the screen as the cmdlet runs. |
Force |
Optional |
Switch Parameter |
Suppresses the display of any non-fatal error message that might arise when running the command. |
Verbose |
Optional |
Switch Parameter |
Reports detailed activity to the screen as the cmdlet runs. |
Detailed Description
If you have locked down your Active Directory domain (that is, if you have disabled permission inheritance) then the domain preparation that takes place when you install Microsoft Communications Server will not be able to add the permissions needed to do future installations of Communications Server or any of its components. (Domain administrators will still be able to perform these installation tasks, but members of the RTCUniversalServerAdmins group will not.) In that case, you will need to use the Grant-CsSetupPermission to grant the RTCUniversalServerAdmins group the appropriate permissions. You will need to do this on a container-by-container basis.
The Test-CsSetupPermission cmdlet enables you to determine whether or not the requisite permissions have been added to a given Active Directory container (that is, the container hosting computers running Communications Server or one of its components). Test-CsSetupPermission returns True if the correct permissions have been applied, and returns False if the correct permissions have not been applied. If the cmdlet returns False, you will need to run Grant-CsSetupPermission in order to make the necessary changes to the Active Directory container.
Return Types
Test-CsSetupPermission returns an instance of the Microsoft.Rtc.SyntheticTransactions.TaskOutput object.
Examples
-------------------------- Example 1 ------------------------
Copy Code | |
---|---|
Test-CsSetupPermission -ComputerOU "ou=CsServers,dc=litwareinc,dc=com" |
The command shown in Example 1 checks to see if the required setup permissions have been applied to the CsServers OU in the litwareinc.com domain.