Professional Web Hosting, Perl Scripting And Developing Blog

Managing and Troubleshooting Hardware When you are ready to continue, click Next so the Windows operating system can search the specified locations for the driver. If the wizard finds a specific driver that is compatible, it installs it. If the wizard finds multiple drivers that might be compatible, it displays a list of matching drivers and allows you to choose the driver to use. As before, if no driver is found, the wizard will try to use Windows Update and find the driver on the Windows Update site. Choosing a Specific Driver or Bypassing the Default Driver Bypassing the default driver makes it possible to install an unsigned driver from a manufacturer rather than a signed driver included with Windows Server 2003. If you want to do this, choose the Install From A List Or Specific Location option when the Found New Hardware Wizard starts, and then click Next to display the search and installation options page. On this page, select Don t Search, I Will Choose The Driver To Install. After a short delay, the wizard shows a list of compatible drivers by model type, as shown in the following screen. If applicable, clear the Show Compatible Hardware option to display all of the drivers that are available by device type. Choose a device, and then click Next to complete the installation. Chapter 13 Installing Non Plug and Play Devices Although Windows Server 2003 doesn t detect or set up non Plug and Play devices automatically, it does maintain a driver cache for these devices. This driver cache has hundreds of drivers, any one of which you might be able to use. You might also be able to use a Windows Part 4: Managing Windows Server 2003 Systems
You need excellent and relaible webhost company to host your web applications? Then pay a visit to Inexpensive Web Hosting services.

Microsoft Windows Server 2003 Inside Out Chapter 13 Click Yes to allow the wizard to use Windows Update to connect to the Internet and search for the device driver at the Windows Update site. If the computer doesn t have an Internet connection or you know another location where the software might be located, click Back, and then choose the Install From A List Or Specific Location option. Installing a Downloaded Driver If Windows Server 2003 detects the Plug and Play device and the Found New Hardware Wizard starts automatically, you can choose the Install From A List Or Specific Location option so that you can install a driver you ve downloaded for the device. Select this option, and then click Next to display the search and installation options page. By default, the Search For The Best Driver In These Locations and Search Removable Media options are selected (as shown in the following screen), and Windows Server 2003 will search all removable drives if you click Next. Because you ve downloaded a driver, you should select the Include This Location In The Search option instead and then enter the full file path to the folder that contains the driver you downloaded. You can click Browse to find the location as well. 384 Part 4: Managing Windows Server 2003 Systems
Please visit Domain Name Hosting services for high quality webhost to host and run your jsp applications.

Managing and Troubleshooting Hardware Sometimes when this happens, you must install the hardware device manually using the Add Hardware Wizard just as you do with non Plug and Play devices. See the section entitled Installing Non Plug and Play Devices later in this chapter for details. More typically, Windows Server 2003 starts the Found New Hardware Wizard, shown in the following screen, which is designed to help you find a suitable driver for the device that was detected. Chapter 13 If this wizard starts, you have the following two options: . Install The Software Automatically Choose this option if the device came with an installation CD or floppy disk that contains Windows Server 2003 compatible drivers. . Install From A List Or Specific Location Choose this option if you ve downloaded a compatible driver or want to choose a specific driver, bypassing Windows default selection. Installing the Software Automatically If Windows Server 2003 detects the Plug and Play device and the Found New Hardware Wizard starts automatically, you can choose the Install The Software Automatically option, which is the recommended and default option. Click Next to access the search and installation options page. By default, Windows Server 2003 searches all removable drives and looks for appropriate Setup Information files. If the wizard finds a specific driver that is compatible, it installs it. If the wizard finds multiple drivers that might be compatible, it displays a list of matching drivers and allows you to choose the driver to use. In some cases, the wizard is unable to find a suitable device driver. If this happens, the wizard prompts, asking if it is okay to connect to the Internet, as shown in the screen on the following page. 383 Part 4: Managing Windows Server 2003 Systems
In case you need quality webspace to host and run your web applications, try our personal web hosting services.

Microsoft Windows Server 2003 Inside Out Chapter 13 Then a balloon message is displayed to tell you that your new hardware is installed and ready to use, as shown in the following screen: In this example, Plug and Play worked as expected. Windows Server 2003 detected the device, used the Plug and Play identification to determine which driver should be installed, and then set up the device. Because there are so many factors involved, detection and setup don t always work so smoothly, however. Sometimes the Windows operating system will warn you about something that you might need to take action to correct. One of the more common warnings you ll see is related to Hi-Speed USB devices being connected to non-Hi-Speed USB ports, as shown in the following screen. This is important because if you are connecting an external hard disk drive or other Hi-Speed USB device, the device won t operate at the rated speed. It will in fact operate at a much slower speed. Note USB 1 is the original USB specification. USB 2 is the newer USB specification, and it is referred to as Hi-Speed USB. Although you can connect USB 2 devices to USB 1 ports, the devices operate at the USB 1 speed (which is many times slower than USB 2). If you want to achieve high-speed USB transfers, you must connect to a USB 2 port, if available. You might also want to consider upgrading the USB ports on the computer so that they are USB 2 compliant. If Windows Server 2003 detects a Plug and Play device after you ve connected it but cannot locate a suitable driver, it displays a warning that a problem occurred during installation, as shown in the following screen: 382 Part 4: Managing Windows Server 2003 Systems
From our experience, we can recommend PHP Web Hosting services, if you need affordable webhost to host and run your web application.

Managing and Troubleshooting Hardware Setting Up New Hardware Devices After you install or connect a new hardware device, you must set up the device so that it is available for use. Unlike Microsoft Windows NT, Windows Server 2003 is much better at helping you perform the related procedures, and in many cases, it will set up new devices automatically using Plug and Play. When Plug and Play works properly, it is a wonderful thing. You simply plug in a new device, wait for the Windows operating system to detect and then configure it. The device is then ready for use. Unfortunately, although Plug and Play technology has advanced tremendously since Windows NT (and even since Microsoft Windows 2000), it doesn t always work. Sometimes, Windows will detect a new device but won t know which device driver to use. Other times, the operating system will not detect a new device at all. Usually, this happens because the device doesn t support Plug and Play. Chapter 13 Note You must be logged on as an administrator to install device drivers. If you re logged on using an account without Administrator privileges, you are prompted to provide a user name and password for an account that has Administrator privileges before you are allowed to install device drivers. You do not, however, need to be logged on as an administrator to install devices. As long as Windows can detect and set up the device automatically, it will do so. It is only when a new driver (meaning one that is not already on the computer) must be installed or problems occur that you must be logged on as an administrator. Managing Plug and Play Detection and Installation Windows Server 2003 Plug and Play is optimized to support universal serial bus (USB), FireWire (IEEE 1394), Personal Computer Memory Card International Association (PCMCIA, or PC Card), and Peripheral Component Interconnect (PCI) devices. When you connect a Plug and Play device for the first time, Windows Server 2003 reads the Plug and Play identification tag contained in the device s BIOS or firmware and then searches its master list of identification tags (which is created from the Setup Information files in the Inf folder). If the operating system finds a signed driver with a matching identification tag, it installs the driver and makes the device available for use automatically. Unlike previous versions of Windows, which display the progress of the Plug and Play process in dialog boxes, Windows Server 2003 provides popup balloon tips in the notification area that tell you about major steps in the process only, such as device detection and finalization. For example, when installing a new disk drive, Windows Server 2003 might display Found New Hardware: Disk Drive, as shown in the screen on the following page. Part 4: Managing Windows Server 2003 Systems
From our experience, we can recommend PHP Web Hosting services, if you need affordable webhost to host and run your web application.

Microsoft Windows Server 2003 Inside Out Chapter 13 Warn This option prompts the user each time either to continue with the installation of an unsigned driver or to stop the installation. Block This options prevents the user from installing unsigned driver software. Windows Server 2003 will not install any unsigned device driver and will not display a warning prompt. 3 To apply these options to only the current user, clear the Make This Action The System Default option. Otherwise, select this option to make this the default for all users. 4 Click OK twice to apply the changes. Note that changes to driver installation made this way can be overridden by Group Policy settings at the site, domain, or organizational unit (OU) level. Regardless of the settings you choose, Windows Server 2003 will not install drivers with known problems. If you try to install a driver with known issues that could potentially harm the server, the Windows Driver Protection facility will block the installation. A warning is displayed that states the driver is known to cause stability problems and that the Windows operating system will disable it to prevent this from happening. To complete the installation of the device, you must obtain an updated driver. Inside Out Managing device driver settings through Group Policy You can manage device driver settings for computers throughout the organization by using Group Policy. When you do this, Group Policy specifies the least secure setting that is allowed. The exception is when Group Policy is set to Block. When you use this setting, unsigned device drivers can t be installed without overriding Group Policy. The Code Signing For Device Drivers policy controls device driver signing settings on a per-user basis. This policy is located in User ConfigurationAdministrative TemplatesSystem. Once you enable this policy, you can specify the action to take: Ignore, Warn, or Block. Once enabled, the system doesn t implement any setting less secure than the established setting. If you re trying to install a device and find that you can t install an unsigned driver, you should first check the System utility settings for driver signing. If you find that the settings are set to Block and you can t change the setting, the Code Signing For Device Drivers policy has been enabled and set to Block in Group Policy. You must override Group Policy to install the unsigned device driver. 380 Part 4: Managing Windows Server 2003 Systems
Check Tomcat Web Hosting services for best quality webspace to host your web application.

Managing and Troubleshooting Hardware Using Signed Device Drivers Speaking of new device drivers, Microsoft recommends that you use signed device drivers whenever possible. Signed device drivers have a digital signature that authenticates them as having passed extensive testing by the WHQL. The digital signature means that you can count on the device driver not to cause your system to crash or become unstable, and also that the device driver hasn t been tampered with by other installation programs or by a virus program. The assurances you get with digitally signed drivers aren t applicable to unsigned device drivers. When you install an unsigned driver, there is no guarantee that it has been tested, and if the driver is poorly written, it is much more likely to cause the operating system to freeze or the server to crash than any other program you ve installed. That said, there are times when you might have to use an unsigned device driver. In some situations, you might find that a particular device doesn t have a signed device driver. Here, you should check the manufacturer s Web site to see whether a signed driver is available because sometimes there is a signed driver, but it s just not distributed with the device or on the Windows Server 2003 distribution disks. If a signed driver isn t available, you might find that you have to use an unsigned driver. Keep in mind that Group Policy might prevent you from installing an unsigned driver. See the sidebar Managing Device Driver Settings Through Group Policy later in this chapter for details. Chapter 13 Note If you have to install an unsigned driver, proceed cautiously and remember to monitor the system closely. If you find that the system is inexplicably freezing or crashing, the unsigned driver is probably to blame and should be rolled back or uninstalled. Remember, any type of faulty driver can cause the system to fail, even a driver for a display adapter, a network adapter, or a sound card. Understanding and Changing Driver Installation Settings By default, Windows Server 2003 warns you when you try to install an unsigned device driver. If you don t want to see this prompt, you can change the driver- signing options to eliminate this warning, and you can also prevent any users from trying to install unsigned drivers. You can change driver settings by following these steps: 1 Start the System utility. In the Hardware tab, click Driver Signing. 2 In the Driver Signing Options dialog box, choose the action you want the Windows operating system to take whenever someone tries to install an unsigned device driver. The options are as follows: Ignore This option allows the user to install any unsigned driver without having to see and respond to a warning prompt. Part 4: Managing Windows Server 2003 Systems
Please visit Domain Name Hosting services for high quality webhost to host and run your jsp applications.

Chapter 13 Microsoft Windows Server 2003 Inside Out Using Windows Device Drivers Windows Server 2003 includes an extensive library of device drivers for display adapters, disk drives, drive controllers, keyboards, mice and other pointing devices, network adapters, and more. These drivers are maintained in a compressed file called Driver.cab. For i386 systems, this file is located in the %SystemRoot%Driver CacheI386 folder. For Intel Architecture 64 (IA-64) systems, this file is located in the %SystemRoot%Driver CacheIA64 folder. All the drivers in the Driver.cab file are certified to be fully compatible with Windows Server 2003 and are digitally signed by Microsoft to assure you of their authenticity. When you install a new Plug and Play compatible device, Windows checks this file for a compatible device driver. If one is found, the operating system automatically installs the device. Through Windows Update, Microsoft makes updates to the Driver.cab device drivers available for download and installation. Inside Out Installing new drivers All device drivers provided through Windows Update have been thoroughly tested in the Windows Hardware Quality Labs (WHQL), and you should be able to count on them not to cause your system to crash or become unstable. However, just because driver updates are available doesn t mean you should install them. In a production environment, you ll rarely want to download and install new device drivers without thoroughly testing them yourself first. Better safe than sorry always. Typically, you install new device drivers because you are experiencing problems with the old drivers. If you aren t experiencing problems, you might not want to update the drivers. Every hardware driver has an associated Setup Information file. This file ends with the .inf extension and is a text file containing detailed information about the device being installed. The .inf file includes the names of driver files, the location where they are to be installed, version information, Registry settings, and other important configuration information. All devices with drivers included in the Driver.cab file have corresponding .inf files. These files are stored in the %SystemRoot%Inf folder. When you install a new device driver, the driver is written to %SystemRoot%System32Drivers and configuration settings are stored in the Registry. The driver s .inf file is used to control the installation and write the Registry settings. If the driver doesn t already exist in the Driver.cab file (and thus does not already have an .inf file on the system), a copy of the driver s .inf file is written to the %SystemRoot%Inf folder. 378 Part 4: Managing Windows Server 2003 Systems
If you are looking for affordable and reliable webhost to host and run your business application visit our ftp web hosting services.

Chapter 13 Managing and Troubleshooting Hardware Working with Device Drivers . . . . . . . . . 377 Managing Devices through Hardware Setting Up New Hardware Devices . . . . 381 Profiles. . . . . . . . . . . . . . . . . . . . . . . . . .398 Obtaining Hardware Device Troubleshooting Hardware Devices Information. . . . . . . . . . . . . . . . . . . . . . 388 and Drivers. . . . . . . . . . . . . . . . . . . . . . .400 Managing Installed Drivers . . . . . . . . . . 394 Unless you ve standardized on a particular hardware platform, most servers that you ll work with will have different hardware components. This means different servers will probably have different motherboards, disk controllers, graphics cards, and network adapters. Fortunately, Microsoft Windows Server 2003 is designed to work with an extensive list of hardware devices. When you install new hardware, Windows tries to detect the device automatically and then install the correct driver software so that you can use the device. If Windows has a problem with a device, you must troubleshoot the installation, which usually means finding the correct device drivers for the hardware component and installing them. One thing to keep in mind when working with devices is that, like other software, driver software can contain bugs. These bugs can cause a variety of problems on your servers, and not only could the hardware stop working, but the server could freeze as well. Because of this, you ll want to monitor routinely for hardware problems and take corrective actions as necessary. It is also helpful to maintain a hardware inventory for servers so that you know which devices are installed and who the manufacturers are. Working with Device Drivers Every hardware component installed on a system has an associated device driver. Drivers are used to handle the low-level communications tasks between the operating system and hardware components. When you install a hardware component through the operating system, you tell the operating system about the device driver it uses. From then on, the device driver loads automatically and runs as part of the operating system. Part 4: Managing Windows Server 2003 Systems
Visit our web design programs services for an affordable and reliable webhost to suit all your needs.

Managing Windows Server 2003 4 The system then opens a command prompt. In the command prompt, enter the password for the designated user account. The desktop will restart, and the Start menu, taskbar, and system tray will return as well. 5 Don t exit the Task Manager; you ll need it again and exiting it could cause the Windows operating system to freeze. So, instead of closing Task Manager, minimize it while you use the desktop in the new context. 6 When you are ready to return to the previous desktop, use Task Manager to shut down Explorer.exe again. Afterward, click New Task in the Applications tab, and then in the Create New Task dialog box, type explorer.exe. This returns the desktop to normal. Creating Run As Shortcuts for Secondary Logons You want it to be as easy as possible to use the secondary logon. If you don t, you ll probably be tempted to use the account with Administrator privileges all the time rather than only when needed. With this in mind, one way to make it easier to work with the secondary logon is to create Run As shortcuts for commonly used tools. You can also modify the menu to use Run As shortcuts instead of running tools directly. Creating Run As Shortcuts on the Desktop To create Run As shortcuts on the desktop, follow these steps: 1 Right-click an open area of the desktop to display the shortcut menu. 2 On the shortcut menu, point to New, and then choose Shortcut. 3 In the Create Shortcut Wizard, shown in Figure 12-10, type the necessary RUNAS command, such as runas /user:CPANDLsysadmin mmc %SystemRoot%System32compmgmt.msc , and then click Next. Figure 12-10. Type the RUNAS command to use, and then click Next. Chapter 12 Part 4: Managing Windows Server 2003 Systems
If you are looking for cheap and quality webhost to host and run your website check Jboss Web Hosting services.