Asked by:
Win2012R2 Powershell - Cannot connect to URI while executing New-CsOnlineSession

Question
-
Hi Folks
Should be a simple one, this works fine on WIn10 client. Trying to run this on a customer Win2012R2 box and it throws a wobbly:
----
$SfBsession = New-CsOnlineSession -Verbose -OverrideAdminDomain $MSDomain -Credential $cred
# Check PSSession
Import-PSSession -Session $SfBsession----
Checking for Connection to S4B
==============================================================
Connecting
VERBOSE: AdminDomain = '*****co****.onmicrosoft.com'
VERBOSE: Discovering PowerShell endpoint URI
Get-CsOnlinePowerShellEndpoint : The underlying connection was closed: An unexpected error occurred on a send.
At C:\Program Files\Common Files\Skype for Business
Online\Modules\SkypeOnlineConnector\SkypeOnlineConnectorStartup.psm1:149 char:26
+ ... targetUri = Get-CsOnlinePowerShellEndpoint -TargetDomain $adminDomain ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-CsOnlinePowerShellEndpoint], WebException
+ FullyQualifiedErrorId : System.Net.WebException,Microsoft.Rtc.Management.OnlineConnector.GetPowerShellEndpointCm
dlet
I've tried playing with TLS1.2 levels but I don't understand why it throws it's toys out of the pram. As you can see I have already specified the override URL. As I say, this works on a Win10 box.
Suggestions?
Thank you in advance.
- Edited by Geekphreek Tuesday, July 14, 2020 3:32 PM Cleaned up title
Tuesday, July 14, 2020 3:32 PM
All replies
-
Hi Geekphreek!
Does anyone else have the same issue?
What is your .net Framework version?
According to your error message, this issue seems related to TLS version.
In this case, we recommend you make sure you are using the most recent version of the .Net Framework. The following document shows TLS 1.0 and TLS 1.1 be prohibited as well:
https://tools.ietf.org/id/draft-moriarty-tls-oldversions-diediedie-00.html
Also, you can try to install the following updates for the .NetFrameWork in Window Server 2012 R2:
For more details about this error message troubleshooting, please refer to:
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Jimmy Yang
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.- Proposed as answer by Jimmyy_YangMicrosoft contingent staff Tuesday, July 21, 2020 9:55 AM
Wednesday, July 15, 2020 7:13 AM -
Hi,
Is there any update on this case?
Please feel free to drop us a note if there is any update.
Have a nice day!Best Regards,
Jimmy Yang
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.Friday, July 24, 2020 9:45 AM