"Access denied 0x80004005" issue - RDP session - Windows server 2016 - User logon time out after disconnecting

Haneesha .Kappala 1 Reputation point
2020-08-01T17:00:23.82+00:00

I have scheduled a task running all the time on my Windows server 2016.

Connecting through RDS, few functionalities require user to be logged on to the server to be processed but it seems user log offs after a time limit. After certain time limit, task was facing "Access denied 0x80004005" Error

i have tried changing the following in RDS host settings in group policy:

automatic re connection -> enabled
deny logoff of an administrator logged in to the console session -> enabled
configure keep alive connection interval -> 99999
session time limits -> disabled
But they didnt help my task, still its facing "Access denied 0x80004005" Error

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,263 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. T. Kujala 8,706 Reputation points
    2020-08-01T17:38:37.287+00:00

    Hi @Haneesha .Kappala ,

    If the user account that runs task is member of Administrators group, you could select "Run with highest privileges" in the task and test if it helps.

  2. Jenny Yan-MSFT 9,326 Reputation points
    2020-08-03T05:59:10.437+00:00

    Hi,

    1. Please check the timeout settings via GUI on server manager of connection broker, open the properties of the collection(s) -- Sessions tab.
    2. For the group policies, if you do not have a RDS Deployment or the RDSH servers are not a member of a collection then you will need to set the session timeouts via group policy instead of in collection properties.
      Also ensure that you've run gpupdate /force on the RDSH servers after modifying settings.
    3. If there is RD Gateway in your deployment, open RD Gateway Manager and please verify the timeouts are set as desired in the Properties of the RD CAPs.

    After making the changes please have your users completely sign off of their session and log back on for the change to take effect.

    Thanks,
    Jenny