IainNIX:
If I understand you correctly, that is how my default policy is set already. My default policy's update repository lists are as follows:
1. site 01
2. site 02
...
...
10. site 10
11. McAfee Http
I'm certain the McAfee Http works because if I manually disable site 01-10 through the "edit repository list" option in the vse console, the update process works fine. (not something I can show the users how to do though ^_^)
My issue is I'm guessing that McAfee tries to connect to site 01 through site 10 first instead of realising that the PC is not connected to the network and hence will not be able to contact site 01 - site 10.
Regards,
WA
Main Topics
Browse All Topics
by: IainNIXPosted on 2009-07-30 at 05:37:18ID: 24979001
yes i have this set on my Pro Pilot setup (think older ePO), as the default task, if my users are off-site and cannot access the repository server via VPN, then the default task then uses the McAfee website as the second update option (providing they have Internet access).
on your update task you just add a second option/location, first points to your repositories, in my case i only have one, in yours, you will likely list all your network repositories and then at the end add the McAfee site. i have noted that sometimes, the McAfee update site does not always supply the daily incremental update files, and sometimes end up d/l the full DAT @ 100Mb.
if you need the sites details to add, let me know, they are normally included in the default tasks setup when the server is installed.