So, when something really went wrong on such an administered Windows machine, it is not so easy to see what is in that "box" causing the error. Or at least what is in that machine installed at all. This is why I decide to adopt and compound many scripts found around Internet into one huge script, which could help me analyzing Windows and underlying hardware. This is done through vbs script which can be downloaded from here. Because it is "dangerous" extension, after downloading, rename it to docummentation.vbs (double "mm" in name is intentionally made to prevent mix with other possible files).
When you run it (as user with Administrator privilege) on the active file system, as a result, a html docummentation.html file is created in current directory (where vbs is placed) with next gathered data:
- Hardware:
- Computer
- BIOS
- Motherboard
- Procesor(s)...
- Memory
- Disk(s):
- Partitions:
- SCSI kontroler(i)
- Network configuration
- Graphic System
- CD/DVD device(s):
- Modem:
- Periferije
- Ports
- OS:
- Installed applications (Add/Remove Programs list):
- Patch(es):
- Services:
- Shared folders:
The End
Regardless this is very short post, making this script took me one night, so I hope it will help someone else as it helped me.Cheers!