Make your own free website on Tripod.com

Prototype Phase - Installation of Windows 2000 Advanced Server

Materials:
Working complete PC
Blank Diskette
Student Diskette, "New Boot A Ver 2.0+"
Student CD-ROM, "Room 6359"
Student CD-ROM, "Microsoft Windows 2000 Server OEM"
Objectives:
The student will become familiar with:
The Windows NT family installation process,
Preparation for installation,
Alternate methods of launching the installation,
Performing the full, clean installation.
Post-install procedures.
Competency:
The student will learn how to implement a typical prototype phase of the server project including pre-installation procedures, perform a full, clean installation of the Windows 2000 Server operating system, and post-installation procedures. The student will also learn how to launch the operating system setup from the Windows 2000 OEM installation media as well as from a DOS prompt including how to create the Windows 2000 Setup diskettes which can also start the installation process.
Windows 2000 Server Pre-Installation Procedures
  1. Before installing a Windows 2000 Server, the operation should follow the server project's Planning Phase in which the general requirements fro the server including the physical platform, physical server framework, operating system, and logical server framework requirements have already been evaluated, researched and chosen. This is assumed to be the case for this exercise. The planning phase includes research of the chosen hardware components of the server's physical platform and their compatibility with each other and the operating system in order to avoid configurational problems in the future which could render the installation useless to the point of having to reinstall all over again.

  2. The server prototype phase involves the construction of the server itself and includes the following steps:

Start the Server's Documentation
  1. It is useless to spend hours setting up the server only to discover that a critical hardware component, such as the RAID controller, was not configured properly. Going back and correcting a RAID controller configuration will almost certainly wipe out all data on the drives forcing the technician to have to start the installation all over again. On a blank sheet of paper write "Server Pre-Install Check List" at the top.

  2. For the Room 6359 Pentium 4 based systems the check list is:

  3. Prepare a notes sheet to record any pertinent information as well.

Pre-installation BIOS/Hardware Configuration
  1. The BIOS configuration pre-installation check list:

  2. Boot to the Room 6359 Student CD-ROM, as this is happening, verify that the voltages recorded in the BIOS Hardware monitor are all within 5% tolerance (check the CPU documentation concerning the VCORE value) and check the CPU and motherboard documentation to verify that the CPU and motherboard temperatures are also within acceptable tolerance.

  3. Change to the K: drive. Copy the file 3C90XCFG.EXE from the diskette provided by the instructor to the K: drive:

    K:\>copy b:\3c*.exe
      1 file(s) copied
    K:\>_
    
    
  4. Run the program by typing its name at the K: prompt "3c90xcfg" then press [Enter]. Press [Enter] within the 3COM NIC Configuration Utility to accept the open and highlighted menu choice to configure the NIC. Write down the Bus #, Dev/Slot #, Node address, I/O address and interrupt level (IRQ). Change to the Test menu and highlight "Run Tests" and press [Enter]. After the NIC has passed a few repetitions, press [Enter] to stop the tests.

  5. Enter the "Test Setup" screen. With "Group 1" highlighted on the left, disable the entire group. Then highlight Group 3 and enable the "Echo test" Attach a cross-over cable from the 3COM NIC to a neighbor's system's 3COM NIC. Highlight the choice "Echo Server" and press [Enter] In the Echo Server screen press [Enter] again to start the echo server. Your neighbor may now highlight "Run Tests" on the Test Menu and press [Enter]. After a few repetitions, have the neighbors PC stop the tests and also stop your system from being the echo server. Reverse their roles and run the test again, this time allow your neighbor's system to be the echo server and your NIC should run the tests. After a few repetitions, stop both functions and exit the utility.

  6. Run GHOST and insert the additional CD-ROM provided which holds a special GHOST restore image of a single relatively empty FAT32 partition. Ghost this image to the hard drive and then reboot to the hard drive.

  7. Insert the Room 6359 CD-ROM and change to the Q: drive. Change to the BIN directory and run scandisk on the C: drive with surface scan:

    C:\>Q:
    
    Q:\>cd bin
    
    Q:\BIN>scandisk c: /surface
    
    
  8. Once the surface scan is complete and reports no errors, execute the "zap" command from the Room 6359 CD-ROM. This will write zeros to the first 128 sectors of the hard drive effectively erasing all partition information. The "funny dot" character at the beginning of the command's name is created by 1) Be sure [Numlock] is on, 2) Press and hold the [Alt] key, 3) type [2], [5], [0] on the calculator pad, 4) Release the [Alt] key.

    Q:\BIN>ˇzap 0
    
    
  9. Run the HWIPE command from the diskette that you will be provided. HWIPE can overwrite the last 8MB of the hard drive with zeros effectively erasing all traces of dynamic drives which a Windows 2000 Server operating system can detect.

    Q:\BIN>a:
    
    A:\>hwipe12
    
    
  10. Once HWIPE is done, remove the Room 6359 CD and diskette. Reboot and insert the Microsoft OEM Windows 2000 Advanced Server installation CD-ROM.

Additional Notes on Server and Domain Names
  1. If the network is a new one then consider the ultimate ramifications of the names of the server and the domain. These names have a 15 character limit and cannot contain weird characters like: ><[]:;|=,+*"? These are legal but not recommended: ~!#$%^&(){} The best characters other than letters and numbers to include would be dashes or underscores. If the network has a naming convention use it. If the network does not have a naming convention then start one. As an example, ARCO Inc. is a startup company but the owner has expressed a strong desire and belief that his company will have branch offices across the U.S. within a few years. Even if his plans fall short it would not hurt to name servers by their city or region and function: "ARCO_MIA_EXCH01" being Arco Inc's first Miami based Microsoft Exchange Server or even "MIA_DC01" for the Miami office's first Domain Controller. Remember also that there are those professionals who advocate short names mainly due to the fact that the domain name and the server's names end up having to be typed into network pathnames more often than any other single names on the network so having to constantly start a UNC pathname with: "\\ARCO_MIA_EXCH001\..." can get irritating quickly whereas: "\\MARS\..." or "\\DC1\..." are less likely to cause carpel tunnel syndrome. These are fine as long as they are well documented as to their roles and they do not get duplicated by accident.

  2. The domain name is not directly tied to the Internet but it can end up so. Convince a new company to research and register a domain name with the Internet authorities even if they do not immediately plan to actually run a website using that domain name, just to have it set aside and available to use, if they do decide to run the website in the future. The cost of reserving a new available domain name is $70 every two years which is a pittance expence for a start up company. If arco.com is already taken try several variations like: arcoinc.com, arco.biz, arco.cc, etc until one is found available. Then contact the Internet authorities and reserve the domain name and pay the fee. At that point the domain can be named the same so if the domain name registered ended up being arcoinc.cc for example then the domain can be named arcoinc.cc also. This allows for a trouble-free and seamless addition of live Internet web services to the existing network. Otherwize remember that even if renaming a domain is possible, it has the potential for creating far too many headaches to be practical so choose the name of the domain well before beginning the installation.

Booting the System with the Windows 2000 Install CD-ROM
  1. The Microsoft OEM installation disc used is the "Windows 2000 Rollout" package which contains Windows 2000 Professional, Windows 2000 Server, and Windows 2000 Advanced Server. A small menu prompts for the letter of which operating system will be installed. Upon pressing the [Enter] key the full installation process begins...

The Text Portion of the Windows 2000 Server Setup

17. The Windows 2000 installation process begins with the Setup program making a preliminary investigation into the system hardware. This is the same for all versions and packages of Windows 2000 and the following is displayed on screen as this takes place:


Setup is inspecting your computer's hardware configuration...













18. After this the Windows 2000 "minikernel" loads and presents the following screen:


 Windows 2000 Setup














  Press F6 if you need to install a third party SCSI or RAID driver...         

19. The message at the bottom is displayed for a few seconds during which time the user can press the [F6] and will be allowed to insert a floppy disk with the drivers for any hard disk controllers that Windows 2000 cannot access normally during this phase of the installation process. In this case the ATA/IDE controllers are industry standard compatible and this action is not necessary.

After the message disappears the Windows 2000 "minikernel" loads all of its standard drivers and components and then proceeds to the next screen:


 Windows 2000 Server Setup


   Welcome to Setup.

   This portion of the Setup program prepares Microsoft(R)
   Windows 2000(TM) to run on your computer.

       To set up Windows 2000 now, press ENTER.

       To repair a Windows 2000 installation, press R.

       To quit Setup without installing Windows 2000, press F3.






  ENTER=Continue R=Repair F3=Quit                                              

20. This is the first screen that identifies which Windows 2000 package is being installed by the title in the upper corner. Since this is a new clean install and we have no need to quit setup yet, press [Enter] to proceed to the next screen:


 Windows 2000 Server Setup


   Setup has determined that your computer's startup hard disk is new
   or has been erased, or that your computer is running an operating
   system that is incompatible with Windows 2000.

   If the hard disk is new or has been erased, or if you want to discard
   its current contents, you can choose to continue Setup.

   If your computer is running an operating system that is incompatible
   with Windows 2000, continuing Setup may damage or destroy the existing
   operating system.

    To continue Setup, press C.
     Caution: Any data currently on your computer's startup hard disk
     will be lost.

    To quit Setup, press F3.





  C=Continue Setup  F3=Quit                                                    

21. This screen only appears if there is no partition table (our case), the partition table is corrupt (better to wipe it than leave it like that), or the partitions are unrecognized by Setup (Linux, OS/2, etc.)

Otherwise, this screen will not appear and the installation process will proceed directly to the next screen:


 Windows 2000 Licensing Agreement











  F8=I agree  ESC=I do not agree  PAGE DOWN=Next Page                          

22. The EULA is displayed in the above screen. It is a legal document and you must agree to it for the OS to proceed to install onto your system. It is recommended that all users of this software read it all the way through at least once in their lives just so you know what Microsoft is making you agree to (they could be demanding our first born!)

Press [F8] to proceed with the installation which takes the process to the next screen:


 Windows 2000 Server Setup


   The following list shows the existing partitions and
   unpartitioned space on this computer.

   Use the UP and DOWN ARROW keys to select an item in the list.

    To set up Windows 2000 o nthe selected item, press ENTER.

    To create a partition in the unpartitioned space, press C.

    To delete the selected partition, press D.

 38091 MB Disk 0 at Id 0 on bus 0 on atapi
        Unpartitioned space                    3091MB                









  ENTER=Install  C=Create Partition  F3=Quit                                   

23. There is no turning back later if the partitions are created incorrectly at this point. The system will be a Domain Controller which means it will have to use NTFS. Our drive is fairly small and it is not recommended to make a C: drive small but the C: drive will be completely isolated from users and another D: drive will be created for data and user access.

To do this the choice [C] has to be pressed here otherwise, Windows 2000 will take the entire drive as the C: drive automatically:


 Windows 2000 Server Setup


   You asked Setup to create a new partition on
   38091 MB Disk 0 at Id 0 on bus 0 on atapi.

        To create the new partition, enter a size below and
        press ENTER.

        To go back to the previous screen without creating
        the partition, press ESC.

   The minimum size for the new partition is      4 megabytes (MB).
   The maximum size for the new partition is   38087 megabytes (MB).
   Create partition of size (in MB):  7000 








  ENTER=Create  ESC=Cancel                                                     

24. With the cursor behind the displayed hard drive size, backspace over it and then type in the desired size; here we will use 7000. Then press [Enter] which will take you back to the previous screen:


 Windows 2000 Server Setup


   The following list shows the existing partitions and
   unpartitioned space on this computer.

   Use the UP and DOWN ARROW keys to select an item in the list.
     To set up Windows 2000 on the selected item, press ENTER.

     To create a partition in the unpartitioned space, press C.

    To delete the selected partition, press D.

 38091 MB Disk 0 at Id 0 on bus 0 on atapi
     C:  New (Unformatted)                    7000MB                
         Unpartitioned space                  31091MB







  ENTER=Install  D=Delete Partition  F3=Quit                                   

25. The new partition is highlighted so we can press [Enter] to proceed to install Windows 2000 Server on this partition. This takes us to the following screen which only appears if the partition has just been created (if it was an existing partition the following screen would be skipped):


 Windows 2000 Server Setup


   The partition you selected is not formatted. Setup will now
   format the partition.

   Use the UP and DOWN ARROW keys to select the file system
   you want, and then press ENTER.

   If you want to select a different partition for Windows 2000,
   press ESC.

     Format the partition using the NTFS file system   
     Format the partition using the FAT file system







  ENTER=Continue  ESC=Cancel                                                   

26. Since this server is going to be a Domain Controller Setup should be instructed to format it as NTFS. Although the partition's file system can be changed after the installation is complete with the CONVERT command, CONVERT is very "dirty" and leaves a mess on the drive which can adversely affect such structures as dynamic drive mirrors or data recovery utilities. Since this is undesirable, the installation should go in with a fresh NTFS file system that will not end up cluttered with junk. Hitting [Enter] with the NTFS choice highlighted launches the next screen:


 Windows 2000 Server Setup


                 Please wait while Setup formats the partition.

       C:  New (Unformatted)                    7000 MB

                        on 38091 MB Disk 0 at Id 0 on bus 0 on atapi.






 
   Setup is formatting...

                              42%
            
 

                                                                               

27. The two previous screens will obviously not appear if the installation is going into a partition that already existed and was already formatted and functional. After the format process is complete the first major file copy begins automatically and looks like this:


 Windows 2000 Server Setup


            Please wait while Setup copies files to the Windows 2000
                            installation folders.
                   This may take several minutes to complete.






 
   Setup is copying files...

                              61%
                       
 
                                                            Copying:ntfs.sys  

28. Windows 2000 setup will automatically proceed through the next 2 screens and reboot the system with no input from the user:


 Windows 2000 Server Setup





        Please wait while Setup initializes your Windows 2000 configuration.






  Saving configuration...                                                      


 Windows 2000 Server Setup


   This portion of Setup has completed successfully

   If there is a floppy disk in drive A:, remove it.

   To restart your computer, press ENTER.
   When your computer restarts, Setup will continue.



 


             Your computer will reboot in 7 seconds...
                       
 
                                                                               

Procedures - The GUI Portion of the Windows 2000 Server Setup

29. Upon reboot the system will now launch Windows 2000 via its native boot sequence. A boot menu is not necessary on this system since it was a clean install so NTLDR proceeds to load Windows 2000 into memory which looks like this:
















Starting Windows...

For troubleshooting and advanced startup options for Windows 2000, press F8.

30. As the text only portion of the loader finishes it initializes the full GUI Windows 2000 kernel which proceeds normally and looks like this:

31. At the late stages of the kernel load, the text mode portion of set up has preloaded settings so that instead of actually launching the operating system (which has not actually been installed yet, the full GUI mode installation routine launches instead. As it prepares for the install it looks like this:

32. Now that the operating system kernel and the installation program are ready the first screen of the installation wizard appears. Click Next:

33. The install wizard proceeds to install all devices that can run on standardized drivers:

34. The install wizard gives the user the opportunity to make regional selections here which will affect the keyboard layout for foreign language support as well as standard notation for time/date and currency. The default is Regional choice is U.S. so click Next:

35. Under normal circumstances I never recommend actually filling these fields out with authentic data since it can sometimes be read by hackers if the system goes on line. However, in a business setting it may be necessary to fill in the company's name but the owner or manager's name should still be kept out of this screen because it gets automatically filled in to almost every piece of software that will touch the computer:

36. Time to pay for it. Remember that possession of the installation CD-ROM does not constitute ownership of the software. It is the possession of a valid product key that constitutes legal possession (you never actually own anything...you should have read the EULA back in the text mode portion that you agreed to earlier) of the software. Enter the 25-character alphanumeric key and click Next:

37. This is one of the few "important" screens of the install wizard where one must understand exactly what the choices are and be sure that the correct choice is made. The Microsoft servers offer two completely different licensing methods for installation. The first method is called "Per Server" This means that the server will allow a certain number of concurrent connections to it and no more. Exceeding this will place the network out of the legal licensure limits that were agreed to earlier and you could run the risk of copyright enfringement. In general the purchaser of the software is the one who knows exactly what they paid for. In "Per Server" the purchaser may have bought a Windows 2000 Server "5 user license" That is a "Per Server" license that will permit five separate workstations to log on and use it at any single moment legally. You can have 10 different machines that do access it, but only five can do so at the same time.

In the "Per Seat" licensing mode the server software that you are installing has no fixed number of users mentioned in the license per se. Instead each client workstation has to have its own Client Access License (CAL) installed on it in order to gain access to the server. If these are not installed then once again the network will be in violation of the licensure agreement.

The advantage of using "Per Seat" versus "Per Server" is discussed above in the Planning section. It is also important to be aware that any server can be converted from one licensing scheme to the other ONCE in its active lifetime. If you want to switch it again, you will have to completely wipe the drive and install again from scratch. Not a wondeful idea having to recreate years of accumulated program data and settings and user data and settings. Set the licensing on our lab servers to "Per Server" and run the number of concurrent connections up to 20 (they won't be running long enough to get Microsoft angry!) and click Next:

38. This is not a big deal with a personal computer but naming a server is a big deal. For the class, use SVRx where x is your station's number. This screen is also asking for the Administrator account's password. This one is the most important single piece of information you will provide this entire installation. If you forget it, you will be reinstalling from scratch all over again. (Also, others might think that you are "not the brightest one on the block"). You can make it easy to remember for now and change it to something tough later. Be sure that the CAPS LOCK is OFF and use "admin" and type it into both boxes:

39. Just like any version of Windows there are optional components that can be chosen to be installed or not installed. The default choices for a Windows 2000 server provide minimal functionality and almost no actual server capabilities. Depending on the intended role of the server components will almost certainly be needed out of here, but they can always be installed after the server is up and running which is what we intend to do here so just click Next:

40. (Note that if the system has a modem attached the "Modem Dialing Information" screen would appear at this point. The Microsoft networking paradigm has come much closer to the x.500 specification and every once in while the server's will actually need to know the correct Time/Date. As such go ahead and set the Time/Date correctly at this point and get the Time Zone correct (You will have to change it unless you live in Tijuana);

41. Windows will now proceed to install all of the networking components selected in the previous screens:

42. Leave the networking settings choice "Typical" and click Next. (we will change the settings later):

43. In our example we are installing the first server of the entire network (all of he tutorials involve the step-by-step process of promoting it and assigning it all of the capabilities necessary for this task) but even if you are installing a lowly member server you can leave the default settings here and either promote it to domain controller or join it to an existing domain later. Click Next:

44. At this point the installation is off to installing another slew of components:

45. If all has gone well so far the installation wizard will progress automatically into this "Performing Final Tasks" screen:

46. When the Final tasks are done the wizard will dump you at this screen (so you don't feel left out) to which you can click the Finish button which will then advance the system to the first logon:

47. At this phase the system loads the netowrk drivers and come online on the network. This is necessary for the ability to present the logon screen and to be able to logon to a domain across the wire:

48. At this point the installation is complete and functional. Press [Ctrl]+[Alt]+[Del]:

49. In this screen provide the user name "Administrator" (it must be capitalized, user names are case sensitive) and the password that you hopefully did not forget from earlier and then click OK:

50. The system will authenticate the user name and password against the security listings and begin the final settings adjustments and load explorer.exe and the next thing after this screen will be the desktop and the installation is totally complete at that point.

51. Go ahead and get rid of the screen that show you how to use the mouse (good grief, they cant use a mouse and you want them to use this server!) and click "I will configure the server later > Next. Uncheck "Show this screen at startup" and close the Configure Your Server window.

Post-Installation OS Configuration
  1. Post-installation activities will be done in the next lecture module.

Review Questions
  1. List the describe the ten steps of the server prototype phase:





























  2. List the information that should be prepared in the "Any Additional Notes" step:








  3. List the describe the checklist items prepared for this specific project's "Start the Server Documentation" step:

















  4. List the describe the pre-installation BIOS configuration steps performed:






































  5. List the pre-installation BIOS configuration steps that are considered physical server security measures:














  6. List the pre-installation BIOS configuration steps taken because the Windows 2000 Server installation lacks the hardware drivers:


  7. List all other pre-installation BIOS configuration steps and the reasons they are performed:














  8. List the describe the pre-installation steps taken concerning the 3COM NIC:








  9. List the describe the pre-installation steps taken concerning the hard drive:











  10. After the "Setup is inspecting your computer's hardware configuration" message what can be done at the first screen of the text portion of setup?


  11. List the user choices are there on the "Welcome to Setup" screen?


  12. The screen after the license agreement allows the user to perform what operation(s) on what device(s)? This is the equivalent of what DOS/Windows command?





  13. After creating partitions on the hard disk(s) what does the next screen do? It is the equivalent to what DOS command?


  14. After formatting the new partition where the server will be installed, what does the text portion of setup do next?


  15. After copying all necessary setup files to the hard drive what does the text portion of setup do next?


  16. What is the first set of items that can be configured in the GUI portion of setup?


  17. List the describe each of the major screens that require user input (other than clicking "Next") during the GUI portion of setup starting with "Regional Settings":

















CopyrightŠ2000-2008 Brian K. Robinson ALL RIGHTS RESERVED