Introduction
Method
Writeup of the lab
The object of today's laboratory work is to
install
Windows Server 2008 onto a PC and configure then test its server
capabilities.
You will be installing this operating system in a virtual
machine (VM) which will allow greater flexibility for the
labwork.
You will be given a set of instructions to login to the VM
environment then you must follow the instructions in
this set of notes.
Follow the instructions below and use a pen and
paper to
keep a record of your responses to the questions.
This work will be assessed informally during the
lab
period and formally at the end of the course.
2. Setup the FTP server to
point at your server. Create an account and a password for the
new user
that you created in part 2 above. Isolate the users and do not
allow
anonymous connections. Make sure that the user has read and
write
permissions. Add the username and password to the whiteboard.
3. Setup Wireshark on your machine. You can download
the
ISO for Wireshark from the VSphere server. Install
Wireshark and make sure that it
is working by sniffing the network for a few seconds.
4. Now you should test the servers on onther group's
machines. You should use a web browser to test the webserver on
another
machine, FTP can be accessed via the command prompt.
5. DNS server. This work is optional but if you have time you must attempt this. Please setup your DNS server and add the canonical name of another group's PC and bind it to their IP address. IP Addresses and names are on the whiteboard. DNS can be tested by using canonical names rather than IP addresses. Be sure to capture the network traffic during your tests with Wireshark.
Keep a record of this work in your log book. Show it to your lab demonstrator before you leave. You will need to submit this work for marking.
In the Workgroup or Domain window enter the name of your workgroup or domain.
A workgroup is a small group of computers on a network that enables users to work together and does not support centralized administration.
A domain is a logical grouping of computers on a network that has a central security database for storing security information. Centralized security and administration are important for computers in a domain because they enable an administrator to easily manage computers that are geographically distant from each other. A domain is administered as a unit with common rules and procedures. Each domain has a unique name, and each computer within a domain has a unique name.
If you're a stand-alone computer, or if you don't know what to enter, or if you don't have the sufficient rights to join a domain - leave the default entry selected and press Next.
The setup process begins loading a blue-looking text screen (not GUI). In that phase you will be asked to accept the EULA and choose a partition on which to install 2003, and if that partition is new, you'll be asked to format it by using either FAT, FAT32 or NTFS.
Start the computer from the CD.
You can press F6 if you need to install additional SCSI adapters or other mass-storage devices. If you do you will be asked to supply a floppy disk with the drivers and you CANNOT browse it (or a CD for that matter). Make sure you have one handy.
If you want, you can press F2 to run the ASR sequence. For that you need a good backup created by the Windows Server 2003 backup program, and the ASR floppy disk. If you plan to install a new copy of 2003 - don't do anything.
Setup will load all the needed files and drivers.
Select To Setup Windows Server 2003 Now. If you want, and if you have a previous installation of the OS, you can try to fix it by pressing R. If not, just press ENTER.
Read and accept the licensing agreement and press F8 if you accept it.
Select or create the partition on which you will install Windows Server 2003. Depending upon your existing disk configuration choose one of the following:
If the hard disk is unpartitioned, you can create and size the partition on which you will install Windows Server 2003.
If the hard disk is already partitioned, but has enough unpartitioned disk space, you can create an additional partition in the unpartitioned space.
If the hard disk already has a partition that is large enough, you can install Windows Server 2003 on that partition. If the partition has an existing operating system, you will overwrite that operating system if you accept the default installation path. However, files other than the operating system files, such as program files and data files, will not be overwritten.
If the hard disk has an existing partition, you can delete it to create more unpartitioned space for the new partition. Deleting an existing partition erases all data on that partition.
If you select a new partition during Setup, create and size only the partition on which you will install Windows Server 2003. After installation, use Disk Management to partition the remaining space on the hard disk.
Select a file system for the installation partition. After you create the partition on which you will install Windows Server 2003, you can use Setup to select the file system with which to format the partition. Windows Server 2003 supports the NTFS file system in addition to the file allocation table (FAT) and FAT32 file systems. Windows Server 2003, Windows XP Professional, Windows 2000, and Windows NT are the only Microsoft operating systems that you can use to gain access to data on a local hard disk that is formatted with NTFS. If you plan to gain access to files that are on a local Windows Server 2003 partition with the Microsoft Windows 95 or Windows 98 operating systems, you should format the partition with a FAT or FAT32 file system. We will use NTFS.
Setup will then begin copying necessary files from the installation point (CD, local I386 or network share).
Note: If you began the installation process from an MS-DOS floppy, make sure you have and run SMARTDRV from the floppy, otherwise the copying process will probably last more than an hour, perhaps even more. With SMARTDRV (or if setup was run by booting from CD) the copying will probably last a few minutes, no more than 5 max.
The computer will restart in graphical mode, and the installation will continue.
The setup process reboots and loads a GUI mode phase.
It will then begin to load device drivers based upon what it finds on your computer. You don't need to do anything at this stage.
Click Customize to change regional settings, if necessary.
Current System Locale - Affects how programs display dates, times, currency, and numbers. Choose the locale that matches your location, for example, French (Canada).
Current Keyboard Layout - Accommodates the special characters and symbols used in different languages. Your keyboard layout determines which characters appear when you press keys on the keyboard.
If you don't need to make any changes just press Next.
If you do need to make changes press Customize and add your System Locale etc.
Type your name and organization.
Type the product key.
Enter the appropriate license type and number of purchased licenses.
Type the computer name and a password for the local Administrator account. The local Administrator account resides in the SAM of the computer, not in Active Directory. If you will be installing in a domain, you need either a pre-assigned computer name for which a domain account has been created, or the right to create a computer account within the domain.
If you enter a password that is blank or does not match the required complexity settings you will get a warning message.
Select the date, time, and time zone settings.
Setup will now install the networking components.
After a few seconds you will receive the Networking Settings window. BTW, if you have a NIC that is not in the HCL (see the What's the HCL? page) and Windows Server 2003 cannot detect it, or if you don't have a NIC at all, setup will skip this step and you will immediately go to the final phase of the setup process.
Press Next to accept the Typical settings option if you have one of the following situations:
You have a functional DHCP on your network.
You have a computer running Internet Connection Sharing (ICS).
You're in a workgroup environment and do not plan to have any other servers or Active Directory at all, and all other workgroup members are configured in the same manner.
Otherwise select Custom Settings and press Next to customize your network settings.
Highlight the TCP/IP selection and press Properties.
In the General tab enter the required information. You must specify the IP address of the computer, and if you don't know what the Subnet Mask entry should be - you can simply place your mouse pointer over the empty area in the Subnet Mask box and click it. The OS will automatically select the value it thinks is good for the IP address you provided.
If you don't know what these values mean, or if you don't know what to write in them, press cancel and select the Typical Settings option. You can easily change these values later.
In the Workgroup or Domain window enter the name of your workgroup or domain.
A workgroup is a small group of computers on a network that enables users to work together and does not support centralized administration.
A domain is a logical grouping of computers on a network that has a central security database for storing security information. Centralized security and administration are important for computers in a domain because they enable an administrator to easily manage computers that are geographically distant from each other. A domain is administered as a unit with common rules and procedures. Each domain has a unique name, and each computer within a domain has a unique name.
If you're a stand-alone computer, or if you don't know what to enter, or if you don't have the sufficient rights to join a domain - leave the default entry selected and press Next.
If you want to join a domain (NT 4.0 domain of W2K/2003 Active Directory domain) enter the domain's name in the "Yes, make this computer a member of the following domain" box.
To successfully join a domain you need the following:
The person performing the installation must have a user account in Active Directory. This account does not need to be the domain Administrator account.
and
The computer must have an existing computer account in the Active Directory database of the domain that the computer is joining, and the computer must be named exactly as its domain account is named.
or
The person performing the installation must have appropriate permission to create a domain account for the computer during installation.
Also, you need to have connectivity to the domain's domain controllers (only to the PDC if on an NT 4.0 domain) and a fully functional DNS server (only in AD domains). Read the Joining a Domain in Windows XP Pro and Requirements when Joining a Domain pages for more on this issue.
Enter the Active Directory domain name (in the form of xxx.yyy, for example: DPETRI.NET) or the NetBIOS name of the NT 4.0 domain (in the form of xxx, for example: DPETRI). Press Next.
Note: If you provide a wrong domain name or do not have the correct connectivity to the domain's DNS server you will get an error message.
A username/password window will appear. Enter the name and password of the domain's administrator (or your own if you're the administrator on the target domain).
Note: Providing a wrong username or password will cause this phase to fail.
Next the setup process will finish copying files and configuring the setup. You do not need to do anything.
After the copying and configuring phase is finished, if Windows Server 2003 finds that you have a badly configured screen resolution it will advise you to change it and ask you if you see the new settings right.
BTW, the minimum supported screen resolution in 2003 is 800X600.
Setup finishes and boots Windows Server 2003.
That's it! you're done!
©
MMClements
Last updated : 07/12/2009 13:21
