Saturday, July 16, 2011
Day 10 Ed 5769
Thursday, July 14, 2011
Day 9 Blog Post
Wednesday, July 13, 2011
Day 8 Blog Post
Today’s assignment consisted of installing and configuring print services on our Windows 2008 server and our Windows work station. The printer we were installing was the Xerox Phaser 4510. Lyle explained the procedure at the beginning of the class.
The first thing to do was to locate the correct printer driver on the internet. We used google to do a search. The search returned many possibilities and we had to be careful to select the right driver. The driver we were looking for was the Xerox postscript driver which is located at this link.
Once we had downloaded the driver we went to server manager and installed print management. We had to use print management to install the driver in order to set up print services on our server. This was the first step in being able to print.
Next we opened print management and created a standard TCP/IP port. The IP address of our printer was 192.168.24.51. This is a static IP address that is assigned to the printer.
Next we clicked on ``have disk`` this is where we installed the driver we had just finished downloading.
Once this was complete we were able to print a test page from our server. Next it was time to push the policy out to our workstations. This was accomplished from server manager. We had to go to users and computers, then domain controllers. We were able to apply the policy to our workstations.
Finally, after rebooting the workstation we were able to print from our workstation. Although this procedure worked for us I think it is worth noting that the work we are doing is difficult to document because of the nature of the work. Unexpected problems arise and how you deal with those problems will affect the process.
The rest of the morning was spent touring Blackbridge Data Center. This was an interesting tour even though it was a bit complex. I understand the concept of data storage. Companies who have data to store will take advantage of the Blackbridge`s services. Blackbridge guarantees that their data is safe and secure. Blackbridge uses a variety of processes and equipment to accomplish this task. It is mind boggling when one considers the electricity, wires, cooling system, physical building and security.
Tuesday, July 12, 2011
Day 7 Ed 5769
Today we started out with an explanation of logon scripts by Lyle. Logon scripts are commands that are executed when endusers log on to a machine on the network. The logon scripts determine what programs, services, desktop icons, etc that the user has access to. For example a student might be limited as to what programs he or she can access or what their desktop will look like.
Before we could get started with today’s work we had to finish up yesterday’s exercises which consisted of remotely turning off one of our workstations and hiding the desktop. We were able to get this done by downloading a free program called specopsgpudate. Once we had the program installed it was a simple matter to go into administrative tools on the Windows 2008 Server, look up the program under group policies and then run the command to turn off the desktop from the server. It is cool that a network administrator can remotely control any machine on the network from a remote location.
Once we had completed yesterday’s tasks we were able to begin working on our login scripts. We used a utility called NETLOGON which allowed us to set up the login script. As usual, we did run into some glitches along the way. It seems our folder list was not replicating across the survey. We could not see all the folders on the main server. We conducted several tests that showed that everything was working properly. It was thanks to Sean who had a look at our configuration and noticed that our server was attempting to replicate from Rocky and Gail’s server. We fixed that problem, rebooted our machines and it was clear sailing after that.
I found the information at this link to be particularly useful.
http://www.petri.co.il/setting-up-logon-script-through-active-directory-users-computers-windows-server-2008.htm
Monday, July 11, 2011
Day 6 Active Directory
Day 6 Blog Post – Installing Active Directory
Today’s task involved installing and configuring active directory on our server and then joining our Windows 7 workstations to our domain.
As this was new to me I found it useful to research a bit of background into active directory. What is it? What function does it perform? Why is it necessary were all burning questions. As I read through various links this short explanation from Wikipedia proved to be very helpful in building my understanding of active directory.
“An Active Directory structure is a hierarchical arrangement of information about objects. The objects fall into two broad categories: resources (e.g., printers) and security principals (user or computer accounts and groups). Security principals are assigned unique security identifiers (SIDs).

After reading up a bit on active directory last night I was ready for Lyle’s explanation and I had no trouble understanding him. His explanation of the “root of the forest” and “trees” in the forest helped me to understand the analogy. The head of the network is the root and all of our networks are trees in the forest. Forest is a synonym for network.
Installing active directory was a pretty straightforward process composed of two main parts. Installing and configuring the software on our Windows 2008 server then joining our Windows 7 workstations to the domain. The latter half of the procedure would prove to be the most challenging.
Once we executed the commands to bring up the active directory wizard we went through the prompts and successfully completed the installation. Afterward it was time to join our workstations to the domain.
I found this video to be particularly helpful in joining our workstations to the domain.
We ran into problems because our machines were unable to find the domain. We tried various things to rectify the problem such as refreshing our DHCP settings on the server, rebooting, checking for updates, ipconfig in the command prompt, pinging our machines, etc all to no avail. Finally, we enlisted the help of classmates and Lyle and we were able to make a connection at the end of the class. We continued to work on creating our objects and user accounts and I am looking forward to completing the task tomorrow.
Saturday, July 9, 2011
Ed 5769 - Day 5
Today started off more or less like the others. The work scheduled for today was the installation of Windows 7 Enterprise on our 2 workstations. Before we began this task we searched for documentation that would help us to accomplish this task. I found this somewhat frustrating because it felt like I was going in circles. I tried different search terms and kept getting returns that I did not feel were useful. Things like blog posts and forum threads but not a lot that looked like technical manuals. For example PDF files with easily recognizable titles. I finally settled on the Microsoft site and I was able to locate some resources.
In the meantime my partner had inserted the Windows 7 Cds and was going through the preliminary installation process. Once that was complete we installed 23 updates then had to located device drivers for our Dell Optiplex 755. These were found on the Dell website, downloaded and installed. A reboot completed the process.
Finally, one last check for updates revealed that there were 5 “important” updates to be installed. We installed those and I could not help but notice that it seemed to take a long time.
The final step is to copy files from our workstations to our file server and vice versa. In order to do this we had to bring up a cmd prompt and enable the administrator accounts. Once this was done I was able to browse to our shared folder and placed a folder in there called “I created this folder on July 8 as a test.” We were able to locate this folder on the shared folder from the other workstation so we are confident the process was completed.
Friday, July 8, 2011
Day 4 Blog Post
We started out the day by running updates on our Windows Server 2008. This took some time and several reboots. While this process was occurring Lyle talked about fixing the router. Afterward we went through telnet to perform checks on our system. We were able to ascertain that our network was functioning correctly because we had 4 lines in the test results. The screenshot below shows the routes that the incoming traffic will take. Routing tables instruct the router where to send incoming packets.

This routing table shows the IP routes for our network as seen in the webview of our alcatel switch.
Some general advice on using the GUI (graphical user interface) The GUI is a way to “see” the switch. Humans like using GUI because we are visual creatures who mostly process sensory information through our eyes.
• Using webview you can see in a graphical manner what is going on.
• It is faster to use the cmd prompt than the graphical. Use the web view to check if everything is correct.
• Try to avoid the cmd prompt.
• Tabs on the side of webview show you the commands.
• How we route our traffic.
• If you have multiple net connected to our network, if we have another connection it goes out somewhere else. Set up a routing table on the switch.
Once we had verified that all of our network connections were working it was time to move on to DNS, File services and DHCP. We set up a shared folder on our file server then checked to see if it was accessible. Lyle talked about the importance of properly setting the permission correctly.
Start off with DNS, then do file services, THEN do DHCP. Must do this one step at a time. DHCP allows any machine to connect to the switch.
Internet explorer enhanced security services should be shut off because otherwise it blocks information that prevents us from doing our DNS, File services and DHCP.
Network 5769.local is our parent name.
WINS: Windows Internet Names Service
DHCP Installation
1. Create the scope. The scope is the range of IP addresses. We had to get this info off our diagrams.
2. Default gateway is our switch’s IP 192.168.13.254 (Gateway and router are the same thing)
We plugged my laptop into the switch and it worked. YAHOO!!
We used knoppix to see if we could use the internet on our workstations. Knoppix is a portable operating system which runs off a CD. It is used on a machine that has no operating system installed etc.
We had to perform this test to see if our DNS was configured properly and to see if our Windows Server works with other operating systems.
From Konqueror in Knoppix I went to Go>SambaShares>Password prompt
Drivers are in Sean’s shared folder #25.50
I was able to get into Sean’s folder and install the drivers on our file server. Updates continued through the afternoon.