Video Screencast Help

GUPs not working after Management server upgrade

Created: 17 Jan 2013 • Updated: 17 Feb 2013 | 19 comments
This issue has been solved. See solution.

Hi,

Recently, i had upgraded all my managerment servers fom SEP11 RU5 to SEP12.1RU2.
Then I noticed that all my GUPs stop functioning. The SharedUpdates folder on the GUPs no longer gets updates even though the agent was updated.
The SEP Agents on my GUPs and clients are still on SEP11RU5 and MR4.

My Question is that does the agents on the GUPs should have the same version as the management server in order for the GUPs to function ?

Please advise.

 

 

Comments 19 CommentsJump to latest comment

Sumit G's picture

 it required to upgrade. Because you upgrade the SEPM version from 11.x to 12.x

Regards

Sumit G.

Ambesh_444's picture

Hi,

Please upgrade all GUP to 12.1 R2 and even check that gup's are getting telnet with SEPM and GUP's are online (connected with sepm) or showing off-line. If it is showing off-line then replace the sylink file for GUP server.. You can export sylink.xml from new SEPM.

 

Thank& Regards,

Ambesh

"Your satisfaction is very important to us. If you find above information helpful or it has resolved your issue. Please don't forget to mark the thread as solved."

Ashish-Sharma's picture

 

HI,

 

There is not much of a Difference between Group Update Provider in SEP 11 and SEP 12.1.

Group update providers (GUPs) are fully backwards compatible. A 12.1 Manager can manage 11.0 GUPs and 12.1 GUPs can update 11.0 clients.

 

Check this thread and mithun comments

https://www-secure.symantec.com/connect/forums/sep...

Thanks In Advance

Ashish Sharma

 

 

SebastianZ's picture

SEP 12.1 RU2 includes a new feature for GUPs functionality:

https://www-secure.symantec.com/connect/articles/sep-121-ru2-and-explicit-group-update-providers

http://www.symantec.com/business/support/index?page=content&id=TECH198640

 

...according to the documentation after SEPM Upgrade to 12.1 RU2 - GUPs does not need to be 12.1 RU2 in order to work properly - although the differences between 11 and 12.1 are quite steep and an upgrade would be highly recommended.

 

One other thing you can try is to delete the old Liveupdate Policy assigned to clients and gups and create a new one - offen happens that the policy gets corrupted during the SEPM upgrade and then cannot be properly read by clients.

.Brian's picture

It's not a requirement for them to be on the same version but it is recommended. Let us know how the upgrade goes and if it fixes your issue.

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.

pete_4u2002's picture

check if the globallist.xml has the GUP ip list. if yes, then you may need to troubleshoot. If you are willing to upgrade , it is the best way moving forward.

SameerU's picture

Hi

Please ugrade the GUP clients to latest version

Regards

 

Sumit G's picture

Have you upgrade the GUP client? Your issue fixed or still pending?

Regards

Sumit G.

TPanalyst's picture

Yes, I did upgrade a few agent, but stillnot working as GUP. Do I need to disable the GUP and enable back ?
If yes, How do I do disable the GUP ?

SMLatCST's picture

Can you check the reg keys identified in the below aricle please?

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

If these do not show that the client believes itself to be a GUP, then can you post us a copy of your LU Policy, and confirm its assignment to the group containing your GUP client.

I don't suppose you've been experimenting with explicit GUPs have you?  As the Explicit GUP option alone is not enough to enable a client as a GUP (a client must be identified as either a Single/Multi GUP in order to activate the GUP function).

TPanalyst's picture

Ok, I finally figured out the problem without upgrade my GUPs agent.
Before the upgrades to SEP12RU2 manager , My GUPs are placed in a separate group from the rest of the clients due to exception rules different. All was working well then.
After the upgrades, all GUPs stopped functioning.
To resolve the problem, I moved all GUPs back to the client group and it start functioning again.
According to the GUP whitepaper, a GUP can be in any group regardless of the Clients.
However, it seems like this is not allowed in SEP12RU2.

Any comments from Symantec ?

SOLUTION
SebastianZ's picture

It should not have changed in 12.1 RU2 - GUP still can be in any group regardless of clients - the only thing to consider is that the GUP should have the same Liveupdate policy assigned as the clients that will take updates from it.

Were these two groups you mentioned with different liveupdate policies?

 

SameerU's picture

Hi

Yes the SEPM and GUP should be on same version

Regards

 

SMLatCST's picture

I'd recommend reviewing the LU Polcies assigned to these different groups.  It sounds as if only one of them correctly defines the GUPs

Sumit G's picture

Gup is working but LU policy of both Group is required same.

However if you required to check the GUP status then use it
https://www-secure.symantec.com/connect/downloads/...

Regards

Sumit G.

Sumit G's picture

kindly update your thread and if issue is close then mark as a solution which help you.

Regards

Sumit G.

TPanalyst's picture

Remove all GUPs from the custom Group. Restart SMC service and all GUPs back online.
Then move the GUPs back to the custom group.

All GUPs back online.

Anyway, I had upgraded all my GUPs to SEP12.1.

 

Thanks everyone