I'm not very familiar with this area of product functionality (mirroring is actually taken care of by the McAfee Agent), but, your posting implies the mirror will work if your source UNC repository looks more like \\server\share\path instead of \\server\share. Is that something you confirmed/tested already?
I would agree with you though, that \\server\share ought to work. But if \\server\share\path works then at least we can document a solution in the KB.
In checking the KB, I do see a few articles that might be worth your time reviewing -
- KB53067 (looks like an old article; probably not applicable)
- KB53033 (looks like an older article too)
Thanks for your response. I did implement the workaround in the client's Edit AutoUpdate Repository by using \\servername\sharename\path last week and it worked. For the path I used 0 and moved all the files into that and adjusted the mirror task on the server that I use to store the mirrored repository. I just needed a single character to fake out the erroneous field validation.
If this is not going to be corrected, then this requirement needs to be spelled out not only in the KB but also in the Users/Product Guide - for those of us who do RTFM. Any such requirement must be documented and not assumed to be known by anyone other than the person who wrote that piece of code. It's a pet peeve of mine: I am not a mind reader.
As for the KBs.
KB53067 - doesn't apply since the validation occurs on a mix of machines - either using Logged on User or a copy and paste for the account to use for this process.
KB53033 - doesn't apply since the server that is hosting the repo was also the one on which the mirror task runs, and it works.
KB53640 - doesn't apply, the error occurs on both 32-bit and 64-bit clients. Additionally, I went ahead and defined credentials to use for all the clients - including going back to those where I had not defined them for testing purposes. Finally we are running agent 18.104.22.1680.
KB65594 - doesn't apply. I am not getting the errors listed. Same as above, agent is 22.214.171.1240.
KB60714 - doesn't apply. Not using EPO. Also agent is 126.96.36.1990.
I have avoided deploying EPO given the problems I have discovered in these forums when changes are made and issues to sitelist.xml files. I need something I don't have to babysit.
What you are attempting to do can be solved so much easier by using a distributed repository.
I have a UNC distributed repo called simply \\servername\epo
Because it's a distributed repositry i don't have to worry about manually editting the clients 'AutoUpdate Repository list' because ePO does all that for me with the agent policies.
Really the question is what special network/system configuration do you have that requires you to do it the way you are attempting to do?
In the paths you specify in your post I see you are not ending the UNC path with a \ after the sharename:
\\servername\DAT try using \\servername\DAT\
If you provide the path with the \ it will read the back slash as the root path of the share directory.
I've verified this in VSE 8.8
1. I have setup a mirror task on my server to mirror the NAI repo. It ran fine.
I setup the mirror to point to the root of the dedicated share I created for it:
The mirrored repo is shared as \\servername\DAT
2. I then go to a client and attempt to add the UNC repo using the VirusScan Console, Tools\Edit AutoUpdate Repository list.
3. When I attempt to add the UNC repo with \\servername\DAT I receive this error.
"Please enter the path to the directory where the updates can be found. A UNC path has the format: \\server\share\path."
I checked the Product Guide for McAfee VirusScan Enterprise 8.8, topic "Adding and editing repositories", page 151. It states this is the proper format for a UNC:
"Available only if you selected UNC path or Local path.
• UNC path — Using UNC notation (\\servername\path\), type the path of the repository where the update files are located."
If a subdirectory is required under the sharename then that should be explicitly stated in the online help AND in the product guide.
I did RTFM before I created the mirror task. Nowhere is the extraneous subdirectory requirement listed with respect to a UNC for purposes of mirroring the NAI repository nor in Adding it to the local client's AutoUpdate Repository list. A proper UNC does not require a path, just the servername and share.
To workaround this is did try to add /Current so the path was like this in the client: \\servername\DAT\current, naturally of course that failed as well, because the DAT file that is required for the client update is in \\servername\DAT.
Is there a patch or hotfix available to fix the client when adding/editing the AutoUpdate Repository list if the type of repository is a UNC so that it accepts \\servername\share?
Message was edited by: lruiz.helm on 8/8/12 1:34:16 PM CDT
I recall trying to use "\" at the end before McAfee issued the patch for the bad signature update a couple of week ago. Prior to that patch, ending the share with "\" did not work.