This content has been marked as final. Show 12 replies
No there isn´t. All distributed repositorie available through ePO will only update from the Masterrepository.
You can add local repsoitories or McAfeeHTTP to the clients repository list for failover reasons.
How about if I assign a "mirror task" on repository server or client which is using "mirror location" as the same location of ePO repository folder.
Also on the autoupdate repository list I have placed http at the bottom.
Can I use this config? Both the client engine and epo use the same folder structure?
No you cannot as ePO saves a catalogue version when replicating and if you mess up with this data the repository will be unusable.
What you can do is configure a mirror task on a client with no epo repository and share this folder via HTTP/FTP/UNC. Then create a local repository in your epo agent policy and specify this new repository.
Whats happens if...
- The Primary is down or not fully functional and therefore not updating Superagent sites or other repositories with current DATs
- Clients are configured to hit one of any available Superagent site or repository for udpates
- Clients are configured to "failover" to the NAI site if no repository is available
- Do the clients blissfully carry on thinking there are no new DATs since they can contact a (out of date) Superagent site and therefore don't hit the failover NAI or Mirror FTP/UNC sites which would have current DATs?
If you masterreporitory fails and you have different distributed reps then the clients will still contact the distributed reps and think there are no new DATs. So in case of an emergency when your epo server fails and the clients have a repository list like this -> 1)ePO Server 2)DistrubRep1 3)DistribRep2 4) McAfeeHTTP you must disable the DistribReps so that the clients will goto McAfee to update their DAts.
Our main problem is that,
we're having websense license problem when all clients update their selves from mcafee.
It would be good to update superagents from mcafee when EPO server fails.
That works if you're notified/aware that your primary server is down, but our systems group doesn't monitor McAfee Processes (SQL and OS yes) and if the primary goes down it can't email me to tell me it's down like it does for SuperAgent replication issues. Typically I'm very aware of our primary status but not on holdiays, vacations, weekends etc.
Where can I read about how to disable the distribution repositories? We had an instance where our Master Server was down for 3 days. All client machines had a failover to McAfee HTTP but only about 30% of the machines actually updated while the Master server was down. sad
I assumed the intended method was McGyver style :-)
Log onto a SuperAgent site and disable the Framework Service, I believe that does the trick(?). Or otherwise affect the server to prevent remote connectivity
I certinaly have plenty of practice Enabling Framwework service on otherwise functional servers when SuperAgent site replication fails...