Symantec says it supports 64-bit but after installing ityesterday on our MOSS farm (which did not go well), a new data sheet sent to us by Symantec says it's not compatible with64bit (win 2003).Anyone been able to get it to work? Opening Central Admin gives me a "service unavailable" message. Haven't poked around much (yet) other than checking that none of the service accounts are locked. I don't want to have to rebuild in 32bit to get the AV to work. Nor do we have the extra money in our budget for Forefront.Gah!ETA -- I know I can have a mixed platform environment, so I'd like to leave my sql box alone (64bit). BUT, can I attach those existing databases to the rebuilt 32-bit sharepoint farm?

aspnet_ regiis to the rescue. Symantec installed 32bit versions of .NET 1.0 and 1.1 and must have registered 1.1. I put it back to the 64 bit version of 2.0 and central admin and our sites (down too) came back up.Now to find a decent 64-bit AV product...

Hi Pierce, Check with the settings of the Antivirus whether it blocks anythink from or to te Temp files i had an issue similar to that , it was solved once i changed the settings of the Antivirus system installed. i thinks your is also the same problem.Hopes this may help youRegards,Ajith George

Moving to General. Admin is more for MOSS's own functions than general questions about third-party products and MOSS.------------------------Comment on the previous post:Ajith George: please do not propose YOUR OWN posts as answers. It is not helpful. Please propose quality posts from others. That IS helpful to the Moderators.

I have been down this road with Symantec. In my case we are using Windows Server 2008 x64.Symantec has an odd support model for Symantec Protection for SharePoint 5.1. Essentially it boils down to this, the scan engine itself is only supported on Windows Server 2003 and the installer on works for Windows Server 2003x86. It seems the reason for this is because it is a 32-bit Java run-time. However a recent article I saw on Symantec shows a manual method to install the scan engine on Windows Server 2003 x64 (http://service1.symantec.com/support/ent-gate.nsf/docid/2008060912551854). Note though the scan engine cannot run on Windows Server 2008 x86 at this point. Now they state they support Windows Server 2003 and 2008 and this is for the SharePoint connector. This connector allows SharePoint to send files for scanning to the scan engine. Now this connector can be installed on Windows Server 2003 x86, Windows Server 2003 x64, and Windows Server 2008 x86. That's right, not Windows Server 2008 x64 -- but I have heard they will be supporting this soon. So what this connector requires you to do if your SharePoint server is not Windows Server 2003 is to have another server on your network running Windows Server 2003 with the scan engine installed on it. Then your SharePoint servers will offload the scanning to this server (because that is where the scan engine is). Obviously this increases your network load and introduces another dependency on your SharePoint environment, but at least you get virus scanning.I hope this clears things up for others as this really bit me.

Symantec protection for Sharepoint 5.1.7 supports all platforms. Windows 2008, Sharepoint 2010. So shouldn't be a problem now