Well how about a new and refreshing idea? I suggest VMK try to run without the automatic disconnect. Maybe it just isn't needed?
Monitoring of the servers and such should be done at various times of the day and under various loads of users to determine if an automatic disconnect is really needed. If everything works okay say 95% of the time, then don't have an automatic disconnect. Another possibility would be to only activate the automatic disconnect for the 5% of the time that it is needed.
If it turns out they really do need an automatic disconnect, then they should time that to match the data from monitoring the servers and such. If that's too difficult (or time consuming) then start with say, a three hour window and monitor performance as listed above. If it works, then that should be the number. If it doesn't work, reduce the number to two hours and see how that works. If an automatic disconnect needs to be used, I suspect it doesn't need to be as often as 45 minutes.
On a slightly different topic, perhaps one of the reasons for having the automatic disconnect is for account security. I can picture a person signing on using a school computer (or other public computer like at a library) and forgetting to sign off when they leave. I believe that sort of issue should be handled at the local level, not by VMK.
Can you tell I used to do a lot of load testing and performance monitoring during my computer career?
qruthie (the 'q' is silent)