Jump to content

Remote controlling as service fails with Windows Server 2019

Recommended Posts


I'm remote controlling other applications mainly in windows services.

Therefore the service has to be logged on sytem account with "Allow service to interact with desktop" and

"NoInteractiveServices" within "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows" has to set to "0" (for Windows Server 2016)

Starting with Windows Server 2019 this route is not longer possible  (due to Microsoft's / Windows new policy).

Starting as an application with autologon is not a good idea due to IT department's restriction.

Starting a RDP session automatically might do the job ... but pretty convoluted.


Does anyone knows a workaround/solution to this challenge?






Link to post
Share on other sites

Hi, sorry for being inprecise.

The autoit script runs within the windows service and remote controls other applications (e.g Starting notepad, waiting for the main window, mouseclick bla.)

This road is no longer possible starting with Server 2019, as the service does not "see" notepad's desktop anymore.




Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...