• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 255
  • Last Modified:

Documenting windows servers

Hi All,

   I have 3 servers running ( Windows 2003, 2008,  SQL 2000, SQL 2005, web servers), I want a good way to document them since im creating a disater recovery documents for each, is there any automated tools or scripts to achive this tasks.

Thanks
0
ITMaster1979
Asked:
ITMaster1979
2 Solutions
 
*** Hopeleonie ***IT ManagerCommented:
Hi ITMaster1979

I do it with SYDI.

Have a look:
http://sydiproject.com/download/
0
 
vaderjCommented:
I am a self employed IT consultant, former SharePoint Support Engineer for Microsoft Support, and I can tell you that, just to make sure I don't miss anything, I do everything manually; Start off by getting a "client verbatim" or, in the clients words what they expect out of the situation, followed by a document that states my impression of what the client expects. My next step is to start a "SOAP" note, which is how we documented cases at Microsoft Support; its an acronym which stands for Subjective (The clients perspective of the situation and expected outcome) Objective (your full assessment of the situation which means the hardware profile (CPU type, speed, amount of RAM, HD's including partitions and size, OS versions and patch levels (just to the SP), and the major function of each server, meaning what major programs are on there and their versions.  A=assessment, which means your assessment of how each of all the variables you have observed are interrelated, what dependencies are involved, etc; P=Plan - This is where you create the document which explains to the client what it is that you recommend, the exact processes, commands, etc that you think they need to accomplish to get them closest to the point of what your interpretation of the 'Subjective' was.

This may sound like a lot of work, but that is because it is a lot of work. This is the difference between the local 'computer guy' and a professional consultant.  There maybe some programs that can profile a  system to a minor level, but it takes grunt work to do it right.
Some tools which I use on a daily basis are:
ProcMon (SysInternals by Mark Russinovich) - This will log every process level action going on in windows
Process Explorer: I always have this running at startup on my work station because I like to break thinks =-)

NetMon - MS packet sniffer - useful at times, but...
WireShark - OSS packet sniffer - the best that there is, its not as easy as netmon however

Notepad++ - just a good general text viewer with built in language highlighting

when it comes to databases, the Data Sources control panel (otherwise, you create a basic text file and call it whatever.UDL ) gives you the ability to create ODBC connections quick - the control panel also allows for performance logging.
 
a good log parser is really nice to have for when you are doing performance analysis and creating multi-GB log files

Like I said, its a log of grunt work, but thats why we get paid the big $$ allegedly
0

Featured Post

SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now