A Symantec Endpoint Protection (SEP) Group Update Provider (GUP) intermittently fails to start GUP role. Changes in GUP status attributed to SEP service restart or reboot. When the GUP role is not started a SEP service restart or reboot is required to start the GUP role.
Sylink Debugging sylink.log
Symantec Management Client (SMC) debug.log
For more information on sylink.log and debug.log refer to http://www.symantec.com/docs/TECH102412
The SEP Client will not initialize the GUP role if it is unable to query the network interface.
In SEP 12.1 Release Update 1 (RU1) and later the GUP role will remain disabled until SEP service restart or reboot if GUPCheckAlive is not configured or set to 0.
Configure GUPCheckAlive with a value greater than zero.
After making these changes, the client will attempt to restart the GUP functionality every 60 seconds based on the value of the GUPCheckAlive registry.