This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(86.4, 20%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELB%3C/text%3E%3C/svg%3E)
Office is reporting it cannot connect to my account (for all my users of the Remote Desktop Server 2008 R2)
yes I have E3 licenses assigned to all my users
Yes set for shared activation
According to your description, are you using Microsoft 365 apps instead of Office 2016?
If yes, please refer to this article first. “"Sorry, we can't connect to your account. Please try again later" error when you activate Office from Office 365”.
There are some troubleshoot steps, you may have a look.
In addition, please note, TLS 1.0 and 1.1 support is being deprecated by Microsoft. If your connections for Office services rely on these TLS protocols, it's best to remove the dependencies on TLS 1.0 and 1.1 and upgrade to TLS 1.2 as soon as possible.
For more information, please refer to "Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows".
Any updates, please let me know.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 50%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
Hello,
I have applied the different solutions you propose but the result is the same.
I'm using Office 365 (version 2002 build 12527.21416) on Windows Server 2008 R2.
I tried to install Office 365 again but the installation is not progressing.
I don't know where to look anymore.
Thanks for your help.
Thomas
@Thomas
As a best pratice on Q&A forum, could you please post a new thread and provide the deatiled information of your issue, such as how did you install Office?
Thanks for your understanding.
@Lanier, Berwick
I am checking this thread, if you have any updates, welcome back and share with us.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 39%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAA%3C/text%3E%3C/svg%3E)
Thanks @Emily Hua-MSFT , used the EasyFix from "Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows" and it fixed Shared Activation with Modern Authentication for me on a 2008 R2 server running Office 365 version 2002.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 3%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECH%3C/text%3E%3C/svg%3E)
Same here. That resolved the issue for us.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 8%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBL%3C/text%3E%3C/svg%3E)
YES!!! This worked for me as well though I also did a full uninstall and reinstall with the ODT tool.
Then ran the EasyFix and verified the registry keys, rebooted and activation for all Microsoft 365 E5 licensees is now working as it had been.
Microsoft needs to turn this into a comprehensive KB since the move to require newer TLS has broken working systems out of the blue.
Hello,
I have the same issue and for the moment i don't find a solution.
I will be happy if someone finds a solution.