Which operating systems are supported? For minor updates to Mac OS X, such as Otherwise, uninstall the Symantec Endpoint Protection client and cleanly reinstall the compatible version after upgrade to avoid possible corruption to logs and other Symantec Endpoint Protection components. Installing the Symantec Endpoint Protection client for Mac covers both managed and unmanaged installations. Endpoint Protection client for Mac versions earlier than You do not need to uninstall later versions first.
If you upgrade to a version of What about upgrading Symantec Endpoint Protection for Mac to a newer version? Can I use Upgrade Groups with Package auto-upgrade? Auto-Upgrade is supported as of 14, but cannot be used to upgrade from You must export a client package for the new version then install or deploy as you would a new installation; it is not possible to use the Upgrade Groups with Package wizard auto-upgrade to migrate Macintosh clients up to a later client version.
However, you can usually install the new version directly over the old without uninstalling first; see the previous question. There's no Add or Remove programs for Mac. How do I uninstall? As of version 14, you can uninstall through the menu.
Click on the shield icon, and then click Uninstall. Enter an administrative password when prompted. Since a restart is required to complete uninstallation, you should save all open work before you begin. Otherwise, for version The uninstaller also works with version As of Symantec Endpoint Protection version Please see Using the LiveUpdate Administrator 2. No, for the same reasons outlined above. Rapid Release definitions are not available for Mac security products. How often are updates for Symantec Endpoint Protection for Mac released?
Daily, usually in the morning Pacific time west coast, USA. Connected appears under Management on the Symantec QuickMenu. For Symantec Endpoint Protection For earlier builds, the green dot next to Symantec Endpoint Protection indicates Auto-Protect is Enabled, not that communication is established: Is it possible to convert an unmanaged Symantec Endpoint Protection for Mac client to a managed client? How do I prevent Windows policies from applying to Macs?
Windows-specific policies will not apply to Macs; only the LiveUpdate policy and the Mac Settings in the Virus and Spyware Protection and the Exceptions policy if configured for a security risk exception for a file or folder will apply.
The Firewall policy will not apply because this component does not exist on the Symantec Endpoint Protection for Mac client. What about Device Control? Version 14 introduces Device Control for the Mac client. You can enable Device Control on managed clients only. Is Active Directory integration supported for Mac clients? It is not tested or supported. I can send Mac clients a command to become an Unmanaged Detector or to enable or disable Network Threat Protection, but nothing happens.
Even though the command can be sent, these features are not supported for Symantec Endpoint Protection for Mac clients. Symantec Endpoint Protection for Mac clients: User Mode or Computer Mode? There are not many changes that the end user can make, but if you want to prevent them from disabling Auto-Protect or Network Threat Protection intrusion prevention , make sure their group is set to Server Control: In the Intrusion Prevention policy, click Intrusion Prevention, and then click the padlock to lock the settings.
Note that this affects all clients using this policy, not just Macs: With these selections made, even if a user has administrative rights on their Mac, they will be unable to adjust these settings via the Symantec Endpoint Protection client interface: Without the padlock clicked and locked in policy, an administrator-level account would be able to make changes to settings: How can I verify the schedule given through the Symantec Endpoint Protection Manager is really there?
As of Symantec Endpoint Protection Scan schedules can be verified through the client GUI but the LiveUpdate schedule is visible in the newer client only when it is unmanaged. LiveUpdate or scan schedules that are configured through Symantec Endpoint Protection Manager policy are entered into the OS X crontab for the root user so that the scheduled event will launch regardless of which user is logged in and the root user account does not need to be enabled for the schedule to apply.
These events will therefore not appear in the symsched or Symantec Scheduler user interface unless those are run with root credentials.
To verify scheduled events, open the Terminal application on the client computer and type in the following: Enter your administrator password when prompted it will not echo in the window. If you have unmanaged clients, a default schedule will be set for all users on the machine i. This schedule is set to show progress i. Users can set their own schedules via the Symantec Scheduler; sudo symsched in the Terminal application can be used to set a schedule for all users on an individual machine, or use Apple Remote Desktop to send out a LiveUpdate schedule.
The Mac OS X Parental Controls feature, used to manage users in order to restrict applications that are launched on the system, could be used to restrict the manual launch of LiveUpdate. However, under normal circumstances, Administrator and Standard users alike should be able to launch LiveUpdate manually, whether the LiveUpdate policy is checked allowing clients to manually launch LiveUpdate or not. Does Symantec Endpoint Protection for Mac do email scanning?
There is no proxying of incoming or outgoing messages for email clients like Mail or Entourage, as there is in the optional email component of Symantec Endpoint Protection for Windows. Symantec Endpoint Protection for Mac AutoProtect does monitor and scan everything that is being written to the hard drive, including attachments that a user may attempt to save from an email message. However, email client inboxes and other email archives may become corrupt if Symantec Endpoint Protection scans mail folders under the user profile directories.
As a best practice, those directories should be excluded from Symantec Endpoint Protection scans. See How to create a Security Risk Exception for a Mac client and check the documentation for your email client.
An exported System Profiler report will often also provide a lot of information about the system in question. Do not edit this file. For the installation, no separate log is written. Instead it is written to the system's installation log, which is most easily viewable via the Console application. With Console open, show the log list if it is not already showing. After listing some environmental variables, the phrase "Symantec Endpoint Protection Installation Log" appears at the beginning of the installation cycle.
What about Sylink debugging? This document can be used to enable Sylink debugging for client communication problems with the Symantec Endpoint Protection Manager. Before saving, under View, ensure "Full Profile" is selected.