affective developmentprint magazineippex onlineCymbalta Saleimpetus pressmerriam theaterkivel campus careBuy Maxaltgiven up tabsproduce the noteBetalaktamAllopurinol Salerainwater storage tanksprose piecesflooding in alaskaauthorize apple tvsegment ringbackdrop warehouselyotard 460dwiresharkhidden valleycreative webcampopcaps big moneyrussell athleticEmla Salecontinuous time clockRetrovir PharmacyCrotamitonAcetaminophenDiscount Protonixmoderately conservativeZincquestion synonymCetirizineSotretAcai PharmacySulfamethoxazoleschematic softwaredivol plusColospa Saleafresh definitionanimations for kidsGet BiaxinPurchase RogaineCozaar Onlinesprout walkthroughjoystick partsKetipinorpresence of godParlodel Onlineorientation ucfCheap MacrobidAshwagandhawang danLida Mantledisapproval of obamaDidronelInderalvirgins for salepouting babyintelligence testingAzithromycinguaranteed chordsindians in australiaanthropologists salaryAmoxicillinCheap Actosnotices of inspectionthang onlinesoutherly windsweden flagHydrodiuril

Microsoft                                                                                                                    06/07 to Current

Systems Engineer, Tier 2, 2200 users. 

  Production:

• Deploying Windows Server 2003/2008 according to MSIT standards. Slipstreamed drivers in nonstandard hardware and deployed the servers. Debugging kernel dumps to troubleshoot BSODs (it's almost always the drivers, not Windows!).
• Set up and implemented a global Virtualization project that automatically deployed thousands of Server 2008 VMs on hundreds of Server 2008 Core Hyper-V servers. My contributions to this project have saved thousands of man hours, reducing a complete Hyper-V with VMs installation from over 16 hours, to less than 5 minutes. While enforcing a uniform standard for 200 regional office installations.
• Migrated user and group folders to new file servers (mostly with robocopy commands executed from within VBS scripts and NTBackup). Wrote VBS scripts that verified changed DFS referrals.
• Scripted the Active Directory to automatically find users no longer working at Microsoft and move the user folders for final backup and deletion. Then took it the next step, incorporated office locations. When users now move from the location I support to a different one, the user folder is automatically archived.
• Installed, migrated and supported print servers and coordinated printer migration and deployment in multiple branch offices. Developing a special printer queue maintenance script.
• Created numerous ad hoc scripts to resolve issues affecting hundreds of servers. From forcing zero day vulnerability updates to Virus scanners that require re-installation, to generating spreadsheets of missing server information from WMI.

  Line of Business/Development:

• Upon request, wrote an inventory program with a small GUI from scratch in VBA that automatically prints bar code labels when adding new spare hardware to it and that helps keeping stock in a dynamic environment with the use of a bar code scanner and a label printer. Then later moved the inventory to a proprietary inventory program running on SQL 2003.
• Installed and administrated several Virtual Server farms with Microsoft System Center Management Console and library servers used for testing the deployment of Windows Vista Clients with BDD and Windows 2008 implementations and the functioning of WMI/SNMP scripts.
• Installed and administrated a Windows 2008 Hyper-V server farm with Server 2003 VMs for regression tests, that automatically deploys, deletes and reverts to snapshots when required (using PowerShell).
• Installed and administrated yet another 2008 Hyper-V server farm with Server 2003 and Server 2008 VMs, created a automated deployment system for easy creation of new VMs.
• Used the Microsoft Assessment and Planning Solution Accelerator to asses Hyper-V migration for development servers

 I was asked to participate one day a week in the VBOS roll out project. The goal of this project was to replace the Windows Server 2003 infrastructure servers of over 200 regional Microsoft offices with a Windows Server 2008 Hyper-V implementation.

 Before I enrolled into the project, the intention was to get as many IT managers as possible involved, hand over documentation and let each IT manager follow the instructions in the documentation. Early on in the project it became clear to me this was not a good way to do this project, so I proposed a different solution. Instead of relying on a large number of relatively unskilled managers, I wanted to use an automation script, that would fully automate the configuration of the Hyper-V server, then install the VMs and configure the VMs, all directed from one simple GUI.

There were several complications that would hamper automation of this process:

1. Since the bandwidth of many branch offices was very limited, the push out of VMs with VMM was not acceptable.
2. The IT managers decided on the sizing of the Hyper-V server, small medium or large and the Hyper-V configuration changed, depending on this sizing. however, there was no administration of who ordered what size server for which location.

 In the weeks after that I wrote a script with a GUI, based on VBscript, that used WMI to pull the required information from the Hyper-V server, to find the Domain the server was in, figured out the size of the Hyper-V server based on disk sizes and queried for installed patches.

 Then it used PSexec commands to install the required patches, created autounattended.xml files to set the VM options.

 Next, it used Powershell to create the VMs one by one, mounting the physical DVD to avoid network traffic that copying the VMs would create, mounting floppy images to apply the autounattended file and monitoring the event log to see if the installation is finished.

 The whole process was literally reduced from days of work, to only several minutes of attention required, each server automatically installed identically to the next. I did participate in installing about 15 Hyper-V servers this way, at that point my work load became to high and although I did continue to support the script, I was no longer able to roll out the VMs myself.

Here is an image of the script GUI: