Ouch..... That is a lot of machines to enter permissions for (100+ servers ). Ill give that a shot.
Main Topics
Browse All TopicsHey all,
I have a large number of windows 2003 servers running VSE 8.5i and the majority of them are unable to update their virus definitions with auto update. Currently I have all servers pointing to a central repository (non- ePO, just a share on another server). All servers are configured with the exact same settings but only a handful will update nightly.
I have tested to make sure the share is accessible from each server and I can also run a manual update against the repository without issues from every server.
These servers are not in a domain. Security and Sharing of the repository is setup for "everyone" with read, write and execute permissions.
here are the error logs from autoupdate:
8/2/2009 3:58:16 PM NT AUTHORITY\SYSTEM Starting task: AutoUpdate
8/2/2009 3:58:19 PM NT AUTHORITY\SYSTEM Checking update packages from repository local.
8/2/2009 3:58:20 PM NT AUTHORITY\SYSTEM Failed to connect to server <servername>. Check the agent log for more details.
8/2/2009 3:58:20 PM NT AUTHORITY\SYSTEM Error occurred while downloading file SiteStat.xml.
8/2/2009 3:58:20 PM NT AUTHORITY\SYSTEM Unable to find a valid repository.
8/2/2009 3:58:20 PM NT AUTHORITY\SYSTEM Closing the update session.
Any help would be appreciated.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
The server is not accepting the remote server when i try and add permissions (either share or NTFS permissions). When entering either <comuptername> or user@<computername> in the "Select user or group" box. I also am unable to choose anything but the local server in the locations section. My Network Places shows all servers though.
"When you say you are pointing to a central repository" Is this
WSUS? If not maybe this is the way to go. If so you might find setting up a scheduled task on each server to update a work around"
No, McAfee has a built in auto-updater you can configure to point to a share on another server. This is how I am setup. Basically the central repository is just a folder on one of the servers that I have share permissions on for everyone.
So to quote myself from my original post:
"I have tested to make sure the share is accessible from each server and I can also run a manual update against the repository without issues from every server.
These servers are not in a domain. Security and Sharing of the repository is setup for "everyone" with read, write and execute permissions."
Let's go back to the OSI layers and step thru the connectivity path.
Double checking: Primarily Layers 1 - 4 . . .
Layer 1: Physical Layer
Layer 2: Data Link Layer 3.6.1 WAN Protocol architecture
IEEE 802 LAN architecture
Layer 3: Network Layer
Layer 4: Transport Layer
Layer 5: Session Layer
Layer 6: Presentation Layer
Layer 7: Application Layer
Also double check: "8/2/2009 3:58:20 PM NT AUTHORITY\SYSTEM Failed to connect to server <servername>. Check the agent log for more details.
8/2/2009 3:58:20 PM NT AUTHORITY\SYSTEM Error occurred while downloading file SiteStat.xml.
8/2/2009 3:58:20 PM NT AUTHORITY\SYSTEM Unable to find a valid repository.
Are there possible typos in the server name / path...
Communication from all servers back to the repo server is solid. As I said before I can browse the server (\\servername\sharename) and move files back and forth just fine from any of the boxes.
"Are there possible typos in the server name / path"
Good question, This is one of the first things I tried but it all is good. I actually copied the path from the config box and pasted it into Run and the repo's share pulled right up.
So the thing that gets me, is I can run the update manually aginst the repo with no problems, but I am logged in when this is going on. The auto update runs when no one is logged in. Im wondering if there is a authentication issue between the two servers. Since this is not a domain im wondering if the server is trying to use local login cradentals (server1\administrator) instead of the repos required cradentals (repo1\administrator). Since repo is not part of a domain it will not let me add security or share permissions for other computers just the local one.
What are your thoughts on this.
Here is a screen shot of each of the locations within McAfee were i can set login info for auto update and the repository that server uses.
The Schedule settings screen if for auto update in general. Filling in the username (administrator) and a password does not resolve the issue. Im not sure how I would put a workgroup in this screen along with user/pw.
The repository settings screen is for setting options for the repo that server looks to for updates. If "use logged-in account" is unchecked then a domain is required to be entered. I am also unsure of how to enter a workgroup in this screen as well.
This is were my Windows experiance has gotten weak. How would I specify a workgroup in these fields.
Thanks
Workgroup vs Domain . . . here is were I must get off the train.
I have not set up Workgroups for business production environments which may be the source of your issue. Workgroups may not be the best strategy for you. Two options come to light. 1. Set up a Domain. 2. Post this question in other areas of EE with a reference to the narrative we have had.
yeah a domain is hopefully a long term solution but it is going to take a while. I was hoping for something I could implement for the time being.
Longer picture is a domain with McAfee ePO to centrally manage AV.
Any suggestions on zones that would be better. I thought i picked the best for this question.
I had a similar problem with McAfee 4.x many many moons ago. The solution back then was to make the shares where the clients pick up their dats from 'null session'. After doing this the clients would update correctly.
Some info for doing this in Win2k can be found here: http://support.microsoft.c
I'm not sure if this stuff is still relevant in 2k3 or 2k8 or the security implications of doing this in the newer OS's but I'm sure there will be some arcticles kicking about somewhere.
RE "Here is a screen shot of each of the locations within McAfee were i can set login info for auto update and the repository that server uses.
The Schedule settings screen if for auto update in general. Filling in the username (administrator) and a password does not resolve the issue. Im not sure how I would put a workgroup in this screen along with user/pw.
The repository settings screen is for setting options for the repo that server looks to for updates. If "use logged-in account" is unchecked then a domain is required to be entered. I am also unsure of how to enter a workgroup in this screen as well.
This is were my Windows experiance has gotten weak. How would I specify a workgroup in these fields. "
The domain name in this case is the netbios computer name of the server that is serving the shares. You could try putting that in the User account settings:
User: administrator
Domain: server computername
Pass: password
having read through the post, it is really clear that you need to setup and manage a domain, and nominate one server as the domain controller.
however, given the task in hand, i do not believe it is a permissions issue with the folder (having the Everyone group set right helps), as you say you can manually run the update. have you checked the SiteList.xml file, as this is where we list our master repository, and also the fall-back if the server is off-line, or if user is off-site (defaults to McAfee's own update website). So if your update fails, they can connect to the McAfee site to get the update.
you might also want to check the McAfee Framework Service and Task Manager services and their service account permissions, as i'm certain these services control the scheduler and update routines. you normally run 3 services on each box, Framework, McShield and Task Manager.
normally your servers would be logged in using a domain admin account, in this case you could try having the local admin account set with the same pwd, and make sure on the schedule config page from your screenshot, you put in the username line -- WORKGROUPname\Username, leave domain line blank and then add your pwd. It might work, and then again it might not, as the software is not really designed for workgroups, but worth a try.
"So if your update fails, they can connect to the McAfee site to get the update."
this is not an option (i wish it was) due to these servers being isolated from the internet.
Looking at the services you mentioned they all use the local system account for the service. I tried changing the login account to the admin account that all servers share but the service will not let me change it. I am also unable to stop the service to edit it. Do you know how I can do this?
Thanks
Business Accounts
Answer for Membership
by: b_haynesPosted on 2009-08-07 at 10:28:30ID: 25045073
Check the permissions. It would appear that the share needs to have explicit permissions set for each box that connects with it.