Client Management Suite

It's been a a while since I have had to do this and am looking for some advice or some best practices. Our Reporting Server seems to be bringing back a mess of inccurate and out of date INV data regarding things like software and the like. We have gotten the go ahead to purge this box and allow our four Notification Servers send up fresh data.

Is there a recommended process for doing this effectivley? We have a total of about 30K nodes in the environment. I would love any siggestions on a specific method to purge this data from the reporting server and in effect start fresh?

Let me know how you would go about it.

Thank you

Derek 

What I ended up doing was essentially recreating a new database (keeping server name, etc) and then pointing the install to that. All the data is gone, but nothing changes on the regional side, so they forward on their normal schedule.

That was certainly a method I have been thinking about. I just need to determine whether or not anyone is pulling directly from the current DB directly.

Hi jharings:

We are considering this option for one of our NS 6.

How can we create a new DB?

Thanks:

      Falquian

Let me know and I can get more detailed.

Essentially,

 1. Using SQL Management Studio, you can right click on the SQL install(instance) and create a new database. Call it Altiris1 or AltirisNew (or whatever, just so you can differentiate it.

NOTE: Do this BEFORE you change anything on the NS.

2. It will be a 'blank' or standard SQL database, and will take your default properties either your DBA or Microsoft has so kindly set for you (database and log location, memory usage, security, etc).

3. Make sure you login to the server via a 'session 0' terminal services (mstsc /admin or mstsc /console) or be on an otherwise direct connection to the server.

4. Open the web browser and do a 'mini-setup' by going to: http://localhost/Altiris/NS/Install/NSSetup.aspx. go through the 4 steps, confirming the details. When you get to the final step select the new database (instead of existing). This process will take some time, but will essentially create all the tables Altiris needs.

5. Nothing should need to change on the regional server(s) inventory forwarding rules. Whenever they next forward, the data will be populated on the reporting server.