How does varying the Min and Max job time out affect performance on ITCM in a large scale deployments?
You can configure jobs to time out if they have not started their execution within a certain time period. The following parameters set a limit to the range of possible time-out values defined when a job is set up.
Would like to make the case to extend the Max job time-out to lessen the Reimage catalog job. Reimaging through Microsoft build process is near 45 minutes and leave little time for larger installs to run.
This should not have a great impact on performance. Once the job has been created the major load on the DM is over. After this the load is only the job triggering which is done by the SS.
Always a good idea to test first though.