12.0
Table Of Contents
- Implementation Guide for Symantec™ Endpoint Protection Small Business Edition
- Technical Support
- Contents
- 1. Introducing Symantec Endpoint Protection Small Business Edition
- About Symantec Endpoint Protection Small Business Edition
- About the types of protection
- Single console management
- How you are protected out-of-the-box
- Key features of Symantec Endpoint Protection Small Business Edition
- Components of Symantec Endpoint Protection Small Business Edition
- Where to get more information about Symantec Endpoint Protection Small Business Edition
- 2. Planning the installation
- 3. Installing Symantec Protection Center
- 4. Preparing for client installation
- 5. Installing the Symantec Endpoint Protection Small Business Edition client
- 6. Migrating to Symantec Endpoint Protection Small Business Edition
- 7. Starting the Symantec Protection Center console
- 8. Monitoring endpoint protection
- About monitoring endpoint protection
- Viewing the Daily Status Report
- Viewing the Weekly Status Report
- Viewing system protection
- Viewing virus and risk activity
- Viewing client inventory
- Finding unscanned computers
- Finding offline computers
- Viewing risks
- Viewing attack targets and sources
- About events and event logs
- 9. Managing security policies and computer groups
- 10. Managing content updates from LiveUpdate
- 11. Managing notifications
- 12. Managing product licenses
- 13. Managing protection scans
- About managing protection scans
- How protection scans work
- About the default protection scan settings
- Enabling File System Auto-Protect
- Scheduling an administrator-defined scan
- Scanning computers
- Updating virus definitions on computers
- About managing quarantined files
- Enabling or disabling TruScan proactive threat scans
- About adjusting the protection scans
- About exceptions
- 14. Managing firewall protection
- 15. Managing intrusion prevention protection
- 16. Managing administrator accounts
- 17. Managing disaster recovery
- A. Maintaining and troubleshooting Symantec Endpoint Protection Small Business Edition
- Restarting client computers
- Finding managed computers
- Converting an unmanaged computer
- Finding the server host name and IP address
- Modifying email server settings
- Modifying the server installation settings
- Investigating client problems
- Troubleshooting Symantec Protection Center communication problems
- Troubleshooting content update problems
- Providing information for Symantec Support
- B. Managing mobile clients and remote clients
- Index
â– Leave as-is the rule that blocks all other traffic.
As a best practice for the Firewall policies for the groups where users log on
through Ethernet or wireless connections, use your default Firewall Policy. For
the wireless connection, ensure that the rule to allow wireless EAPOL is enabled.
802.1x uses the Extensible Authentication Protocol over LAN (EAPOL) for
connection authentication.
About best practices for Virus and Spyware Policy settings
As a best practice for the Virus and Spyware policies for remote clients, use your
default Virus and Spyware Policy. The default policy suspends scans when the
remote client operates from batteries to extend battery life.
About best practices for LiveUpdate Policy settings
If you maintain strict control over Symantec content and product updates for
your clients, you should consider changing your LiveUpdate Policy for your remote
clients.
For the group of remote users who log on without a VPN, we suggest you change
the LiveUpdate Scheduling frequency to one hour. This setting makes it more
likely that clients update their protection when they connect to the Internet.
For all other groups, it is a best practice to use the Symantec Protection Center
to distribute product software and content updates. An update package that is
distributed through the management console is incremental rather than a complete
package. The update packages are smaller than the packages that are downloaded
directly from the Symantec LiveUpdate server.
About client notifications
For your remote clients that are not logged on over VPN, it is a best practice to
turn on notifications for virus and security risks. You can turn on these
notifications in the Virus and Spyware policy.
Turning on notifications helps to ensure that remote users are aware when a
security problem occurs.
About monitoring remote clients
Notifications and logs are essential to maintain a secure environment. In general,
you should monitor your remote clients in the same way that you monitor your
other clients. You should always check to see that your protections are up to date
Managing mobile clients and remote clients
About client notifications
162