We are testing 10.2.200.12 and plan to go live in a couple months. I have not needed to Reboot the server in a while. I had to reboot it today and ran into an issue or question about order and auto starting of services.
I had stopped the task agent services then stopped application pool.
When the server came back up the Application Pool started but the Task Agent Services did not. I had to manually start them then stop and start the Application pool.
What needs to be set so I don’t have to manually do this? I could not find it in any of the settings. If I have to do this manually what is the correct order or process.
Doing routine rebooting might be a good script to write to ensure repeatability. If
you have some PowerShell experience you could possibly look at calling the appropriate items in order you dictate.
I’m not the authority here, but I believe if you stop the Task Agent Service, this is considered to be a system level action, and the service will start automatically when the server boots. If you stop the individual agents, this is more of a business process, and you have to restart the agent. If this isn’t intentional behavior, I’ve found that it works this way, which can be nice when you don’t want a task agent to run, but you do need to restart the server. If they always restarted all task agents, scheduled things could happen when you otherwise intend to temporarily suspend the agent. Again, just my observations.