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.

Problem with Gups

Created: 27 Dec 2010 | 8 comments
Rodrigo Benedik's picture
0 0 Votes
Login to vote

Hi,

 

Is there any problem on RU5 with GUPS, I'm asking because I've assigned my servers wich are domain controllers and are not at the same folder that clients are.

What I noticed is after I put them as GUP there are some servers that are not getting updates, and if i withdraw the Lu policy from the server it became to update again.

All clients and servers are at RU5, and the communications seems to be ok,( and the doubt is when take the gup policy the server became to update again!!!).

 

Thanks!!!

Comments

Rick Bywalski's picture
27
Dec
2010
0 Votes 0
Login to vote

Try RU6

If memory serves it was RU6 where the GUP no longer needed to be in the same group.  I may be wrong though.

Brian81's picture
27
Dec
2010
1 Vote +1
Login to vote

You need to make sure you

You need to make sure you create the LU policy for the GUP and assign it to the group that the GUP is in.

Prachand's picture
27
Dec
2010
0 Votes 0
Login to vote

Can you please get the sylink

Can you please get the sylink log from one of the Clients?

Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)

Kurt G.'s picture
27
Dec
2010
1 Vote +1
Login to vote

There are some issues with GUPs that have been resolved in the

There are some issues with GUPs that have been resolved in the latest release of SEP, RU6MP2.

There were several different issues with GUPs not working as expected in previous builds. It would be recommended to migrate to the latest release in order to ensure you are not experiencing these issues.

In addition as Brian81 mentioned above, both the client group and the GUP group needs to have a LiveUpdate policy designating the server as a GUP. The simplest way to perform this is to create a shared LiveUpdate policy with the same GUP configuration.

If you do not wish to use a shared LiveUpdate policy, you would need to ensure that the Server is listed as a GUP for its group LiveUpdate policy and that the clients' group that is to update from the GUP also has the same server listed.

Kurt G.
Symantec Technical Specialist: Endpoint Security Advanced Team

Symantec Corporation www.symantec.com

Symantec Enterprise Support: (800) 342 0652 

Pawel Lakomski's picture
28
Dec
2010
0 Votes 0
Login to vote

Moreover, what kind of GUPS

Moreover, what kind of GUPS do you use (single or multiple GUP)? What is your bypass time set in LU policy?

--

Cheers,

Symantec Technical Specialist
Symantec Certified Specialist
MCP & MCITP
Cisco Certified Network Associate
Citrix Certified Administrator

 

Rodrigo Benedik's picture
28
Dec
2010
0 Votes 0
Login to vote

Are Multiple GUP

And the policy I've put on both groups clients and servers, but what is happening is the servers that is providing the updates do not get anymore updates, and if i take out the policy work fine. At the clients sylink the server is on the gup list and at servers the shared LU folder is created. I'll try to update to the latest version to see....:(

Rodrigo Benedik

Rafeeq's picture
28
Dec
2010
0 Votes 0
Login to vote

hi

for them to work as GUP port 2967 should be open, check if thats open on u r servers.

Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq

pete_4u2002's picture
28
Dec
2010
0 Votes 0
Login to vote

client should be

client should be communicating on the GUP on port 2967, are you able to telnet?

can you post the sylink logs.