Video Screencast Help

Can SEPM prioritise Updates?

Created: 30 Oct 2012 • Updated: 30 Oct 2012 | 7 comments
This issue has been solved. See solution.

I currently have a setup with multiple GUPs and was just wondering if there was any way as soon as a definition update is available to the SEPM to get it to prioritise updating the GUPs first before any clients? As on some of the groups I have a setup where they can only recive updates from the GUP only and usually by the time the GUP gets updated and starts to update the machine there's another def release so the machines are always playing catch up.

Comments 7 CommentsJump to latest comment

Ashish-Sharma's picture

HI,

You will Configure all sep Client will be update Only GUP not be trying Default management server.

 

Thanks In Advance

Ashish Sharma

 

 

GeoGeo's picture

There are still groups of clients that goto default manager as well on the setup but want to know if SEPM can proritise the update of the GUPs first before it starts to update the other clients?

Please review ideas and vote there could be something useful :)

https://www-secure.symantec.com/connect/security/ideas

 

_Brian's picture

There is nothing like this available to prioritise. Perhaps you can add the Idea.

Ashish-Sharma's picture

Hi,

May be this option not available.

You can Create Policy setting all sep client update virus defination only GUP.

Thanks In Advance

Ashish Sharma

 

 

pete_4u2002's picture

if you set to bypass GUP after X minutes/hrs the client will connect to SEPM for update request

GeoGeo's picture

I've submitted an idea on the forums for this functionality.

https://www-secure.symantec.com/connect/ideas/sepm-gup-priority-update

Please review ideas and vote there could be something useful :)

https://www-secure.symantec.com/connect/security/ideas

 

SOLUTION
SMLatCST's picture

This idea is not really required for GUP functionality.

GUPs don't provide updates to other SEP clients from their own definitions, but rather have a separate repository for definitions provided via the GUP feature (as per http://www.symantec.com/docs/TECH102541).  As such, GUPs are not required to already be on the latest definitions for the other SEP clients to obtain the latest defs from them.

Case in point, you can lock a GUP to yesterday's definitions (using a separate LU Content policy), but it will still be able to provide today's defs to other clients.

#EDIT#

As an aside, despite it not being required, you can generate the behaviour you've described by putting all your GUPs in a separate group and changing that group's "Communications Settings" to use either PUSH mode or a smaller Heartbeat interval.  This means the GUP are more likely to be aware of the latest definitions earlier than other SEP Clients.