Patch management load on startup / login speed
I have some questions about the overhead in terms of start up time/log on time when I use scripting to carry out functions like patch management, and the general communication between the desktop support client and the server. I work in a school environment where start-up/login time & shut down time is an issue � it eats into short 30 min lesson periods.
When the patch management is running, does it start to download patches during start-up/log-on or does it wait until the user is signed in? If downloading patches, does it do so with a lower priority so that other user generated services (documents, web browsers, etc) have priority?
What happens if a patch is not fully downloaded during a users session? Does it get appended to the next session or is the complete patch downloaded again?
What data is communicated to the Server during start up? Does the data collection or communication process use much processor/network resource?
Thank you
John
When the patch management is running, does it start to download patches during start-up/log-on or does it wait until the user is signed in? If downloading patches, does it do so with a lower priority so that other user generated services (documents, web browsers, etc) have priority?
What happens if a patch is not fully downloaded during a users session? Does it get appended to the next session or is the complete patch downloaded again?
What data is communicated to the Server during start up? Does the data collection or communication process use much processor/network resource?
Thank you
John