Things are not so sad after all, because this break gave me the time to come up with this document. I hope this will stand as a must read for network administrators and security experts out there. As new technologies and new viruses will emerge, some of the information may soon be obsolete, but I think that above the batch code presented here, the lesson to be learned is that it makes sense to look at what you got and what you can do with it before going for expensive software purchases that can deliver most of what you want, not always the way you want, and the possible bugs and flaws that are likely to come with it. You benefit from having knowledge of what's going on on peoples PC, and no remote-monitoring software can beat the human approach (and the human approach will never crash due to system failure). A few early extra steps can save you a lot of steps in the long run (especially the steps you have to make to go from one PC to another).
As for me, I have started to refine my knowledge in computer security, and I am getting anxious at trying some new ideas on my next workplace. I intend to implement a UNIX way of dealing with security in Windows NT networks. This will surely prove to be fertile grounds for new documents like this one.
11. The sad thruth
Appendice A: Something extra
Table of contents