We're going to relocate/shift datacentre soon. Prior to shifting, I'm compiling a list
of things to check on the Windows server so that after moving to the new place
& power up, should there be problems with the servers/services, I could quickly
check & narrow down if the problem lies within the Windows server (or external
to the server.
If it's within Windows server, would like to be able to narrow down if it's due to
certain applications/tools not started or hard disk or ... problem.
I've got a few checks so far, so appreciate if anyone can add on to it :
a) sc queryex >> check.txt
b) netstat -a | find "LISTEN" >> check.txt
(services like Oracle server, webserver etc listens on ports to
provide services to clients)
c) netstat -r >> check.txt (to get the routing table??)
what about "route print" ??
d) mem/c >> check.txt (in case there's faulty memory,
to get vendor to replace it)
e) what disk check can we do? chkdsk ??
f) what about 'arp table' : there's tendency to have such
problems after power down & power up between the
network switch/router & server & would be good to
know if the fault lies with server or network
g)"ipconfig/all >> check.txt" is useful??
h)'winmsd' launches a GUI & we can save it as a .nfo file.
Anyway to capture it to a text file. Btw is winmsd useful
at all? If hardware vendor needs to know the parts to
i)how can we capture the "device manager" output : I
usually right-click on My Computer, Manage, to get to
Device manager but it's in GUI (good to capture it in text)
Any command for health check for CPU board?
A bare metal backup using Acronis will be taken before
In the older days of Win 3.1 or MSDOS, I could do "fdisk" to
capture the disks' partitions (in Linux, it's 'fdisk -l" ) : what's
the equivalent for this in Win XP/2003? In case there's a disk
crash, we'll need to rebuild the partition sizing back