The task has always run with the highest privileges, using an admin account, and set to run whether or not the user is logged on. However, now I am getting the task failing with an 0x2 error (which also happens if the task is run manually), and I've tried everything I can find suggested online - with or without speech marks in the fields, with or without the Start in field filled in. And it seems to have worked for several years. I therefore created a batch file to manually start it (containing one line - net start tssdis) and scheduled that individually on each terminal server, to run 15 minutes after the reboot. Several years ago I noticed that sometimes the connection broker service would start then immediately stop randomly after the reboot, and would not restart automatically. Therefore, I've created a scheduled task on the management machine which reboots the terminal servers in the middle of the night. ![]() ![]() We have several terminal servers (2019), and on all of them there are some Excel addins in use which can be temperamental and need a reboot if they give trouble.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |