Reflection #1

My name is Cameron White, and I have an internship with a company called IPconfigure. I did not specifically choose IPconfigure to complete my internship; I applied to many places, and IPconfigure was the one company to give me a chance. However, it was my top choice for places to work. This is because it is in a prime location very close to my house, and it has a great work-life and school balance, all with competitive pay. This made IPconfigure a prime spot for me to complete my internship. 

IPconfigure is a video surveillance company that offers both hardware and software solutions. The hardware department, which is its own department within the company, includes assembling and packaging the servers to run the camera system. We get the hardware pieces in separately and have to fully assemble the servers from the ground up. Another department is the software side. This includes developers and engineers working together to create new software that will help the company improve and keep pace with the rapid advancement of technology today. There is also a team that tests the software that is already out there to constantly find and fix bugs that may be in the software. They help the company improve the lives of its users, making sure the software is up to date and runs proficiently. Lastly, there is the support team. They are the “front end” of the company. They get calls and talk directly to customers, helping them through common and sometimes new software and hardware problems. They help walk the customer through fixing or finding the problem with hardware parts. And can directly work on the software side through their own computers. IPconfigure was started in 2003 by Chris Uiterwyk who was a Navy veteran. He started the company in Norfolk, Virginia. In 2012, Chris bought a building in an old gas plant from the 1930s on Bowdens Ferry Road. This move not only gave the company a unique home but also supported the revitalization of the Lambert’s Point neighborhood. The company began with the goal of creating video surveillance software that was open-standard, flexible, and easy for customers to use. Over time, it grew to also provide hardware assembly alongside its software. Today, IPConfigure continues to focus on innovation, customer needs, and forward-thinking technology while remaining a proud veteran-owned business.

IPconfigure sells many products, and the company focuses on delivering its state-of-the-art software. However, it also delivers some hardware parts. IPConfigure sells a range of video surveillance products, including its Orchid video management software, which comes in different versions like Orchid Core and Orchid Fusion to support unlimited cameras across multiple sites. The company also builds and ships its own SteelFin servers and storage systems, designed specifically for handling the heavy demands of video data. The servers are configured on-site at IPconfigure to work seamlessly with Orchid software, giving customers a complete, reliable solution. Also, IPConfigure offers hardware kits, storage systems, and software licenses for different camera counts, along with accessories and add-ons such as additional camera licenses and charging stations. 

IPconfigure serves a wide range of customers, some including WAWA, Dollar Tree, and UNC Chapel Hill. For Wawa and Dollar Tree, the company provides both software services and a steady supply of servers. These two customers rely heavily on IPConfigure’s hardware, which means the team is constantly assembling and shipping servers to meet their ongoing needs. In contrast, UNC Chapel Hill also uses the servers built by IPconfigure, but they primarily use the software side of IPConfigure’s offerings, because they do not expand as much as the other companies, so they do not need as many servers. They all use the Orchid platform to manage and simplify their video surveillance needs.

The first orientation training at IPConfigure was very smooth and well-organized, which made the process easy to follow. The company seemed very professional and put together, and they knew how to make the orientation seamless. The training itself was detailed, but not too difficult to understand. After going through the steps a couple of times, it became much easier to get the hang of it, especially if you already had some prior knowledge of building computers. Overall, my first impressions of the company and the internship were very positive.

Reflection #2

Doing my internship at IPconfigure in Norfolk, Virginia, showed me a management environment that is both highly supportive and hands-on. IPconfigure is a technology company. Specializing in video camera software and building and repairing hardware, like computer servers. Being in the industry, many things are very important, like teamwork, communication, and problem-solving. These are all essential parts of the daily workflow. I report directly to my supervisor, Mark, who oversees the assembly department I work in. From the very first day, it was clear to me that Mark plays a very active role in our department. Both on the technical and managerial sides of the operation.

We hold monthly performance review meetings. We discuss my progress, review any challenges I may have faced, and set goals for the following month. These meetings provide structure and accountability, but what makes the management environment at IPConfigure unique for me is the daily involvement of Mark with us. He works in the technical support room, and that room is separated from us by just one door. Mark is constantly checking in on us throughout the day to provide technical guidance and updates on what we need to switch our attention to, to help get the work done as efficiently as possible. He does all this without putting a feeling that someone is always watching us. This accessibility makes it easy to ask questions and receive quick feedback without having to schedule formal meetings.

The way Mark manages can be described as practical and hands-on. When we encounter a technical issue, he encourages us to brainstorm possible solutions first, offering hints or suggestions when needed. If those approaches don’t solve the problem, he steps in himself to help troubleshoot the issue directly. Watching him work and explain each step has been a great learning experience. Most of the things that I watch him do to solve problems on these computers, I have either encountered in class or encountered in a class later on. Also, Mark does not just give simple instructions or go really fast to get it over with. Instead, he goes into detail on why this solution fixes a problem and what to do if some of those steps do not work. He is really trying to teach us the most possible to become better at our position. 

The management style at IPconfigure fits the company’s relatively small size; it is very teamwork-based. The company has different departments, including Tech Support, Computer Engineering, and Human Resources. Each department works like its own small team, but everyone still helps each other when needed. Adding on to that, communication at IPconfigure is very open and casual. People talk to each other in a comfortable, friendly way while also being respectful. The work environment is definitely more relaxed, but of course, it is also focused on being productive as well. There is a lot of mutual respect between management and staff. If someone does not work there and looks in, they would not be able to tell who is a manager and who is just regular staff. 

Overall, I found the management environment at IPConfigure to be very effective and supportive. The mix of hands-on leadership, open communication, and trust in employees helps keep IPconfigure a motivating a fun place to work. Every time I come into work, I know what is expected of me and what I have to do. Having Mark as a manager is a great experience because of how much he taught us and improved our confidence in the workplace. IPconfigure not only helped me improve my technical skills but also showed me what good management looks like in a real workplace.

Reflection #3

With my internship at IPconfigure, there are many different tasks. However, these tasks come with a general workflow. These tasks are things like assembling servers, putting these servers on server racks and wiring them up, then boxing these servers and stickering them to be sent out on a pallet to the customers. It’s important as an assembler to follow this process precisely and keep it consistent, this is so that it ensures the quality and reliability of the product for the clients. The purpose of this paper will be to describe how these tasks are completed in detail so that you can understand what a server assembler at IPconfigure does.

Assembling servers sounds more complicated than it is. While most people can not just walk in and build a server successfully, it is not that hard to pick up. I will describe the whole process we do for the Dollar Tree (DT) servers we build. First we have to make sure we are getting the correct components that go with that order. We organize all the components close to a box with the serial number that goes to the order we have to fill. Then we distribute equal amounts of servers and server hardware to each assembler. After we have distributed all the hardware and servers we then begin to build the servers. All the hardware components for the servers include the server chassis, motherboard, power supply, ram sticks, SSD or solid state drive, CPU or Central Processing Unit and CPU fan, and lastly the hard drive. Once you’ve made sure you have all the hardware to build the server you first start with building the motherboard. For the motherboard you will need the CPU, the CPU fan, ssd, and two RAM sticks. First, we begin with putting the two Rams takes in the correct slots with a space in between them. Then we move on to putting in the SSD. Then you put in the CPU carefully to make sure you do not bend any pins. And then after all that has been assembled you put the CPU fan over top of the CPU, and then you have completed the motherboard. Once you’ve completed the motherboard you then carefully place it into the server chassis. You will then need to screw in the motherboard. The motherboard takes eight screws to fully fasten down. Once you have the motherboard screwed into the server chassis you will need to install the network card (NIC card). You now need to connect all the wires from the power supply to the motherboard. you can connect these wires in any order you like, Personally I like to connect them and this order. First, I plug in the CPU power cord, then I plug all the auxiliary cords in for the power LED, the power button, and other auxiliary functions, then I plug in the SATA cables for the hard drive, Then I plug in the cord for the USB, and lastly I plug in the motherboard power cord. After all these have been plugged in you need to cable manage and make sure none of the cables are touching any fans inside the server. Then you close the chassis and plug it in at the station we are working at to make sure it turns on. The motherboard will either show a white, yellow, or red light. If it shows a white light everything has been assembled correctly and works. But, if it shows an orange or red light something has gone wrong. Most of the time it is either the RAM sticks have not been fully  pushed in, or the CPU is bad or damaged. 

After we’ve assembled the server. We now move to racking. With this step we have to take the servers and bring them to our server rack station. Each rack can hold up to 10 servers. Most Dollar Tree orders we do call for 25 servers. This means that for one order we fill two and a half racks. Once we’ve completely filled these two and a half racks we then move behind the racks and start to plug the servers in. We plug in the power cord, USB for the mouse and keyboard, the ethernet cord that goes into the NIC card, and the HDMI cord. Now move over to the computer screen. On the rack there is a switch with different numbers to go to each computer on the rack. You will start at number one and go through the BIOS of all the servers, one at a time. In the BIOS we are changing things like fan speed too high, restart after AC power loss from off to on, and general performance settings. Once we get done with configuring the BIOS the people who work in support above us then take over the computer and install IPconfigures camera software. Once support is done we watch over the computer as it goes to the update and make sure everything installs successfully. After everything is installed and everything looks good we take the servers off the rack and bring them to the next station. 

Now we’re on to boxing the servers. Boxing the servers is one of the more simple tasks that the assemblers do. During boxing all we do is wrap the server in a plastic bag, put two styrofoam pieces on each end of the servers and put them in a box. Along with the server we put three pieces of paper with information on it on how to successfully connect the server and how to fix common problems that many customers have with the servers. After we have put the servers in the box along with the three sheets of paper, we now print out box labels with serial numbers to each computer. These labels get placed on the right hand side of the box to make everything consistent for the customer. After we have labeled all the boxes we then fit all 25 servers on a pallet, wrap them tightly with Saran Wrap, and then place package slip labels in a visible place on the Saran Wrap. We then take the pallets into a warehouse room using a pallet jack, and leave them there for the shipping side of IPconfigure to then ship them out to the customer.

In summary, as an assembler we have to deal with many parts of the assembly process. We build servers from the ground up. We then have to move these servers to a server rack. After we have plugged in all the computers to the server rack. Then we have to go through the BIOS and configure them. Lastly, package these servers up to get them ready for shipment. Learning all these processes has really given me great experience in the tech industry, primarily in the hardware field. 

Final Paper

I chose my internship at IPconfigure for many reasons. Some of these reasons include the location, modern facility, connections, and the work environment. The location of IPconfigure is one of the biggest reasons IPconfigure was number one in my search for an internship. IPconfigure is located only a few streets from where I live. I can drive there in 3 minutes, bike there in 7 minutes, and walk in 20 minutes. This means no matter what situation I’m in, I can always easily get to work.

Second, the facility is very modern. The inside is easy on the eyes and does not look like a jail cell. There is a ping-pong table, a TV with a gaming console in the kitchen for people on their lunch breaks, and an upstairs area with an arcade cabinet and workout machines. All of those added up to make the facility very appealing to me.

Third, before I worked there, a few of my friends were hired and worked there. This helped me get an inside connection to the company and the hiring manager. This made my application a bit stronger, which made me want to apply there more.

Lastly, the work environment is amazing. As mentioned before, there are many amenities to make the mundane workflow a bit more lively and fun. This was appealing to me as it would for anyone. Those were the things that set IPconfigure apart from other companies. IPconfigure and some other companies were appealing to me because they fit into my degree. The company focusing on IT, hardware, and other technologies really draws me towards the company. I wanted and needed exposure to real-world work in the IT field, and I could get that done and love my job at IPconfigure.

Three learning outcomes I wanted out of my internship at IPconfigure were to gain a deeper understanding of the technology field, strengthen my problem-solving skills, and build connections. Gaining a deeper understanding of IT and other technology systems is not only something that interests me, but it is also something I need to succeed in the IT field. I also wanted to strengthen my problem-solving skills. Having a job where I have to think on the fly and do new things on my own is something I admire. At IPconfigure, I get to challenge myself in many aspects. I get to work through technical tasks, including things like building new servers. A lot of the time, when I come into work, there are new server chassis and new hardware that I have to figure out how to assemble. This makes me have to actually use my skills to figure out where things go and how they all fit together. I also love when things break, but not because they are broken. I love having to figure out what went wrong and getting the satisfaction of fixing it and seeing it work. Lastly, I wanted to build connections at IPconfigure. In the technology industry, who you know is more than half the battle when it comes to getting a job. This is why I wanted to make as many good impressions and meet as many people as possible at my place of work. 

IPConfigure is a technology company that specialises in building physical servers, security cameras, and camera management software. The company creates both the hardware and the software that businesses need to run their security systems. Because of this, IPConfigure works with many different companies and organisations that need reliable security equipment. One of the biggest customers IPConfigure works with is Dollar Tree. Most of the servers we build are for their stores, so a lot of our daily work is focused on filling their large orders. We also build servers and provide support for companies like McDonald’s and Wawa. For Wawa, the work is mostly software and support rather than building a large number of servers. Different companies use IPConfigure’s products in different ways depending on what they need for their stores or buildings. IPConfigure also gets orders from other places, such as local school systems and police departments. These are usually one-time orders and much smaller than Dollar Tree or McDonald’s. Even though they aren’t big contracts, they still show that IPConfigure works with a wide range of customers and can build systems for many kinds of environments. 

The company is veteran-owned by Chris Uiterwyk, who started IPConfigure in 2003 in Norfolk, Virginia. He built the company from the beginning and has grown it into a well-known name in the security and surveillance field. His leadership has shaped the company into a place that values teamwork, quality work, and building reliable products for customers who depend on them.

My early days at the company were great. On my first day, I was greeted by everyone who worked there with a smile. I felt very welcomed working there, everyone was willing to help with any question or problem I had. Furthermore, the facility and work environment were very nice. The kitchen and other areas were nicely set up and had a good atmosphere, along with the warehouse and server assembly area where I worked. All the tools and work stations were very organised, and each station was filled with an adequate amount of tools.

When I arrived at my station on the first day, I was put with a senior assembler to learn how to complete all the tasks I had to do during a normal workday. This included building the servers, racking and imaging the servers, and finally, boxing the servers and putting them on pallets to ship out. The workflow was very well set up and organised, which made the company and the work look very professional. Every six months, you go to a performance meeting, and they evaluate everything about you. They look at how you work, your cleanliness, your teamwork, and your timeliness. They rate all those from one to five; you do not get anything for a good review, but it does show you how they see you and what you can improve on to be a better employee.

For my team in the assembly room, I was very lucky. Because three out of the five assemblers were friends I had previously to working there, this made it easy to feel comfortable in the assembly room and easy to get used to who I was working with. The company culture is very relaxed, and you are able to get up, go to the kitchen and grab a snack or a drink if you have some downtime. A lot of time in the assembly role, there is a decent amount of downtime, because we oversee the updates of the servers, and those can take some time. During the updates, we can take breaks and go to the kitchen if needed and do anything else we need to. The internship role is definitely a vital role in the company; they need assemblers.

While it is a basic level internship and to some would be relatively easy, it can still challenge you to think and will have you confused at times. But this is what you want. It helps you to become a strong applicant in future job applications, and it helps you understand IT roles better than you could without it. Personally, I was very excited for the role. I knew that IPconfigure was a great place to work from my connections inside the company. 

The management at IPconfigure was great, especially for the assembly and support side. For the assembly room, our direct manager was a man named Mark G. Mark would check in many times a day. He was always letting us know if tasks needed to be done and in what order. Mark was a very helpful and hands-on manager. If anyone had any problems, he would tell us how to fix it and see if we could do it ourselves. If that did not work, then he would try and fix it himself, but while he was fixing it, he would let us watch, and he would describe everything he was doing to help us better learn what went wrong and how to fix it next time.

This really meant a lot to everyone who worked in the assembly room. Mark cared about our future and wanted to teach us everything he knew. Communication within support was good. Mark sat right outside the door of our assembly room, and he had a window so he could see in. This meant if anything happened, he was there close by, and if he needed to tell us anything, something as simple as switching tasks or calling us in for a meeting. The hierarchy of management was simple at IPconfigure. The assemblers were a part of the support division; our manager was Mark, who worked in support, and was the assembly manager of support. However, all of the support team was higher than us and could help us out if needed. Then, ahead of Mark, was the support room manager, then after that comes the CTO (chief technical officer), then after him is the CEO (chief executive officer). 

Our daily responsibilities included things like building physical servers, racking the servers on server racks and imaging them, and packaging the servers for shipment. I will describe the whole process we do for the Dollar Tree (DT) servers we build. First, we have to make sure we are getting the correct components that go with that order. We organise all the components close to a box with the serial number that goes to the order we have to fill. Then we distribute equal amounts of servers and server hardware to each assembler. After we have distributed all the hardware and servers, we then begin to build the servers. All the hardware components for the servers include the server chassis, motherboard, power supply, RAM sticks, SSD or solid state drive, CPU or Central Processing Unit and CPU fan, and lastly the hard drive. Once you’ve made sure you have all the hardware to build the server, you first start with building the motherboard.

For the motherboard, you will need the CPU, the CPU fan, ssd, and two RAM sticks. First, we begin by putting the two Rams takes in the correct slots with a space in between them. Then we move on to putting in the SSD. Then you put in the CPU carefully to make sure you do not bend any pins. And then after all that has been assembled, you put the CPU fan on top of the CPU, and then you have completed the motherboard. Once you’ve completed the motherboard, you then carefully place it into the server chassis. You will then need to screw in the motherboard. The motherboard takes eight screws to fully fasten down. Once you have the motherboard screwed into the server chassis, you will need to install the network card (NIC card). You now need to connect all the wires from the power supply to the motherboard.

You can connect these wires in any order you like. Personally, I like to connect them and this order. First, I plug in the CPU power cord, then I plug all the auxiliary cords in for the power LED, the power button, and other auxiliary functions, then I plug in the SATA cables for the hard drive, then I plug in the cord for the USB, and lastly I plug in the motherboard power cord. After all these have been plugged in, you need to cable manage and make sure none of the cables are touching any fans inside the server.

Then you close the chassis and plug it in at the station we are working at to make sure it turns on. The motherboard will either show a white, yellow, or red light. If it shows a white light, everything has been assembled correctly and works. But if it shows an orange or red light, something has gone wrong. Most of the time, it is either that the RAM sticks have not been fully pushed in, or the CPU is bad or damaged. 

After assembling the server, The Next Step would be racking. and this step, we bring the completed servers to the server rack station. These stations can hold up to 10 servers. it typical Dollar Tree order requires 25 servers, which means we need to fill two and a half racks. Once all the racks are filled, we then must move to the back of the racks and plug the servers in. We plug in a power cord, a USB cord for the mouse and keyboard, an HDMI cord for the monitor, and an Ethernet cord into the NIC card. We then must fill out some short paperwork describing which order these servers belong to.

After all the physical connections are plugged in, we then move to the computer monitor. Each rack is connected to a switch that has numbered ports that correspond to each server on the rack. We then begin at number one and move all the way through all 10 computers on the two racks and all five on the third rack until we have completed all the BIOS settings we have to change on each server.

Inside the BIOS, we can configure several settings for the server. These settings include increasing the fan speed to high, which causes all the fans to spin at maximum speed, cooling the server a lot. Then you change the restart after AC power loss option from off to on so that the server will restart after any power loss, so nothing fries in the server. Lastly, you adjust other performance-related settings as needed for the server.

Once all the BIOS configurations are complete, the support team who works right beside us can then remotely take over the servers and install IPconfigures camera management software. This takes some time, and they have to do some work remotely by SSH’ing into the server, and then they have to physically go into the assembly room to continue to do updates and configure the server.

After support finishes up with the camera management software installation. They let us know, and we will then monitor the servers as they run through the updates to ensure everything installs correctly without errors. When the software and updates are complete and the server passes all checks, we then move on to the next step. We now do what we call sticker the servers. In this process, we print out serial numbers on a sticker and place them on the correct server. How we find this direct server is pretty easy. While support is installing the camera management software, they also do a process called Ansible on the computer, and when they do this, they assign each server a serial number linked with its IP address. We then log into the server, find the IP address and the serial number linked to it and sticker that server with the correct sticker. After we sticker, we remove the servers from the rack and bring them to the next station to complete some of the final steps. 

Now we begin the final steps and the server assembly process. This step is boxing; it is one of the simpler tasks performed by the assemblers, but it’s still very important and has an optimised layout to follow. During the step, we’ll first wrap each server in a protective plastic bag. Then we place two styrofoam caps on each end of the server to keep it secure inside the box and safe from bouncing around. Once the server has the styrofoam pads on, it is then placed inside the box along with three informational sheets.

These three informational sheets explain how to properly connect the server to the internet, to the cameras, and provide solutions to common issues that customers may experience. We will then put all twenty-five box servers onto a pallet and wrap them in plastic wrap, and use edge protectors to protect the edges of the boxes. Lastly, we use a pallet jack to move the finished palette into the warehouse area and from there, the shipping Department takes over and prepares the servers for delivery to the customers. 

Sometimes you will have to do one-off servers. These one-off servers will usually be a bit more difficult, and no one, not even the managers, will know exactly how it goes together. This is where the problem-solving that I love so much comes into play. With these one-offs, it will be a completely new chassis and new hardware. They will then tell the assembly room to figure out how it goes and see if it works when we turn it on. We do have a lot of practice and knowledge when it comes to putting together servers, so it is not a shot in the dark, but it definitely takes some brainstorming and teamwork to get it done correctly within the workday. The one-offs or something we in the assembly room look forward to, because they are something different and challenge us in many ways. After we’ve completed the one-off server, we will get one of the people in the support room who works with Mark and is very intelligent when it comes to hardware, to look at the server and give one last check before we plug it in and see if it works. After we completed the one-off server, we then run through the same process as mentioned before with the Dollar Trees. We take it to the server rack, we image the BIOS, and then we package it up for delivery. 

All these tasks are necessary for the business because they sell these physical servers, which make them money, and they need people to build them. However, they cannot take time away from the support room and have the people from support build them because they need to be helping our clients out with any problems and fixes they may have with our software, their cameras, and or their servers they get from us. In addition,  having assemblers building servers all day, five days a week, gets them really used to how they are assembled and how they are imaged. This can then make the Assemblers build servers faster, more efficiently, and with better quality. Lastly, it helps IPconfigure save some money as well. The workers in the assembly room are paid at a lower rate than the people and the support room, and having a few people work at a lower rate rather than splitting someone’s work that is paid more can help the company save money and the long run.

Hardware assembly at IPconfigure does not directly use cybersecurity skills or knowledge, but you definitely need to be aware of your own cybersecurity for the company’s well-being. While the job does include aspects of cybersecurity, like understanding the basics of Linux, that is really the full extent to which you use your cybersecurity knowledge and skills. When troubleshooting Hardware or connection problems with the server, you need to be able to navigate through the Linux command system and see things that are wrong within the server and be able to fix it. While cybersecurity experts need to know a lot more than just that, this does still act as a stepping stone towards cybersecurity jobs in the future.

All these skills I’ve learned from classes I’ve taken at Old Dominion University. These classes have taught me a basic understanding of network Concepts, Linux commands, and file system navigation.  However, what I think you can implement and what this job teaches you is the other side of cybersecurity. This side is keeping you and your company safe from any vulnerabilities that you can control. At IPconfigure, we do have work emails and work accounts. These work accounts need to stay secure, or else unauthorised people can gain access to sensitive information. Even as an assembler, I have access to the majority of things that the public should not.

This is where our previous cybersecurity knowledge needs to come and play. As an employee, you should never respond to any suspicious emails with sensitive information, you should always log out of any computer that you are using once you’re done, and never tell anyone any usernames or passwords to computers that are not authorised to use the computers. Also, any personal passwords set to any work account need to meet a minimum requirement of eight or more characters while using symbols, capitals, and numbers. Must these skills I had already known before working at ipconfigure, but being able to actually apply these skills helps with understanding exactly how they help and how important they are. 

The classes I’ve taken at Old Dominion University have helped prepare me for my job at IPconfigure. While taking these classes, I knew the information was important; however, I did not know how common a lot of the concepts I’ve been taught are used on a day-to-day basis. For example, some of my Linux-based classes have done the most good for me at IPconfigure.  this is because when anything goes wrong on the servers I have to use Linux commands and go through Linux file systems to see if anything is wrong and to see if I can fix it. this means that I need to know what looks right in a file system and what could be wrong so you have to have decent knowledge of the Linux file system and Linux command line. These classes also talk about steps on how to troubleshoot certain problems, and a few of these problems have popped up at work. While it may have taken me a few minutes to remember exactly what to do, I was able to recall the class and the work I had done to help navigate to the solution. Having previous knowledge also helped me be more confident when tackling big troubleshooting problems, which led to my managers and higher-ups within the company to put more trust in me, and gave me a little bit more autonomy when I work. 

Some areas where Old Dominion University did not fully prepare me were the hands-on IT skills that are often needed in real-world jobs. This is understandable because my major is cybersecurity, and the classes in that program focus more on software, security concepts, finding and fixing vulnerabilities, and understanding how attacks work. Most of what we learn is theory-based or focused on using security tools, not physically working with hardware. Because of that, there was not much training on things like installing components, building systems, or troubleshooting hardware issues, which are skills I use every day at my internship.

Even though this focus makes sense for a cybersecurity degree, many students, including myself, learn very quickly that most people do not get hired directly into cybersecurity roles right out of college. Employers want experience, and the easiest way to gain that experience is by starting in hands-on IT jobs, networking positions, or entry-level help desk roles. These jobs expect you to know basic hardware skills, how to fix simple computer problems, how to work with switches, and how to understand the physical side of technology. This means students often end up learning these skills on the job instead of learning them in school.

Because of this reality, I think ODU could make the cybersecurity program even stronger by including more IT-related classes or requirements. For example, the program could require at least one class that teaches students how to assemble a computer from the ground up, how to install and replace hardware parts, and how to troubleshoot problems like faulty RAM, CPU issues, or motherboard errors. Another useful class would teach basic networking with hands-on labs, where students practice cabling, setting up switches, identifying ports, and learning how physical network layouts work in real environments. 

These additions would not have to become a major part of the degree, but they would make the transition into the workforce much smoother. Many students do not realise that cybersecurity jobs usually come later in a career, and that the first step is almost always an IT or networking role. If the cybersecurity program included more hands-on IT training, students would feel more prepared and confident when they enter their first job. It would also help them understand how hardware, networking, and troubleshooting all connect to cybersecurity, making them stronger candidates in both fields.

Since I have been working at IPconfigure for a while now, I feel like I’m able to evaluate the internship outcomes that I set when I first started working there. First, I definitely did gain a deeper understanding of IT, cybersecurity, and networking as a whole. The Internship gave me amazing hands-on experience and really good managers to make sure that I was actually learning what I was doing and not just repeating a task over and over. With all the different things that have broken over time and new and unexpected servers to build and operating systems to figure out, it has definitely tested my problem-solving skills. Not only has it just tested my problem-solving skills, but it has also improved it as well. Having to deal with new problems that arise with the same Hardware or just new hardware in general has really made me have to think and solve problems faster and more efficiently than I ever have. With this, it definitely boosts my confidence when new tasks arise. I now have the confidence to complete the task and figure out how to do it in the best way by myself. Lastly, I’ve gained many connections while working at IPconfigure. Not only were they work connections, but they are also human connections, and I’ve gained many friendships through being there. I see these connections as an investment in my future, knowing that later on I have people that I know and I’m friends with who could help me land a future job or be a good reference to future employers. Looking at this, I would say all the outcomes that I wanted to gain from this internship, I have definitely gained, with more to add on. 

Some of the most motivating and exciting aspects of the job are things like working at a professional IT company, confidence in a path for future career at the company, confidence in the material I’m learning, doing work that matters and contributes to the company and a big way, and hands-on work that is technical. IPconfigure is a big tech company. There are some cool things that come along with working at it big tech company. Some of these things I previously mentioned, like the amenities, including things like the ping pong table, the game station, and the upstairs room with arcade cabinets and workout equipment. You just don’t find things like this at a regular job, and if you did, most jobs do not have the downtime to use them at all. At IPconfigure, you definitely work the majority of the workday, but you still have time to use these amenities and actually make them worth the space that they take up.

Having things to do around the office can liven up the work area, which can make work feel more relaxed and less stressful. It is also confidence-inspiring to be able to get an internship at such a professional IT company. Being in that environment can really get you in the headspace and mentality to work at a company with the same environment at a higher level. Secondly, being able to get an internship in college and it be a pretty in-depth job in the IT field does bring you confidence in your future growth within this industry.

Building connections at the company and being able to pick up the material quickly, and being a good employee, brings confidence and the possibility of moving up in the company, and not having to leave to get a better job. Lastly, it is very exciting and motivating to be learning real-world material on how to troubleshoot servers, how to do basic networking, and work with hardware. This also brings confidence in the future because knowing how to do all this stuff is great for your resume and can help land bigger jobs after college. All these combined can make anyone excited for their future in the IT  field after having the experience and knowledge an internship at IPconfigure can give you.

There’s only been one notable discouraging aspect of working at IPconfigure. However, this can be linked to all fields within Tech. For a span of five months, there was no work to be done; only one or two assemblers would come in two times a week for three hours a day. This was definitely a huge shift from the amount of work that we had had at the beginning of the internship and throughout the middle of the internship. This was a hard time for all the assemblers because we had no work, and being away from work for that long was only doing damage to what we could be learning while we were at work. While this was not ideal, it was still a lesson to be learned. It taught all of us that slow days can come and that work may not always be there. And times like this at other companies, many people could be fired and end up having to look for a new job and hoping to find one with similar benefits, pay, and quality of life. This can be hard for many, and it is a big pill to swallow, because this is a common occurrence within the IT field. However, everyone in assembly was lucky not to be fired; we still had a job whenever work came back. In the last few months, it has recently come back, and all these numbers have been able to work a consistent schedule, which has made everything feel back to normal. However, because we missed five months of work straight, there was a bit of a learning curve to get back into the flow of things. We had to be reminded multiple times of how things go together. And we had to reteach each other on many steps that we may have missed. However, even with this huge setback, the Internship still continues to be a positive environment and a place to still learn and gain more skills within IT.

Some of the most challenging aspects of the job were things like being assigned tasks that I had not done before, having to figure out how to do those tasks independently, and balancing asking for help and trying to solve problems myself. Throughout my whole time working at ipconfigure, while not consistent, there were many times when I had to tackle new servers or new challenges that I had not faced before.

When it came to building new servers, it was basically just me trying to connect old servers that I had built before to a new one and see if I could make any connections between the two to help me successfully install all the hardware correctly and wire the server correctly. Having to figure out these tasks independently was hard, but I was given more than enough time to be able to think, research, and ask questions so I could complete the server and a timely manner. 

While having to figure out how to build these new servers was mostly up to me. I could also ask my manager for help whenever  I needed it. I tried to balance asking questions and completing things myself adequately. But most of the time, I would end up working on the server for a while, then I would ask my manager for help, and then we would both end up brainstorming and figuring out how to complete the server together. This was not so much because I needed the help to complete the server, but it was more that my manager, Mark, loved helping on the hardware side, and when you would ask one question, he would come in there and stay until the server was built.

Other challenging tasks would be things like troubleshooting when my server does not work. Since I’m relatively new to the company, when something goes wrong, I do not know exactly what it is most of the time. If it comes down to troubleshooting, I normally have to research and or recall back to my classes to know what to look for and how to get to it. Most of the time, when it comes to troubleshooting on the software side, I do not need to ask as many questions because Linux is a widely used system and there are a lot of Articles and forms to help troubleshoot any basic problem. When it comes to completing these challenging tasks independently, I always try to come in with a fresh mind and tackle the tasks myself. I know that just with a little bit of work and research, many tasks can be solved easily.

However, I do not want to waste anyone’s time, and I don’t want to harm anything further than what it already is, so if it is a challenge that I’m not up to face, then that is where I ask for help. I believe asking for help and times like that is just as good as solving the problem by yourself, because when you ask for help, someone who knows how to fix it can then show you how to do it, and you can then repeat that perfectly next time anything like that happens. Whichever way you get the problem fixed, they both can build confidence for the next time anything happens, and they both can lead to a successful professional within the IT field.

Some general advice I would give for future interns at IPconfigure would be things like come in with basic Linux knowledge, and be comfortable with the command line and the navigation of file systems. Assemblers will have to deal with the Linux operating system on a daily basis. The managers will expect you to be able to complete many tasks within Linux by yourself, because if you ask too many questions, then it takes time away from their work that they need to get done.

Another thing would be to be prepared to learn hands-on Hardware skills. In assembly, the work is very hands-on; the bulk of the job is building servers and moving them on and off server racks. You definitely don’t want to be clumsy, and you want to have some prior knowledge of computer hardware before you jump into the job. Building servers can be very delicate work; being clumsy can lead to broken hardware, which then can get you fired pretty quickly.

While you do not want to ask too many questions, management definitely likes it when you do ask questions and look eager to learn and do things the right way. They also respect honesty. Breaking a piece of hardware is just a part of the job; while it should not happen often at all, it does happen, so being honest when hardware is broken is something the management looks for when analysing an employee.

Also, you’ll need to be able to pay attention closely to small details when you are learning how to assemble servers. Being able to build a server after watching one be built only a few times is something you will need to be able to do.  and assembler can build upwards of 50 servers a day, and ipconfigure needs all the assemblers to be able to meet numbers like that. So, not having to have someone check over your work consistently and having to look at other people’s servers while you are building is something you will need to be able to get over quickly.

Lastly, something all employers look for is being able to show up on time and communicate clearly with supervisors and team members. This is a big part of being successful at IPconfigure,  while they are very relaxed and you will not get fired if you show up late a couple of times, communication is the real key, as long as you communicate your timeliness to a manager, then you will be fine. 

Having this internship has definitely motivated me for my future classes and any other coursework I will have at Old Dominion University. With one semester left, I plan to take everything I learned at IPconfigure and apply it in the classroom, whether it’s helping me understand assignments better or contributing more during discussions with my classmates. I now feel like I have real experience to bring to the table, and that makes me more confident when talking about IT topics or answering questions from my peers.

Working at IPconfigure has also changed the way I think about my career. Before this internship, I thought I would only want to work in cybersecurity. But being exposed to the physical side of IT, especially networking and hardware, has actually made me enjoy that type of work more. Because of that, I’ve decided to take more IT-based classes during my last semester so I can get stronger in those areas. This experience has pushed me toward wanting a networking or IT operations job instead of jumping straight into cybersecurity right away. Even though my degree will be in cybersecurity, the skills I’m learning, the hands-on experience I’ve gained, and the certifications I plan to earn will all help me find a good networking job in the future.

This internship has also changed the way I learn. Before, I struggled when I had to learn something by just reading a book, slides, or long notes. But after getting hands-on experience every day—building servers, fixing problems, and actually touching the equipment—I learn things much faster and remember them better. Doing the real work helped everything finally “click,” and now I feel way more confident when completing assignments or tackling new material. This makes me more excited about my last semester, because I know I can handle whatever coursework comes my way now that I have real experience backing it up.

In conclusion, this internship has taught me a lot about IT, hardware, and what a real workplace environment is actually like. It took everything I learned at Old Dominion, especially from my Linux courses, and gave me a chance to use those things in real life instead of just in a classroom. At IPconfigure, I had to use many of the Linux commands I learned in my classes, and I had to rely on my understanding of the Linux file system to troubleshoot problems on different servers. This showed me how important it is to really know the basics, because when something breaks, the basics are what help you fix it.

The internship also showed me how important cybersecurity is, even when you are not working in a full cybersecurity job. Before this, I mostly understood cybersecurity in theory, but actually using it at work helped me understand why you have to keep your accounts safe, follow password rules, and be careful with any information you have access to. Even simple things like logging out, avoiding suspicious emails, and protecting credentials matter a lot more when you see how much trust a company gives you.

IPconfigure has probably taught me more about hardware and networking than any class I have ever taken. I learned how to build servers from the ground up, installing CPUs, RAM, SSDs, power supplies, and all the other components. I learned how to wire everything correctly, how switches work, how to troubleshoot hardware failures, and how to put all the pieces together so the server actually functions. Getting this hands-on experience made everything easier to understand, especially compared to when I was only reading about these things in a textbook.

Another major thing I learned was what a professional work environment is supposed to feel like. Before this, I didn’t know what to expect from a real IT company. IPconfigure showed me that a workplace can be relaxed and friendly while still running smoothly and getting work done at a high level. It taught me how important communication is, whether you’re talking to coworkers, supervisors, or people in different departments. It also taught me what it means to take responsibility for your work and how much it matters to stay honest, reliable, and willing to learn.

Overall, this internship helped me grow both professionally and personally. I gained hands-on skills, problem-solving experience, confidence in my abilities, and a better understanding of what kind of career path I want to follow. All of these lessons will help me as I finish my degree at Old Dominion and move into the IT field after graduation. Looking back, I’m very grateful that I had the chance to intern at IPconfigure because it has prepared me for my future better than I could have ever thought I would be.

Table of Contents:

1. Introduction

1.1 Why I Chose My Internship

1.2 Learning Outcomes and Objectives

1.3 Overview of IPConfigure (Company Background)

1.4 Orientation, First Days, and Initial Impressions

2. Management Environment

2.1 Supervisor (Mark G.) and Management Style

2.2 Communication, Support, and Daily Check-Ins

2.3 Overall Management Structure and Hierarchy

3. Major Work Duties and Responsibilities

3.1 Daily Tasks in the Assembly Room

3.2 Full Dollar Tree Server-Building Process

• Component Preparation
• Motherboard Assembly
• Chassis Installation and Wiring

3.3 Racking, BIOS Imaging, and Software Installation

3.4 Stickering, Boxing, Packaging, and Palleting

3.5 One-Off Server Builds and Problem-Solving

3.6 Importance of These Duties to the Business

4. Use of Cybersecurity Knowledge

4.1 Limited Direct Cybersecurity Tasks

4.2 Security Awareness and Safe Practices

4.3 Using Linux Skills for Troubleshooting

4.4 How This Experience Builds Toward Future Cybersecurity Roles

5. How ODU Prepared Me (and What It Didn’t Prepare Me For)

5.1 Skills Learned from ODU Courses

5.2 Linux, Networking, and Troubleshooting Knowledge in Practice

5.3 Gaps in Hands-On IT Training

5.4 Suggestions for Improving the Cybersecurity Program

6. Evaluation of Internship Outcomes

6.1 Gaining a Deeper Understanding of IT and Networking

6.2 Growth in Problem-Solving Skills

6.3 Building Professional and Personal Connections

7. Most Motivating and Exciting Aspects of the Internship
8. Most Discouraging Aspect of the Internship
9. Most Challenging Aspects of the Internship
10. Recommendations for Future Interns
11. Impact on the Remainder of My Time at ODU

12. Conclusion

12.1 Overall Takeaways

12.2 How the Internship Influenced My Future Career Path

12.3 Final Reflection on the Internship Experience