firstname.lastname@example.orgThe only way I'm aware of doing anything with the hotfixes is to have it enabled or disabled. I've gone back to manual updates because when it cycles the asp.net process. This apparently can happen when a hotfix is released that involves a dll or when the asp.net process recycles at a set time.
They have a hotfix that's being tested already from what i'm being told but hasn't been released public yet until it is confirmed working. Here are the suggestions i was given:
1. One suggestion to stop it from occurring during the day is to turn of automatic hotfixes and then manually apply them during the late afternoon or evening. I know that is a pain but if you do this for the interium (until the session hotfix is completed) the customer experience won't be impacted.
2. You can change the automatic recycle to be off hours so that does not run every 29 hours. You change that setting in IIS (from the developer here is what you do) - if they are using an application pool and if that pool is configured with the default setting of ‘Recycle worker processes (in minutes): 1740’. This will cause a recycle every 1740 minutes or 29 hours. A better configuration would be to advise the customer to set up recycling at a specific time, when volume is low.
I have not tried option 2, i just got for option 1 and then disclose in support tickets that i open that we have automatic checks turned off on purpose.