RemoteApp and Desktop Connections the update was not successful

RemoteApp and Desktop Connections update problem 0x8007052e

Archived Forums

>

Remote Desktop Services [Terminal Services]

  • Question

  • 0

    Sign in to vote

    Hello,

    In our company environment we are using Windows 2012 R2 based RDS farm deployment with 2 HA connection brokers[these 2 servers are also have Web access role installed]. All client PC's have Windows 8 OS installed. We publishing remote application programs for our users via RemoteApp and Desktop Connection. Everything works fine except on thing that time to time RemoteApp and Desktop Connection are not updating and shows this error:

    Then we clicking "update now" system asking to enter credentials. After the entering domain username and password everything is updating. After this procedure updating works fine 2-4 weeks and then start failing again. Our users required to change password every 3 months. That means password changing can't be the reason of this error.

    Maybe it can be related with server rebooting? All RDS farm machines reboots once per month during the server patching

    Thanks for help in advance.





    • Edited by Andrej Trusevic Thursday, February 5, 2015 9:50 AM

    Thursday, February 5, 2015 9:23 AM

  • 0

    Sign in to vote

    Yes, after credentials are provided everything works and no other error messages logged.

    Saturday, February 7, 2015 3:03 PM

  • 0

    Sign in to vote

    Hi - I was just reading your thread on the error, and I have exactly the same symptoms. 3-4 weeks working, then the error. No reason for it in the Task Scheduler.

    Did you get to the root cause?

    Many Thanks

    Ian

    Tuesday, May 17, 2016 10:42 AM

  • 0

    Sign in to vote

    Hi all,

    This problem still exists in Windows Server 2016 and Windows 7 and Windows 10 clients.
    It's a bit different than the problem of Andrej. Even when providing the correct credentials, the update is not succeeding and the credential pop-up is appearing again.

    The only workaround is removing the workspace and re-apply it through Group Policy.

    I've made a little script for this, but a permanent fix is desired.

    reg delete HKEY_CURRENT_USER\Software\Microsoft\Workspaces\Feeds /f
    rmdir %APPDATA%\Microsoft\Workspaces\ /s /q
    rmdir "%APPDATA%\Microsoft\Windows\Start Menu\Programs\%Name% RDS [RADC]" /s /q
    gpupdate /force

    Anyone facing the same issue or has more info on how to resolved this?

    Kind regards,

    Thomas


    Thursday, March 28, 2019 10:06 AM

Chủ Đề