One of the things that are regularly forgotten is to set certain antivirus scanner exclusions for SCOM (and other applications as well to be honest). All of the virus scanners can be set to exclude certain paths or processes or file extensions. Some of the scanners have some kind of script scan protection. In almost all cases it is best to set the correct exclusions as not doing so might give strange errors. These are mostly related to scripts not running or giving errors. And as you know a lot of SCOM is also script based.
These links will provide the right advice for setting your exclusions the right way:
Antivirus Exclusions for MOM and OpsMgr
http://blogs.technet.com/b/kevinholman/archive/2007/12/12/antivirus-exclusions-for-mom-and-opsmgr.aspx
Kevin’s pages are always the ultimate resource 💡
Antivirus exclusions for Operations Manager 2007
http://blogs.msdn.com/b/nickmac/archive/2008/07/18/antivirus-exclusions-for-operations-manager-2007.aspx
http://social.technet.microsoft.com/wiki/contents/articles/recommendations-for-antivirus-exclusions-in-mom-2005-and-operations-manager-2007.aspx
One more important thing when you are running McAfee is stopping the ScriptScan module on servers. Check out this post and links from it to the McAfee pages:
http://ianblythmanagement.wordpress.com/2007/08/13/mcafee-again/
If other antivirus programs also implement something like ScriptScan than you know what to do to avoid strange errors.
