Video Screencast Help
Search Video Help Close Back
to help

GUP question (should be simple)!

Created: 06 Aug 2012 | Updated: 07 Sep 2012 | 7 comments
Marty Kuklinski's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Let's say I have a Group (I have a GUP in this group), also in this group I have 2 sub-groups (let's say workstations and servers), if I assign the sub-groups to get updates from the GUP in the main group, will it work?  Or do I need a GUP for each sub-group.

 

I want to keep workstations and servers in different groups due to the policy differences, but would only like to use 1 GUP for def updates.

 

Thoughts?

Thanks

Marty

Comments 7 CommentsJump to latest comment

dgh's picture

That will work. As long as the clients know which GUP to use, and that client knows it is a GUP, it will work.

0
Login to vote
  • Actions
Marty Kuklinski's picture

I know that (because I tried it) if I have a group with all the GUPs in it, other groups don't update.  I tried to put my GUPs into their own group, and other groups wouldn't update from them.

0
Login to vote
  • Actions
ManishS's picture

Hi,

Understanding and Identifying the different Group Update Provider (GUP) Options in SEP 11.0.5 RU5 and Later

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

Don't read over this important paragraph:

However, there are two situations where a GUP in a different subnet may be contacted:
  • If you have configured a "Backup" Group Update Provider on a different subnet (if Group Update Providers on the local subnet are unavailable). 
  • If you have configured a GUP from a different Subnet as a Single Group Update Provider.

The GUP whitepaper is also a good reference.

Check this fourms for help.

https://www-secure.symantec.com/connect/forums/gups-different-groups

Thanks In Advance.

Manish

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

SOLUTION
+1
Login to vote
  • Actions
dgh's picture

The documents posted above by Manish are very good references. Your setup is almost identical to ours - we use servers as GUPs because they are available 24/7, but we have desktops and servers in separate groups so we can apply different scan policies etc.

Try using the fully qualified domain name in the GUP assignment field of the LiveUpdate policy. Check Windows Firewall is not blocking GUP requests.

+1
Login to vote
  • Actions
Brian81's picture

It depends on the conditions you use for the clients to identify what GUPs to use but as long as they are the same, they should update regardless.

+1
Login to vote
  • Actions
Mithun Sanghavi's picture

Hello,

Thumbs up to the above comments.

The computer that you select as the GUP must have a LiveUpdate policy that defines it as a GUP. Clients a GUP serves must have a policy that points them to their GUP.

If the Group Update Provider runs a Firewall, you must modify the Firewall policy to receive communications on TCP port 2967.

Hope that helps!!

Mithun Sanghavi
Symantec Technical Support Engineer, SEP
MIM | MCSA | MCTS | STS | ITIL v3

Twitter: @mithun_sanghavi

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<&a

0
Login to vote
  • Actions
SameerU's picture

Please enter the IP address of GUP in multiple Group Update Provider

Regards

 

0
Login to vote
  • Actions