Today we had an overview about Voice Over Internet Protocol (VOIP). This is a fascinating subject and complicated subject. However, a technician will encounter VOIP phones regularly and having an understanding of the basic concept of how it works is truly relevant. I am impressed by the innovative solution Alex came off with in addressing the need of a student to have an analog phone work on the VOIP server. In all honesty, I haven’t worked with VOIP at all and listening to Alex explain the subject in a application case is truly helpful.
We also did a lab assignment about how to provision a VOIP phone. Although we ran out of time to finish I am sure that we will be able to tomorrow.
Today we learned the STAR method of responding to behavioral-based interview questions by segmenting the response as a situation, task, action and result. The assignment is to pick 3 questions from a list of interview questions and apply the star method in the response.
We also practiced behavioral interview questions with a partner and reversing roles as interviewer and interviewee. Practice does make it a little easier and less stressful.
We continued where we left off with the assignment yesterday. After we imaged the computer we had to rename it and join the domain for CTP which is EVO. It is recommended that renaming the PC and joining the domain be done separately to avoid any Windows quirks. Renaming the computer can be done by right clicking the Windows logo then clicking System, renaming the computer. The computer restarts with the new name applied. Joining a domain is done similarly with a changing from a work group to domain which in this case evo.ctp.lan. One can also search the domain in the search bar. A pop-up will ask for the credentials in order to join the domain. Then the computer will restart and at that point one can login as ‘other user’ and login using his class credentials.
Next we performed a imaging using an image of Windows 2010 with Office 2016. This was done with essentially the same procedure as the first imaging we did. However, we discovered that this image was not syspreped and was not giving the Windows OOBE we wanted. So we had to perform a sysprep on the machine to have the OOBE. This can be done in three ways – use the run command to run sysprep, locate sysprep via Graphical User Interface (GUI) and double click the .exe file and execute syprep using cmd. This restarts the computer which runs the OOBE process including the creation of the local admin. Logging in as the local admin allows us to change the computer name and join the domain. After the two consecutive restarts we can log in as ‘other user’ with class credentials with the new image of the computer now with Office 2016.
Today we learned all about how to image a computer. I remember a couple of times I had to image my computer because the hard disk on my computer was failing. However, I don’t often use imaging on a regular basis. However, as a technician one is expected to know how to create an image and image computers especially in an enterprise setting.
Our lab assignment for today was to image a computer using an image located in a network storage. We used the Acronis True Image software to recover the image to one of the vacant classroom computers. Our first try was not successful due to the size of the network image we were using and probably because we were accessing the resource at almost the same time. Anyway, we learned a lot and were able to install a new Out of the Box Experience (OOBE) of Windows on the target machine. Tomorrow we will continue with the final set-up the computer.
Today we had our first quiz. Thankfully, Alex gave us a review of what he discussed last week in preparation for the quiz. He also explained the difference between BIOS and UEFI. That review refreshed a lot of memories . 🙂
Finally, our group checked/changed the BIOS settings of the primary boot device to be hard disk in the Scott, Neil and Laboratory computers.
Another interesting day for the CTT class. We learned all about what happens when you push the power switch on the computer. There are 4 initial steps the computer goes through when push the switch. First it goes to POST (Power On Self Test) where the computer checks if it has the minimum requirements to start. It it doesn’t it generates an audible signal which are called POST codes indicating what the problem is. Second it loads the firmware commonly called BIOS, UEFI or CMOS and uses the configuration files to look for the device to boot from. This is set through the boot order sequence in the BIOS setup. Finally, it loads the OS(Operating System) in the boot device chosen which is normally the hardisk.
I looked BIOS settings of the class computers, lab computers and a Lenovo T430 and determined what key to push to get to the BIOS setup utility. The class computers which are Lenovo Think Centre M Series you push Enter or F12. The lab computer which is an HP Compaq dx7500 you push F10. The Lenovo T430 has a button on the top left part of the keyboard to get into BIOS.
I worked on the HP which was a working computer with a hardisk but no operating system. I opened up the computer and took out the pair of memory modules. When I turned it on the post code error was a short beep followed by a long beep. So according to the HP site that code is a memory problem. The other post errors are enumerated below.
Have I Been Pwned, the breach notification service that serves as a bellwether for the security of login credentials, has just gotten its hands on its biggest data haul ever—a list that includes almost 773 million unique email addresses and 21 million unique passwords that were used to log in to third-party sites.
This was a cool day. We went on a ‘field trip’ although just within the Ed Roberts Campus. Alex toured us to the Minimum Point of Entry (MPOE), Main Distribution Frame (MDF) and the Intermediate Distribution Frame (IDF) that serves the networks of the different organizations located in the campus. It was really quite an impressive site to see the work and effort put in making all these connections work. I was in awe at the complexity of the wiring/cabling and the different devices which are working in the background. Everybody had a grand time listening to Alex explaining how work and just taking pictures.
This day was also really informative when Alex gave as a brief glimpse of networking and IP protocol concepts. Identifying how many IPs belong to a network is confusing for anybody who tries it for the first time. However, it gets clearer with time. The key is looking at the network identifier.
Lastly, we looked at the BIOS settings of a computer and learned to change the boot order.
