Symantec Antivirus for Macintosh 10.2, Symantec Scheduler events do not run as expected
|Article:TECH104487|||||Created: 2008-01-27|||||Updated: 2009-01-12|||||Article URL http://www.symantec.com/docs/TECH104487|
Scheduled events for Symantec AntiVirus for Macintosh that will trigger for any user that is logged in, or if no user is logged in due to the event being set for the root user, will not trigger after installing Symantec AntiVirus 10.2 for Macintosh. These events include Scheduled Scans and LiveUpdate.
Scheduled events which are missed when a user is not logged in are not executed when a user logs in.
- LiveUpdate events created by non-root users will launch but do not complete when launched while logged in as Admin or root.
1. Symantec Scheduler NortonMissedTasks functionality was looking for /var/cron/tabs for the crontabs. In OS X 10.5.x, the crontabs have been moved to /var/at/tabs.
2. Symantec Scheduler tasks scheduled by root user are run as the Admin or Guest user when executed within those users’ space.
Follow the instructions below to solve this issue:
These issues are addressed in version 4.0.3 of the Symantec Scheduler. This version is available via LiveUpdate, or can be downloaded from here for those who cannot use LiveUpdate to update their software. The disk image of SAV for Mac 10.2.1 also includes the newer Scheduler (this is the only difference between the 10.2 and 10.2.1 installer images; 10.2.1 is also referred to as 10.2e).
Download and unzip the attached .dmg disk image and run the installer to update to version 4.0.3 of the Symantec Scheduler. Scheduled events for all users should now behave as expected.
Clarification of new functionality in Scheduler 4.0.3
Scheduled Scans will always take place when they are scheduled. The results are not posted until the user who requested the scan logs in.
If no one logged on for a scheduled LiveUpdate, it will be postponed until someone logs on. This is a problem with LiveUpdate, not with the Symantec Scheduler.
Symantec is aware of this issue and is currently investigating it. This document will be updated when new information becomes available.
Article URL http://www.symantec.com/docs/TECH104487