Sage 100

Just starting bumping into this at some clients while trying to RDP to them. The quick fix is to uninstall a MSFT update, but it will reappear if you don't deny it forever. The permanent fix is to install the MSFT updates on the server side as well. https://social.msdn.microsoft.com/Forums/windowsapps/en-US/82b9f99b-436d-4e66-a461-06401d30ba13/remote-desktop-suddenly-broken-due-to-credssp-encryption-oracle-remediation?forum=WAVirtualMachinesforWindows

If the client doesn't have immediate access to their server, then the workaround is the only thing possible (along with uninstalling the update). We actually have a KB on that as well, since we were cornered in this situation as a hosting provider with no control over our user's workstations. For those dealing with the same issue: https://support.gotomyerp.com/portal/kb/articles/receiving-message-an-authentication-error-has-occurred-resolved

Between this and the MS update that screwed up paperless AGAIN - fie on MS!!!!!

@JeffSchwenk Thanks! Good info. I just ran into this recently.

I had this battle yesterday with a remote server. IT ended up unchecking ""Allow connections only from computers running Remote Desktop with Network Level Authentication"" found in Computer > Properties > Change Settings > Remote Tab. I'm sure it undermines all of the security that Microsoft was trying to put in place with the update but at least work can continue.

@KateKrueger This solution will work, but not in all cases. If you're stuck, you can do the GPO / Registry work around. It's easy to do, reversible, and definitely solves the problem until everything is correctly patched.

Add this to your registry on your local computer if you want to use RDP: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters] ""AllowEncryptionOracle""=dword:00000002 Once you add this you need to reboot your computer and then you can connect again.

Just ran into this - thanks everyone!