-
Title
Powershell Error connecting to Lync / Skype for Business Pool -
Description
When attempting to connect to your Lync 2013 or Skype for Business pool you get the following error:
"An error occurred while attempting to initialize Lync Powershell 2. Make sure that the server is reachable. Verify that Windows Powershell 2 is installed and that the account used for the test Execution has sufficient rights."
Or
"Failed to resolve the target into the domain controller. Discovery data cannot be retrieved.
Windows API function (DsGetDcName) failed because 'The specified domain either does not exist or could not be contacted'"
-
Cause
The Override FQDN under Internal Web Services In the topology builder was configured. -
Resolution
When connecting to your Lync 2013/Skype pool if the Override FQDN under Internal Web Services In the topology builder is set that is the name that must be specified when connecting to your pool.
For Example if you create a Lync 2013/Skype pool named "pool1.company.com" but have the "Override FQDN" set to "Lync2013.company.com", When connecting to your pool in the SOM console you will need to specify Lync2013.company.com as the pool name.
To verify if the "Override FQDN" is set on a Lync server with the Topology Builder installed open Topology Builder and import your curent topology.
Go to properties of your pool and look under "Internal Web Services"
Some troubleshooting steps to test the remote powershell connection to your pool try the following from your SOM Server open up a powershell prompt and try the following steps. For the command at step 3 replace "pool1.company.com" with your pool name. If you get an access denied connecting to the pool name check to see if the "Override FQDN" is set and try connecting to that name. Also you can try connecting directly to a Front End Server.1. Get thecredentials for the Remote environment$credential = get-credential
2. Set session options to bypass the PKI checks - I trust the far side
$sessionoption = New-PSSessionOption -SkipCACheck -SkipCNCheck -SkipRevocationCheck
3. Create a new PowerShell Session, using the below example replacing it with your connection URI:
$session = New-PSSession -ConnectionUri https://pool1.company.com/ocspowershell -Credential $credential -SessionOption $sessionOption
4. assuming the above line worked, import the cmdlets needed for Lync
import-pssession $session
At this point you should be connect and be able to run your Lync/Skype Commands.
Try running get-csuser