SMS collections

SMS collections (Full Version)

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003

Message

jseber1982 -> SMS collections (10/9/2008 1:08:19 PM)
When machines are found on a discovery at one of the child primary servers, it will be sent up to the central right? I fell into our environment and i am working on streamlining our overloaded servers. Currently our central and all 3 primary servers are running machine discoveries on the same OU.s Would it make sense to make the east server only discover machines that are in the east OU? Same for west and Canada? And technically if that is the case.. why is our central server even running discoveries? Maybe on the central.. i can have it discover stuff that doesnt fall under east or west.. like enterprise servers

criticalerror -> RE: SMS collections (10/9/2008 3:06:47 PM)
We have a Primary site and 2 sceonday sites here. I have the same discovery settings for each site. I am only scanning a specific OU so it isnt very intensive to the hardware or network. You can throttle this data to only pass from child to parent if that would help you. It really kind of depends on how your sites and services are setup in AD and your boundries in SMS. If anything I would disable discovery on the child sites and just let the central site handle but again, we have plenty of bandwidth between sites and have all child site boundries configured as remote raoming boundries at the Primary site. Jeremy

jseber1982 -> RE: SMS collections (10/9/2008 3:23:15 PM)
we have an odd setup which i would like to change. Our central, east coast, west coast, and canada primaries are all sitting in the same rack with a gigabit connection. All of our secondary sites have a 256k, 512, or a 1.5meg atm connection under each of the primaries(besides central) we have approx 60 secondaries. 6000+ machines. No clients are connected to the primaries.. Each secondary boundary is that local sites AD site name., All of our software installs are based off of AD group queries that will remove the machine from the collection once inventory sees that it has it installed. Because of this,, our software inventory goes off every 30 minutes for all machines, and ad group discovery also happens every 30 minutes.. and all collections update every hour.. It is super intensive on the servers because of how often this is going on. I am gunna work on tuning down how often this stuff happens, but for now i just want to optimize it. I figure if the east coast primary will be having only east coast clients, why not make that one the first one that sees the discovery, and just replicate it up. No point in the west coast seeing it. I figure,, east coast sees east, west coast sees west....Central sees enterprise servers and machines

criticalerror -> RE: SMS collections (10/9/2008 4:07:25 PM)
That sounds like a solid plan. Your environment is more complex then mine but without looking through the SMS planning guide I would say that the plan seems logical. Our inventories run once a day and ill force them if I need some something to happen faster. Good luck man and if you have had plenty of coffee you can dig through this doc for specific answers .. http://technet.microsoft.com/en-us/library/cc179958.aspx Its the concepts, planning, and deployment guide for sms 2003

jseber1982 -> RE: SMS collections (10/10/2008 9:23:55 AM)
I hope this actually makes a difference now that i think about it.. I am making the servers get info from replication instead of getting it themselves. Would that even be beneficial? In terms of bandwidth and cpu,, probably about the same, But different queues on the server. They are in the same rack, so i guess replication wont be a problem.

skissinger -> RE: SMS collections (10/10/2008 9:43:19 AM)
I have 1 question: Software Inventory every 30 minutes? That can be intensive--to the client. Have you monitored your clients' inventoryagent.log and confirmed that the SW Inventory that occurred at say 9am is even done before the 9:30am one should start? Depending upon your client hardware, it might be perfectly fine. But if you have older hardware with lots of files and multiple local drives, I could see overlap there. Why SW Inv every 30 min? You have queries designed around versions of a .exe? Could you perhaps redesign those collection queries to be around versions reported from Add/Remove Programs, or a custom regkey? A delta Hardware Inventory would be much less intensive on the client (usually <20 seconds for a delta--of course depending upon what you have on/off/extended in hinv--but still it's not the minutes/hours a Software Inv can take.

jseber1982 -> RE: SMS collections (10/10/2008 2:35:55 PM)
How do you specify whether it is a delta or full?

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.234375