Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
Michael Barnes

Cannot configure remote web access on Server 2016

Just completed a migration from SBS 2011 to Server 2016 Standard running the Essential role. Everything went pretty smoothly except for setting up remote web access. Running the remote access wizard from within the dashboard I log in using a Microsoft account but then get "an error occurred while setting up your domain name". In the dashboard log it shows Get live account name failed.

Anyone seen this error and know how to resolve it?

 

Thanks

asked05/16/2021 07:08
259 views
Add Comment
Last Activity 05/16/2021 14:32

1 Answer(s)

  • Mariette Knap

    Hello Michael,

    It is a known issue by now because Windows Server 2016 + Essentials does not default to TLS 1.2. The solution is to run the Powershell commands from below and reboot the server. After that try to run the wizard again.

    Pls, run this Powershell from an elevated Powershell prompt

    # PowerShell
New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force

New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\.NETFramework\v2.0.50727" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\.NETFramework\v2.0.50727" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force

     

    answered 05/16/2021 07:43
    Add Comment
    Michael Barnes

    Hi Mariette

    I see you've modified your original answer suggesting we run the Powershell commands whereas originally you posted some regfiles. I've actually already imported those files and this has resolved the problem. Would you suggest also running the Powershell commands above or do these essentially do the same thing?

    Mike

    Mariette Knap

    The Powershell is a bit more thorough. If you run that it will add more to what I previously suggested with the reg entries. The Powershell entries should fix it though without setting SCHANNEL in TLS12-Enable.reg

    replied 05/16/2021 09:25
    Reply
    replied 05/16/2021 08:31
    Michael Barnes

    Thanks Mariette. I spent what seemed like an age searching on Google for a solution to this and found nothing. You came back with a solution within minutes - should have just asked you first :) 

    Mariette Knap

    Thanks :)

    replied 05/16/2021 09:22
    Reply
    replied 05/16/2021 08:20
Add an Answer