SharePoint 2019 Timer Jobs running only on App Server By Default

Question

I migrated from SP 2013 to SP 2019. I have 2 WFE + 2 APP servers. I see a difference in timer job. In SP 2013 all timer jobs used to run on both the front ends, but in SP 2013 all timer jobs I see are scheduled to run on both App Server. Is this an issue or is it by default? For eg. I took screenshot of one random timer job from SP2019. It is scheduled to run on both app server. This is the case with all OOB as well as custom timer jobs. But in SP2013 farm it was all on WFEs

Answer 1

Hi @shashank ,

After some research, we think it is by default and there shouldn't be any bad effects. There is currently no official document documenting how the timer job picks the server. However per my knowledge, in your migration process, you should first migrate SP2013 to SP2016 and then SP2019. There is a concept of main role in SP 2016, which does not exist in SP 2013. These are some changes that have only been made since SP2016.

See reference:
Description of MinRole and associated services in SharePoint Servers 2016, 2019, and Subscription Edition

We will set up some similar environments to observe, and any updates will be post here. :)

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

in general it is Ok to have timer jobs running on App server. However if you need to run it on WFE you may try this: go to Central administration > Manage content databases > Select appropriate web app and click on the content database from the list > In "Preferred Server for Timer Jobs" dropdown list select required server.