Site Servers Problem
Updated: 08 Nov 2011 | 6 comments
This issue has been solved. See solution.
In my environment I have a console NS 30 site and servers.
My problem is that my site servers are not pointing to my console, they are pointing their agents to other site servers for the console and not as they should.
I've checked the settings and apparently is OK
Discussion Filed Under:
Comments
For what?
When you say they point to site servers and not the NS server, for what? What are they receiving from other site servers? Where do you see this? What settings did you check and verify? Screenshots work great if you don't want to type everything out.
Mike Clemson, Senior Systems Engineer
Intuitive Technology Group -- Symantec Platinum Partner
The idea is that
The idea is that the NS distribute the packets to the Sites Servers, and they distirbuamcomputatadores for the network.
I think that the Site Server should point to the NS, and computers should point to the Site Server. Right?
What is happening is that my Site Servers are pointing to themselves, when they link toother Site Server network.
I checked the settings in Settings Package Servers and Task Servers Settings.
Carlos Eduardo CUSTODIO
Altiris Consultant
Check site server config, manually assign site servers to NS
Ensure that you have site server assignments. All subnets should be assigned to a site, and all sites should have at least one site server. Once this is done, all clients should be checking in with the site server(s) within the same site as the particular client.
If you want to force your site servers to get their packages from the NS, and not from each other, you can manually assign all site servers to the NS. Go to the NS within Settings > Notification Server > Site Server Settings. Expand Site Management > Site Servers and then expand your NS and select 'Manually Assigned Agents. Click New and select 'All Site Servers Target', click the > button, and click OK. All site servers will now use the NS as their site server, ensuring that all packages are obtained from the NS.
Does this help?
Mike Clemson, Senior Systems Engineer
Intuitive Technology Group -- Symantec Platinum Partner
This is partly normal
The Site Servers will pull packages from the closest package server. IE: The closest (on the network) server with the "Package Server" plugin installed. They also look to the NS. This is "by design" as it allows a multiple site server setup to act as a "mesh" network when distributing packages, decreasing both network load and distribution time. This can complicate matters though, as a "bad package" can take awhile to be purged from the system if you have many site servers running.
Make sure that your sites are set up properly too. If everything is in "Default-First-Site-Name" then you just have a big fat mesh network running. If you break the site servers out into their own sites with their own Ip ranges to cover, then you will have a bit more of a vertical structure to your package system.
Be aware as well, the primary NS doesn't (and shouldn't) run the package server plugin. It only distributes packages to site servers, and doesn't need the package server plugin for that.
Lastly, you may actually need to run multiple NS servers if you have several large sites. Once installed, these can all be controlled centrally by using the "heirarchy" settings on each NS. Just pick one NS and have it set as the primary on every NS, then you just run everything from that one console.
Hope that helps. Good luck!
I can configure them to look
I can configure them to look only to the NS?
Carlos Eduardo CUSTODIO
Altiris Consultant
Hello Carlos, It could be a
Hello Carlos,
It could be a name resolution that is preventing the clients not to point to the site server instead point to the NS. so do a NSlookup from the NS to the Site, viceversa, and the client to the Site and viceversa.
if name resolution is working the the responses you received above are the answer :)
Nelson Villegas
Would you like to reply?
Login or Register to post your comment.