NETWORKING WITH DIFFERENT OS

Transcription

1 Unit 1 NETWORKING WITH DIFFERENT OS Installation windows 98 OS- Installation windows 7- Installation Windows Server 2008 O- Using windows control panel and its options. Configure and support Transmission Control Protocol/Internet Protocol (TCP/IP). - Configure Windows XP Professional to operate on Windows networks Unit 2 Concept Domain controller- Difference between workgroup and Domain controller- DNS- installation and configuration DNS- Installing domain controller- uninstalling domain controller- connecting client to domain controller- Concept network mappingmanual mapping and auto mapping- remote desktop sharing- web connectivity Through logmein- using net meeting- Unit- 3 Creating Local users and groups- adding users to group- assigning rights to the usersconfiguring local security rights- using NTFS permissions- Creating Domain user and group- assigning user rights- resetting user password- adding user to group- deleting user account- sharing file and folder- providing security- Security inheritance. Unit-4 Installing and Configuring Hardware Devices - Working with Drivers - Troubleshooting Hardware Devices the Hardware Wizard Using Driver Rollback to restore advice driver-configure hardware devices - Drivers on a Computer - Running creating an answer file - Setup Manager Wizard Unit-5 Introduction-Windows XP, Install Windows XP Professional by using the System Preparation Tool- Basic Program Layout- Screen Saver Settings- Configure and manage file systems- Troubleshoot the boot process and other system issues- Configure the desktop environment, and use profiles to control desktop customization. 1 P a g e

2 Unit 1 Installation windows 98 OS To install Windows 98, you must have one of the following products: The "Microsoft Windows 98 Upgrade" product. This upgrade product is available on CD-ROM. When you use the Windows 98 Upgrade version, you must have a copy of the previous version of Windows on CD-ROM or on floppy disks for the compliance-check procedure during Setup. Make sure that you have your qualifying version of Windows on CD-ROM or on floppy disks before you run Setup. Note that you must also have a Windows 98 Startup disk to install this product. The "Microsoft Windows 98 for PCs Without Windows" product. This version is available on CD-ROM. A Windows 98 Startup disk is included with the product. Minimum Hardware Requirements to Install Windows 98 The minimum hardware requirements include: 486DX 66-MHz or faster processor (Pentium recommended) 16 megabytes (MB) of memory (24 MB recommended) 195 MB of free hard disk space (the required space may vary from 120 MB to 295 MB, depending on your computer's configuration and the options you choose to install) CD-ROM or DVD-ROM drive 3.5-inch high-density floppy disk drive Video adapter and monitor that support VGA or higher resolution Microsoft Mouse or compatible pointing device System Updates, Device Drivers, and Other Considerations CMOS Antivirus Utility It is important to disable any CMOS antivirus utility that is enabled on your computer before you run Setup. If you are not sure if this feature is enabled on your computer, view the documentation that is included with your computer, or contact the computer manufacturer. Drive Overlay Software If your computer uses drive overlay software to enable large hard disk support, the drive overlay software must be installed before you install Windows 98. System Updates and Device Drivers To ensure that your hardware and software is compatible with Windows 98, verify that you have the latest drivers, Basic Input Output System (BIOS), or patches for your hardware and software before you run Setup. If your computer uses proprietary hardware and you try to install Windows 98 on a clean hard disk, you may receive error messages. Before you install the retail or upgrade 2 P a g e

3 version of Windows 98 on your computer, check with the hardware manufacturer and verify that there are no known issues. Also, if your current version of Windows was preinstalled on your computer and was bundled with a software package that is on a Restore CD-ROM, you may not be able install the programs that are on the Restore CD-ROM. If this is the case, use the hardware manufacturer's Restore CD-ROM to install Windows 95 and the included programs first, and then run Setup from the Windows 98 Upgrade version. View your original hardware documentation if you are not sure how to run the Restore CD-ROM. WARNING: When you run the Restore CD-ROM, it may delete all of the data on your hard disk. Real-Mode CD-ROM Support The Windows 98 Startup disk contains generic CD-ROM drivers that work with most CD-ROM drives. The Windows 98 Startup disk contains generic, real-mode ATAPI CD- ROM and small computer system interface (SCSI) drivers that can enable CD-ROM drives after you boot from the Windows 98 Startup disk. These CD-ROM drivers are not guaranteed to work with all CD-ROM drives. They may work as a replacement driver if the real-mode CD-ROM drivers that are included with your CD-ROM drive are not available. If these drivers do not work with your CD-ROM drive, view the documentation that is included with your hardware, or contact your hardware manufacturer. How to Prepare the Hard Disk for the Windows 98 Installation Procedure WARNING: The following information applies to preparing an empty hard disk for the installation of Windows 98. If you use the following steps on a hard disk that is not empty, all of the data that is on that hard disk is deleted. Before you install Windows 98 on an empty hard disk, you must first create a primary partition and then format a file system on that partition. Each allocated space on the hard disk (primary partition or logical drive) is assigned a drive letter. Windows 98 supports the FAT16 and FAT32 file systems. When you run the Fdisk tool on a hard disk that is larger than 512 MB, you are prompted to choose a file system. The FAT16 file system has a maximum of 2 gigabytes (GB) for each allocated space, or drive letter. For example, if you use the FAT16 file system and you have a 6-GB hard disk, you can have three drive letters (C, D, and E), each with 2 GB of allocated space. The FAT32 file system supports drives up to 2 terabytes in size and stores files on smaller sections of the hard disk than does the FAT16 file system. This results in more free space on the hard disk. The FAT32 file system does not support drives that are smaller than 512 MB. How to Partition the Hard Disk After you decide which file system you want to use, run the Fdisk tool: 1. Insert the Windows 98 Startup disk in the floppy disk drive, and then restart your computer. 3 P a g e

4 2. When the Microsoft Windows 98 Startup menu is displayed, choose the Start computer without CD-ROM support option, and then press ENTER. 3. At a command prompt, type fdisk, and then press ENTER. 4. If the hard disk is larger than 512 MB, you receive the following prompt: Your computer has a disk larger than 512 MB. This version of Windows includes improved support for large disks, resulting in more efficient use of disk space on large drives, and allowing disks over 2 GB to be formatted as a single drive. IMPORTANT: If you enable large disk support and create any new drives on this disk, you will not be able to access the new drive(s) using other operating systems, including some versions of Windows 95 and Windows NT, as well as earlier versions of Windows and MS-DOS. In addition, disk utilities that were not designated explicitly for the FAT32 file system will not be able to work with this disk. If you need to access this disk with other operating systems or older disk utilities, do no enable large drive support. Do you wish to enable large disk support (Y/N)? If you want to use the FAT32 file system, press Y, and then press ENTER. If you want to use the FAT16 file system, press N, and then press ENTER. 5. After you press ENTER, the Fdisk Options menu is displayed. Press 1 to select the Create DOS partition or Logical DOS Drive option, and then press ENTER. 6. Press 1 to select the Create Primary DOS Partition option, and then press ENTER. 7. After you press ENTER, you receive the following prompt: Do you wish to use the maximum available size for primary DOS partition? FAT32 File System: a. If you chose the FAT32 file system in step 4 and you want all of the space on the hard disk to be assigned to drive C, press Y, and then press ENTER. b. Press ESC, and then press ESC to quit the Fdisk tool and return to a command prompt. c. Skip to step 10. FAT16 File System: d. If you chose the FAT16 file system in step 4, and you want the first 2 GB on the hard disk to be assigned to drive C, press Y, and then press ENTER. e. Press ESC to return to the Options menu, and then skip to step i. f. If you want to customize the size of the partitions (the logical drives) on the hard disk, press N, and then press ENTER. g. A prompt is displayed for you to type the size that you want for the primary partition in megabytes or percent of disk space. Note that for a Windows 98-based computer, Microsoft recommends that you make the primary partition at least 500 MB. Type the size of the partition that you want to create, and then press ENTER. h. Press ESC to return to the Options menu. 4 P a g e

5 i. Press 2 to select the Set active partition option, and then press ENTER. j. When you are prompted to type the number of the partition that you want to make the active partition, press 1, and then press ENTER. k. Press ESC to return to the Options menu. l. To assign drive letters to the additional space on the hard disk: 1. Press 1, and then press ENTER. 2. Press 2 to select the Create Extended DOS Partition option, and then press ENTER. 3. The option that appears displays the maximum space that is available for the extended partition. You can adjust the size of the partition or you can use the default size. Note that the default maximum space is recommended, but the space can be divided between multiple drive letters. Type the amount of space that you want, press ENTER, and then press ESC. 4. The Create Logical DOS Drive(s) in the Extended DOS Partition menu is displayed. This is the menu that you use to assign the remaining hard disk space to the additional drive letters. Type the amount of space that you want to assign to the next drive letter at the Enter logical drive size in Mbytes or percent of disk space (%) prompt, and then press ENTER. 5. A table that lists the drive letter that you created and the amount of space that is on that drive is displayed. If there is still free space on the hard disk, it is displayed near the bottom of the table. Repeat steps 1 through 4 until you receive the following message: All available space in the Extended DOS Partition is assigned to local drives 6. After you receive this message, press ESC, and then press ESC to quit the Fdisk tool and return to a command prompt. After you create the partitions, restart you computer with the Windows 98 Startup disk in the floppy disk drive. When the Windows 98 Startup menu is displayed, choose the Start computer without CD-ROM support option, and then press ENTER. When a command prompt is displayed, type format c:, and then press ENTER. NOTE: If you receive a "Bad command or file name" message, you may need to extract the Format.com utility to your Startup disk. To do this, type the following command at a command prompt, and then press ENTER: extract ebd.cab format.com After the Format.com utility is extracted to your Startup disk and a command prompt is displayed, type format c:. When you successfully run the Format.com utility, you receive the following prompt: 5 P a g e

6 WARNING, ALL DATA ON NON-REMOVABLE DISK DRIVE C: WILL BE LOST! Proceed with Format (Y/N)? Press Y, and then press ENTER to format drive C. After the format procedure is finished, you receive the following prompt: Volume label (11 characters, ENTER for none)? This is an optional feature that you can use to type a name for the hard disk. Type an 11-character name for the drive, or leave it blank, and then press ENTER. Repeat steps 10 through 13 for any additional drive letters that you created in step i. How to Install Windows 98 After you partition and format your hard disk, you can install Windows 98: 1. Insert the Windows 98 Startup disk in the floppy disk drive, and then restart your computer. 2. When the Windows 98 Startup menu is displayed, choose the Start computer with CD-ROM support option, and then press ENTER. 3. If CD-ROM support is provided by the generic drivers on the Startup disk, you receive one of the following messages, where X is the drive letter that is assigned to your CD-ROM drive: Drive X: = Driver MSCD001 Drive X: = Driver OEMCD001 NOTE: If your CD-ROM drive is not available after you boot from the Windows 98 Startup disk, install the CD-ROM drivers that are included with your CD-ROM drive. For information about how to obtain and install the most current driver for your CD-ROM drive, view the documentation that is included with your device, or contact your hardware manufacturer. 4. Insert the Windows 98 CD-ROM in the CD-ROM drive, type the following command at a command prompt, and then press ENTER X:\setup where X is the drive letter that is assigned to your CD-ROM drive. 5. When you receive the following message, press ENTER, and then follow the instructions on the screen to complete the Setup procedure: Please wait while the Setup initializes. Setup is now going to perform a routine check on your system. To continue press Enter. Installation windows 7 Installation process I recommend that you check Windows 7 System Requirements list to ensure that your hardware is supported by Windows 7. If you don't have Windows 7 drivers for all your hardware, it is a good idea to download all the drivers from the hardware manufacturer s website and save all the necessary drivers on a CD-R or a USB drive before you start the installation. 6 P a g e

7 Windows 7 DVD is bootable. In order to boot from the DVD you need to set the boot sequence. Look for the boot sequence under your BIOS setup and make sure that the first boot device is set to CD-ROM/DVD-ROM. Step 1 - Place Windows 7 DVD in your dvd-rom drive and start your PC. Windows 7 will start to boot up and you will get the following progress bar. Step 2 - The next screen allows you to setup your language, time and currency format, keyboard or input method. Choose your required settings and click next to continue. Step 3 - The next screen allows you to install or repair Windows 7. Since we are doing a clean install we will click on "install now". Step 4 - Read the license terms and tick I accept license terms. Then click next to continue. 7 P a g e

8 Step 5 - You will now be presented with two options. Upgrade or Custom (Advanced). Since we are doing a clean install we will select Custom (Advanced). Step 6 - Choose where you would like to install Windows 7. If you have one hard drive you will get a similar option to the image below. You can click next to continue. If you have more that one drive or partition then you need to select the appropriate drive and click next. If you need to format or partition a drive then click Drive options (advance) before clicking next. Step 7 - Windows 7 starts the installation process and starts copying all the necessary files to your hard drive as shown on the image below. 8 P a g e

9 Step 8 - It will go through various stages of the setup and will reboot your system few times. Step 9 - When your PC reboots it attempts to boot from DVD as its the first boot device. Do not press any key during the boot prompt so Windows 7 will continue with the installation by booting from the hard drive. Step 10 - After the reboot your computer will be prepared for first use. 9 P a g e

10 Step 11 - At this stage you need to choose a user name and computer name. Click next to continue. The user account you create here is the Administrator account which is the main account for your Windows 7 that has all the privileges. Step 12 - Choose your password and password hint just incase you forget your password and need to jog your memory. Step 13 - You can now type the product key that came with Windows 7 and click next. If you do not enter the product key you can still proceed to the next stage. However Windows 7 will run in trial mode for 30 days. You must therefore activate Windows within 30 days otherwise you can not access your computer after 30 days. Step 14 - Help protect your computer and improve Windows automatically. Choose Use recommended settings. 10 P a g e

11 Step 15 - Review your time and date settings. Select your time zone, correct the date and time and click next to continue. Step 16 - Select your computer's current location. If you are a home user then choose Home network otherwise select the appropriate option. Step 17 - Windows will now finalize the settings for your computer and restart. Step 18 - After the final restart Windows 7 will start to boot up. 11 P a g e

12 Installation Windows Server 2008 Installing Windows Server 2008 is pretty straightforward and is very much like installing Windows Vista, but I thought I'd list the necessary steps here for additional information. For those of you who have never installed Vista before, the entire installation process is different than it used to be in previous Microsoft operating systems, and notably much easier to perform. Using Vista's installation routine is a major benefit, especially for a server OS. Administrators can partition the system's hard drives during setup. More importantly, they can install the necessary AHCI or RAID storage drivers from a CD/DVD or even a USB thumb drive. Thus, error-prone floppies can finally be sent to the garbage bin. Note: Windows Server 2008 can also be installed as a Server Core installation, which is a cut-down version of Windows without the Windows Explorer GUI. Because you don t have the Windows Explorer to provide the GUI interface that you are used to, you configure everything through the command line interface or remotely using a Microsoft Management Console (MMC). The Server Core can be used for dedicated machines with basic roles such as Domain controller/active Directory Domain Services, DNS Server, DHCP Server, file server, print server, Windows Media Server, IIS 7 web server and Windows Server Virtualization virtual server To use Windows Server 2008 you need to meet the following hardware requirements: Component Processor Memory Requirement Minimum: 1GHz (x86 processor) or 1.4GHz (x64 processor) Recommended: 2GHz or faster Note: An Intel Itanium 2 processor is required for Windows Server 2008 for Itanium-based Systems Minimum: 512MB RAM Recommended: 2GB RAM or greater Maximum (32-bit systems): 4GB (Standard) or 64GB (Enterprise and Datacenter) Maximum (64-bit systems): 32GB (Standard) or 2TB (Enterprise, Datacenter and Itanium-based Systems) Available Disk Minimum: 10GB Recommended: 40GB or greater Note: Computers with more than 16GB of RAM will require more disk space for paging, 12 P a g e

13 Space Drive hibernation, and dump files DVD-ROM drive Display and Super VGA (800 x 600) or higher-resolution monitor Keyboard Peripherals Microsoft Mouse or compatible pointing device Follow this procedure to install Windows Server 2008: 1. Insert the appropriate Windows Server 2008 installation media into your DVD drive. If you don't have an installation DVD for Windows Server 2008, you can download one for free from Microsoft's Windows 2008 Server Trial website. 2. Reboot the computer. 13 P a g e

14 3. When prompted for an installation language and other regional options, make your selection and press Next. 4. Next, press Install Now to begin the installation process. 14 P a g e

15 5. Product activation is now also identical with that found in Windows Vista. Enter your Product ID in the next window, and if you want to automatically activate Windows the moment the installation finishes, click Next. If you do not have the Product ID available right now, you can leave the box empty, and click Next. You will need to provide the Product ID later, after the server installation is over. Press No. 15 P a g e

16 6. Because you did not provide the correct ID, the installation process cannot determine what kind of Windows Server 2008 license you own, and therefore you will be prompted to select your correct version in the next screen, assuming you are telling the truth and will provide the correct ID to prove your selection later on. 7. If you did provide the right Product ID, select the Full version of the right Windows version you're prompted, and click Next. 16 P a g e

17 8. Read and accept the license terms by clicking to select the checkbox and pressing Next. 9. In the "Which type of installation do you want?" window, click the only available option Custom (Advanced). 17 P a g e

18 18 P a g e

19 10. In the "Where do you want to install Windows?", if you're installing the server on a regular IDE hard disk, click to select the first disk, usually Disk 0, and click Next. If you're installing on a hard disk that's connected to a SCSI controller, click Load Driver and insert the media provided by the controller's manufacturer. If you're installing in a Virtual Machine environment, make sure you read the "Installing the Virtual SCSI Controller Driver for Virtual Server 2005 on Windows Server 2008" If you must, you can also click Drive Options and manually create a partition on the destination hard disk. 19 P a g e

20 11. The installation now begins, and you can go and have lunch. Copying the setup files from the DVD to the hard drive only takes about one minute. However, extracting and uncompressing the files takes a good deal longer. After 20 minutes, the operating system is installed. The exact time it takes to install server core depends upon your hardware specifications. Faster disks will perform much faster installs Windows Server 2008 takes up approximately 10 GB of hard drive space. The installation process will reboot your computer, so, if in step #10 you inserted a floppy disk (either real or virtual), make sure you remove it before going to lunch, as you'll find the server hanged without the ability to boot (you can bypass this by configuring the server to boot from a CD/DVD and then from the hard disk in the booting order on the server's BIOS) 20 P a g e

21 12. Then the server reboots you'll be prompted with the new Windows Server 2008 type of login screen. Press CTRL+ALT+DEL to log in. 13. Click on Other User. 21 P a g e

22 14. The default Administrator is blank, so just type Administrator and press Enter. 15. You will be prompted to change the user's password. You have no choice but to press Ok. 22 P a g e

23 16. In the password changing dialog box, leave the default password blank (duh, read step #15 ), and enter a new, complex, at-least-7-characters-long new password twice. A password like "topsecret" is not valid (it's not complex), but one like "T0pSecreT!" sure is. Make sure you remember it. 23 P a g e

24 17. Someone thought it would be cool to nag you once more, so now you'll be prompted to accept the fact that the password had been changed. Press Ok. 24 P a g e

25 18. Finally, the desktop appears and that's it, you're logged on and can begin working. You will be greeted by an assistant for the initial server configuration, and after performing some initial configuration tasks, you will be able to start working. Using windows control panel and its options. As with previous versions of Windows, the Windows 2000 Control Panel is the central hub for making any variety of system changes. The Control Panel contains a collection of programs called applets that form the graphical user interface through which most changes to the Registry are made. Mentioned in Chapter 4, using the Control Panel applets is the preferred method for making Registry changes. This is due to the ease in which a mistake can be made using the Registry Editor. Collectively the Control Panel applets are the most powerful function of Windows 2000 next to the Registry Editor. The reason is that while Explorer provides the interface for file and folder manipulation, the Control Panel provides the ability to manipulate any of the hardware in your system as well as control the administrative functions of the operating system. In this chapter, we will take a look at the following topics: Defining the main applets in the Control Panel Working with hardware settings Working with operating system settings Installing hardware Defining the Main Applets in Control Panel With Windows 2000, Microsoft has captured the best of both worlds with respect to the Windows NT 4.0 and Windows 9x (95 and 98) Control Panel applets. For example, Windows 9x users have long enjoyed the Device Manager (located under the System applet) for managing hardware, a feature Windows NT users did not have. Windows NT users have long been able to configure their environment variables and startup options through Control Panel whereas Windows 9x users had to manually edit config.sys, autoexec.bat, and msdos.sys files to obtain equivalent functionality. In many ways Windows 2000 tries to converge the user friendliness of Windows 9x with the power and stability of Windows NT. Many of the applets are similar to what Windows 9x and NT users have seen in the past. The Display applet is practically unchanged from Windows 98 and eliminates the requirement to click "test" in NT 4.0 before applying a new display resolution. Other applets such as Printers, Fonts, Keyboard, Mouse, Date/Time, Power, and Accessibility Options are very similar to what they have been in the past, though in many cases are more wizard driven than in previous versions of Windows. We'll focus on a few of the most highly used applets as well as a couple of new additions. 25 P a g e

26 Add/Remove Hardware Add/Remove Hardware is an updated version of the "Add New Hardware" applet from Windows 9x and NT 4.0. Add New Hardware, as the name implies, gave users the ability to install and configure new hardware devices. The Windows NT version of Add New Hardware did not include any Plug and Play functionality, but rather allowed the user to manually install a device driver included with NT or from a user-provided location ("have disk"), after selecting the appropriate category of device that was to be installed, such as SCSI controllers or network adapters. Windows 9x gave the user the option of letting Windows search for a Plug and Play device in addition to manually installing a device driver. The Windows 2000 Add/Remove Hardware Wizard includes all of the functionality of the Windows 9x Add New Hardware Wizard and more. When you first open the Add/Remove Hardware Wizard you are given a choice of hardware tasks, as shown in Figure 1. Figure : The Add/Remove Hardware Wizard allows the user to perform a variety of hardware related tasks. The Add/Troubleshoot a device task is similar in function to the original Add New Hardware Wizard. First, Windows 2000 attempts to detect a device through Plug and Play, and if it doesn't detect a new device it presents the option to install a driver manually. Additionally, there is the option to troubleshoot a device, which will be discussed later in this chapter along with uninstalling and unplugging devices. Add/Remove Programs The Add/Remove Programs applet has a fresh new look to it in Windows 2000, as shown in Figure, but works the same as it did in NT P a g e

27 Figure 2: The Add/Remove Programs applet gives a new look to an old standby Change or Remove Programs Change or Remove Programs lets you either uninstall complete applications, or add or remove individual components of applications that support that feature. Multifaceted applications such as office suites typically allow you to change components of programs without having to completely remove and reinstall the entire application. Add New Programs Add New Programs is another example of an applet that has converged Windows NT and Windows 9x. You can still install new floppy based or CD-ROM based applications through this applet, but Windows 2000 has also incorporated the Windows 98 "Windows Update" utility into Add New Programs. Windows Update is a utility through which you can add new Windows features, device drivers, and system updates over the Internet. This enables you to keep your Windows 2000 operating system up to date as bugs and security holes are found and patched and as Microsoft adds new functionality. Add/Remove Windows Components Add/Remove Windows Components is where you can customize your installation of Windows As in NT 4.0 you can add components that were not installed during the initial operating system setup or remove components you no longer want installed. A difference in Windows 2000 is that Microsoft has moved Networking Services from the Network Control Panel applet in NT 4.0 to the Windows Components Wizard of Add/Remove Programs. Tip You can still configure additional network services through the Network and Dial-up Connections Control Panel applet by clicking the Advanced menu and selecting Optional Networking Components. This brings up the Windows Components Wizard without having to go through Add/Remove Programs first. 27 P a g e

28 Administrative Tools An important difference between NT 4.0 and Windows 2000 is that Microsoft has moved the Administrative Tools from the Start Menu to the Control Panel. This move is in keeping with the strategy that the Control Panel is the central hub for configuring the operating system. A common complaint with earlier versions of NT was the lack of cohesiveness when it came to administering the system. Tools were scattered here and there and every tool had a different interface. Windows 2000 attempts to address those complaints by providing both a centralized location (Control Panel) and a unified look and feel (MMC Microsoft Management Console) to system administration. The Administrative Tools are implemented as a series of MMC Snap-Ins and will be covered in more detail throughout the book. Tip For NT 4.0 users who preferred Administrative Tools on the Start Menu, it can be added back through Taskbar Properties by checking the "Display Administrative Tools" checkbox on the Start Menu Options tab. Users and Passwords The Users and Passwords applet replaces the older User Manger (NT Workstation) and User Manager for Domains (NT Server) applets from NT 4.0. In this applet you can configure user and group settings, and configure whether or not users have to enter a username and password to login or have to press ctrl-alt-del. If your network uses a certification authority for authentication you can manage certificates in this applet as well. System The System applet is host to a wide variety of functions that enable you to configure your computer's settings. System is possibly the most important of the Control Panel applets, so we will look at each of the property sheets that make up the applet. It is divided into five property sheets as follows: General Network Identification Hardware User Profiles Advanced General The General property sheet is the same as in NT 4.0. It provides information such as the version of the operating system, who the operating system is registered to, the license key, and information regarding the processor and amount of RAM installed in the computer. 28 P a g e

29 Network Identification The Network Identification property sheet is new to Windows 2000 and is what used to be the General tab of the Network Control Panel applet in NT 4.0. On this property sheet you can change the name of the computer and configure workgroup or domain membership for your workstation or server. Hardware The Hardware property sheet is the location for configuring your system's hardware. It includes a button that links to the Add/Remove Hardware applet and, like NT 4.0, gives you the ability to setup and configure multiple hardware profiles. Tip Another exciting new feature of Windows 2000 is driver signing, which attempts to maintain the integrity of the operating system files by allowing you to configure whether or not to overwrite digitally signed files when you install applications. By default file signatures are ignored, meaning all files will be installed regardless (the same as NT 4.0). There are also options to warn you before installing an unsigned file or to block unsigned files from installing at all. Device Manager is the applet that Windows 9x users have had available to them while NT 4.0 users had to rely on the archaic Windows NT Diagnostics that provided much less functionality. Using Device Manager you can view and change device properties, update device drivers, configure device settings, and uninstall devices. User Profiles The User Profiles property sheet is where you configure local vs. roaming profiles. Profiles are discussed in depth in Chapter 13. Advanced The Advanced property sheet contains options to configure performance options, environment variables, and startup and recovery options. Each of these is discussed later in this chapter. Working with Hardware Profiles Hardware profiles are a feature of Windows 2000 that enables the operating system to have multiple hardware configurations. By default, when Windows 2000 boots, every device driver that is currently installed is loaded into memory. A default profile called "Profile 1" is created during the Windows 2000 installation and every device installed is enabled during the boot process. For desktop computers that is usually desirable, but where hardware profiles are especially useful is with notebook computers. Many people have docking stations for using their notebook computer in an office, but do not take it with them when they take their notebook home or when traveling. You might have a 29 P a g e

30 hardware profile named "Docked" that loads device drivers for a network card and laser printer that are part of your docking station. You could also have a second profile called "Undocked" for use in a hotel room or at home that loads a modem rather than the network card. While you could just load everything in one profile regardless of your location, you would end up with error messages logged in the System Log (Event Viewer and logs are discussed in Chapter 26). Creating and Modifying Hardware Profiles As previously mentioned, configuring hardware profiles is done through the System applet in Control Panel. After clicking the Hardware tab, click the Hardware Profiles button at the bottom. That will bring up the dialog shown in Figure 3. Figure: Configuring hardware profiles in Windows 2000 through the Control Panel System applet. Creating a new profile is accomplished by selecting the generic "New Hardware Profile" and clicking Copy. Assign a name to your new profile and click OK. The new profile will default to enabling every installed device; you will likely want to modify the profile to your specific needs. This is done through the Device Manager rather than the Hardware Profiles property sheet. The Device Manager, shown in Figure 4, is accessed from the Hardware property sheet of the System applet just like Hardware Profiles. 30 P a g e

31 Figure 4: The Windows 2000 Device Manager console enables you to configure settings for hardware devices, including in what hardware profiles the devices should be enabled. In Device Manager, a device can be enabled or disabled in a particular profile through the General properties of an individual device. For example, double-clicking on an installed modem will bring up the properties. At the bottom of the General property sheet is the "Device Usage" option. You can select your desired options from the drop down list. Using a Hardware Profile If you only have one hardware profile Windows 2000 will, of course, use it every time you boot the computer. However, if you have more than one profile you have a couple of options as to how Windows behaves during the boot process. As shown at the bottom of Figure 5-3 there are choices for hardware profiles selection when Windows starts. By default Windows will countdown from 30 seconds before loading the first profile listed if you do not intervene. You can also have Windows wait indefinitely for you to make a profile selection. Viewing the Properties of a Hardware Profile For profile selections to work, first you have to make the profile available as an option when Windows starts. This is done by highlighting the profile and clicking Properties, which brings up the window shown in Figure P a g e

32 Figure 5: Properties of a hardware profile. By clicking the "Include this profile as an option when Windows starts" checkbox you can control whether a profile is available for use. This is handy if you no longer need a particular profile but you do not want to delete it right away, or if you will be using one particular configuration for an extended period of time and do not wish to have other profiles available during that time. That scenario might take place if you went on an extended business trip where you were not going to be using the docking station back in your office any time soon. Working With Operating System Settings Windows 2000, like NT 4.0, gives you the option to configure settings that affect the behavior of the operating system through the System applet in Control Panel. After opening System Properties, click the Advanced tab to find the operating system settings. Configurable options include: Performance Options Environment Variables Startup and Recovery 32 P a g e

33 Performance Options Performance options give you the ability to control how applications use memory. When you click on the Performance Options button you a presented with the window shown in Figure 6. Figure 6: Configuring Windows 2000 Performance Options The first option on this property sheet is for application response. By default Windows 2000 will optimize performance for applications rather than background services. Windows 2000 manages system processing, which includes allocating processor time to processes that are running. The operating system can allocate tasks between multiple processors or multiple processes on a single processor. Choosing the Application Response preference, however, allows you to decide whether Windows should give more processor time to the programs you are working in or to background tasks such as printing. Setting the response to favor applications will result in a faster response time from the application you are actively working in, which is generally the desired option. A print server, though, would be set up to favor background tasks rather than active applications since the majority of the server's work would be processing background tasks. Windows 2000, like Windows NT, uses a thread priority process in order to determine which application to give CPU time to and in which order to do it. Windows 2000 does this on a scale of 1-31, with 31 being the highest priority and 1 being the lowest. Table shows a list of the thread priorities. Table 1 Thread Priorities in Windows 2000 Base Priority class Thread priority 31 Real-time Time critical 26 Real-time Highest 25 Real-time Above normal 24 Real-time Normal 23 Real-time Below normal 22 Real-time Lowest 16 Real-time Idle 33 P a g e

34 15 Idle, Normal, or High Time critical 15 High Highest 14 High Above normal 13 High Normal 12 High Below normal 11 High Lowest 10 Normal Highest 9 Normal Above normal 8 Normal Normal 7 Normal Below normal 6 Normal Lowest 6 Idle Highest 5 Idle Above Normal 4 Idle Normal 3 Idle Below normal 2 Idle Lowest 1 Idle, Normal, or High Idle An obvious question would be, if Windows 2000 gives CPU time to the highest priority app, how are lower priority apps ever executed? Good question! Windows 2000 dynamically adjusts the priorities, boosting lower priority applications so that eventually as the CPU continues to multitask, the application gets to use some CPU time. This process works very quickly, so even lower priority apps will respond within a reasonable amount of time. 34 P a g e

35 Virtual Memory The second configurable performance option is virtual memory, shown in Figure 7. Figure: The Virtual Memory property sheet When Windows runs low on available RAM and needs more memory to complete a task, it uses the hard drive to simulate system RAM. This is called virtual memory and is much slower than system RAM. This is because hard drive speeds are measured in milliseconds while RAM is measured in nanoseconds. Another name for virtual memory in Windows 2000 is the pagefile, and, in fact, Windows creates and uses a special file called pagefile.sys for virtual memory. The default size for the pagefile in Windows 2000 is the amount of system RAM plus 12 MB. So, a system with 128 MB of RAM would initially have a pagefile of 140 MB. For a basic workstation or server, this number might be appropriate but servers running other Microsoft BackOffice applications such as Exchange Server or SQL Server usually need to increase the default virtual memory size. Refer to the product specific documentation for recommended virtual memory settings. You set the size of the pagefile by selecting the drive you want the file to be located on, typing a number into the Initial Size box shown in Figure 5-7 and the Maximum Size box and clicking Set. You will be prompted to reboot after clicking OK. The initial size is just that--the size of pagefile.sys when Windows 2000 starts up. The maximum size is how large pagefile.sys is allowed to grow during the processing of tasks as the system works. 35 P a g e

36 Tip It might seem advantageous at this point to simply set a pagefile much higher than you need so you will not have to worry about running out of memory. However, Windows 2000 will not efficiently use a pagefile that is too large, resulting in potentially worse system performance than if the virtual memory size had been left at the default settings. The default virtual memory settings are often not the most efficient, but there are some guidelines that you can use when configuring virtual memory settings. Windows 2000 sets up the page file to be on the boot partition where the operating system was installed. This is inefficient because Windows will by nature perform a lot of disk I/O on the system files. Having to simultaneously read and write to the page file while doing the same with system files slows Windows down. Therefore it is recommended that the page file be moved to a different physical disk, preferably onto a partition that has no other data or programs that will be frequently accessed. Windows 2000, like Windows NT before it, supports advanced disk configuration options on NTFS partitions such as disk mirroring and disk striping. These features provide fault tolerance and performance benefits, and are discussed later in this book in a chapter on managing disks. The downside to moving the entire page file though is that if Windows crashes it will be unable to write debugging information to a dump file (discussed later in this chapter). To address that, a page file using the default settings should be left on the system partition and another page file should be created on a different physical disk as outlined above. The Windows 2000 operating system has algorithms that allow it to use multiple page files in the most efficient manner, and in this case it will opt to use the page file on the less frequently used drive rather than the one on the system partition. Should Windows crash, though, it would be able to create a dump file for troubleshooting purposes. In addition to configuring the size of the page file, you can also configure the maximum size of the Registry from the Virtual Memory property sheet. As with the page file you can specify the largest size the Registry is allowed to grow, and nothing is gained by setting the maximum size artificially high. Using Environment Variables Most current systems administrators can remember the dark days of DOS when manually editing system files such as config.sys and autoexec.bat was a way of life. Windows 2000 though, like NT 4.0 before it, provides a convenient GUI interface for configuring the environment variables that is shown in Figure P a g e

37 Figure : Configuring environment variables in Windows Environment variables are divided into User Variables and System Variables. As the name suggests, User Variables are specific to the user and, other than TEMP settings, are usually only required for specific applications. System Variables are common to the operating system no matter who is logged in. Typically the settings an administrator might edit under System Variables would be the TEMP files folder and the PATH statement. In DOS and Windows 9x, these particular settings were located in the autoexec.bat file. By clicking New you can create a new User or System variable, and Edit allows you to modify an existing variable, such as to add an additional folder to the PATH statement. Deleting a System variable should be done with great care and only if you are sure of the potential consequences of that setting being removed. Understanding Startup and Recovery Options The Startup and Recovery Options, shown in Figure 9, allow you to control the behavior of the system during startup and during a crash. If you only have Windows 2000 installed on your system it will be the default operating system. It will be the default operating system as well in a dual boot scenario if it was the last operating system installed. If, for example, you had a Windows 98 system and you installed Windows 2000 as a new installation, you would have the option when the Boot Menu appeared of choosing either OS. The menu by default counts down from 30 seconds before loading the default operating system if there is no intervention. On the Startup and Recovery 37 P a g e

38 property sheet, you can tell Windows which operating system should be the default and for how long the menu should be displayed before loading the default. While Windows 2000 is generally a stable operating system, there will be times when you experience the infamous "Blue Screen of Death" fatal error. The Recovery options let you determine what actions Windows takes when a fatal error occurs. By default it will write an event to the system log, but you can also have Windows send an administrative alert to a remote user or computer if the alerter service is configured. This is especially helpful to notify system administrators immediately when a server goes down to ensure the quickest response time possible. Windows can also write debugging information to a dump file, memory.dmp. This is enabled by default on Windows 2000 Server but must be manually enabled on Windows 2000 Professional. The contents of the dump file means nothing to most administrators but can be used by Microsoft to help troubleshoot the cause of the crash. If debugging information is written to a dump file, it is beneficial to also check the box to automatically reboot. If an application caused the fatal error, typically Windows will start back up without a problem. This will enable users to get back to work while you work to determine the specific cause of the crash through the dump file. If the server does not automatically reboot, it will stay at the fatal error screen until someone manually resets the system. Installing Hardware Windows 2000 has made great strides over NT 4.0 in the process of installing hardware, mainly due to the more robust Plug and Play support. NT 4.0 had very limited PnP capabilities through the pnpisa service, but pnpisa supported only a small variety of hardware. Windows 2000 has full blown PnP support similar to Windows 98 and supports a much larger variety of hardware than NT 4.0. Tip You must be logged into the computer using an account that is a member of the administrator's group in order to install hardware. Plug and Play Hardware A Plug and Play system is one that has a PnP compatible BIOS, operating system, PnP devices, and PnP-aware applications. If you have a PnP compatible system, installing PnP hardware is generally pretty simple. Follow the manufacturer's instructions to physically install the device and power up the computer. Windows 2000 should detect your new hardware and start the Found New Hardware wizard. Follow the on-screen prompts to install the appropriate device driver if Windows does not automatically install a driver for you. Windows 2000 comes with a substantial library of device drivers, so in many cases it will already have a driver that will work with the device you are installing. If Windows does not have a driver, you will be prompted for the location of the driver 38 P a g e

39 Non-Plug and Play Hardware If the hardware you are installing is not Plug and Play compatible, also known as a legacy device, Windows will not detect it automatically and launch the Found New Hardware wizard. In most cases legacy devices have physical jumpers on the device or proprietary software utilities that come with the device that are used to configure the hardware settings. Jumpers must be set at the time the device is physically installed in order for the device to work properly. Installing a device driver for non-plug and Play hardware is done through the Add/Remove Hardware wizard. Using the Add/Remove Hardware Applet As previously mentioned, the Add/Remove Hardware applet builds on the functionality of Add New Hardware in NT 4.0. When you launch the Add/Remove Hardware wizard it will first attempt to detect Plug and Play devices that might not have been configured. If it does not detect a device you will be presented with the window shown in Figure 5-9 and given the opportunity to "Add a new device" or troubleshoot a device that already has a driver loaded for it. Figure 9: Installing a non-plug and Play device or troubleshooting an existing device is done through the Add/Remove Hardware wizard. In a bit of redundancy due to reusing existing NT 4.0 code from its Add New Hardware wizard, Windows 2000 will give you the default choice of searching for PnP devices again when you select add a new device. Alternatively you can choose to select your hardware from a list. First you select the category of the device you wish to install, such as Display Adapters, then the specific make and model of the device you are installing. If Windows 2000 does not have a driver for your device you can select "Have Disk" to point the operating system to updated driver files. Follow the prompts and reboot if necessary to enable your hardware. 39 P a g e

40 Device Troubleshooting If you are having trouble getting an installed device to work you can use the Add/Remove Hardware applet to launch the Hardware Troubleshooter, shown in Figure 10. Figure 10: The Hardware Troubleshooter helps you resolve problems with installed hardware. Using the Hardware Troubleshooter is a matter of selecting the general type of problem you are having and stepping through a series of questions and suggestions to get your device working. These are the basic troubleshooting steps that a repair technician would take in troubleshooting the problem, and in most cases will enable you to get your hardware working without having to call the manufacturer's tech support. Uninstall/Unplug a Device If you want to uninstall a hardware device from your system or unplug a device (most typically associated with notebook computers), you would also use the Add/Remove Hardware wizard. When you select this option you are given two choices, one to remove a device and the other to unplug/eject a device. When you choose to uninstall a device you are shown a list of installed devices that can be removed. By default hidden devices, which are system level drivers usually essential to the operation of Windows 2000, are not shown. Checking the box to Show Hidden Devices makes them appear in the list, but great care should be taken before removing one of these devices. Only remove one if you are sure that the result will be desirable. Unplugging or ejecting a device is usually related to notebooks and PCMCIA (also known as PC Card) devices. Windows 2000 does not directly support hot swappable devices, that is, devices that can be added or removed on the fly where Windows will 40 P a g e

41 automatically detect their presence or lack there of. Going through the unplug/eject option lets you tell Windows you are about to unplug a device from your system such as a PCMCIA modem. The operating system will then tell you it is safe to eject the device. Tip If you frequently unplug/eject devices while Windows 2000 is running, you can select the checkbox to "Show Unplug/Eject icon on the taskbar" on the "Completing the Add/Remove Hardware Wizard" page. This will keep you from having to run the Add/Remove Hardware wizard every time. Viewing Available Hardware Resources Figure 4 showed the Device Manager console, which is the primary interface for viewing and modifying hardware resources. The Device Manager is organized in a tree format with the top branches representing device categories. Expanding a branch shows devices of that type that are installed on the system. This view is called "Devices by type." To view available hardware resources in Device Manager, click the View menu and select "Resources by connection." This will divide the console into groups for DMA, I/O, IRQ, and Memory. Expanding the IRQ branch for example will show you a list of IRQs in use and what devices are using them. This information is also available through the Computer Management administrative tool (Device Manager can also be accessed through Computer Management), but you need Device Manager if you want to do more than just view the resources in use. Altering Hardware Resource Assignments The default view in Device Manager is "devices by type," which is the easiest view for modifying hardware resources. To change a resource setting for a device, first expand the branch for the device category, such as network adapters. Then double click the device you want to modify to bring up the properties. Click the Resources tab to view the current resources for the device. If the "use automatic settings" checkbox is checked, Windows has assigned resources to this device and is managing those resources. This is the preferred method since it allows Windows to juggle any PnP devices to accommodate special resource requirements. If it is a legacy device though that requires manually setting the resources, you can uncheck the box and adjust the settings to match the hardware. Windows will dynamically update the conflicting device list at the bottom of the window to show you if a resource you have selected is already in use by another device. Resource configuration is shown in Figure P a g e

42 Figure: Windows 2000 allows you to configure resource settings for individual devices, useful for setting up non-plug and Play hardware. Transmission Control Protocol/Internet Protocol (TCP/IP) In order for communication to occur on a network all parties must use a common language. In IT networks this is known as a protocol. There are many different protocols available for computer networks. The most common and widely used being TCP/IP. TCP/IP is the standard protocol that is used on the internet. In order for any network to access the internet you must use the TCP/IP protocol suite. TCP/IP is required by Active Directory. For this reason, TCP/IP is the default protocol for Windows XP and Protocols Reference is often made to the TCP/IP stack. This consists of layers of mini applications which perform the discrete job of sorting and filtering the data packets picked up by the NIC and then passing the packet on to the next layer for further processing. Eventually a coherent message pops out of the top of the stack into the operating system for the user to read. The reverse is also true i.e. converting of the reply into data packets that can be sent over the network media. 42 P a g e

43 The layers in a TCP/IP stack write headers for network messages as well as decoding them. Each level in the stack adds a portion to the network packet whichh its counterpart in the receiving computer will understand. Strictly speaking, the NIC isn t part of TCP/IP, but protocols are bound to a particular adapter. At the receiving computer, the headers are stripped off as they pass up through the TCP/IP stack until only the bare payload is presented to the user. The DOD Four Layer Model TCP/IP is often referred to as the TCP/IP protocol suite. TCP/IP is in fact a group of protocols/applications working together to provide network communication. TCP/IP was invented by the US Department of Defence (DOD) to allow machines to communicate over a network. It is a simpler model than the 7 layer OSI model. The different components of TCP/IP all function at different layers. These layers group the different components into four different categories. The Application Layer The Application Layer contains the applications that use TCP/IP such as Internet Explorer and Outlook. The Application Layer also contains Application Programming Interfaces (API) such as Winsock, which enables applications to use TCP/IP. The Transport Layer The Transport Layer is responsible for the transfer of data on the network. There are two different transport protocols TCP and UDP. Both protocols provide transport but work in different ways. Transmission Control Protocol (TCP) TCP is a connection-orientated protocol. Both sides confirm that the data is being sent and received. 43 P a g e

44 User Datagram Protocol (UDP) UDP is a connectionless-orientated Protocol. Both computers presume the other side has received the data. As an example, name resolution uses UDP. If the query fails then a TCP name query is made. The Internet Layer To send data the sender must have a method of distinguishing the recipient. This is called an IP address and they take the form of a unique number on the network. The Internet Protocol is responsible for these addresses. The Internet Control Messaging Protocol (ICMP) is used to test connectivity between machines by sending ICMP messages using the PING command. The Internet Group Messaging Protocol (IGMP) is used to send data to groups of machines, e.g. Streaming Video. This is known as Multicast. The Address Resolution Protocol (ARP) is responsible for changing an IP address into the network card s physical address. Every network card has a unique physical address hardwired into the card itself which is needed for communication on a network. The Physical Layer The Physical Layer is responsible for the actual physical media and how the data is sent to another machine, e.g. Fibre Optic, ATM. There are many ways to send data down the cable, the most common technologies for LANs are Token Ring and Ethernet. In order for two machines to communicate they must be using the same technology or be connected via a bridge. Configure Windows XP Professional To Operate On Windows Networks There are two methods to start Windows XP by using a clean boot: Method 1: Use the Guided Help Method 2: Manually starting XP with a clean boot (advanced user only) Start with the first method. If it does not work and you are comfortable trying a more advanced method, try the second. Method 1: Guided Help Before you start Before you start to install and use Guided Help: 44 P a g e

45 You must be running Windows XP Home Edition, Windows XP Professional, Windows XP Media Center Edition, or Windows XP Tablet PC Edition to install Guided Help. You must be logged on as an administrator or a member of the Administrators group to configure Windows XP to start by using a clean boot. You can use Guided Help to clean-boot your computer or to restore your computer from a clean-boot state. Guided Help can guide you through the steps, or can automatically perform the steps for you. Notice that the actions that Guided Help performs can be undone after Guided Help is finished. To undo the actions, run Guided Help again. When you are prompted by Guided Help, click the Normal startup option or the Clean boot option. For more information about Guided Help, click the following article number to view the article in the Microsoft Knowledge Base: If the guided tour helped you start in a clean-boot state, you are finished with this article. If you have to return your computer to a normal startup state, go to "Steps to configure Windows to use a Normal startup state." If the guided tour did not help, you can try method 2 if you are comfortable trying an advanced method. If you are not comfortable with the advanced steps, go to the "Next Steps" section. Method 2: Manually starting XP with a clean boot (advanced user only) This section is intended for advanced computer users. If you are not comfortable with advanced troubleshooting, you might want to ask someone for help or contact Support. To manually start Windows XP with a clean boot, follow these steps: Step 1: Start the System Configuration Utility 1. Click Start, click Run, type msconfig, and then click OK. 2. The System Configuration Utility dialog box is displayed. Step 2: Configure selective startup options 1. In the System Configuration Utility dialog box, click the General tab, and then click Selective Startup. 2. Click to clear the Process SYSTEM.INI File check box. 3. Click to clear the Process WIN.INI File check box. 4. Click to clear the Load Startup Items check box. Verify that Load System Services and Use Original BOOT.INI are checked. 5. Click the Services tab. 6. Click to select the Hide All Microsoft Services check box. 7. Click Disable All, and then click OK. 8. When you are prompted, click Restart to restart the computer. 45 P a g e

46 Step 3: Log on to Windows 1. If you are prompted, log on to Windows. 2. When you receive the following message, click to select the Don't show this message or launch the System Configuration Utility when Windows start check box, and then click OK. Notes o o o You have used the System Configuration Utility to make changes to the way Windows starts. The System Configuration Utility is currently in Diagnostic or Selective Startup mode, causing this message to be displayed and the utility to run every time Windows starts. Choose the Normal Startup mode on the General tab to start Windows normally and undo the changes you made using the System Configuration Utility. Step 4: Optional step to disable features If the clean boot fixed the error, you do not have to perform this step. Important If your problem is not fixed and you do have to follow this step, it permanently removes all restore points from your computer. The System Restore feature uses restore points to restore your computer to an earlier state. If you remove the restore points, you can no longer restore Windows to an earlier state. sthis step temporarily disables Microsoft features such as Plug and Play, networking, event logging, and error reporting. 1. Click Start, click Run, type msconfig, and then click OK. 2. The System Configuration Utility dialog box is displayed. 3. Click the General tab, click to clear the Load System Services check box, and then click OK. 4. When you are prompted, click Restart to restart the computer. If these steps helped you start your computer in a clean-boot state, you are finished. If these steps did not help, go to the Next Steps section. If you have to return your computer to a normal startup state, go to Steps to configure Windows to use a Normal startup state. Steps to configure Windows to use a Normal startup state After you used the clean boot to resolve your problem, you can follow these steps to configure Windows XP to start normally. 1. Click Start, and then click Run. 2. Type msconfig, and then click OK. 3. The System Configuration Utility dialog box is displayed. 46 P a g e

47 4. Click the General tab, click Normal Startup - load all device drivers and services, and then click OK. 5. When you are prompted, click Restart to restart the computer. 47 P a g e

48 Unit 2 Concept Domain controller Over the years, public perceptions of what domain control really is have taken on an almost mystical nature. Before we branch into a brief overview of domain control, there are three basic types of domain controllers. NT4 style Primary Domain Controller NT4 style Backup Domain Controller ADS Domain Controller The Primary Domain Controller or PDC plays an important role in MS Windows NT4. In Windows 200x domain control architecture, this role is held by domain controllers. Folklore dictates that because of its role in the MS Windows network, the domain controller should be the most powerful and most capable machine in the network. As strange as it may seem to say this here, good overall network performance dictates that the entire infrastructure needs to be balanced. It is advisable to invest more in standalone (domain member) servers than in the domain controllers. In the case of MS Windows NT4-style domains, it is the PDC that initiates a new domain control database. This forms a part of the Windows registry called the Security Account Manager (SAM). It plays a key part in NT4-type domain user authentication and in synchronization of the domain authentication database with BDCs. With MS Windows 200x Server-based Active Directory domains, one domain controller initiates a potential hierarchy of domain controllers, each with its own area of delegated control. The master domain controller has the ability to override any downstream controller, but a down line controller has control only over its down line. With Samba-3, this functionality can be implemented using an LDAP-based user and machine account backend. New to Samba-3 is the ability to use a backend database that holds the same type of data as the NT4-style SAM database (one of the registry files) [1] The Backup Domain Controller or BDC plays a key role in servicing network authentication requests. The BDC is biased to answer logon requests in preference to the PDC. On a network segment that has a BDC and a PDC, the BDC will most likely service network logon requests. The PDC will answer network logon requests when the BDC is too busy (high load). When a user logs onto a Windows domain member client the workstation will query the network to locate the nearest network logon server. Where a WINS server is used, this is done via a query to the WINS server. If a net logon server cannot be found from the WINS query, or in the absence of a WINS server, the workstation will perform a NetBIOS name lookup via a mail slot broadcast over the UDP broadcast protocol. This means that the net logon server that the windows client 48 P a g e

49 will use is influenced by a number of variables, thus there is no simple determinant of whether a PDC or a BDC will serve a particular logon authentication request. A Windows NT4 BDC can be promoted to a PDC. If the PDC is online at the time that a BDC is promoted to PDC, the previous PDC is automatically demoted to a BDC. With Samba-3, this is not an automatic operation; the PDC and BDC must be manually configured, and other appropriate changes also need to be made. With MS Windows NT4, a decision is made at installation to determine what type of machine the server will be. It is possible to promote a BDC to a PDC, and vice versa. The only method Microsoft provides to convert a Windows NT4 domain controller to a domain member server or a standalone server is to reinstall it. The install time choices offered are: Primary Domain Controller the one that seeds the domain SAM. Backup Domain Controller one that obtains a copy of the domain SAM. Domain Member Server one that has no copy of the domain SAM; rather it obtains authentication from a domain controller for all access controls. Standalone Server one that plays no part in SAM synchronization, has its own authentication database, and plays no role in domain security. Difference between workgroup and Domain controller Networking in Windows means that you would need to setup a domain or a workgroup so that all the computers connected can communicate with each other. Whether you have a domain or a workgroup is all up to your network administrator and the scale of your network. Workgroups are used when there are only a few computers in the same location that needs to be connected. Domains, on the other hand, are meant for large scale deployments where there are dozens of computers connected to the network. Even computers from outside the location can connect to the domain with the use of VPN technologies. Workgroups are substantially easier to create compared to domains. You would simply need to connect two computers to a switch and assign them to the same workgroup, you already have a working workgroup. In order to have a domain implemented, you 49 P a g e

50 would need to set-up a domain controller which is the computer that authenticates and users who wants to connect and provides them the resources that are afforded them. The domain controllers are also essential in adding an extra layer of security for the system beyond the normal usual security from individual computers which is what s available in workgroups. Although it is harder to implement a domain compared to a workgroup, it adds better scalability to the whole system which is essential for the expansion of businesses. Adding accounts or computers in a workgroup would mean that each computer needs to be configured for each account, this is time consuming and cumbersome especially when the computers number in the dozens. In a domain, the administrator can do all this on a single terminal in a very short time. Aside from scalability, domains are also very structured and you can assign what services or folders a specific account can access. This feature is not available in workgroups and anyone connected to the workgroup can access the same services and resources. DNS The domain name system (DNS) is the way that Internet domain names are located and translated into Internet Protocol addresses. A domain name is a meaningful and easyto-remember "handle" for an Internet address. Because maintaining a central list of domain name/ip address correspondences would be impractical, the lists of domain names and IP addresses are distributed throughout the Internet in a hierarchy of authority. There is probably a DNS server within close geographic proximity to your access provider that maps the domain names in your Internet requests or forwards them to other servers in the Internet. Before you start to configure your DNS, you must gather some basic information. Internic must approve some of this information for use on the Internet, but if you are configuring this server for internal use only, you can decide what names and IP addressestouse. You must have the following information: Your domain name (approved by Internic). The IP address and host name of each server that you want to provide name resolution for. Before you configure your computer as a DNS, verify that the following conditions are true: Your operating system is configured correctly. In the Windows Server 2003 family, the DNS service depends on the correct configuration of the operating system and its services, such as TCP/IP. If you have a new installation of a Windows Server 2003 operating system, then you can use the default service settings. You do not have to take additional action. 50 P a g e

51 You have allocated all the available disk space. All the existing disk volumes use the NTFS file system. FAT32 volumes are not secure, and they do not support file and folder compression, disk quotas, file encryption, or individual file permissions Install DNS 1. Open Windows Components Wizard. To do so, use the following steps: a. Click Start, click Control Panel, and then click Add or Remove Programs. b. Click Add/Remove Windows Components. In Components, select the Networking Services check box, and then click Details. InSubcomponents of Networking Services, select the Domain Name System (DNS) check box, clickok, and then click Next. If you are prompted, in Copy files from, type the full path of the distribution files, and then click OK. Configure DNS 1. Start the Configure Your Server Wizard. To do so, click Start, point to All Programs, point toadministrative Tools, and then click Configure Your Server Wizard. 2. On the Server Role page, click DNS server, and then click Next. 3. On the Summary of Selections page, view and confirm the options that you have selected. The following items should appear on this page: o Install DNS o Run the Configure a DNS Wizard to configure DNS If the Summary of Selections page lists these two items, click Next. If the Summary of Selectionspage does not list these two items, click Back to return to the Server Role page, click DNS, and then click Next. 4. When the Configure Your Server Wizard installs the DNS service, it first determines whether the IP address for this server is static or is configured automatically. If your server is currently configured to obtain its IP address automatically, the Configuring Components page of the Windows Components Wizard prompts you to configure this server with a static IP address. To do so: a. In the Local Area Connection Properties dialog box, click Internet Protocol (TCP/IP), and then click Properties. b. In the Internet Protocols (TCP/IP) Properties dialog box, click Use the following IP address, and then type the static IP address, subnet mask, and default gateway for this server. c. In Preferred DNS, type the IP address of this server. d. In Alternate DNS, type the IP address of another internal DNS server, or leave this box blank. e. When you finish setting up the static addresses for your DNS, click OK, and then click Close. After you click Close, the Configure a DNS Server Wizard starts. In the wizard, follow these steps: 51 P a g e

52 f. On the Select Configuration Action page, select the Create a forward lookup zone check box, and then click Next. g. To specify that this DNS hosts a DNS zone that contains DNS resource records for your network resources, on the Primary Server Location page, click This server maintains the zone, and then click Next. h. On the Zone Name page, in Zone name, specify the name of the DNS zone for your network, and then click Next. The name of the zone is the same as the name of the DNS domain for your small organization or branch office. i. On the Dynamic Update page, click Allow both nonsecure and secure dynamic updates, and then click Next. This makes sure that the DNS resource records for the resources in your network update automatically. j. On the Forwarders page, click Yes, it should forward queries to DNS servers with the following IP addresses, and then click Next. When you select this configuration, you forward all DNS queries for DNS names outside your network to a DNS at either your ISP or central office. Type one or more IP addresses that either your ISP or central office DNS servers use. k. On the Completing the Configure a DNS Wizard page of the Configure a DNS Wizard, you can click Back to change any of the settings. To apply your selections, click Finish. After you finish the Configure a DNS Wizard, the Configure Your Server Wizard displays the This Server is Now a DNS Server page. To review all the changes that you made to your server in the Configure Your Server Wizard or to make sure that a new role was installed successfully, click Configure Your Server log. The Configure Your Server Wizard log is located at %systemroot%\debug\configure Your Server.log. To close the Configure Your Server Wizard, click Finish. Installing domain controller Domain controllers provide network users and computers with the Active Directory service, which stores and replicates directory data and manages user interactions with the domain, including user logon processes, authentication, and directory searches. Every domain must contain at least one domain controller. You install a domain controller by installing Active Directory on any member or stand-alone server (except those with restrictive license agreements). When you install the first domain controller in your organization, you are creating the first domain (also called the root domain) and the first forest. You can add additional domain controllers to an existing domain to provide fault tolerance, improve service availability, and balance the load of existing domain controllers. You can also install a domain controller to create a new child domain or new domain tree. Create a new child domain when you want a new domain that shares a contiguous namespace with one or more domains. This means that the name of the new domain 52 P a g e

53 contains the full name of the parent domain. For example, sales.microsoft.com would be a child domain of microsoft.com. Create a new domain tree only when you need a domain whose Domain Name System (DNS) namespace is not related to the other domains in the forest. This means that the name of the new domain tree s root domain (and all of its children) does not contain the full name of the parent domain. A forest can contain one or more domain trees. Before installing a new domain controller, you will need to consider pre-windows 2000 compatible security levels and identify the DNS name of the domain. For more information, see Checklist: Creating an additional domain controller in an existing domain. The most commonly performed tasks when installing a domain controller are creating a new domain in a new forest, tree, creating, and adding a domain controller to an existing domain. To create a new domain in a new forest 1. Open the Active Directory Installation Wizard. 2. On the Domain Controller Type page, click Domain controller for a new domain, and then click Next. 3. On the Create New Domain page, click Domain in a new forest, and then click Next. 4. On the New Domain Name page, type the full DNS name for the new domain, and then click Next. 5. On the NetBIOS Domain Name page, verify the NetBIOS name, and then click Next. 6. On the Database and Log Folders page, type the location in which you want to install the database and log folders, or click Browse to choose a location, and then clicknext. 7. On the Shared System Volume page, type the location in which you want to install the Sysvol folder, or click Browse to choose a location, and then click Next. 8. On the DNS Registration Diagnostics page, verify if an existing DNS server will be authoritative for this forest or, if necessary, choose to install and configure DNS on this server by clicking Install and configure the DNS server on this computer, and set this computer to use this DNS server as its preferred DNS server, and then click Next. 9. On the Permissions page, select one of the following: Permissions compatible with pre-windows 2000 Server operating systems 53 P a g e

54 Notes Permissions compatible only with Windows 2000 or Windows Server 2003 operating systems 10. Review the Summary page, and then click Next to begin the installation. 11. Restart the computer. To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure. The server on which you perform this procedure will be promoted to the first domain controller in the forest root domain. The wizard options on the Permissions page affect application compatibility with pre-windows 2000 and Windows Server 2003 operating systems and are not related to domain functionality. The Active Directory Installation Wizard allows Active Directory domain names up to 64 characters or up to 155 bytes. Although the limit of 64 characters is usually reached before the limit of 155 bytes, the opposite could be true if the name contains Unicode characters consuming three bytes. These limits do not apply to computer names. To create a new child domain in an existing domain tree 1. Open the Active Directory Installation Wizard. 2. On the Domain Controller Type page, click Domain controller for a new domain, and then click Next. 3. On the Create New Domain page, click Child domain in an existing domain tree, and then click Next. 4. On the Network Credentials page, type the user name, password, and user domain of the user account you want to use for this operation, and then click Next. 5. On the Child Domain Installation page, verify the parent domain and type the new child domain name, and then click Next. 6. On the NetBIOS Domain Name page, verify the NetBIOS name, and click Next. 54 P a g e

55 Notes 7. On the Database and Log Folders page, type the location in which you want to install the database and log folders, or click Browse to choose a location, and then clicknext. 8. On the Shared System Volume page, type the location in which you want to install the Sysvol folder, or click Browse to choose a location, and then click Next. 9. On the DNS Registration Diagnostics page, verify the DNS configuration settings are accurate, and then click Next. 10. On the Permissions page, select one of the following: Permissions compatible with pre-windows 2000 Server operating systems Permissions compatible only with Windows 2000 or Windows Server 2003 operating systems 11. On the Directory Services Restore Mode Administrator Password page, type and confirm the password you want to assign to this server's Administrator account that will be used when the computer is started in Directory Services Restore Mode, and then click Next. 12. Review the Summary page, and then click Next to begin the installation. 13. Restart the computer. To perform this procedure, you must be a member of the Domain Admins group or the Enterprise Admins group in Active Directory, or you must have been delegated the appropriate authority. As a security best practice, consider using Run as to perform this procedure. For more information, see Default local groups, Default groups, and Using Run as. The server on which you perform this procedure will be promoted to the first domain controller in a new child domain. When a child domain is added to an existing tree domain, a two-way, transitive, parent and child trust is established by default. The wizard options on the Permissions page affect application compatibility with pre-windows 2000 and Windows Server 2003 operating systems and are not related to domain functionality. The Active Directory Installation Wizard allows Active Directory domain names up to 64 characters or up to 155 bytes. Although the limit of 64 characters is usually reached before the limit of 155 bytes, the opposite could be true if the name contains Unicode characters consuming three bytes. These limits do not apply to computer names. 55 P a g e

56 To create a new domain tree in an existing forest 1. Open the Active Directory Installation Wizard. 2. On the Domain Controller Type page, click Domain controller for a new domain, and then click Next. 3. On the Create New Domain page, click Domain tree in an existing forest. 4. On the Network Credentials page, type the user name, password, and user domain of the user account you want to use for this operation, and then click Next. 5. On the New Domain Tree page, type the full DNS name for the new domain, and then click Next. 6. On the NetBIOS Domain Name page, verify the NetBIOS name, and then click Next. 7. On the Database and Log Folders page, type the location in which to install the database and log folders, or click Browse to choose a location, and then click Next. 8. On the Shared System Volume page, type the location in which to install the Sysvol folder, or click Browse to choose a location, and then click Next. 9. On the DNS Registration Diagnostics page, verify if an existing DNS server will be authoritative for this forest or, if necessary, choose to install and configure DNS on this server by clicking Install and configure the DNS server on this computer, and set this computer to use this DNS server as its preferred DNS server, and then click Next. 10. On the Permissions page, select one of the following: Permissions compatible with pre-windows 2000 Server operating systems Permissions compatible only with Windows 2000 or Windows Server 2003 operating systems 11. On the Directory Services Restore Mode Administrator Password page, type and confirm the password you want to assign this server's Administrator account that will be used when the computer is started in Directory Services Restore Mode, and then click Next. 12. Review the Summary page, and then click Next to begin the installation. 13. Restart the computer. 56 P a g e

57 Notes To perform this procedure, you must be a member of the Domain Admins group or the Enterprise Admins group in Active Directory, or you must have been delegated the appropriate authority. As a security best practice, consider using Run as to perform this procedure. For more information, see Default local groups, Default groups, and Using Run as. The server on which you perform this procedure will be promoted to the first domain controller in a new domain tree. When a new domain tree is created in an existing forest, a two-way, transitive, tree root trust is established by default. The wizard options on the Permissions page affect application compatibility with pre-windows 2000 and Windows Server 2003 operating systems and are not related to domain functionality. The Active Directory Installation Wizard allows Active Directory domain names up to 64 characters or up to 155 bytes. Although the limit of 64 characters is usually reached before the limit of 155 bytes, the opposite could be true if the name contains Unicode characters consuming three bytes. These limits do not apply to computer names. To install an additional domain controller in an existing domain 1. Open the Active Directory Installation Wizard. 2. On the Domain Controller Type page, click Additional domain controller for an existing domain, and then click Next. 3. On the Network Credentials page, type the user name, password, and user domain of the user account you want to use for this operation, and then click Next. See Note below for more information. 4. On the Additional Domain Controller page, enter the full DNS name of the existing domain for which the server will become a domain controller, and then click Next. 5. On the Database and Log Folders page, type the location in which you want to install the database and log folders, or click Browse to choose a location, and then clicknext. 6. On the Shared System Volume page, type the location in which you want to install the Sysvol folder, or click Browse to choose a location, and then click Next. 57 P a g e

58 Notes 7. On the Directory Services Restore Mode Administrator Password page, type and confirm the password you want to assign to this server's Administrators account that will be used when the computer is started in Directory Services Restore Mode, and then click Next. 8. Review the Summary page, and then click Next to begin the installation. 9. Restart the computer. To perform this procedure, you must be a member of the Domain Admins group or the Enterprise Admins group in Active Directory, or you must have been delegated the appropriate authority. As a security best practice, consider using Run as to perform this procedure. For more information, see Default local groups, Default groups, and Using Run as. To create an additional domain controller from restored backup files, start the Active Directory Installation Wizard by typing dcpromo /adv at a command prompt. Uninstalling domain controller The procedures in this section describe the methods for removing a Windows Server 2008 or Windows Server 2008 R2 domain controller from a domain: Removing a domain controller by using the Windows interface Removing a domain controller by using an answer file Removing a domain controller by entering unattended installation parameters at the command line After AD DS is removed, the DNS server role remains installed and running if it was previously installed on the domain controller. But any Active Directory integrated DNS zones that were installed are removed. By default, the AD DS removal process also attempts to remove the Domain Name System (DNS) delegations for the zones that point to the domain controller. If the DNS server no longer serves any purpose after you remove AD DS, use Remove Roles Wizard to remove DNS server role. If you remove the DNS server role, you must reconfigure any DHCP scopes and DNS clients that resolved against this DNS server to use a suitable alternative (typically, another DNS server running on a domain controller within the same domain). 58 P a g e

59 Removing a domain controller by using the Windows interface You can use the Active Directory Domain Services Installation Wizard to remove a domain controller from an existing domain. Administrative credentials To perform this procedure, you must be a member of the Domain Admins group in the domain. To remove a domain controller by using the Windows interface 1. Click Start, click Run, type dcpromo, and then press ENTER. 2. On the Welcome to the Active Directory Domain Services Installation Wizard page, click Next. 3. If the domain controller is a global catalog server, a message appears to warn you about the effect of removing a global catalog server from the environment. Click OK to continue. 4. On the Delete the Domain page, make no selection, and then click Next. 5. If the domain controller has application directory partitions, on the Application Directory Partitions page, view the application directory partitions in the list, and then remove or retain application directory partitions, as follows: If you do not want to retain any application directory partitions that are stored on the domain controller, click Next. If you want to retain an application directory partition that an application has created on the domain controller, use the application that created the partition to remove it, and then click Refresh to update the list. 6. If the Confirm Deletion page appears, select the option to delete all application directory partitions on the domain controller, and then click Next. 7. On the Remove DNS Delegation page, verify that the Delete the DNS delegations pointing to this server check box is selected, and then click Next. 8. If necessary, enter administrative credentials for the server that hosts the DNS zones that contain the DNS delegation for this server, and then click OK. 9. On the Administrator Password page, type and confirm a secure password for the local Administrator account, and then click Next. 10. On the Summary page, to save the settings that you selected to an answer file that you can use to automate subsequent operations in Active Directory Domain Services (AD DS), click Export settings. Type a name for your answer file, and then click Save. Review your selections, and then click Next to remove AD DS. 59 P a g e

60 11. On the Completing the Active Directory Domain Services Installation Wizard page, click Finish. 12. You can either select the Reboot on completion check box to have the server restart automatically or you can restart the server to complete the AD DS removal when you are prompted to do so. 13. Open Server Manager. Click Start, point to Administrative Tools, and then click Server Manager. 14. In Roles Summary, click Remove Roles. 15. If necessary, review the information on the Before You Begin page, and then click Next. 16. On the Remove Server Roles page, clear the Active Directory Domain Services check box, and then click Next. 17. On the Confirm Removal Selections page, click Remove. 18. On the Removal Results page, click Close, and then click Yes to restart the server. Removing a domain controller by using an answer file To remove a domain controller in a domain where other domain controllers exist requires only Domain Admin credentials. You can also create the password for the local Administrator account for the member server. If you do not specify the password in the answer file, the administrator password is blank. If you are removing AD DS permanently, uninstall the AD DS server role binaries from the server after you remove AD DS from the domain controller. To remove the AD DS server role binaries, use the dcpromo /uninstallbinaries command. Administrative credentials To perform this procedure, you can use any account that has Read and Write credentials for the text editor application. To create an answer file for removing a domain controller 1. Open Notepad or any text editor. 2. On the first line, type [DCINSTALL], and then press ENTER. 3. Create the following entries, one entry on each line. For a complete list of parameters for removing AD DS, see Demotion Operation or type dcpromo /?:Demotion at a command line. username=<administrative account in the domain> 60 P a g e

61 userdomain=<domain name of the administrative account> password=<password for the account in UserName> administratorpassword=<local administrator password for the server> removeapplicationpartitions=yes removednsdelegation=yes DNSDelegationUserName=<DNS server administrative account for the DNS zone that contains the DNS delegation> DNSDelegationPassword=<Password for the DNS server administrative account> 4. Save the answer file to the location on the installation server from which it is to be called by dcpromo, or save the file to a network shared folder or removable media for distribution. Administrative credentials To remove a domain controller, you must be a member of the Domain Admins group. To remove a domain controller by using an answer file At an elevated command prompt, type the following command, and then press ENTER: dcpromo /unattend:"<path to the answer file>" Removing a domain controller by entering unattended installation parameters at the command line You can run dcpromo /unattend command on a domain controller to perform an unattended removal of AD DS. If you are removing AD DS permanently, uninstall the AD DS server role binaries from the server after you remove AD DS from the domain controller. To remove the AD DS server role binaries, use the dcpromo /uninstallbinariescommand. For a complete list of parameters for removing AD DS, see Demotion Operationor type dcpromo /?:Demotion at a command line. To remove a domain controller by using the command line At an elevated command prompt, type the following command, and then press ENTER: dcpromo /unattend /username:<domain admin> /userdomain:<domain> /password:<da password> /administratorpassword:<local admin password> 61 P a g e

62 Where: domain admin is the name of an account that is a member of the Domain Admins group. domain is the name of the domain for the domain controller. DA password is the password for the account that is a member of the Domain Admins group. local admin password is the password that will be used for the local administrator account on the server after AD DS is removed. The following example removes a domain controller from a domain named contoso.com, removes the AD DS server role binaries, and sets the local administrator password to p@$$w0rd: dcpromo /unattend /username:da1 /userdomain: contoso.com /password: DA1_password /administratorpassword: p@$$w0rd Connecting client to domain controller One of the first major tasks a domain member computer has to do when it starts is to locate a domain controller. Generally, this task requires the use of a Domain Name System (DNS) server, which contains records for each domain controller in the domain, and the Locator, a remote procedure call to the computer's local Net logon service. Starting Up When the client computer starts, its Net logon service starts automatically (in the default configuration). This service implements the DsGetDcName application programming interface (API), which is used to locate a domain controller the client begins by collecting a number of pieces of information that will be used to locate a domain controller. This information includes the client's local IP address, which is used to determine the clients Active Directory site membership, the desired domain name, and a DNS server address. Finding the Domain Controllers Net logon then queries the configured DNS server. Net logon retrieves the service resource (SRV) records and host (A) records from DNS that correspond to the domain controllers for the desired domain. The general form for the queried SRV records is _service._protocol.domainname, where service is the domain service, protocol is the TCP/IP protocol, and domainname is the desired Active Directory fully qualified domain name (FQDN). For example, because Active Directory is a Lightweight Directory Access Protocol (LDAP)-compliant directory service, clients query for _ldap._tcp.domainname (or or _ldap._tcp.dc._msdcs.domainname when locating the nearestdomain controller). 62 P a g e

63 Each domain controller in a domain will register its host name with the SRV record, so the client's query results will be a list of domain controller host names. The client also retrieves the associated A records, providing the client with the IP address of every domain controller in the domain. The client then sends an LDAP search query, via the User Datagram Protocol (UDP), to each domain controller. Selecting a Domain Controller After the client locates a domain controller, the client uses LDAP to access Active Directory on a domain controller, preferably one in the client?s own subnet. The domain controller uses the client's IP address to identify the client's Active Directory site. If the domain controller is not in the closest site, then the domain controller returns the name of the client's site, and the client tries to find a domain controller in that site by querying DNS. If the client has already attempted to find a domain controller in that site, then the client will continue using the current, nonoptimal domain controller. Once the client finds a domain controller it likes, it caches that domain controllers information,and the client will continue to use that domain controller for future contacts (unless the domain controller becomes unavailable). Concept network mapping Network mapping, otherwise known as Internet mapping, is a group of tasks used to study Internet connectivity and determine how network systems are operated. In effect, network mapping develops visual materials that can be used for a large variety of purposes, ranging from business to national security. Network mapping makes use of software to identify operating systems and other technical information, but can also provide a better overall understanding of how different networks operate. Basic network mapping tasks include flow charts, network diagrams, and device inventories. More advanced techniques, such as active probing, can be used to create network maps and to analyze the network and its processes further. Active probing gathers information on the system by sending probe packets into the network. After probes are released, they report back information on the IP details of the network. This information can be used to determine how the networks operate, which can then be used to map the system. Networks are now a fast growing system even outside the corporate world, making network mapping such a valuable concept. These networks tend to be overwhelmingly complex, however, especially as they grow larger and involve different devices and connections. Network mapping deciphers these complex networks and breaks them down into segments that are more easily understandable. As mapping takes place, network systems can be visualized to communicate how the network operates. The utilization of network mapping does have its downsides. Setting up a network mapping system can be burdensome in itself, and the keeping the system running 63 P a g e

64 properly can be even more toiling. Without proper maintenance, the network map will not be effective if new devices or connections are added. Network mapping tools can be extremely important when placing the system into effect. The range of software that can be implemented includes both open-source and commercial software. Some programs use less automation, whereas others may require less effort. For network engineers, mapping is conducted without the need for automation. Network mapping tools that are automated usually incorporate network discovery methods to construct network maps. In terms of business, network mapping is used to create comprehensive maps of the Internet business network. Network mapping creates a visualization of the network. It shows relationships between devices throughout the network that, afterwards, can be used to better understand and analyze the system. Manual mapping and Auto mapping Remote desktop sharing We have more than 250 users with 7 branches; It was a difficult task to support those users desktop by a limited number of technicians; Using Desktop Central it has become easy to support the users throughout head office and branches for trouble shooting or software installation- it is like instant support to the users which helped our IT department keeping our users smiling.now we can support our users instantly wherever they are in Head office, branch office or in roaming Desktop Sharing enables the administrators to connect and control remote Windows desktops in the LAN and WAN. Accessing computers at a remote location in WAN can be either through VPN or through Internet. It is a web-based tool enabling access from anywhere in the LAN without requiring any native client. It allows almost all operations to be performed on the remote desktop. Desktop Sharing Features Access computers in LAN and WAN. Web-based tool enables access from anywhere in the LAN. Automatically installs the desktop-sharing agent in each desktop. No individual authentication is required to gain access to a remote desktop. Supports viewing/accessing remote desktops using Active X and Java Plug-ins. Prompts user confirmation before providing the access to a remote desktop. Supports locking the users keyboard and mouse when 64 P a g e

65 accessing from remote. Users screen can also be blacked out so that they are not aware of the changes you make. Ability to send "Cnt+Alt+Del" command to access a locked computer. Ability to switch between users' applications using "Alt+Tab" command. Ability to remotely transfer files across machines. Usage of 128-bit Advanced Encryption Standard (AES) encryption protocols during Remote Control operations. Multi-Monitor Support with easy switching options. Configurable screen resolution to fit the screen size. Web-Based Remote Control Desktop Central provides a web-based access to the remote computers. This means that a remote connection can be established from anywhere and does not require client software to be installed in order to access remote desktops. The administrators can also establish connection through a VPN to take control of a remote desktop. Protects Users' Privacy When connecting to remote computers using Remote Desktop Sharing, the adminstrators have an option to whether get user's permission before connecting to their desktop. Selecting this option would pop up a request window in the user's desktop seeking remote access. This is to ensure that the user's privacy is maintained. ActiveX and Java Viewers Desktop Central supports accessing a remote desktop either using ActiveX or Java plug-ins. This enables accessing a remote desktop from any browser like Internet Explorer, Firefox, Flock, etc. Remote File Transfer Desktop Central allows you to remotely access desktops and transfer files between them. The Remote Desktop Sharing mechanism supports remote login to any desktop in your network by any user account that has Remote Control privileges. Files can be transferred across domains and workgroup machines via the Active-X Viewer and Java viewers. And the entire process is Fast, Reliable, and Secure. 65 P a g e

66 Multi-Monitor Support In case you are connecting to a remote machine that has more than one monitor, the Desktop Central Remote Control options will automatically detect this configuration and displays it on the ActiveX tool bar. Further, the user can select a particular monitor that is associated with a remote machine individually and this will be displayed over the Remote Control session that is established. Multi-Monitors are especially useful when you need to troubleshoot a remote machine in a collaborative manner. Desktop Central's dual monitor support facilitates easy remote control set up and easy switching options between the primary and secondary monitors. Desktop Sharing - Supported OS Versions Desktop Sharing supports connecting to desktops running any of the following OS versions: Windows 2008 Windows Vista Windows 7 Windows 2003 Windows XP Windows Web connectivity through log main Remote access may well be the greatest innovation in computing since the mouse. Unfortunately, the remote access configuration process is daunting. Everything from antivirus programs to flaky modems to firewalls can single-handedly derail remote connection attempts. Remote connection alternatives try to overcome these obstacles with ease of use and tighter security. One of the most popular options is LogMeIn. Erik Eckel explains how to configure LogMeIn Pro s features and maximize the usefulness of this remote connectivity platform. Even if your entire network infrastructure is configured to properly recognize and pass remote access traffic, simply forgetting to enable Windows Remote Desktop connections, supply a password with a Windows XP user account, or configure a user s server-based account settings to permit remote access results in failure and frustration. Worse, trying to print information from a remote workstation on a local printer is fraught with peril. Microsoft claims its RDP implementation supports passing the required print drivers between platforms, but it usually doesn t work. If it did work well, why would Microsoft be touting the 2008 server platform s TS Easy Print as such an important new feature? 66 P a g e

67 For all these reasons, remote connection alternatives thrive. LogMeIn s free software provides a simple method of connecting to a remote workstation or server from any Internet connected system. LogMeIn Pro, meanwhile, adds secure connections, remote printing support, and simplified file transfer to the mix. Here s how to configure LogMeIn Pro s features and maximize the usefulness of this remote connectivity platform. This blog post is also available as a TechRepublic download. Create an account The first step in using LogMeIn is creating an account. Simply visit and create an account using the provided link. The next step, after creating an account, is to load the LogMeIn Pro software on the computer you wish to access remotely. LogMeIn installation Install LogMeIn Pro by selecting that option (the LogMeIn Pro link) from LogMeIn s Web site (from the PC you wish to serve as the remote access host). When you create a new LogMeIn account, the option is automatically presented. (You ll be instructed to click the Add Computer link.) (Figure A) Figure A Click the Add Computer link when creating an account to install LogMeIn Pro on the workstation or server you wish to serve as the remote access host machine. Upon clicking Add Computer, the LogMeIn software will begin downloading. The program is approximately eight megabytes in size, so depending upon your Internet connection, the process should take only a few moments. 67 P a g e

68 When the software has downloaded, you can run the installation program. The LogMeIn setup program will appear, as shown in Figure B. Figure B The LogMeIn setup program walks you through installing the remote connectivity software. After accepting the license agreement, you can choose either a Typical or Custom installation. When choosing the Custom option, the next screen you ll see provides you with the opportunity to name the system. This is the name that will appear when you attempt to connect to the system remotely. The rest of the Custom installation enables specifying proxy settings (if necessary) and the destination installation folder. When the installation program completes, a menu will appear indicating LogMeIn is enabled and online (Figure C). An icon also appears within the Windows System Tray (Figure D). At this point, the system can be accessed remotely by any user knowing the LogMeIn user account name and password. No firewall ports require configuration, nor do server account settings need to be updated to enable remote access. 68 P a g e

69 Figure C LogMeIn confirms it is enabled and online upon completing installation. Figure D LogMeIn also adds an icon to the Windows System Tray. Connect to a remote LogMeIn-enabled system To connect to the remote system on which you ve installed LogMeIn Pro, enter in the address bar of the computer s Web browser. On the LogMeIn home page, supply your LogMeIn username ( address) and password and click the Log Me In button (Figure E). 69 P a g e

70 Figure E Users can, from any Internet connected system, remotely access any PC or server with LogMeIn installed on it. The PC or server upon which you installed and enabled the LogMeIn software will appear (Figure F). 70 P a g e

71 Figure F LogMeIn-enabled PCs and servers associated with your LogMeIn account appear on the My Computers page. Click the link for the system to which you wish to connect. You ll see a screen indicating that LogMeIn is connecting to that remote system. Next, you ll see a login screen for the remote Windows system. Here, you need to enter a username, password, and domain for a valid account on the system to which you re connecting (Figure G). 71 P a g e

72 Figure G Once LogMeIn connects you to the remote system, you still must log in to the remote system as if you were sitting in front of it. Once you ve successfully logged on to the remote system (by supplying a valid user account and password) the connection will be complete. As you can see in Figure H, the LogMeIn Pro software will present you with six options: 1. Remote Control 2. File Manager 3. Guest Invite 4. File Share 5. Preferences 6. Help 72 P a g e

73 Figure H LogMeIn Pro presents users with these six options. Each of these items provides its own features and optional settings. Let s explore each individually. Remote Control Selecting Remote Control opens the remote system and displays its desktop. While completing the connection, LogMeIn Pro redirects print jobs to your local default printer automatically. A menu appears providing three options: Connect My Default Printer To The Remote Computer, Synchronize My Clipboard With The Remote Computer, and Remember SYSTEMNAME And Don t Display This Dialog Again. Select (or clear) any of the check boxes as required. Upon clicking Proceed, LogMeIn will display the remote system s desktop (Figure I). You can then control the remote system as if you were physically seated in front of it. 73 P a g e

74 Figure I LogMeIn Pro shares data with remote systems via a secure 256-bit encrypted connection. Several options enable customizing the remote control session. Users can select color quality, choose whiteboard or laser pointer mode, choose to match screen resolutions between connected systems, fit the remote window to the current window, or view the remote system actual size. All those options are accessible from the View menu. Full Screen and Connect Drives (for simplifying the sharing of files between the two systems) buttons also appear at the top of the Remote Control window. Should you need to perform a Ctrl+Alt+Del keystroke combination on the remote system, LogMeIn supplies a button for that, as well (Figure J). 74 P a g e

75 Figure J LogMeIn Pro s toolbars present numerous options for customizing the remote desktop display. Clicking the More button from LogMeIn s menu bar displays a second toolbar. From the second toolbar, users can specify the remote screen size in pixels, set the zoom value, and open a chat session for connected guests. Guest Invite Using LogMeIn Pro s Guest Invite feature, LogMeIn Pro subscribers can invite specific individuals to temporarily access the PC or server s desktop. Note that for this feature to work, the user must be seated at the host system. File Manager Selecting File Manager opens a new LogMeIn Pro window. That window features two columns, one for the current system and a second window listing the remote system s files and folders. Exchanging files between the two systems is as simple as dragging and dropping the files between the two windows (Figure K). 75 P a g e

76 Figure K LogMeIn Pro s File Manager makes quick work of remotely exchanging files between two systems. File Share LogMeIn Pro s File Share feature enables sharing files with specific contacts. The feature works by creating a secure link to files on the remote system. That secure link can then be shared with contacts with whom you wish to share files. In addition to creating the secure link, LogMeIn Pro users can specify that users receive a certain number of downloads or provide a timeframe within which the files must be accessed. Preferences Using the Preferences menu, users can customize Remote Control sessions, Security Settings, Network Settings, Log Settings, Reboot Options, and Advanced Options (Figure L). Among the Remote Control session settings that can be customized are general settings (such as enabling guest invitations), security (such as disabling host keyboard and mouse, blanking the host s monitor, and locking the console if the session is broken), visible and audible notification (alarm beeps for alerting the user when remote 76 P a g e

77 control sessions start or end), interactive user s permission (such as requiring a remote user to approve the remote connection request), remote printing, and drive connection. Simple check boxes are provided for enabling (or disabling) each clearly listed feature. Security settings that can be customized include access controls (defining or editing user-specific permissions), changing the Windows system password, preventing specific IP addresses from connecting to the host, filtering IP addresses, logs, SSL setup, and personal passwords. File transfer limits, bandwidth restrictions, and idle time settings are configured from within Network Settings, as are proxy settings. Among the Log Settings that can be configured are the number of days for which log files should be kept, system log parameters (for sending log files to a Syslog server) and remote control recording (LogMeIn Pro can create video files of remote sessions). From the Reboot menu, users can opt to restart the LogMeIn session. Users can also choose to reboot the remote system normally. Should a program have locked up, users also have a hard reboot option (and even an emergency reboot alternative) available in which Windows isn t permitted to gracefully shut down. Instead, these reboots force Windows to restart as if the reset button were physically depressed on the front of the remote host computer. Further reboot options include a safe-mode reboot (in which Windows starts in Safe Mode with Networking Enabled) and a reboot scheduled for a specific time. Advanced Options available to LogMeIn Pro users include disabling HTML-based remote control, disabling HTML content compression and customizing specific log on messages. The default language settings are also configured from within the Advanced Options menu. 77 P a g e

78 Figure L LogMeIn enables users to customize numerous session settings. Help From the Help menu, LogMeIn provides a Getting Started guide designed to quickly bring new users up to speed using the remote connectivity software. There s also an online user manual, as well as more information on the software license. Customer support and feedback links are provided within the application s Help menu. Using net meeting What is Net meeting? Net meeting is a conferencing client developed by Microsoft that allows users to interact in real time over the internet. Most people call it a "video conferencing client", but it is actually capable of much more than that. It includes: A Chat client, similar to AOL Instant Messenger 78 P a g e

79 An Audio and Video conferencing client A Whiteboard, which is a shared drawing space where people can collaborate in real time. Application Sharing, where you can choose to share an application you are running with others in your conference. Note here that while other users will need to have Net meeting installed, they do not need to have a copy of the application you are sharing installed. A file transfer application for sending files What Do I Need? A PC running a Windows variant, such as Windows 95, Windows 98, Windows NT 4.0, Windows 2000 or Windows XP. You should have Internet Explorer 4.0 or better installed as well. Note that Windows XP and 2000 come with Net meeting already installed. The PC should a reasonably current machine, such as a Pentium II 233 MHZ or better. A slower machine may work, but audio and video performance will suffer. It should have a decent amount of Ram (64 MB or better). A sound card is not mandatory, but for audio conferencing, some sort of audio interface is necessary. Net meeting uses the Videoconferencing standard.h323. There are other products that use this standard as well, including a solution for Macintosh users. See the section "For Mac Users" at the end. A Microphone and Headphones If you want to participate in an audio conference, you need a microphone. You need not spend a lot of money. A inexpensive SoundBlaster compatible (this is important) microphone (less than $10.00) and a inexpensive pair of headphones (like the kind that can be used with a Walkman) is all you need. You can also opt for a headset that has the microphone built in; this is all a matter of preference. Using headphones instead of a pair of speakers is preferred, since the microphone will pick up what is coming over the speakers, and will lead to a strange and disconcerting "echo" effect. A Network connection While it is possible to use some functions in NetMeeting with a 56k modem, a faster network connection is preferable. For Video or screen sharing, use at least a Dual ISDN connection (112 kbs). A Cable Modem or DSL connection is perfectly adequate for any of the features in NetMeeting when at home. Most campuses have at least 10 mb/s connections, which is good enough to do decent low frame rate video and good audio, as well as all the other features in NetMeeting. 79 P a g e

80 There are some additional issues concerning use of NetMeeting iin special situations, such as with a firewall, or through a home networking router. A brief outline on the issues is being written, and will appear shortly. The Software You will need the Netmeeting software itself. If you are currently running Windows 2000 or XP, you do not need to install it; it comes with the standard install. Under Windows XP, you may need to "unhide Netmeeting to launch it directly: Go to your Start menu and select "run". Type in "conf.exe" (no quotes). The Netmeeing setup wizard will then start, and ask you whether you would like shortcuts created (yes you do). For Windows 2000, look in your Start menu under Accessories/Communication to launch it. You should also confirm that you have at least version 4.0 of Internet Explorer installed. You can get the latest version of Internet Explorer at: Otherwise, you will need to download it. Microsoft's main NetMeeting page is at: and the link to download it is at: It's also recommended (but not necessary) that you install MSN messenger. Messenger is an "instant messaging" application, similar to AOL instant messenger, which allows people to chat online. MSN Messenger is particularly useful as it makes it very easy for two people to "find" each other online, and set up a NetMeeting Conference. You will need to set up a "Passport" (better known as User ID) for yourself via MSN's site, but it costs nothing, and you get an additional account as a bonus. You can get MSN Messenger at: After you get everything set up, you should ask other folks that you want to "NetMeet" with what their MSN userid is. You can add those into your MSN Messenger application, and when you are online, it will let you see if your friends are online, as well as let them see if you are online. This makes setting up a NetMeeting session very simple. 80 P a g e

81 Getting Started via a conferencing server We are running a test Conferencing server that we will be using as the primary way to meet online. When you first run NetMeeting, you will need to set it up. This is very straighforward. Pay close attention if it asks you for your connection speed -- this is important, and may prevent you from seeing a conference. If it asks you during the install whether or not you want to log into a directory server on startup, you may want to say "No", especially if you have not set up a MSN Passport. It is recommended that you make the following changes to your setup. First, select "Options" under the "Tools" menu: You should start with these settings. Note it is not necessary to put "kvetch.nrrc.ncsu.edu" in your directory field since we are not logging into a directory. Please put your name in the right fields, though. This is how others will idenify you. 81 P a g e

82 Starting a Netmeeting via MSN Messenger To set up a NetMeeting Session, you should first log in via MSN Messenger, to let others know that you are available. MSN Messenger installs a little icon in your system tray, on the far right hand side. It looks like a little group of people (sorry, working on a screen shot that will be included shortly). Click on it, and log in. After a few moments, you will have a dialog that will list yourself, and any other people that you can added to your list of favorites. If they are online, they will be highlighted; double clicking on them will bring up a chat session, where you can chat via text. You can then invite a person to a NetMeeting session. Look under the "Tools" menu, and select "Send an Invitation" using Netmeeting. The other person will be notified that you have invited them. After they accept the invitation, the session will begin. 82 P a g e

83 How to Use Netmeeting Netmeeting is a program available on your computer that lets you communicate with other people. When on campus, you can "netmeet" with anyone else on the campus network. Among other things, you can show someone else what is on your computer, and you can see what is on their's. With a telephone, it works great to ask and answer questions about your computer. I. Where is Netmeeting? You can find Netmeeting from your Start Button. (Click on it.) Then, go to "Programs" > "Accessories" > "Communications" > "Netmeeting". II. How can I make a call? When you have finished initializing the program (see box on left), you will get a program running that looks like the one above. To make a call, type the username of who you want to netmeet with. For example, to call Andy Heiser, type "heiser" in the top box. 83 P a g e

84 Whoever you call needs to have started Netmeeting on their computer. In "Tools" > "Options" you can set Netmeeting to start automatically whenever you turn on your computer. III. How can I show someone my computer screen? To show someone your computer screen, click the button in the lower left corner. Then, choose "Desktop", and click "Share". IV. How can I allow someone to take control of my computer? To allow someone to take control of your computer, click the button in the lower left corner. Then, choose "Desktop", and click "Allow Control". You can re-gain control at any time by pressing any key. 84 P a g e

85 Creating Local users and groups Unit- 3 In a Windows server environment, it is very important that only authenticated users are allowed to log in for security reasons. To fulfill this requirement the creation of User accounts and Groups is essential. User Accounts In Windows Server 2003 computers there are two types of user accounts. These types are local and domain user accounts. Thelocal user accounts are the single user accounts that are locally created on a Windows Server 2003 computer to allow a user to log on to a local computer. The local user accounts are stored in Security Accounts Manager (SAM) database locally on the hard disk. The local user accounts allow you to access local resources on a computer On the other hand the domain user accounts are created on domain controllers and are saved in Active Directory. These accounts allow to you access resources anywhere on the network. On a Windows Server 2003 computer, which is a member of a domain, you need a local user account to log in locally on the computer and a domain user account to log in to the domain. Although you can have a same login and password for both the accounts, they are still entirely different account types. You become a local administrator on your computer automatically because local computer account is created when a server is created. A domain administrator can be local administrator on all the member computers of the domain because by default the domain administrators are added to the local administrators group of the computers that belong to the domain. This article discusses about creating local as well as domain user accounts, creating groups and then adding members to groups. To create a local user account: 1. Log on as Administrator, or as a user of local administrator group or Account Operators local group in the domain. 2. Open Administrative Tools in the Control Panel and then click Computer Management, as shown in Figure 85 P a g e

86 3. Click Users folder under Local Users and Groups node, as shown in Figure. 4. Right-click Users and then click New User in the menu that appears, as shown in Figure 3: 86 P a g e

87 The New User dialog box appears as shown below in Figure 5. Provide the User name and the Password for the user in their respective fields. 6. Select the desired password settings requirement. Select User must change password at next logon option if you want the user to change the password when the user first logs into computer. Select User cannot change password option if you do not want the user to change the password. Select Password never expires option if you do not want the password to become obsolete after a number of days. Select Account is disabled to disable this user account. 7. Click Create, and then click Close: 87 P a g e

88 The user account will appear on clicking Users node under Local Users and Groups on the right panel of the window. You can now associate the user to a group. To associate the user to a group, you need to: 8. Click Users folder under Local Users and Groups node. 9. Right-click the user and then select Properties from the menu that appears, as shown in Figure. 88 P a g e

89 10. Click Member of tab. The group(s) with which the user is currently associated appears. 11. Click Add. The Select Groups dialog box appears, as shown in Figure P a g e

90 12. Select the name of the group/object that you want the user to associate with from the Enter the object names to select field. If the group/object names do not appear, you can click Advanced button to find them. Also if you want to choose different locations from the network or choose check the users available, then click Locations or Check Names buttons. 13. Click OK. The selected group will be associated with the user and will appear in the Properties window of the user, as shown in Figure Adding users to group Just like user accounts, the groups on a Windows Server 2003 computer are also of two types, the built in local groups and built in domain groups. The example of certain built in domain groups are: Account Operators, Administrators, Backup Operators, Network Configuration Operators, Performance Monitor Users, and Users. Similarly certain built in local groups are: Administrators, Users, Guests, and Backup operators. 90 P a g e

91 The built in groups are created automatically when the operating system is installed and become a part of a domain. However, sometimes you need to create your own groups to meet your business requirements. The custom groups allow you limit the access of resources on a network to users as per your business requirements. To create custom groups in domain, you need to: 1. Log on as Administrator and open Active Directory Users and Computers MMC from the Administrative Tools in Control Panel, as shown in Figure Right-click the OU and select New->Group from the menu that appears. The New Object Group dialog box appears, as shown in Figure Provide the name of the group in the Group name field. The group name that you have provided will appear in the Group name (pre-windows 2000) field to ensure that group is functional on domain computers that are using earlier versions of Windows such as Windows NT. 4. Select the desired group scope of the group from the Group scope options. If the Domain Local Scope is selected the members can come from any domain but the members can access resources only from the local domain. If Global scope is selected then members can come only from local domain but can access resources in any domain. If Universal scope is selected then members can come from any domain and members can access resources from any domain. 5. Select the group type from the Group Type options. The group type can be Security or Distribution. The Security groups are only used to assign and gain permissions to access resources and Distribution groups are used for no-security related tasks such as sending s to all the group members. 91 P a g e

92 6. Click OK. You can add members to group just as you add groups to members. Just right-click the group in Active Directory Users and Computers node in the Active Directory Users and Computers snap-in, select Properties, click Members tab from the Properties window of the group and then follow the steps from from Creating Local User Accounts section. Assigning rights to the users- configuring local security rights Configuring User Rights Although the built-in capabilities for accounts cannot be changed, user rights for accounts can be administered. These rights authorize users to perform specific actions, such as logging on to a system interactively or backing up files and directories. User rights are different from permissions because they apply to user accounts, whereas permissions are attached to objects. Keep in mind that changes made to user rights can have a far-reaching effect. Because of this, only experienced administrators should make changes to the user rights policy. Microsoft defines user rights in two types of categories: Logon Rights and Privileges. These are defined as follows: Logon Right: A user right that is assigned to a user and that specifies the ways in which a user can log onto a system. An example of a logon right is the right to log on to a system remotely. 92 P a g e

93 Privilege: A user right that is assigned to a user and that specifies allowable actions on the system. An example of a privilege is the right to shut down a system. User rights define capabilities at the local level. Although they can apply to individual user accounts, user rights are best administered on a group account basis. This ensures that a user logging on as a member of a group automatically inherits the rights associated with that group. By assigning rights to groups rather than individual users, user account administration can be simplified. When users in a group all require the same user rights, they can be assigned the set of rights once to the group, rather than repeatedly assigning the same set to each individual user account. User rights that are assigned to a group are applied to all members of the group while they remain members. If a user is a member of multiple groups, the user's rights are cumulative, which means that the user has more than one set of rights and privileges. The only time that rights assigned to one group might conflict with those assigned to another is in the case of certain logon rights. For example a member of multiple groups who is given the "Deny Access to This Computer from the Network" logon right would not be able to log on despite the logon rights granted to the user by other groups. The user would be logged on locally with cached credentials, but when attempting to access the domain resources would receive the following message: In general, however, user rights assigned to one group do not conflict with the rights assigned to another group. To remove rights from a user, the administrator simply removes the user from the group. In this case, the user no longer has the rights assigned to that group. Assigning User Rights User rights are assigned through the Local Policies node of Group Policy. As the name implies, local policies pertain to a local computer. However, local policies can be configured and then imported into Active Directory. Local policies can also be 93 P a g e

94 configured as part of an existing Group Policy for a site, domain, or organizational unit. When this is done, the local policies will apply to computer accounts in the site, domain, or organizational unit. User rights policies can be administered as follows: 1. Log on using an administrator account. 2. Open the Active Directory Users and Computers tool. 3. Right-click the container holding the domain controller and click Properties. 4. Click the Group Policy tab, and then click Edit to edit the Default Domain Policy. 5. In the Group Policy window, expand Computer Configuration, navigate to Windows Settings, to Security Settings, and then to Local Policies. 6. Select User Rights Assignment. Note: All policies are either defined or not defined. That is, they are either configured for use or not configured for use. A policy that is not defined in the current container could be inherited from another container. 7. To configure user rights assignment, double-click a user right or right-click on it and select Security. This opens a Security Policy Setting dialog box. 94 P a g e

95 For a site, domain, or organizational unit, individual user rights can be configured by completing the following steps: 8. Open the Security Policy Setting dialog box for the user right to be modified. 9. Select Define these policy settings to define the policy. 10. To apply the right to a user or group, click Add. 11. In the Add user or group dialog box, click Browse. This opens the Select Users Or Groups dialog box. The right can now be applied to users and groups. The following selection options appear on the Select Users Or Groups box: Name: The Name column shows the available accounts of the currently selected domain or resource. Add: Add selected names to the selection list. Check Names: Validate the user and group names entered into the selection list. This is useful if names are typed in manually and it is necessary ensure that they're actually available. 1. To access account names from other domains, click the Look In list box. A drop-down list will appear that shows the current domain, trusted domains, and other resources that can be accessed. Select Entire Directory to view all the account names in the directory. 95 P a g e

96 Note: Only domains that have been designated as trusted are available in the Look In drop-down list. Because of the transitive trusts in Windows 2000, this usually means that all domains in the domain tree or forest are listed. A transitive trust is one that is not established explicitly. Rather, the trust is established automatically based on the forest structure and permissions set in the forest. 2. After selecting the account names to add to the group, click OK. The Add user or group dialog box should now show the selected accounts. Click OK again. 3. The Security Policy Setting dialog box is updated to reflect the selections. If a mistake is made, select a name and remove it by clicking Remove. 96 P a g e

97 4. When finished granting the right to users and groups, click OK. Configuring Local User Rights For local computers, such as Windows 2000 Professional, apply user rights by completing the following steps: 1. Log in as Administrator. 2. Open Start, point to Programs, point to Administrative Tools, and then click Local Security Policy. 3. In the Local Security Settings window, navigate to Local Policies, and then select User Rights Assignment. 4. To configure user rights assignment, double-click a user right or right-click on it and select Security. This opens a Security Policy Setting dialog box. The effective policy for the computer is displayed, but it cannot be changed. However, the local policy settings can be adjusted. Use the fields provided to configure the local policy. Remember that site, domain, and organizational unit policies have precedence over local policies. 97 P a g e

98 5. The Assigned To column shows current users and groups that have been given a user right. Select or clear the related check boxes under the Local Policy Setting column to apply or remove the user right. 6. Apply the user right to additional users and groups by clicking Add. This opens the Select Users Or Groups dialog box. Local users and groups can now be added. 7. To access account names from the domain, click the Look In list box. There should be a list that shows the current machine, the local domain, trusted domains, and other resources that can be accessed. Select the local domain to view all the account names in the domain. Using NTFS permissions When using share permissions and NTFS permissions together, if there is a conflict in the configuration, the most restrictive permission prevails. For example, if a user has NTFS full access to a specific file in a folder that is not shared, the user cannot access the file from the network. In this case, the user can sit down at the computer that contains the file, log in and access the file, because sharing permissions do not affect local access. One strategy for providing access to resources on an NTFS volume is to share folders with the default shared folder permissions and then control access to shared folders by assigning NTFS permissions. When you share a folder on an NTFS volume, both shared folder permissions and NTFS permissions combine to secure file resources. Shared folder permissions provide limited security for resources. You gain the greatest flexibility by using NTFS permissions to control access to shared folders. Also, NTFS permissions apply whether the resource is accessed locally or over the network. When you use shared folder permissions on an NTFS volume, the following rules apply: 98 P a g e

99 You can apply NTFS permissions to files and subfolders in the shared folder. You can apply different NTFS permissions to each file and subfolder that a shared folder contains. In addition to shared folder permissions, users must have NTFS permissions for the files and subfolders that shared folders contain to gain access to those files and subfolders. When you combine shared folder permissions and NTFS permissions, the more restrictive permission is always the overriding permission. Planning The first step is planning how folders will be shared. To do this, make a list of what data will be stored and what user groups will require access. For example, types of data may be employee data, customer account status data, customer service data, management guideline data, and so on. Groups of users may be managers, administrators, sales reps, customer service reps, and so on. Create a table with three columns: Column 1 displays each data folder by name and location Column 2 displays the shared folder name Column 3 displays the name of the user group with assigned folder permissions File and Printer Sharing for Microsoft Networks To share any folders or other network objects, you must have File and Printer Sharing for Microsoft Networks as a networking component in your local area connection. To add this component: 1. In the Windows System Tray, right-click the Local Area Connection icon and choose Status from the context menu. The Local Area Connection Status dialog box appears. 2. Click Properties. The Local Area Connection Properties dialog box appears. 99 P a g e

100 Figure 6 Local Area Connection Properties dialog box 1. To add the File and Printer Sharing for Microsoft Networks check box, click Install and choose it from the Services category. 2. Select the File and Printer Sharing for Microsoft Networks check box and click OK. Creating a Domain User Account The process of creating a domain user account is more or less similar to the process of creating a local user account. The only difference is a few different options in the same type of screens and a few steps more in between. For example you need Active Directory Users and Computers MMC (Microsoft Management Console) to create domain account users instead of Local Users and Computers MMC. Also when you create a user in domain then a domain is associated with the user by default. However, you can change the domain if you want. Besides all this, although, a domain user account can be created in the Users container, it is always better to create it in the desired Organization Unit (OU). 100 P a g e

101 To create a domain user account follow the steps given below: 1. Log on as Administrator and open Active Directory Users and Computers MMC from the Administrative Tools in Control Panel, as shown in Figure Expand the OU in which you want to create a user, right-click the OU and select New->User from the menu that appears. 3. Alternatively, you can click on Action menu and select New->User from the menu that appears. The New Object User dialog box appears, as shown in Figure Provide the First name, Last name, and Full name in their respective fields. 5. Provide a unique logon name in User logon name field and then select a domain from the dropdown next to User logon name field if you want to change the domain name. The domain and the user name that you have provided will appear in the User logon name (pre-windows 2000) fields to ensure that user is allowed to log on to domain computers that are using earlier versions of Windows such as Windows NT. 101 P a g e

102 6. Click Next. The second screen of New Object User dialog box appears similar to Figure Provide the User name and the Password in their respective fields. 8. Select the desired password settings requirement: Select User must change password at next logon option if you want the user to change the password when the user first logs into computer. Select User cannot change password option if you do not want the user to change the password. Select Password never expires option if you do not want the password to become obsolete after a number of days. Select Account is disabled to disable this user account. 9. Click Next. 10. Verify the user details that you had provided and click Finish on the third screen of New Object User dialog box. 11. Follow the steps 9-13 mentioned in creating a Local User Account section to associate a user to a group. Resetting user password Passwords add a level of security to your computer. When sharing a computer with others, your customized settings, computer programs, and system resources are more secure when you assign a password to your logon name or user account name. 102 P a g e

103 The steps to perform this task differ depending on whether your computer is a member of a network domain or is part of a workgroup (or is a stand-alone computer). My computer is on a domain You must be logged on as an administrator or a member of the Administrators group in order to complete this procedure. If your computer is connected to a network, network policy settings may also prevent you from completing this procedure. 1. Open User Accounts in Control Panel. 2. On the Users tab, click the name of the user whose password you want to change, and then click Reset Password. 3. In New password and Confirm new password, type the new password, and then click OK. Note: You can change passwords only for local computer accounts, such as guest, administrator, or accounts you create for your computer. You cannot change your network logon password in User Accounts. To change your own password, press CTRL+ALT+DELETE and then click Change Password. My computer is not on a domain If no password has been assigned to the user's account, a password will need to be created before it can be changed. For information about creating a password, click Related Topics. The steps to perform this task differ depending on the type of user account you have. If you have a computer administrator account 1. Open User Accounts in Control Panel. 2. Click your account name. 3. Click Change my password. 4. In Type your current password, type your current password. In Type a new password and Type the new password again to confirm, type your new password. You can also enter descriptive or meaningful text in Type a word or phrase to use as a password hint to help you remember your password. 5. Click Change Password. If you have a limited account 1. Open User Accounts in Control Panel. 2. Click Change my password. 103 P a g e

104 3. In Type your current password, type your current password. 4. In Type a new password and Type the new password again to confirm, type the new password. You can also enter descriptive or meaningful text in Type a word or phrase to use as a password hint to help you remember your password. 5. Click Change Password. Adding user to group By adding a user account to a group, you can avoid having to grant the same access and permission to many different users one by one. Members of a group can make the same types of changes to settings and have the same access to folders, printers, and other network services. 1. Open Microsoft Management Console by clicking the Start button, typing mmc into the Search box, and then pressing ENTER. If you are prompted for an administrator password or confirmation, type the password or provide confirmation. 2. In the left pane of Microsoft Management Console, click Local Users and Groups. 3. Double-click the Groups folder. 4. Right-click the group you want to add the user account to, and then click Add to Group. 5. Click Add, and then type the name of the user account. 6. Click Check Names, and then click OK. Deleting user account Open the User Accounts Tool You might want to delete user accounts if a previous user of your computer no longer needs access to it. 104 P a g e

105 Click on the Start Menu, then click Control Panel In the Control Panel, click User Accounts. Within the User Accounts window, click the User Accounts icon. 105 P a g e

106 Select the Account to Delete Select the account to delete (In this example, Elwood Blues is selected). Click on Delete the account. Confirm Keeping or Deleting User's Files 106 P a g e

107 Confirm that you want to keep or delete the user files associated with this account Note that the final screen shows that the account has been deleted Sharing file and folder You can share the files and folders stored on your computer, on a network, and on the Web. The method you choose depends on whom you want to share files with, and what computer they will use to access the files. If you both use the same computer You can put the files you want to share in the Shared Documents folder. Files stored in the Shared Documents folder or its subfolders are always available to other users on your computer. Setting Security on a Folder Before You Share It 1. Log on to your computer as a user who is a member of the Power Users group or the Administrators group. Click Start, point to Programs, point to Accessories, and then click Windows Explorer. 2. Click the drive or folder in which you want to create a new folder. 3. On the File menu, point to New, and then click Folder. Type a name for the new folder (for example, Accounts Receivable), and then press ENTER. 4. Right-click the new folder, and then click Properties. Click the Security tab. 5. Click to clear the Allow inheritable permissions from parent to propagate to this object check box. In the Security dialog box, click Copy. NOTE: The inherited permissions are copied directly to this folder. 6. To add a set of permissions, in the Properties dialog box, on the Security tab, click Add. In the Select Users, Computers, or Groups dialog box, double-click the appropriate user accounts or groups (for example, Accounting, Sales, and Jane Smith). When you have selected all the users and groups you want to assign permissions to, click OK. The groups and users you added, along with the Everyone group, are displayed in the top half of the Security tab. Follow the next steps to complete the process: 1. In the Name list, click each user or group one at a time, and then apply the correct permissions in the Permissions list. For example, for the Accountants group, for the Modify permission, click Allow. For the Sales group, for the Read & Execute permission, click Allow. For the user Jane Smith, for the Full Control permission, click Allow. 2. After you have set the appropriate permissions, click the Everyone group, and then click Remove. 107 P a g e

108 Sharing a Folder 1. Click Start, point to Programs, point to Accessories, and then click Windows Explorer. 2. Right-click the appropriate folder (for example, Accounts Receivable), and then click Sharing. 3. In the folder's properties, click Share this folder. Use the default name for the share. Click Permissions. 4. In the Permissions for dialog box, click Add. 5. In the Select Users, Computers, or Groups dialog box, double-click the Authenticated Users group, and then click OK. 6. In the Permissions for dialog box, click the Authenticated Users group. 7. In the Permissions list, for the Full Control permission, click Allow. After you have set the appropriate permissions, click the Everyone group, and then click Remove. (Or) Follow these steps on any Windows XP computer to share file resources across a local network. Individual files, an entire folder, or an entire Windows drive can be shared with Windows XP network configuration. 1. Ensure Windows XP Simple File Sharing is enabled. 2. Open Windows Explorer (or My Computer). 3. Navigate to the file, folder or drive folder to be shared, and click once on its icon to select it. 4. From either the File menu or the right-click menu, choose the "Sharing and Security..." option. A new Properties window appears. If this option did not appear on the menu, ensure that a valid file or folder was selected in the previous step. 5. Click the Network tab in the Properties window. If no Network tab appears in the window, but a Sharing tab appears instead, close this window and ensure the Simple File Sharing option was enabled in the earlier step before proceeding. 6. Click the Share This Folder option in the Properties window to enable sharing of this resource. This allows all other computers on the local network to access file(s) but not modify them. To grant others permission to modify these files, click the "Allow Network Users to Change My Files" checkbox to enable this option. Alternatively, if the Network tab is not enabled, make required settings in the Sharing tab to configure the equivalent sharing. Choose "Share this folder" to enable sharing. 7. Click Apply or OK to save these settings. 108 P a g e

109 Security inheritance Files and subfolders can inherit permissions from a parent folder. By default, any new permissions you assign to a folder are passed on to subfolders as well. Thus, when you create a new subfolder in your My Documents folder, it inherits the permissions you've set for your profile. If you made your user profile private, the new subfolder and any files you create or store within it will be private as well. You can prevent permissions from being inherited by changing the inheritance options for a folder. You can specify that subfolders or files (or both) no longer inherit permissions that have been assigned to the parent folder containing them. Instead, only permissions you explicitly apply to files and subfolders will apply. To see the inheritance options for a selected folder, right-click the folder icon, choose Properties, and then click the Security tab. Click Advanced to display the Advanced Security Settings dialog box. The Inherited From column in the Permission Entries list shows the parent folder from which a given set of permissions is inherited. For example, the Everyone group inherits Full Control permissions from the ACL on the root folder of drive E, whereas the other permissions, designated as <not inherited>, have been applied directly to this folder. In this example, the inherited permissions are getting in the way of the tight security we want to apply to this folder. To remove the inherited permissions, clear the Inherit from Parent the Permission Entries That Apply to Child Objects check box. You see the following dialog box, which warns you to specify how you want to reset the permissions on the selected folder. Choose one of the following three options: Copy this option copies the permissions from the parent folder to the current file or folder and then breaks the inheritance link to the parent folder. After choosing this option, you can adjust the permissions to suit your security needs. Remove this option removes any permissions that were inherited, keeping only those permissions that you've explicitly assigned to the file or folder. Cancel This option closes the warning dialog box and leaves the inheritance options intact. When you remove inherited permissions from a folder, it becomes a new top-level folder. By default, any permission you assign to this folder ripple down the hierarchy of subfolders and to files within those subfolders as well. For an excellent illustration of how these settings all work together, look at the permissions on your user profile after you choose the Simple File Sharing option to make the folder private. Using Simple File Sharing, click the Make This Folder Private option, and then turn off Simple File Sharing. When you click the advanced button on the Security tab of the "private" folder, you'll see that the Inherit from Parent the 109 P a g e

110 Permission Entries That Apply to Child Objects check box has been cleared and that the permissions on the folder now include only the System account and your user account, both with Full Control permissions. The net effect is to block out every user except you. In some cases, you may want to apply two or more sets of permissions to the same folder for the same group, with each set of permissions having different inheritance settings. For instance, say that you and several coworkers on a shared computer are working on a top secret project. You've set up a shared folder called Project X Files for use by everyone who has an account on your computer. In the main folder, you've stored a handful of document templates that you want members of the team to use when creating new documents; you've also set up subfolders to hold files that are currently being worked on. In this scenario, you might want the Every one group to have Read & Execute access to files within a top-level folder, and Full Control over subfolders. Using this arrangement of permissions, you can allow users to open templates stored in the top-level folder, while protecting those templates from accidental changes or deletions. By using a different set of permissions on subfolders, you can allow users to create new files and modify previously saved documents. To apply permissions with this level of fine-grain control, follow these steps: 1. Open the properties dialog box for the top-level folder you want to adjust (Project X Files, in this example), and click the Security tab. Then Click Add. 2. In the Select Users Or Groups dialog box, enter Administrators and click OK. 3. Choose Administrators from the Group Or User Names List at the top of the properties dialog box, and then select the Allow box to the right of the Full Control entry in the Permissions list. Click Add again. 4. This time, enter Everyone in the Select Users Or Groups dialog box and click OK. 5. Choose Everyone from the Group Or User Names List, and then select the Allow box to the right of the Read & Execute entry in the Permissions list. 6. Click the Advanced button to open the Advanced Security Settings dialog box. 7. If necessary, clear the Inherit From Parent The Permission Entries That Apply To Child Objects check box (and then select Copy when the security warning appears). 8. Select the entry for Everyone, and click the Edit button to open the Permission Entry dialog box. Open the Apply Onto list, choose This Folder And Files, and click OK. 9. From the Advanced Security Settings dialog box, click Add. 10. In the Select User Or Group dialog box, enter Everyone and click OK. 11. In the Permission Entry dialog box, check the Full Control box, choose Subfolders Only from the Apply Onto list, and then click OK. With these settings, you and other members of the Administrators group can add and change files in the main folder; you can also add subfolders. All other users can view 110 P a g e

111 and open files in the main folder but can't create new files, change existing files, or delete files or subfolders. They can, however, save files in the subfolders you create. What's the advantage of using inherited permissions in this fashion? Each time you create a subfolder, Windows automatically applies the proper permissions to it, using the inheritance settings you defined. Without these settings, you would be forced to define permissions from scratch for each new subfolder. That's a lot of needless work, with the potential for errors and inconsistencies. More important, if you decide to change the permissions later-for instance, changing the Full Control permission for subfolders from the Everyone group to a more limited group of users-you can make a single change and have the changes apply to all the child folders automatically. 111 P a g e

112 Unit-4 Installing and Configuring Hardware Devices Installing and configuring hardware consists of physically installing hardware controllers, running hardware setup programs, and configuring software controllers to support the new devices. After the hardware is physically installed and configured, you are ready to install SCO OpenServer. Software controllers for most hardware devices are configured automatically by the installation. If your system experiences installation difficulties because of hardware problems, such as conflicting IRQs or drivers recognizing hardware incorrectly, you can manually configure drivers by running the Device Configuration Utility (DCU) from within the SCO OpenServer installation. See ``Installing and configuring hardware'' for more information. Hard disk detection By default, SCO OpenServer is installed on the primary hard disk found for the primary Host Bus Adapter (HBA). Note that the installation also gives you the option of selecting a different hard disk for installation, if desired. NOTE: SCO OpenServer cannot install on a device that is not detected. Be sure to review the device information presented on the installation screens, so that you do not inadvertently install SCO OpenServer on a secondary disk because the primary disk is not found. If a secondary disk is not present and the primary disk is not detected, the installation warns that it cannot proceed. The rules for determining which hard disk is the primary drive are: Disks attached to IDE interfaces always take precedence over disks attached to SCSI HBAs. Ordinarily, IDE interfaces are designated primary and secondary by their physical setup (jumpers, for example). IDE disks are usually designated as master and slave by jumper settings on the disk drive. SCO OpenServer will install on the first IDE disk that is discovered. IDE disks are detected in the following order: primary master, primary slave, secondary master, and finally secondary slave. When multiple SCSI HBAs are present, by default, the HBA with the lowest BIOS address is primary. 112 P a g e

113 With SCSI disks, the disk with the lowest target ID is used as the primary disk. This is typically ID 0, but it can be otherwise. Most SCSI BIOSs allow the selection of the bootable target ID. To install SCO OpenServer on a disk other than the one with the lowest numerical target ID or on a disk attached to a SCSI HBA other than the one with the lowest BIOS address, you must override the default disk selection. It is recommended that you detach all external USB hard disks before starting an SCO OpenServer installation. This precaution will prevent any possibility of accidentally installing SCO OpenServer on the USB hard disk. You must be familiar with your system's physical configuration before you begin the installation. When the hardware diagnostics are run as the system first powers up, check the console messages for recognition of your devices. If you do not see what you expect, check the system BIOS setting to make sure there are no conflicts. Check power and bus cables to make sure they are well attached. Once the SCO OpenServer HBA autodetection is complete during the installation process, you can use <Alt><SysReq>h to switch from the installation screen to the system console (VT0) to see diagnostic messages for devices that successfully load. HBA and disk information may be present on the screen. Use <Alt><SysReq><F1> to switch back to the virtual terminal running the installation. When configuring disk setup, verify the disk sizes being reported on the screen as well as the device names being presented. Device names contain the information about the controller and target ID for the disk to which it refers. Supported Host Bus Adapters (HBA) SCO OpenServer Release 6 supports the following Host Bus Adapter (HBA) drivers. NOTE: A subset of these drivers, as represented in this table, are included in the CD boot image and thus available for automatic detection when the installation begins. If your system requires one of the other supported HBAs, you will need to extract it from the SCO OpenServer installation CD or from a separate disk containing the necessary updated or third-party driver(s). You can extract HBAs from any of these sources as part of the installation process. SCO OpenServer Release 6 Host Bus Adapter (HBA) drivers 113 P a g e

114 Driver Supported Models Available from CD Boot Image aacraid Adaptec SCSI RAID 2120S/2200S/2130S/2230S and Serial X ATA RAID 2410SA/2810SA/21610SA HBAs adpu320 Adaptec Ultra320 Family PCI SCSI HBAs X adsa Adaptec AHA-274x/AIC-7770 EISA SCSI HBAs adsb Adaptec AIC-789x/AHA-294xU2x/295xU2x/AHA-395xU2x X 7800 Family PCI Ultra 2 SCSI HBAs adsc Adaptec AHA-154x/AHA-164x/AHA-174x SCSI HBAs adse Adaptec AHA-174x EISA SCSI HBAs adsl Adaptec AIC-7560/AIC-78xx/AHA-29xx/AHA-39xx/AHA-49xx X 7800 Family PCI SCSI HBAs adss Adaptec AHA-15x0 6X60 SCSI HBAs adst70 Adaptec AIC-789xA/AHA-29160/39160 Ultra160 Family PCI X SCSI IHV HBAs ahci AHCI v1.0-compliant SATA HBAs, including controllers X based on Intel ICH6M, ICH6R, ICH7M, and ICH7R chipsets. amd AMD PCI SCSI HBAs blc BusLogic SCSI HBAs c8xx LSI Logic/Symbios 53c8xx/53c1010/53c1510 PCI SCSI X HBAs ciss Compaq Smart Array 5300/5i/532 HBAs X cpqsc Compaq Wide-Ultra SCSI HBAs X dak DAC 960, extremeraid, and AcceleRAID SCSI HBAs dpt DPT 2011/2012/2021/2022/2122/2322 SCSI HBAs flashpt BusLogicFlashPoint PCI SCSI HBAs hpsas HP Smart Array P600 HBA X i2oosm Intel I2O Block Storage and SCSI OSM HBAs X ida Compaq SMART Array Controller HBAs X ide Generic IDE/ATAPI HBAs X iir Intel Integrated RAID (IIR) HBAs X mega MEGA SCSI HBAs X mpt LSI Logic PCI to SCSI and Fibre Channel HBAs X qlc1020 QLogic QLA10xx PCI SCSI HBAs qlc12160 QLogic QLA12160 PCI SCSI HBAs qlc1280 QLogic QLA1280 PCI SCSI HBAs qlc2100 QLogic QLA2100 PCI Fibre Channel HBAs qlc2200 QLogic QLC2200 Fibre Channel IHV HBAs X qlc2300 QLogic QLC2300 Fibre Channel IHV HBAs X 114 P a g e

115 rstmp EMC Symmetrix Disk Restamp Driver for EMC Symmetrix RAID storage systems X Installation boot devices One of the following installation media devices is required: a bootable CD-ROM drive a supported network adapter, and a preconfigured network installation server, for network installation. See ``Installing SCO OpenServer products over the network'' for information on performing an installation over the network. Note the following about SCO OpenServer bootable CD-ROM support: SCO OpenServer Release 6 bootable CD-ROM support uses the ``El Torito'' extension of the ISO 9660 standard, in no-emulation boot mode. The system must allow you to specify CD-ROM as a boot device in the system BIOS, and must not use a proprietary CD-ROM boot scheme. Set the boot sequence of your system BIOS to start with the CD-ROM drive. For SCSI CD-ROM drives, set the SCSI controller so that BIOS support for sequence set in the BIOS includes the CD-ROM device before the network device. The SCO OpenServer Release 6 installation automatically detects the CD-ROM drive to use. If your system contains multiple CD-ROM drives, make sure that the installation CD-ROM drive contains the SCO OpenServer Release 6 CD and that all other CD-ROM drives are empty. Otherwise, you run the risk that the wrong drive will be detected for installation. Working with Drivers A driver is a special type of software that's needed to get different pieces of hardware to work right with your computer. First off, just to make sure we're all on the same page, let me briefly explain the difference between the two basic computer terms "hardware" and "software". It's actually pretty simple -- "hardware" refers to all of the physical pieces of equipment, like your mouse, your computer's screen (or monitor), the hard drive, etc. "Software" is all of the parts of the computer that you can't really see or touch. Software would include things like Microsoft Word, your program, Windows or the Mac OS, plus all of your personal files like letters, photos, music, and more. One way to think about it is like this: hardware is like your brain, the physical part of your body, while software is like your mind or your thoughts -- the non-physical part of 115 P a g e

116 yourself. Software runs on hardware, just like your thoughts "run on" your brain. Now let's talk more specifically about drivers. Here's the easy way to think about the computer term driver: Imagine that every piece of hardware, including your printer, your mouse, and so on, speaks a different language. So one speaks French, another one speaks Italian, another one Cantonese, and so on. So when you plug in a new printer and turns it on, your computer says "hi" and the printer answers in a foreign language the computer doesn't understand. So it needs an interpreter. And when I say interpreter, I mean just like in the real world, like if a foreign diplomat comes to the country but doesn't speak the local language. They need an interpreter to help them communicate with the locals. That, basically speaking, is what a driver is -- an interpreter that helps your computer talk to a specific piece of equipment. And you need a different interpreter for each piece of equipment (or each general type) that you hook up to the computer. Now in some cases, the driver may be "preinstalled" on your computer (in other words, the computer already has the interpreter ready and waiting in case it's needed) and in other cases, it needs to either be installed from a CD, or downloaded off the Internet, and then installed on the computer. But either way, the computer needs that driver before it can talk to the printer or whatever other type of device you may have hooked up to the computer. 116 P a g e

117 Troubleshooting Hardware Devices the Hardware Wizard The Hardware Troubleshooting Wizard allows convenient troubleshooting through the Device Manager interface. By clicking the Troubleshoot button on the General tab for a device, you will be walked through a series of pages to help resolve the problem. Windows Server 2003 offers a series of Troubleshooters, which ask for details on the symptoms, suggest resolutions and link to additional information on the problem. There are 17 built-in troubleshooters, covering the following areas: System setup Startup/Shutdown Display Home networking Hardware Multimedia and games Digital Video Discs (DVDs) Input Devices Drives and Network Adapters USB Sound Modem Internet Connection Sharing Internet Explorer Outlook Express (Messaging) File and Print Sharing Printing 117 P a g e

118 Using Driver Rollback to restore advice driver Device Driver Roll Back reinstalls the driver you were using previously and restores any driver settings that were changed when you added the new driver. Note that you cannot restore printer drivers with Device Driver Roll Back. To roll back a device driver to a previous version: 1. Log on to the computer by using an account with administrative privileges. 2. Click Start, and then click Control Panel. 3. Under Pick a category, click Performance and Maintenance. 4. Under or pick a Control Panel icon, click System. 5. On the Hardware tab, click Device Manager. 6. In the device list, expand the device type branch that you want to work with. For example, Display adapters. 7. Right-click the device that you want to work with, and then click Properties. 8. On the Driver tab, click Roll Back Driver. Click Yes when you receive the following message: Are you sure you would like to roll back to the previous driver? 9. The previous device driver is restored. Click Close. 10. Quit Device Manager, and then click OK. Configure hardware devices You can configure the details regarding your hardware using Device Manager. Device Manager shows you how the hardware on your computer is installed and configured, and how the hardware interacts with your computer's programs. You will typically use Device Manager to check the status of your hardware and update device drivers on your computer. To access Device Manager: Right click My Computer, click Manage, and then click Device Manager. To view the status of a device: 1. Open Device Manager. 2. Double click the type of device you want to view. 3. Right click the specific device you want, and then click Properties. 4. On the General tab, under Device status is a description of the device status. 118 P a g e

119 If the device is experiencing a problem, you ll see the type of problem in the Device status box. You might also see a problem code and number and a suggested solution. If you call a support line, this number can be useful for determining and diagnosing the problem. For information on how to resolve hardware device problems, click Troubleshoot to start the Hardware Troubleshooter. To install a new driver from Device Manager: 1. Open Device Manager. 2. Double-click the type of device you want to update or change. 3. Right-click the specific device driver you want to update or change. 4. Click Update Driver to open the Hardware Update Wizard. Follow the wizard instructions. Note : If you install a new driver and your system becomes unstable, you can easily uninstall the driver and reinstall the old driver with Driver Rollback. To uninstall a device: 1. Open Device Manager. 2. Double click the type of device that you want to uninstall. 3. Right click the specific device you want to uninstall, and then click Uninstall. 4. In the Confirm Device Removal dialog box, click OK. When you're done uninstalling the device, turn off your computer, and remove the device from the computer. Drivers on a Computer Definition: A driver is a small piece of software that tells the operating system and other software how to communicate with a piece of hardware. For example, all printers come accompanied with drivers to install that tell the operating system exactly how to print information on the page. Sound card drivers tell your software exactly how to translate data into audio signals that the card can output to a set of speakers. The same applies to video cards, keyboards, monitors, etc. The drivers for each piece of hardware in your Windows computer are centrally managed from Device Manager, available in all versions of Microsoft Windows. 119 P a g e

120 Running creating an answer file The answer files Wizard The first step is to create the answer file to put on the CD. The answer file contains all the parameters to install a standard version of Windows 2000 or XP. Each operating system requires its own answer file. Unzip deploy.cab from the Windows XP CD in a temporary directory. (You can find it under: \SUPPORT\TOOLS) or you can download it from wwww.microsoft.com/download. It s better to download it from the Microsoft website because; it s going to be the latest version available. When a new service pack comes out, they add some functions. Start SetupMGR.exe, select what you need. 120 P a g e

121 Unfortunately the Wizard is doing only a simple answer file, so you going to have to edit the answer file manually. You can find help for the commands in the Deploy.cab, ref.chm and deploy.chm. It s easier to start with an answer file, that s already working. Even on the Microsoft Website there are some syntax error on their samples. Important Sections of the answer file Here are some examples of answer files. Figure 1 is made with Setupmgr.exe without any modification. 121 P a g e

122 Components This section contains entries for installing the components of Windows. Example: Calculator, Outlook Express, games. GuiRunOnce This section contains commands to execute the first time the user logs on to the computer after the installation completes. It is good to apply the last critical updates, registry fixes, or installation of applications. The Batch file that runs in Runonce is Final.cmd, located in \$OEM$\APPS\Patch. Networking This section configures the network cards. If left empty, the network cards will be installed with the default settings. You can configure, all the protocols settings, and networking services installed. LCID HEX Valid Locale ID English_United_States : English_United_Kingdom : P a g e

123 Regional Settings This section contains entries for installing regional settings and the configuration of the Keyboard languages during Setup. See figure 3 for the main Keyboard code. Having the good keyboard configuration is not easy. Even if you have the good Keyboard code, the default English US keyboard will probably come back. The easiest way to walk around this issue is to fix the good keyboard configuration directly in the registries. English_Canadian 1009 French_Standard French_Canadian 040c 0c0c 1009: : : c: c 0409: c0c: : My Unattended installation does it the first time a user log on. This is done through the Final.cmd batch file. Shell This section contains entries for specifying the visual style of the user interface. (The way the Desktop looks) You can configure Windows XP to use the classic desktop, in this section. To use Windows Classic startup menu, change the value in [SHELL] to DefaultStartPanelOff=Yes. Unattended This is the main section; most of the settings are there, like drivers policies, partitions, activation of Windows. Setup Manager Wizard To install the Windows 2000 Setup Manager Wizard and use it to create an answer file. An answer file (the Unattend.txt file) is used to help automate Windows 2000 installations by providing Windows Setup with the information that it needs during an unattended installation. How to Install and Run the Windows 2000 Setup Manager Wizard The Windows 2000 Setup Manager Wizard is not installed by default. To install and use the Windows 2000 Setup Manager Wizard: 1. Start Windows Explorer, and then open the Support\Tools folder on the Windows 2000 Server CD-ROM. 2. In the right pane, double-click the Deploy.cab file to open it. 3. On the Edit menu, click Select All. 4. On the Edit menu, click Copy. 123 P a g e

124 5. Create a new folder on your local hard disk. To do this: a. Click Local Disk (C:). b. On the File menu, point to New, and then click Folder. c. In the New Folder name box, type the name that you want, and then press ENTER. Right-click the new folder that you created, and then click Paste. Double-click the new folder to open it, and then double-click the Setupmgr.exe file. The Windows 2000 Setup Manager Wizard starts. Follow the instructions in the wizard to create an answer file. If you use the answer file to install Windows from a CD-ROM, you may need to add the Windows 2000 product key information. To do this: 1. Use Notepad to open the Unattend.txt file that you created. 2. On a new, blank line under the [UserData] section, type the following line, where AB123 is a 5-character portion of the 25-character alphanumeric Windows 2000 product key: ProductID="AB123-AB123-AB123-AB123-AB123" 3. On a new, blank line under the [Unattended] section, type the following line: Repartition=Yes 124 P a g e

125 Unit-5 Introduction-Windows XP Windows XP was introduced in November 2001 with a great sales campaign. Compared with the previous Windows Me there has also been a very extensive updating of Windows. The main features in the new program are: Technologically Windows XP is based on the Windows NT and Windows 2000 programs (and thus not on Windows 98/Me). With this Windows XP is a genuine 32 bit program. Windows XP replaces both Windows 2000, Windows NT and Windows 98/Me. Windows XP has a new user interface with new buttons, icons and windows. Windows XP is optimized to work with digital pictures, sound- and videorecordings (with use of the modern pc-plugs USB and FireWire). All in all this is a very extensive updating especially when compared to Windows 98/Me. Windows is an operating system To learn knowing Windows XP, you must understand that it is a operating system. This means that Windows XP is a collection of programs, which enables the entire pc to work. Among Windows most important tasks I could list: Assist in starting the pc. Control and handling of all hardware, including RAM, i/o, cards and controllers. Read-in of a graphics user interface with windows, menu bars etc. Forms a platform for the user programs (applications) like Word, Internet Explorer, Photoshop etc. Handling of user data in files. Beyond the pure operating system tasks Windows XP includes a large collecton of smaller and larger tools. Among others Windows XP comes with Internet Explorer and the multimedia player Windows Media Player, which are independent user programs. 125 P a g e

126 Figure 1. Windows XP is both an operating system and a program package. Graphics user interface Windows XP is first of all characterized by a smart graphics user interface that you need to get acquainted with. The user interface is built basically on the same model we know from Windows 2000 og 98/Me, but the appearance has changed quite a bit. There are many features that you need to know; here are some of the most important: The Start button, which covers a wide range of Menus. It is in access to all the See the review on page 6ff and read how you can modify the menu on page 29. The task bar is normally seen near[n1] 126 P a g e

127 The task bar is the daily cockpit, from where you control your work. You can modify the task bar in many ways, which I show later. Quick start bar Desk top. That is the large area you see when Windows XP starts. Compared with earlier Windows editions there are much fewer default icons on the desk top, which can be modified in different ways (see among others pages 73ff and 81). Figure 2. The desk top, which lies "below" all program windows. Hyperlinks. The Windows XP user interface makes extensive use of hyperlinks (previously referred to as shortcuts). Hyperlinks appear as small icons, and they can be placed in many places on the Windows XP user interface. Hyperlinks are known from web, where you can open various home pages by clicking on them. In the same way Windows XP gives you very easy access to files, home pages, programs and other objects. You will be working with hyperlinks among other places on pages 24 and 72ff. Windows Explorer and My Computer. Windows Explorer is really your tool to work with files, folders, programs, hyperlinks, Control panel and much more. The starting point for 127 P a g e

128 work with Windows Explorer is often My Computer. That is a system folder that shows and gives access to most of the pc s resources. You will work a lot with Windows Explorer in the exercises in this booklet. Figure 3. "This computer" is a very important folder, which opens access to the pc s drives, folders and files. The control panel is the entry to the pc s various settings such as controlling hardware units through the so-called drivers (as I illustrate on page 81). 128 P a g e

129 Figure 4. The control panel has a new look in Windows XP. The three central and well known components Windows Explorer, My Computer and the Control panel are all substantially revised in Windows XP. There are many new feaures added and overall a greatly improved and more flexible handling, which can be recognized from one situation to another. Install Windows XP Professional by using the System Preparation Tool The "System Preparation Tool," or "Sysprep," facilitates the mass deployment of Microsoft Windows XP Professional. It changes the system files on a computer so that the next time the computer is started with those files, the operating system will adapt itself to the current hardware environment. The hard drive that has had "Sysprep" run on it can then be duplicated, or "cloned," on other disparate hardware platforms. When those computers are started, the applications and configuration settings remain the same, and the proper drivers are loaded. Significant efficiency gains are realized through the elimination of repetitive installation and configuration steps. Drivers for all potential hardware devices Microsoft Windows XP installation CD 129 P a g e

130 1 Install and configure all desired applications on the Windows XP Professional computer. 2 Change all desired configuration settings on the Windows XP Professional computer. 3 Open "Windows Explorer" by clicking the "Start" button, "All Programs," "Accessories" and then the "Windows Explorer" icon. 4 Double-click "My Computer" on the left side and click the "C:" drive icon. 5 Click the "File" menu from the top-left corner, then select "New" and then "Folder." 6 Type "sysprep" as the new folder name and press the "Enter" key on the keyboard. 7 Insert the "Windows XP Professional" installation CD into the CD-ROM drive of the computer. 8 Click the drive letter representing the CD-ROM drive in the left side in "Windows Explorer." 9 Double-click the "Support" folder and then the "Tools" folder on the right side. 10 Double-click the "Deploy.cab" file to open it, and select the "Sysprep.exe" and "Setupcl.exe" files by holding down the "CTRL" key on the keyboard while clicking both file names. 11 Copy the two selected files by selecting the "Edit" menu from the upper left corner and selecting "Copy" from the drop-down menu. 12 Click the "C:" drive on the left side and double-click the new "sysprep" folder on the right side to open it. 13 Paste the two copied files into the "sysprep" folder by selecting the "Edit" menu from the upper left corner and selecting "Paste" from the drop-down menu. 14 Open a "Windows Command Prompt" window. Click "Start," then "Run," type "cmd" into the dialog box and click "OK." 130 P a g e

131 15 Type the following command into the "Command Prompt" and press the "Enter" key on the keyboard. The system will automatically shut down after the "Sysprep" program finishes running. C:\sysprep\sysprep.exe -forceshutdown 16 Clone the hard drive of the computer to other target computers that Windows XP Professional should be installed on (see Resources). When the target computers are started for the first time, a setup routine will run, and they will be configured in the exact manner as the original computer, with the same applications already installed. Basic Program Layout Windows XP Now you are going to do the practical work with Windows XP. If you have not done so already, turn on your pc now. The start All programs have to be started; Windows XP is no exception, but it happens automatically. When you turn on power to the pc, it boots, the pc gets ready, and the operating system and its various programs are read in. 131 P a g e

132 Microsoft has done much to optimize the start-up, so ordinarlly Windows XP willl be ready run in 30 seconds after you turn on power. That is a substantial improvement especially when compared to Windows 2000 and NT, which could demonstrate a very slow start-up. After start-up You usually have to click on a user name, since other users may use the same pc (see the description on page 61). To select a user is really called log on. See Figure 5. Once you have logged on, you will get to Windows XP itself. This picture may look slightly different from pc to pc. Figure 5. Windows XP gives additional users the option of their individual log-on. The Start button First we will look at the Start button, which most people are familiar with. 132 P a g e

133 The only change in Windows XP is that the button is now green and got a rounded appearance... The start button is your main entry to the pc. A single click on that opens the Start menu, which I will describe here. You can also activate it with the Windows key I use that often: Figure 6. The Windows key activates the Start menu directly. You can actually operate the Start button in yet other ways. Try to press Control+Escape. Hold the Control key and press the Escape key simultaneously, then the Start menu opens. The Start menu The Start menu (Figure 7) has a rather new look in Windows XP, but the structure is about the same as before. You find: A number of hyperlinks to various programs and functions. An item that opens the sub menu All programs. Two buttons in the bottom of the menu, which can be used to change user (Log off) and to close the computer respectively. 133 P a g e

134 Figure 7. The Start menu, which opens when you press the Start button. The menu is divided in two lists. The left program list In the left half of the menu you see a list with hyperlinks to selected programs. This list actually consists of two sections. On top are hyperlinks to important programs (Internet and in Figure 8). Here you can add and rmove hyperlinks. If I right click on the Internet hyperlink, I could choose the menu item Delete from this list : 134 P a g e

135 Correspondingly I can add hyperlinks to the list. That would typically be a menu item that I find elsewhere in the menu structure, and which I want to emphasize with a fixed position in the left program list. I select the appropriate menu item and right click on that. Then I choose Attach[n2] The bottom section in the left program list is automatically updated with hyperlinks to the most recently used programs. Here we are talking about programs, which you open with the menus Start In Figure 8 you see six hyperlinks (Noteblock, Paint etc.). Those are hyperlinks that are installed in my list, beyond my control. That happened because I have used or installed the listed programs. I can remove these hyperlinks from the list if I do not want to see them, but I don t have to worry about that. If I don t use them, they will automatically be replaced with hyperlinks to the programs I use: 135 P a g e

136 The left list in the Start menu consists of two sections with each their own function. The six hyperlinks in the bottom of the left list are thus dynamic ; they change with your work. The right list in the Start menu in fig has 9-11 fixed hyperlinks, which can activate a number of central Windows functions All programs The start menu thus contains a number of hyperlinks. But the most important is probably the access to the pc s programs. You find that in the menu item All programs, which can be opened by pressing letter a. You can see that by the underlining of the first letter: That menu item opens accesss to a list of varous programs. Some of those are installed with Windows XP, you have installed others yourself. Here is my list: 136 P a g e

137 The list with all programs is seen to the right. If you examine the list, you can find two types of menu items: Hyperlinks, which give direct access to specified programs such as Windows Update, remote support, Internet Explorer etc. Access to sub menus, which are associated with specific program groups. They are recognized by the small arrow to the far right. In Figure you thus see the program groups CloneCD, JetAdminV3.4 and Macromedia Fireworks 4. Some of the sub menus are installed by Windows XP. Those are Play, Start and Accessories. The others belong to program packages that I have installed on the pc. Some of the menu items have a built-in help text, which activates when the mouse cursor rests upon them. Try to place the cursor on the top item, Windows Update. Then the help text appears in a yellow box: 137 P a g e

138 Try to find for yourself the other menu items that have help texts. Now look at the Accessories sub menu. It covers various small programs, which are installed with Windows XP: In this menu you again find access to new sub menus (there are four of them on top of the list), but beyond that there is access to 12 small programs: If you open the sub menu Entertainment, you get access to three (or possibly more) small programs: 138 P a g e

139 This means that if you want to activate the SoundRecorder program, You need to navigate through the following menu structure: The start menu This entire operation can be done with the mouse, but you can actually also use the keyboard. Nearly all Windows programs have menus, which can be operated from the keyboard. Try for yourself to press the following sequence: Windows-key, a, t, u, Enter Then one menu layer after another opens, and finally the SoundRecorder program (if it is placed on top of the list). If you check while you press the letters a and e, you will see that the letters match the first letter in Accessories and Entertainment. You can probably not use the program Soundrecorder for anything just now, so close it with menu items File --> Exit: Test the menu structure So you see that there is a multi layer hieratic menu structure. Try the following exercise for yourself, where you move around in the menu structure just using the keyboard: 1. Open the start menu by pressing the Windows key. 2. Press a[n3] 3. Press ArrowDown a couple of times until you reach the menu item games. 139 P a g e

140 4. Press ArrowRight to open the sub menu Games. There are 11 games included in Windows XP. Use the ArrowDown key to move down though them. Read the help text at each game[n4] 5. After you have looked at each game, press ArrowLeft. That closes the games sub menu. Then press ArrowDown a couple of times until you reach the menu item accessories. Open that with ArrowRight. 6. Press ArrowDown, ArrowDown, ArrowRight to reach the system tools submenu. Try also here to look at each individual menu item. 7. Now you can close the menus by pressing the Escape key four times. For each press one menu layer closes. Other programs When you install new programs, they are usually placed in the menu system All programs. Windows XP actually tells you (with a small speech bubble ) when new programs are installed: The menu structure in All programs is expanded as time goes by. Fortunately you are free to change the structure; you can add and delete elements as needed. Screen Saver Settings To set or change a screen saver 1. Open Display in Control Panel. 2. On the Screen Saver tab, under Screen saver, click a screen saver in the list. Note 140 P a g e