Tracking Registrations

[Johnwkay72]

I am curious how others out there are Tracking their BA client registrations and their changes over time so that there is a repository of information about a backup node. For small installations a spreadsheet would suffice but how about 4000 nodes with BA and TDP??

Thanks in advance for sharing your experiences and or suggestions.

 

[marclant]

Not sure I follow the question. Sounds like you want to know when nodes were registered? If that's the case, you could do a simple SQL query to get the node names and registration date:

select node_name,platform_name,reg_time from nodes order by reg_time desc

 

[Johnwkay72]

Hmm. I guess I was not clear enough. Let me try again.
We are looking to track the CHANGES to registered nodes against their Original and initial registration for auditing purposes. Yes, we have a ticket system but it is cumbersome to search and requesters do not always fill it out the same way.

Example:
02/05/201 - NODE-JOE is registered:
reg node node-joe password dom=windows clopt=windows ....
def assoc windows 2100 (21:00) node-joe
def collocm windows6 node-joe

03/15/15 - Change the Sched to 21:30 per app owner
03/20/15 - change colloc to windows3 due to consolidation of collocation groups
04/01/15 - Change CLOPT to SQL as they installed SQL
...
So I could have a tedious method like either:
1) 4000+ txt files for each registration and then the team is responsible to keep up to date.
2) a Excel spreadsheet with every change.
...
I am interested how anyone out there in TSM land might be doing this.

 

[marclant]

Sounds like you need some sort of change management system. Create a change ticket for any node addition/modification/deletion. Then report on those changes.