Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Using Location Awareness with GUPS

Updated: 21 May 2010 | 3 comments
jsnyder's picture
0 0 Votes
Login to vote

Hello all,

 

I just wanted to double-check a proposed architecture for our SEP 11 environment here at my company. 

 

The scenario is this - many of our users travel between offices on a daily basis and so we want to make sure that the SEP 11 client is looking at the local GUP for definitions so traffic happens over the LAN and not the WAN.

 

What we are proposing is setting up a GUP in each office to handle definitions.  Then we would create a "location" for each office based off of networking settings and have location awareness turned on.  So as clients travel between offices location awareness will be able to determine which office they are in.  We would then have a Live Update policy for each office that points to the local GUP.

 

Basically it would look like this:

 

Clients in Office A:   Live Update policy for location A points to Location A GUP

Clients in Office B:   Live Update policy for location B points to Location B GUP

etc,etc

 

My question is can GUPS be assigned in this manner?  Everything I keep reading always talks about GUPS and clients within a group.  However, what we are proposing is not to use groups (which are static) but instead to use location awareness since that is more applicable for us due to our traveling user base.

 

From what I can see this should work just fine, but I wanted to run it by others before we impliment it.

 

Jeff

Comments

jsnyder's picture
18
Jul
2008
0 Votes 0
Login to vote

The sound of crickets chirping is deafening.  Could someone from Symantec let me know if this will work or not?  A lot of our architecture depends on it.

 

Can I set-up my architecture as follows:

  • All clients reside under Global group
  • A separate Live Update policy exists for each office and will specify a local machine as a GUP (ie Office A Live Update policy uses machine A as a GUP, Office B Live Update policy uses machine B as a GUP, etc)
  • As clients travel between offices location awareness determines which office they are in and applies the correct Live Update policy, thus pointing the client to the correct GUP.

 

In essence this is what I want to achieve:

  • Client travels to Office A.
  • Location awareness then applies Office A's Live Update Policy which has GUP "A" listed
  • Client then travels to Office B
  • Location awareness then applies Office B's Live Update Policy which has GUP "B" listed

 

I don't want to use groups because my environment is not static enough for me to assign clients that way.

 

Thanks,

Jeff

RickJDS's picture
18
Jul
2008
0 Votes 0
Login to vote

Since GUP's are defined in Live Update policies and those policies are location specific, it should work as you can have multiple location per group.  You just have to specify the ip address range or subnet info (or any of the other options) to make the locations unique.

susanthas-123's picture
18
Jul
2008
0 Votes 0
Login to vote

Hi,

 

I'm not sure the if that is a suitable solution. One thing is you may have to creat n number of location awarness plocies adn also live update polcies. Apart fromt hat when a client visit a site how soon would he get the policy updated and then update the def. Conisdering all these one best option is if the users pc is not in the original location then reterive the latest def from the internet. (Of course I assume other sites having internet connections) 

I know therotically your solution should work but being deployed so many SEP deployments in client sides I doubt what you're trying to acheive.