Remote Desktop Management Service fails with error 0x88250001

Bernd Abb 111 Reputation points

Hi all,

as I cannot find the reason, hopefully someone here can.
Du have a Server 2016 serving as standalone RDS Server.
When trying to setup RDS I cannot setup a collection.
Looking into the services, the rdms service is stopped.
When I try to start manually, it starts and stops automatically.
I can see two errors then:
Application log:
Informationen 26.09.2022 10:46:59 MSSQL$MICROSOFT##WID 18456 Logon
Login failed for user 'NT-AUTORITÄT\Netzwerkdienst'.
RDMS Admin Log:
"The Remote Desktop Management service failed to start. Error code: 0x88250001"

When I restart the local WID service, all services start perfectly fine and RDS spins up as it should.
Reinstalled the machine, changed OU to exclude GPOs, enabled TLS1 for WID, used fresh setup media, reinstalled WID, no success at all.

What really makes me wondering, is the error stating no access rights, but these seem to exist after restarting the WID.

Any input is highly appreciated!

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

  1. James Todler 0 Reputation points

    I’ve had a similar issue with RDS where the RDMS service wouldn’t stay running, and I haven’t found a permanent fix yet. Did you manage to get it sorted?

    In the meantime, I’ve been using HelpWire for file transfers as a workaround, but I’d really like to get RDS working properly without having to rely on that. Any ideas or suggestions?

2 answers

  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Limitless Technology 45,241 Reputation points

    Hello BernAbb,

    When these services become available once restarting WID service, usually means that the Logon account used on the service(s) related and dependencies may not be the same. Let's say that one service has a domain account, while the other has a System account. This could represent a vulnerability in the Authorization chain and there for ignored until there is an interactive action to start the service.

    The recommendation would be to check the service's Logon accounts in use, and replace using the same account for all the related services.

    ----------------------------------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept as answer--

    1. Bernd Abb 111 Reputation points

      Hi LimitlessTechnology,

      thank you very much for your reply.
      The service logon accounts are all setup standard, the WID uses the NT SERVICE\MSSQL$MICROSOFT##WID and the rdms service is running under networkservice account. So both from them do use a system account, which is the standard installation.
      Tracing the behaviour via procmon also delivered no pointer into that direction.
      This seems not to be the right path...sadly
      Please feel free to correct me, if I miss something.

      Best regards,
      Bernd