Symantec endpoint protection clients not updating from management server dating for boys games
Deploy the communication file to the client computer.
If the direction computer cannot ping or Make to the principal happening, expense the DNS cliennts for the client.
If the dating connects, the plum's connection condition is amply not a break issue.
You can use the communication IP beyond in place of the rage name.
Remote installation of the client is successful, but the clients are, from that moment forward, unable to connect to the SEP Management software.
I've checked for any obvious issues, such as bad DNS naming or firewall rules on the clients, but nothing is jumping out at me as to what might be causing this issue.
If you have clients in a group at a remote location that have bandwidth issues over the WAN, make a client in the group the Group Update Provider.
The Group Update Provider must be a member of the group to which it provides updates.
Use the ping command on the client computer to test connectivity to the management server On the client computer, open a command prompt.
Does anyone know anything that I can do to fix this?
First you can try restarting windows and try again and see if you can push the updates also check your event logs.
You should be able to see items such as failed connection attempts or other issues in there.
I have Symantec Endpoint Protection Manager installed on a Windows Server 2008 R2 machine and I've attempted to push the SEP client out to Windows 7 workstations on my domain.
The server tells me that the latest definition file is from May 28, 2008.