is the policy number after change of LU policy same on SEPM and SEP client?

can you create a test group and assign same LU policy and move the server and check if it becomes GUP?

1. The client acting as Gup and Sepm should be on same version - YES
2. GUP policy should be configured correctly - YES
3. Once the Gup is created ,reboot the Gup machine once - YES
4. In Sep manager Go to client tab and gup client >right click and check if it configure as gup ,If it is the message displayed will be True . - Shows :False
5. make sure the communication is ok between Sep manager and Gup - YES
6. If recent firewall or some changes were made to network might be affecting for the Gup which are configured - DISABLED FIREWALL
7. Monitor Shared updates folder - No folder appears
8. Try creating a test gup - Will test
9. Check Space on Gup machine - More than enough space

Hi,

Could you please check the following article.

Test SEP to GUP and GUP to SEPM communication

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

Hello,

Troubleshooting the Group Update Provider (GUP) in Symantec Endpoint Protection (SEP)

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

Configuring the Group Update Provider (GUP) in Symantec Endpoint Protection 11.0 RU5 and later

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

When a client becomes the GUP

• The mini HTTP server code will be a DLL extension to the SMC Agent. The design has the GUP running independently of the internal content handling. GUP is loaded by the SMC Agent when configured. When it starts up, it begins to listen on the configured port. It continues to listen until it is shut down.
• All of the clients in the group receive the same proxy policy configuration. The one that matches the proxy address or hostname is the proxy and will load the micro web server.
• The computer that is designated as the GUP will create a directory if it does not already exist at the following location: C:\Program Files\Symantec\Symantec Endpoint Protection\SharedUpdates The "SharedUpdates" folder will cache all proxied files. For the first round of implementation this will only be managed LU content. No other communication or content will be proxied. Getting index files and profiles, posting state and logs, etc. will be done directly with server.

• The "SharedUpdates" directory will be populated when the GUP receives a request to see if the requested files are present in the local cache. If the file is present, it responds to the request with the file. If it is not present then the GUP holds the pending request, and re-issues the same "GetLUFile SyLink" request to the server. When that file arrives, it is added to the GUP cache.
• The GUP code can only get content updates from Symantec Endpoint Protection Manager. As far as the GUP is concerned, it does not know about the client it resides on. Even if the client were to be updated through alternative means such as: Intelligent Updater or Symantec Internal Liveupdate, the GUP would not be able to use those updates to proxy for other clients. The release build will show the following warning:

You can check if the SEP client on your server is a GUP both from the client and the SEPM.

1. Client:

Run netstat -an in the command prompt. If the SEP client is listening on port 2967, it's a GUP (or at least with a very high probability).

2. Client:

Check if the SharedUpdates folder exists (specialty of GUPs), e.g.

<SEP installation folder>\12.1.1101.xxx\Bin\SharedUpdates

3. SEPM

Clients > Group > Clients tab > right-click on GUP > Edit Properties > "Group Update Provider False/True"

4. SEPM

Clients > Group  > Clients tab > Tasks > Search Clients. Search for "Group Update Provider = True"

sepm and gup should be of same version.

Have you assigned that GUP policy into that group where GUP is placed?

If not then assign the same and check, hope it will be a solution for you.