Throughout my internship I learned and improved a lot in regards to troubleshooting computers, projectors, and other technology. I learned to check the least complex possible solutions first and efficiently testing remaining possible solutions until the correct one is found.
I learned a lot about the Windows 10 operating system including some shortcuts to do administrative tasks and other cool things as well as getting to image hundreds of computers to Windows 10. I learned about projectors and how to care for them to extend their life and I learned how to efficiently handle any task in front of me no matter how repetitive. I figured out a lot of new powershell trying to create the script to change local admin passwords which ended up not being needed but it was a good exercise and test of my powershell skills.
There were also many support tickets out for random technology problems that we had to solve including iPad set-up, managing cables and transferring user data between google drive accounts, fixing the sound on a projector, among other things.
The coolest thing we completed was programming the Arduino chip to automate the chromebooks setup which added them all to the domain. We had to modify the script to only automate what we needed done and then add other things.
I learned in this career that every problem is different and there are so many different technologies to learn in the field. Also with a little trial and error I can apply what I have learned in my classes to successfully troubleshoot and fix almost any problem.
Throughout my internship I realized I want to be in a help desk or desktop support position in the future because everyday is has new problems and I would be fixing new things which means I would get to learn more and more about technology everyday and I would hope to never be bored! The other cool aspect of a help desk position is getting to teach the end user and answering their questions regarding technology in a language that they can understand.
The only aspect of my internship that I would change would have been to get more hands on in networking and learning about networking. I didn’t learn very much about the schools network infrastructure, switches, access points, or other networking equipment or management and I would have enjoyed that. Because of that I didn’t get to apply very much of my knowledge in networking.
The internship met my expectations for learning computer support but not for learning networking. I feel like I was well prepared for the tasks we handled and could do well as a desktop support person.
Resolving support tickets. Troubleshoot projector and document camera. Connect and move technology that was disconnected and moved to clean floors. Test projectors, computers, and document cameras to ensure that the video, sound, and multiple sources were working correctly. Cleaned up and deleted profiles using advance user profile properties to speed up a slow computer that had saved many profiles.
Unboxed chromebooks. Plugged all of the chromebooks chargers into the carts. Delivered carts to classrooms.
This week I learned time management and getting things done, even if a little bit repative, efficiently. Even though I didn’t get much hands on computer work most days I still took away valuable lessons and worked hard.
Unpacked chromebooks. Set up chromebooks with the Arduino chip.
Unpacked chromebooks. Set up chromebooks with the Arduino chip. Threaded chromebook chargers into the carts.
Unpacked chromebooks. Set up chromebooks with the Arduino chip. Threaded chromebook chargers into the carts. Removed hard drives from surplus desktop computers.
Moved a bunch of old desktops, monitors, keyboards, mice, and cables from multiple classrooms and put them into storage. Took a lot of machines from storage to surplus in a different building. Swapped equipment between classrooms. Set up and rearranged teachers desk and all associated cabling.
Continued adding students group to guests group on HP Streams. Updated some of the computers group policies using the command gpupdate /force.
This week I did a bunch a repetative tasks including imaging hundreds of computers from Windows 8 to Windows 10, naming them, adding them to the domain, installing applications on some, and other miscellaneous tasks. I learned a lot of keyboard shortcuts to speed up the process of these tasks and I learned some troubleshooting such as times the wifi would not connect or the computer wouldn’t join the domain. Most were simple fixes that were easily resolved. So I learned to always look at the most simple possible solutions first because it usually solved the issue quickly.
Added the students group to guests group on each computer so that students profiles are not saved locally which would cause the computers hard drives to fill up with student profiles. Finished up reimaging and adding HP Streams to the domain and changing their names.
Imaged using Paragon, changed the computer names of the HP Streams then added to the domain.
Continued imaging Windows 8 to Windows 10 and installing applications on the HP Streams.
Continued imaging HP Streams. Imaged over 100 computers from Windows 8 to Windows 10.
This week I did a lot of unpacking and setting up of the chromebooks and chromebooks carts. The project that I learned the most from was programming the chip to automate the chromebooks setup, that was awesome and we figured it out fairly easy just searching google. I learned a lot from that experience. I learned some cool things about MacBooks, such as how to add them to a domain and change the shared name. I also learned to image a computer very quickly.
Imaged 60+ HP Streams that we started working on a couple days ago but had an error with the image. It was resolved and we continued imaging using Paragon on flash drives. They are all going from Windows 8 to Windows 10. Renamed each machine and joined to domain.
Unpacked and assembled chromebooks carts and unpacked chromebooks. Recycled cardboard.
Learned the google admin console where policies are applied to all of the chromebooks. It’s basically like active directory but using google. It manages users and devices. It can even push out apps to selected devices. Each device has a folder with devices in it much like an OU which is sorted by school and room number. Things updated on google admin console get pushed out to the devices almost instantaneously because it is pushed out.
Then we looked at active directory users and computers to compare it to the google admin console. Unlike google admin console computers in active directory need to be restated or have run gpupdate for the changes to apply.
Lastly we began setting up some MacBook airs.
Unpacked and assembled chromebook carts.
Today we worked with a small chip called an Arduino Pro Mini which can do a lot of awesome things but we are using it to automate the set up of chromebooks by using an answerfile like script.
First we installed the windows application to use the sketchbook which is just your collection of scripts and the script editor. Then we installed the drivers for the chip. After locating the correct chip and port in the sketchbook we were able to load the chip with a script that made the lights blink to test it (as shown below).
We got a script for the automation of chromebooks and made the changes we wanted to be automated in the script and loaded it onto the chip. The green light started blinking in a heartbeat pattern after the upload letting us know the script was loaded and working.
Unboxed and set up 80+ chromebooks using the answerfile script created earlier and automated the setup to a couple minutes because of the automation each using 5 of the chips on 5 chromebooks at a time. Then we cleaned up all the trash and cardboard from the unboxing and disposed of it all. Lastly we started setting up the chromebooks carts with all the chargers.
Put an image on 10 flash drives for imaging 50+ hp laptops. Figured out how to get image/backup image from/to the network using Paragon. The hp laptops were giving an error when trying to restore, we were thinking it has something to do with the image file.
Unboxed 30+ MacBooks and set up the cart with all of the chargers to put them all in.
For the final day of this week I learned a lot about troubleshooting issues and managing time with many projects going on at once. I was able to help in the troubleshooting process on many occasions and learned a lot about testing and trying different solutions until the right one was reached. I felt like I grew a lot in the troubleshooting sense. I also learned a lot about cleaning up a lot of clutter and lot of cable management which included some interference issues and how the cables are combined to keep them from tangling up under desks and out of piles. Lastly learning about imaging with the Paragon software was really interesting.
Took inventory of computers taken out of classrooms to locate in spreadsheets and mark as removed.
Went around cleaning another schools projector filters.
Changed computer names on the computers in all of the classrooms at a school to remove all old computers in active directory.
I learned about imaging and deploying an image using Paragon. First you drag and drop the Paragon boot files onto a USB then either backup or restore an image. Backup an image to make an image of the computer or restore to deploy an image to a computer.
To deploy an image, first put the image you want to restore on the flash drive and then plug it into the new computer and boot the computer using the flash drive. Choose restore from the image on the flash drive to deploy that image on that computer. Choose the hard drive to restore the image to and then wait for the program to compete the restore.
After deploying the image there were a few additional changes that needed to be made such as the home pages on each browser needed to be set and the applications and desktop shortcuts created. These changes were made on the standard user account and then a script is ran as administrator to make all the changes as made on the standard user to each profile as people log onto the computer.
We changed the name, joined the computer to the domain, and added the computer to the correct OU in active directory, then ran gpupdate /force to update group policies. Then we had to install updates and it was good to go!
Later in the day we went around to all of the classrooms in one school and cleaned the filters in the projectors which is suppose to help the bulbs last longer.
First we started the day by going back over to the library with the two chromebooks that were to be set in kiosk mode for the library catalog. We were not able to get the link to the catalog to work in the chromebook or the kiosk app and suspect it is a problem with the library catalog itself.
We attempted to move a teachers desk and all the associated cables and tech from one side of the room to the other but ran into difficulties removing the unused cable from behind the projector and whiteboard. The cables used were also too long and were causing degraded image quality.
Later set up an iPad and an apple ID for a staff member and installed an app that she needed on the ipad as well.
Finally we emptied out a closet of surplus technology at one of the schools and took the stuff back to the annex building for storage.
Today we transferred the data from one google drive account to another by downloading the first accounts data and then uploading it to the second account for the new employee taking over the others job.
We had to manage some extra long cables and cable mess at a few workstations, one where the desk had been moved across a room. We used cable ties to organize cables and removed unused cables to reduce clutter. Worked with and ensured functionality of a document camera and projector after moving cables.
We had to remove 4 desktop computers from a classroom that no longer needed them as well as a cart full of tech equipment that was taking up space and unloaded all of this equipment back to the administration building annex.
At the end of the day we had to get a couple of chrome books into kiosk mode using an app so that the chrome book was only able to access a certain website and nothing else in this case the library catalog. We ran out of time to complete this project.
Today was the first day of my internship. First off, I was taken on a tour of all of the different school buildings and was able to see each buildings networking closet. I saw all of the server racks and tons of cabling that they are having pulled and replaced to cat 6 this summer.
Later I worked on trying to figure out a Powershell script that could change thousands of computers local administrator password remotely. While searching for the solution I found many different scripts that could be customized to do exactly what we needed but we ended up finding a command line program that could change the password without using Powershell. It is hard with Powershell because each machine has a unique encryption key that creates a problem when remoting into the computer since you are not at that computer, but it can be done if you have the right script. It is built into a suite called PSTools. Pspasswd allows you to take a document that contains a list of computers to change the password for each computers local administrator. This list can be made by going into active directory users and computers and choosing the OU you want to get the computers from and then choosing export on the menu bar. When the command is run it displays the computer name and that the password has been changed. We went into a computer lab and tested it on 5 computers and it worked but had trouble when one computer was turned off when the command was ran. The command just hung on that computer and the didn’t continue to change the passwords of the computers that were listed after the one that was turned off. We will need to do some investigating on this problem and more testing to see if this is our solution or if we should go back to the powershell leads we were working on before.
Lastly I was shown the school districts support ticketing system. It allows the district employees to add a ticket for their problem by school building and the system will handle the ticket and give it to the appropriate tech. Then the tech can respond to the ticket by asking additional questions or fix the issue and then close the ticket.
Hi! I am Christina Olinger and this is my blog about my IT 270 Summer Internship at Sedro Woolley School District. I am a student at Bellingham Technical College and on my 7th quarter. I am hoping to graduate at the end of Winter Quarter 2018. Thanks for reading!