Details of these solutions will not be provided in a pubic facing website. Potential employers may inquire during an interview.
Recreating IT support tools
The Problem:
One of the main tools we used for interacting with ActiveDirectory was blocked after a change to group policy.
The Solution:
I created a script, complete with GUI, which implemented the required features (querying and adding computers) in powershell. From there new features were added to automate other tasks to include software installation, user migration, workflow improvements, version control, and remote administration functions. I've since added logging and job control functions.
The Problem:
One of the main tools we used for interacting with ActiveDirectory was blocked after a change to group policy.
The Solution:
I created a script, complete with GUI, which implemented the required features (querying and adding computers) in powershell. From there new features were added to automate other tasks to include software installation, user migration, workflow improvements, version control, and remote administration functions. I've since added logging and job control functions.
Repairing legacy scripts and programs
The Problem:
A standalone, air-gapped system was used to create the imaging media for the shop. One day, the script simply stopped working. The original creator of the script was no longer with the company and the code was entirely uncommented.
The Solution:
On inspecting the code, I noticed the mount locations were hard coded in some locations and unspecified in others. Where the system was airgapped, single purpose, the script ran by effectively just assuming that mount points would be created with the same drive letter each time without any way of enforcing that. I added code to detect the assigned drive letter to remove the hard coded components. I also revised the interface and cleaned up the code by moving the imaging code to a function call rather than repeating the instructions for every case.
The Problem:
A standalone, air-gapped system was used to create the imaging media for the shop. One day, the script simply stopped working. The original creator of the script was no longer with the company and the code was entirely uncommented.
The Solution:
On inspecting the code, I noticed the mount locations were hard coded in some locations and unspecified in others. Where the system was airgapped, single purpose, the script ran by effectively just assuming that mount points would be created with the same drive letter each time without any way of enforcing that. I added code to detect the assigned drive letter to remove the hard coded components. I also revised the interface and cleaned up the code by moving the imaging code to a function call rather than repeating the instructions for every case.