Is this FTP repository in the SitesList managed by ePO?
If so you can run a Daily Server Task to Replicate Distributed Repositories which will push out the content out from ePO Master a Repository after you have pulled the DAT down from McAfee.
McAfee Volunteer Moderator
Certified McAfee Product Specialist - ePO
Thanks for your reply... Here's the deal: There is NO ePO deployment on any of the networks. They just set up an FTP site using Microsoft IIS, created a commonupdater site and upzipped a SuperDat into the folder. Then they set each client up to use ftp:\\site.site/commonupdater as the palce to go for DAT updates.
So, I come onboard and notice that the DAT's haven't been updated in months. I have a lot of expereince with ePO and plan on setting one up once approved, but in the meantime, I want to get the current FTP site updated. Everything I've tried always results in errors in downloading the DAT after updating.
I've never managed a purely FTP-only site and don't know what I'm doing wrong... So, I wanted to know what was availabel out there that will show me how it's done from scratch to get things rolling until I get ePO going.
Distribute a new C:\ProgramData\McAfee\Common Framework\SiteList.xml to each of the computers. That will tell the clients to update from wherever you want it to.
What I do is install Virusscan on a file server, setup a mirror task, and point each client to the file server share (\\servername\mcafee\). This is a fast and easy way keep everyone updated. If you have to keep ftp, then install Virusscan on the IIS server, setup the mirror task and set the mirror location to the ftp root directory.
Thanks for the info... I'll give it a try on one of our smaller networks.