Once this rule has been added to your firewall you can go back to step 2 above, click on ‘Update’ under ‘Policy profile’ and you will see that ‘Server :’ will now have a machine name or IP address next to it.Īfter 5-10 mins your client software will be updated. Symantec uses ‘TCP 8014’ for this communication and this will need to be opened on your firewall between your Public DMZ and your internal LAN. So from this we can see that the client software cannot communicate with the management software. Remove client packages assigned to the client groups. Disable the Protect client files and registry keys Application Control Policy. Under general information you will see ‘Server : Offline’ instead of a valid machine name or IP address. Step 2: Back up and prepare for disaster recovery (critical) Step 3: Prepare Symantec Endpoint Protection 11.x managers. Help and Support>Troubleshooting>Management Tab This was verified by going to :ġ.Symantec Icon in the system tray>Right click>Open Symantec Endpoint ProtectionĢ. I was able to deploy the client software to the web server but it was then unable to contact the management server for policy updates. In the LiveUpdate policy, choose Server Settings in the left pane. Select the group in which the client or clients can be found that need to be updated manually. However, you can use LiveUpdate to force the workstations to update using the. I recently had a situation in my network where I wanted to protect a new server with Symantec Endpoint Protection but the client machine was in a different DMZ (Demilitarized zone).įor example, the Symantec Endpoint Protection Manager is on my internal LAN and the web server I wanted to protect is in my public DMZ. jdb file: In the Symantec Endpoint Protection Manager (SEPM), go to Clients. Workstations get the latest antivirus, policy, and agent upgrades automatically.
0 Comments
Leave a Reply. |