I will have the updated data at location one, and I have other data at location two.
Let's say I have two different locations. These distribution points in Symantec record the data needed to update all the other systems When I need to send a file to update all the other systems, I send it to these distribution points. The ATMs are always on the network because they're connected with other points at every branch and location. I set up distributional points on systems and ATMs. To centrally manage the antivirus, I have to set up distribution points because I have more than 14,000 endpoints altogether distributed across more than 250 branches in Nigeria. The activities on servers and ATMs are dynamic, so the antivirus must also be very light. It's a stripped-down version that removes some of the components and add-ons that are not part of the endpoint protection engines, so the agent is lighter and can be deployed faster. The agents for the ATMs and servers aren't as heavy as the ones for workstations. I have three different kinds of agents on the endpoint that I can use to control access. The management server will give me the current status. If I want to check the status of any asset, I need to get the details like the IP address and the hostname of the system. There's a central management server we use to manage all the endpoints, regardless of the categories, and we install an agent on all the endpoints that reports to the management server. So this article attempts to link the names to build numbers in an easy to read list.Symantec Endpoint Protection has an antivirus with anti-malware and application control capabilities that we use to protect assets like servers, workstations, and ATMs.
I come across this quite often – Symantec Endpoint Protection releases as a name (eg SEP 12.1.4 MP1), but then in other areas they are referred to by their build number (e.g.
0 kommentar(er)
