ed 5769- day 5 July 7

Day 5 Blog July 7
We had a couple housekeeping items to work on before we got to Windows 7 installation on the 2 workstations.
On the windows server 2008 device
1)Server 2008 activation using the MAK protocols ,
MAK - multiple activation key authenticates to the internet once.

Start /right click on computer/properties/windows activation change product key
We then entered the server 2008 product key Lyle gave us, and this registered our machine and we would not loose the installation of server 2008

2) Enable remote desktop services
Start/system properties/remote/select allow connect
On server, command prompt oobe was run.
3) Pointing server 2008 to the correct server in the room for integration with active directory need to have it pointing 192.168.181.50
DHCP services /server options/ general add this dns 192.168.181.50.
This becomes the second DNS address in our protocol ( the first dns address is our local server 192.168.10.50, the second is the Lyles server 192.168.181.50) as well as 142.66.33.100and 142.66.33.101

Installing Windows 7 on the workstation.
This process was fairly straight forward using the Install DVD Lyle had given us. Using the F12 function on the bootup sequence, we booted off the DVD.
The windows DVD ran through its install. We selected English language
When asked what type of install, we choose custom
Installed it in the disc 0 partition, as there was enough room for the 15 GB install , then clicked apply
Then the installation started through the 5 processes 1) copying files, 2) Expanding files 3)Installing features 4) Installing updates 5) completing Installation. These 5 steps only took approximately 15 minutes and went through one restart.
After starting Windows for the first time a screen with user name came up we called it JS-blh00000 , JS stands for john sandie and blh 00000 was a label on the computer
The password screen came up and we gave the password admin5769. This was done for consistency , and benefits later on with active directory install. All the desktops in the class had this password.
I selected use recommended settings in the set up windows for updates
I set up the Mountain standard time, to correlate with the server, and the correct local time
For the computer current location –I selected work.
The computer went through a start up and the home screen came up again
I ran the command prompt- and Ip config . I got an address of 192.168.10.102, which is correct for a dhcp address from our server for a workstation
I opened a browser and the internet was connected.
Start/control panel/system and security/system. We saw the basic information on the computer. At the bottom of this screen was the Windows activation /change product key. This allowed us to put in the windows 7 MAK product key Lyle had provided us. Activation was successful after we put in the code.
We ran the start/all programs /windows update to run any updates. We had to do this 3 times as the computer needed to reboot after downloading and installing the updates. The final update check came with no updates, so we were good to go.
We checked start/control panel/system and security/system/device manager
There were2 items that needed drivers, which were 1) PCI Serial Port and 2) PCI Simple Communications Controller . These were the same drivers as the previous server 2008 install on the Dell Optiplex 755 machines. We went to the Dell support site and selected the Optiplex 755 unit and installed 3 drivers for the chipset even though they were for Vista 32 bit. There were no drivers for Windows 7 for this model of computer. These were executed on the workstations, and then on device manager the errors went away.
We were able to go to start/network and see the 2 workstations and the laptop .We were not able to see the server50 on the network. We were only able to share a file with the server by typing 192.168.10.50 in the dialogue box above the start menu. We had to use the admin 5769 pw and we had access to the shared file from the workstation to the server
We followed some instructions from Lyle to correct DHCP corrections on the server, but still have to find where the problem is on our server services settings with the file sharing.