Endpoint Protection

Quick question regarding GUPs as I am having an issue since we moved over to a new SEPM 12.1 RU2 infrastructure whereby the server we have allocated as a GUP, is still showing false in it's clients properties, not contactable on port 2967 and does not contain any of the files I would expect.

The SEPM server in our DC is behind a firewall. Port 2967 is open from the SEPM to the GUP server as well as 8014. As a managed client the server is as expected, but I cannot make it a GUP.

Our previous SEP environment was 12.1 and the SEP client on the server was also a GUP within this infrastructure and functioned without issue. We are now going through the process of joining our global SEP environment and stood up a new SEPM server in one of our regional DCs. The plan is to decomission the old SEP environment once migration is completed but in order to complete the migration I need the GUP to work.

The server's SEP client is the correct version - 12.1.2015.2015

does not it has shared updates folder ?

is the client communicating to SEPM?

is the LU policy set have this client to become GUP? Is the client taking the same LU policy.

No the folder does not exist.

The client is communicating correctly with SEPM and it is utilising the same LU policy within which it is defined as a GUP. We are using explicit GUPs for roaming clients

Ah ha, I was wondering if you'd been testing out the Explicit GUP thing.

I'd recommend reading up on the help for the Explicit GUPs, as it does state that using the Explicit GUP option does not turn the the identified clients into GUPs.

You must have a separate policy assigned to the clients you want to be GUPs, and this policy must use the Single or Multi GUP options to enable the GUP function.

thumbs up to above advice.

You need to make GUP either in multiple GUP or single GUP for client to act as GUP.

check this explicit GUP info

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

read out note

configuring an "Explicit Group Update Provider list" does not turn clients into Group Update Providers. 

Ah I see

That has worked, I entered the server as a single GUP and it is now working. Thank you!

So if I get this correctly...

With my group structure as such that I have a Severs group and also a Workstations group for example, I could assign an LU policy to the servers group wth multiple GUPs spcified and then for the workstations group I could have an LU policy with explicit GUPs specified so workstations in each subnet went to the relevant GUP?

As an asid... how long should it take before the share updates folder is populated? It is now created but still empty.

as soon the client request the SEPM for content and the GUP is ths source, the SEPM will generate delta/full definition that will be published on shared updates folder.