Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SMS 2003 Database

Status
Not open for further replies.

GSC

MIS
Mar 27, 2001
464
EU
Hi,
I was wondering how you guys keep your SMS database clean.
We have about 25000 clients on our central server and we run and AD system discovery on the computers OU once a week.

We've created a lot of reports that we send out to our site admins where we ask them to remove inactive clients from AD so that they don't get imported when the AD System Discovery runs but that doesn't always work so good so our reports are not 100% accurate.

Currently I'm comparing data from AD and SMS to remove the "inactive" clients on a weekly basis instead of the 30 days it takes SMS to remove an inactive account.

Any thoughts or tips would be greatly appreciated.

Thanks,
GSC
 
Well you can always change your site Maintenance tasks to reflect what you want, for instance the delete aged discovery data could be moved down to a week (but what if someone goes on vacation foe two weeks....)

There are many settings in there you can tweak, just make sure you dont get to aggressive and the delete dates are in line or you will create a firestorm of network activity, meaning if you set things like delete aged inventory history every week, but only inventory every two weeks...you see where I am going here.

Another way to automate discovery data is to make sure you are DNS/AD scavenging which will automate the deletion of old /DNS AD records so SMS won't "discover" machines that are not really there:

DNS/AD scavenging


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top