W2K19 server - remoteapps issue

%3CLINGO-SUB%20id%3D%22lingo-sub-1527638%22%20slang%3D%22en-US%22%3EW2K19%20server%20-%20remoteapps%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1527638%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20got%20a%20good%20for%20you%20all...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20one%20windows%2010%20v1909%20workstation%20that%20is%20unable%20to%20connect%20back%20into%20remoteapps%20after%20the%20user%20logs%20off%20the%20workstation.%20It%20will%20work%20on%20the%20first%20login%20to%20the%20workstation%2C%20once%20the%20user%20logs%20off%20it%20is%20unable%20to%20connect%20back%20again.%20Nor%20is%20it%20able%20to%20remote%20desktop%20to%20the%20server%20(it%20is%20able%20to%20remote%20desktop%20to%20any%20other%20server%20in%20the%20office).%26nbsp%3B%20We%20can%20get%20an%20%22internal%20error%20has%20occured%22%20msg%20.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20other%20workstations%20in%20the%20office%20is%20having%20this%20issue.%20We%20have%20enough%20TS%20licenses%20in%20license%20manager%20with%20an%20extra%204%20licenses%20to%20spare.%20We've%20disconnected%20the%20TS%20sessions%2C%20checked%20the%20event%20logs%20(which%20shows%20authentication%20is%20successful%20for%20that%20workstation)%2C%20restarted%20remote%20deskop%20services%20on%20the%20server.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20only%20fix%20we%20have%20now%20is%20to%20reboot%20the%20server.%20Then%20the%20workstation%20is%20able%20to%20connect%20until%20the%20user%20logs%20off%20from%20it.%20(which%20we%20informed%20then%20to%20not%20to%20at%20the%20moment)%20When%20it%20is%20working%2C%20we%20can%20close%20out%20of%20remote%20apps%2C%20go%20back%20into%20it%20without%20an%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20Installed%20the%20latest%20updates%20on%20the%20windows%2010%20-%26nbsp%3B%20didnt%20help.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%20we%20do%20not%20have%20a%20windows%20restore%20point%20to%20fall%20back%20on.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20included%20a%20screenshot%20of%20the%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20is%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EChargr%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1527638%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eremoteapps%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETerminal%20services%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EW2k19%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1527862%22%20slang%3D%22en-US%22%3ERe%3A%20W2K19%20server%20-%20remoteapps%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1527862%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20this%20is%20a%20domain%20joined%20desktop%2C%20you%20may%20have%20a%20corrupted%20GPO.%20You%20may%20need%20to%20perform%20a%20domain%20removal%2C%20clean%20not%20the%20GPO%20settings%2C%20then%20re-join%20desktop%20to%20domain.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1528232%22%20slang%3D%22en-US%22%3ERe%3A%20W2K19%20server%20-%20remoteapps%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1528232%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F380907%22%20target%3D%22_blank%22%3E%40RADCOE%3C%2FA%3EThanks%20for%20the%20reply%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%20the%20machine%20is%20joined%20to%20the%20domain%20-%20disjoin%20-%20rejoin%20did%20not%20work.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20tried%20all%20the%20suggested%20fixes%20in%20the%20link%20as%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fappuals.com%2Ffix-remote-desktop-connection-internal-error-has-occurred%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fappuals.com%2Ffix-remote-desktop-connection-internal-error-has-occurred%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hello everyone,

 

I got a good for you all...

 

We have one windows 10 v1909 workstation that is unable to connect back into remoteapps after the user logs off the workstation. It will work on the first login to the workstation, once the user logs off it is unable to connect back again. Nor is it able to remote desktop to the server (it is able to remote desktop to any other server in the office).  We can get an "internal error has occured" msg .

 

No other workstations in the office is having this issue. We have enough TS licenses in license manager with an extra 4 licenses to spare. We've disconnected the TS sessions, checked the event logs (which shows authentication is successful for that workstation), restarted remote deskop services on the server.

 

The only fix we have now is to reboot the server. Then the workstation is able to connect until the user logs off from it. (which we informed then to not to at the moment) When it is working, we can close out of remote apps, go back into it without an issue.

 

Also Installed the latest updates on the windows 10 -  didnt help. 

 

Unfortunately we do not have a windows restore point to fall back on.

 

I included a screenshot of the error.

 

Any help is appreciated.

 

thanks,

 

Chargr

2 Replies
Highlighted

If this is a domain joined desktop, you may have a corrupted GPO. You may need to perform a domain removal, clean not the GPO settings, then re-join desktop to domain.

Highlighted

@RADCOEThanks for the reply

 

Yes the machine is joined to the domain - disjoin - rejoin did not work.

 

We tried all the suggested fixes in the link as well.

 

https://appuals.com/fix-remote-desktop-connection-internal-error-has-occurred/