Moved to ePO for better handling.
What about if you try the mirror task to get the Package from FTP?
What about if you type in the machine which fails in the IE browser http://update.nai.com/products/commonupdater can you reach the Package? Do you have any kind of authentication? Do you have any error with Firewalls/proxy?
Thanks for your attention to my problem, sorry for my bad English though.
Unfortunately, our ePO server cannot go through FTP. It goes to the world via Cisco firewal, and only HTTP allowed.
On machine which fails, I can open the link in browser, and I can download files from there - I reach the Package.
No authentication needed, as far as I know - firewall just allows us to see Mcafee, Microsoft, and several other sites.
I tried this thing: via FTP client I downloaded the whole package on the "full Internet" machine. Copied the base to the "problem" computer. Made my files as a Local repository. Started update - done. Started mirror - error. Some more folders created in "current" folder, but I still have error.
I don't know how it's possible - "good" update but "bad" mirror from the same source.
No problema it is pleasure to help
No worries, my English could be horrible too
Well it could be possible if the VSE packages needed for the Update has been downloaded ...
Ok, so let's start with the troubleshouting
We need to enables McAfee agent debug loging:
Now, we need to reproduce the issue again.
Can you please collect the McAfee agent log to check if we can find some clear error which could give us some more info?
Please, upload the log when ready.
Why don't you use ePO to create a distributed repository and disable that repository in the McAfee agent\repository policy for the clients?
That way you can use ePO's infrastructure to place the files on machine. You can also select which packages you want to copy to it, so you can reduce the size of the file structure. We have a similar scenario and use this method.
Thanks for your opinions! Now week-end started, so I'll try to start logging in working days.
About distributed repository - yes, I thought about that, and maybe I'll try - but it will be completely another method. Now I want to solve, why my mirror task worked earlier - and now not working, or working partially (some files appear locally, but that's all finishes in error).
Now one more thing I done recently. I made a full local copy of ypdate package from McAfee FTP via FileZilla client. I did it at home, on my own PC - without any firewalls. Then I moved it to a machine with VSE 8.8.4 installed locally. This machine has never been under ePO, just local VSE. I pointed to my downloaded files as a update source. Started Update - Done. Started Mirror - Fail!! Why? No ePO, no McAfee Agent, just full set of files and local VSE. And mirror failed.
I'm beginning to think that something changed in update repositories, something that crashes mirroring. In my main problem, yes, there can be errors - Firewall, ePO, Agents - there is place for mistakes. But in my experiment... no place for errors. And mirroring still fails.
What do you think?
The debug login can give us more info I though.
Please, keep us posted.
I've made everything as in KB article about start logging - changed 3 keys in Windows registry. Then started mirror task again, it failed as usual, but no new files appeared in my "C:\Documents and Settings\<username>\Application Data\McAfee\Common Framework\DB\Support DLL\DebugTraceFiles\" folder - only some old txt logs from 2011 year. Maybe logs are stored in some other place? Or my server needs reboot to start logging? No help about it found in KB article.
Do you really need to use a mirror task? I gave up using them ages ago as i always had issues with them.
Setup a distributed repository and see how that goes. Plus you can just download what you need.