Blousers suck. They pop off, roll out, cut off circulation, take time and skill to configure each morning (neither of which I have for blousers) and when they do work, they ride up the leg exposing your socks. Tucking in or tying the pant leg lanyards (for lack of a better word) is another option for keeping your pant legs looking up to standard, but inevitably the pant legs pop loose and you have "snakes" spring forth from your boots. Fortunately, early on in my career I read those old Ranger Rick digest books and found a cool little trick that has kept me from screwing around with my pant legs every 5 minutes.

UPDATE: I've overhauled the Installer tool box design. The peg board is still used (sort of) but its just there to hold the MOLLE panel. Giving credit where credit is due, the panel was made by Mark at custommollegear@gmail.com. He did a great job, had a good turn around for about $90, and did pretty well working with my seemingly bizarre specifications.

The pouches were purchased at an army surplus store and most of them were gutted and re-sewn by my wife to accommodate the type of tools each would carry. The first prototype tool box i built had problems with the parts container shelf breaking. It was made out of pegboard. this time around I used steel, haven't had a problem since. The toolbox as pictured currently has one overseas deployment and probably 15 major projects tallied up and has been a real asset on the job site, but getting it there is not for the faint of heart; it weighs about 115lbs when loaded up. While it does have wheels, most job sites are not wheel friendly, and just getting it off the truck (alone) can really take a toll on the back if the installer is not careful.

This script uses a text document with a list of domain computers (defined under INPUT_FILE_NAME) to conduct a Census remotely that captures in a CSV (OUTPUT_FILE_NAME) the Computer name, image Date, Model, Serial Number, Hard Drive Serial Number, Antivirus version (McAfee), Last user on the machine, and the IP address. An example input and output file is attached.

Problem: The way we were mapping people to their Home drives (h drives) was through active directory (the 'Profile-Home Folder-Local path' option). When we migrated to a new server, we needed to change the server to the new server in ADUC A little while after that, we decided to start mapping people to their home drive via VBscript rather than through ADUC. In order to be successful, we needed to clear the local path string in ADUC and assign the script via GPO to each users logon script. Problem was no one wanted to waste 10 hours getting carpal tunnel. removing these values manually. To further complicate the problem, our VBScript mapped the home folder using the %username%, some of which were changed since the folder was created. This meant that for those select users, the script would not work.
Solution: We created a script that would change the 'local path' value to the new server. Later, we created one that would clear out all the 'local path' values of a defined OU. To rename the folder to the current username, we created another script that would scan each folder, look at the usernames that have permissions, ignore usernames that it was defined to ignore, then if it found a username that it was not told to ignore and found that it did not match the folder name, it would prompt the admin to change the folder name to the current user name. Wicked, ain't it? Attached file has all necessary scripts to do what was just described.