Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Better scheduling when upgradering SEP

Created: 28 Sep 2009 | 2 comments
LasseF's picture
5 Agree
1 Disagree
+4 6 Votes
Login to vote

Hi

I would like to see a better scheduling agent in SEPM. For example to have the option so force upgrade on a complete group instantly instead of having to add a time periode in the "Upgrade Schedule". I normally don't use the "Upgrade Schedule", I just added the new package and let SEPM do the rest, but with the latest upgrade that was not good enough.
I found out, while testing the new version, that the upgrade procedure would disconnect the LAN connection for a very short periode of time and when that happend it would give some errors in a program we use and also Outlook 2007 would say that some of the clients didn't have a connection to the Exchange server. This was not a problem before version 11.0.5002.333.

I see the following as a way to improve the scheduling agent:
- Force instant upgrade on "My Company" or a specific group
- Schedule a upgrade that actually starts on all computers at the same time
- Being able to tell SEPM that it should install the latest upgrade during logon, so that it doesn't run while the users are working.
- SEPM should be able to send a message to the user when it starts the upgrade, currently it tells when it begins the download, not the actual installation.

By being able to do a more specific upgrade it will be possible to tell the users when not to use their computers due to SEP maintenance.

/Lasse

Comments

timaa's picture
29
Sep
2009
2 Votes +2
Login to vote

I like your force idea

I do know that whenever the application is upgraded (and the client has the firewall) network connectivity is impacted because of how the firewall is tied to the TCP stack.

Scuba Steve's picture
29
Sep
2009
3 Votes +3
Login to vote

I am pretty sure that all

I am pretty sure that all versions will stop the network stack when upgrading the firewall driver. This has to be done in order to replace the mini-filter driver. I do believe that this isn't a product issue, as this will most likely happen to any product that is tied into the network stack.

The only other option would be to have the product upgrade, and then force the user to reboot so that we could unload and load the new network drivers into the stack at reboot. I guess it comes down to how much user impact would be involved. A quick disconnect/reconnect, or a full system reboot.