Video Screencast Help
New Company Name and Logo Announced. Learn More.

Frustrated with configuring Explicit GUPs for Roaming Clients

Created: 04 Feb 2013 • Updated: 04 Feb 2013 | 4 comments
This issue has been solved. See solution.

Happy Monday all angry

For more than two weeks I have been trying to configure explicit GUPs for Roaming Clients. Our SEPM version is version 12 RU2. Our GUPs are SEP 11 RU7 MP1. And our clients are RU7 MP1 and below.

I recently opened a case with Symantec, and now the tech is saying that ALL SEPMs, GUPs, and CLIENTs must be SEP 12 RU2.

I do not believe this at all!!!!!!!!

I have seen documentation where it is ok if SEPM is version 12 RU2 but the GUPs and clients can be any version and this will work.

Please guys, can you point me to documentation. And if possible, if I can PM the Case number to have this resolved I will be most grateful yes

Discussion Filed Under:

Comments 4 CommentsJump to latest comment

Brɨan's picture

Not true.

It is not a requirement to be on the same version but it is recommended especially when issues arise and troubleshooting needs to be done. Plus, there may have been a bug  in a previous release.

Now in your case, this is a new feature in 12.1.2 so it may make sense that is has to be on 12.1.2. Assuming this is the new feature you are using...

What's new in Symantec Endpoint Protection 12.1.2

Article:HOWTO81091  |  Created: 2012-10-24  |  Updated: 2013-01-30  |  Article URL

Understanding "Explicit Group Update Providers (GUPs) for Roaming Clients" in Symantec Endpoint Protection (SEP) 12.1.2

Article:TECH198640  |  Created: 2012-10-19  |  Updated: 2012-11-15  |  Article URL

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

Just to confirm, the SEPM and the end client must be on SEP12.1RU2, but the GUP itself does not:

As it goes, have you reviewed the below articles on Explicit GUP Behaviour?

SMLatCST's picture

To help walk this through:

The SEPM must be on v12.1RU2 in order to tell a client (via the policy) to use an Explicit GUP.

The end client must be on v12.1RU2 in order to understand the new field in the policy and try to use an Explicit GUP.

The GUP doesn't care who is using it, all it knows is to enable itself as a GUP (v11RU5+)

Don't forget that the Explicit GUP function alone will not enable the GUP functionality in your intended GUP.  A GUP will only become a GUP if it is told via the Single GUP or Mulitple GUP part of the LU Settings policy, so you've got to enable that bit too.