system updating/company communication

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

hiya,

i would be interested what CF members use to hold technical details, diagrams and credentials of systems they support.
Does your chosen method have any facility for storing historical changes/prior set ups of the supported systems?

All input much appreciated!

Boycie

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

I have a big A4 notepad with lots of scribbles in it.

I also have generalised documentation in a 25 page word document.

 

Depending what credentials and details you're looking to hold; what you're describing (for the most part excluding diagrams) is a CMDB. This should also hold historical data and much more.

You could even go one step further and have something like BladeLogic or Opsware (Now HP) Automation, which would not only maintain this data and populate your CMDB for you but also take care of all of the change and service management that goes with it.

Regards

T.

 

What have you broken mate?