Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

How to Configure Location Awareness for laptops

Created: 09 Jan 2013 • Updated: 09 Jan 2013 | 5 comments
DClark's picture

Hi all,

 

I was asked if it is possible to configure a laptop so it would sense where it is and then pull the updates from the nearest GUP available. From what I read Location Awareness might just be the right tool, but I could not grasp from the KB articles if this is possible.

 

What I would like to know is:

 

-Can a system be configured to sense a local GUP and then connect to it?

-If possible, how can this be configured?

-Are there any risks or considerations for this setup?

 

Thanks,

 

David

Comments 5 CommentsJump to latest comment

.Brian's picture

Yes, you can configure two different location, one for off the network and one for on the network and assign two separate policies. You would create one LiveUpdate policy and set it for clients to get updates from Symantec and assign it to the Off Network location and than create another LiveUpdate policy which defines the GUP and assign to the On Network location

 

Best Practices for Symantec Endpoint Protection Location Awareness

Article:TECH98211  |  Created: 2009-01-20  |  Updated: 2012-06-07  |  Article URL http://www.symantec.com/docs/TECH98211

 

Using location awareness with groups

Article:HOWTO26994  |  Created: 2010-01-08  |  Updated: 2010-01-15  |  Article URL http://www.symantec.com/docs/HOWTO26994

 

How To Optimize Endpoint Protection for Branch Offices using GUPs, Load Balancing, and Location Awareness

Article:TECH94122  |  Created: 2009-01-21  |  Updated: 2011-01-24  |  Article URL http://www.symantec.com/docs/TECH94122

 

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

SMLatCST's picture

To be fair, as we're mentioning GUPs, you may not need go to so much trouble.

The multiple GUP feature allows you to define a long list of GUPs which is passed onto SEP clients.  Using this feature, the SEP Clients then take this list, determine if it is in the same subnet as any of the GUPs, and use one if so.

This is best used if you are able to find a machine to act as a GUP in each of your subnets, but negates the requirement to use Location Awareness.  As the logic is performed by the SEP Clients, this is generally easier to implement.

There aren't really any risks to using GUPs per se as it is just a proxy cache for defs, but you do need to consider what SEP clients should do if a GUP fails (i.e. should they not update at all, use a 'backup' GUP, or go straight to the SEPM?).

I'd recommend reading up ont he below article on GUP best practices:

http://www.symantec.com/docs/TECH93813

http://www.symantec.com/docs/TECH95353

If you're still interested in Location Awareness, the Brian's links should sort you out.

Ajit Jha's picture

Hi,

I was about to post this above example by SMLatCST, its really a good one. You should go through the Scenarios mentioned in it. Also ypu can have understandings on Explicit Group Update Providers (GUPs) for Roaming Clients

http://www.symantec.com/business/support/index?pag...

Regard's

Ajit Jha

Technical Consultant

ASC & STS