what system rights are required to install devices

Device drivers: Installation and configuration

To install hardware devices on Windows servers, admins must install the appropriate device drivers first. Here are some guidelines for installing, configuring and troubleshooting device drivers.

System administrators frequently have to install hardware devices such as disk controllers and network cards on their Windows servers. To do and so, they must install the appropriate device drivers on the server first.

Here are some guidelines for installing, configuring and troubleshooting device drivers, which provide the necessary interface betwixt the application programs and the actual hardware, on Windows 2000 server system.

Methods of installing device drivers

Admins can install device drivers on a server in four means.

Running the Setup. Device drivers are automatically installed for all detected devices during installation of Windows 2000 system on the server computer
Starting the computer. Whenever the server is started, new devices are detected and their device drivers are automatically installed
Scanning for new hardware.Add/Remove Hardware Sorcerer can be used to perform the hardware-detection procedure and desired device driver installation
Manual installation. You can use the Add together/Remove Hardware Wizard to specify the device you desire to install, or yous tin right-click the .INF file that comes with the driver and cull Install.

Note: You must have administrative privileges on the server to install device drivers

Configuring devices using Device Managing director

Device Managing director displays information well-nigh all devices installed on your server. It displays a listing of devices that were either detected or for which drivers are installed. The icon for the device indicates whether the device is in proper working condition.

Normal icon indicates that the device driver has initialized successfully while an Assertion point on icon would mean that device is incorrectly configured and a Stop sign on icon means that device could not be initialized due to hardware conflicts.

To resolve hardware conflicts and to override the resources or the device driver that were assigned to a device, follow these steps:

Start Device managing director by typing 'Devmgmt.msc' in the Run dialog box.
Right-click the desired device and select Properties.
Click the Resources tab on the Properties dialog box.
Click the resources to exist changed and and so articulate the "Use automatic settings" checkbox.
Click Modify Setting and then change the value of the setting to the desired value.

Still best thing to exercise is to let Plug and Play resolve conflicts whenever possible.

Changing the driver source location

While adding a device to your system, Windows 2000 provides a driver, which gets installed from the Driver.cab file in the systemroot\DriverCache\I386 binder. Tthis file is approximately 50 MB. If the driver cannot be establish in Driver.cab, Windows 2000 will prompt you for the location of the commuter.

It's a skilful idea to continue this file at a key location so that all clients install drivers from a consistent key source. To modify the source path in the Registry and delete the local copy of Driver.cab, but update the data for the "SourcePath" value in his key in the Registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
This will also save space on the hd of client computers.

Updating and removing device drivers

Administrators often have to update the existing device drivers or remove them. To update a device driver:

Start Device Managing director by typing 'Devmgmt.msc' in the Run dialog box.
Right-click the desired device and select Properties.
Click the 'Commuter' tab and then click the Update Driver button.

To remove a device:

Outset Device Managing director past typing 'Devmgmt.msc' in the Run dialog box.
Correct-click the desired device and select Properties.
Click the 'Commuter' tab and then click Uninstall button

Note: Removing the device does not actually delete the device driver itself. What it does is remove references to the driver from the Registry so that the figurer does non load the driver.

Upgrading from uniprocessor to multiprocessor

Many times the demand arises to get your server upgraded in terms of software and hardware. If Windows 2000 was originally installed on a unmarried processor PC and a second processor is to exist added, you demand to update the system software. To exercise so::

Outset Device manager by typing 'Devmgmt.msc' in the Run dialog box.
Expand the Computer icon and make notation of the computer model.
Right-click the estimator model beneath the Computer icon and select Properties.
Begin the Upgrade Device Driver Sorcerer by clicking on the Update Commuter button from the Commuter tab.
Choose Display a List of Known Drivers For This Device so click Next.

By selecting Evidence All Hardware of This Device Class, you can choose from a list of supplied multiprocessor drivers. If you lot take W2k-specific multiprocessor drivers, use the Have Disk button.

Driver signing

Driver signing ensures that the drivers take been certified by Windows Hardware Quality Labs (WHQL). It has been implemented in Windows 2000 to improve the quality of drivers and increment the overall stability of the Windows operating system.

Microsoft digitally signs all files and drivers on the Windows 2000 installation CD. But administrators often download drivers from the Internet or get them from various hardware vendors. To configure how these third-party drivers should be handled:

Open Command Panel.
Select the System Backdrop icon.
Switch to Hardware tab, and click the Driver Signing button.

A dialog box opens which has three checkboxes:

Ignore (allows installing all files, regardless of the file signature)
Warn (displays a message to the user before installing an unsigned file). This is normally the default setting.
Block (restricts the installation of unsigned files).

Check the required checkbox and hit OK.

Disabling devices and services for a specific contour

Individual devices and services may be configured to load or not load as office of a Hardware Profile. To disable devices:

Open up Device Manager and select Properties of the desired device
On the General tab nether 'Device Usage' label select Practise non use this device (disable) option
Click OK.

To disable services:

From Administrative Tools, select Services.
Select the Log On tab from the Properties dialog of any of the Services
Click on Enable or Disable for the selected Hardware Profile.

Driver installations: failure and recovery

Here are three problems that commonly occur during the installation of a device driver and their solutions:

Problem: Wrong commuter is installed

Solution: Press F8 at startup and use the Last Known Expert Configuration

Problem: Driver gets installed partially or some files are missed during installation.

Solution: Utilize a command-line utility called "System File Checker" that can verify the version of protected system files and revert to a previous version. Type sfc.exe /scannow on the command prompt for running the utility.

Trouble: Files are decadent during installation.

Solution: Uninstall or remove the device commuter, restart the server and reinstall the commuter.

About the author: Rahul Shah currently works at a software firm in India, where he is a systems administrator maintaining Windows servers. He has also worked for various software firms in testing and analytics, and also has experiences deploying client/server applications in dissimilar Windows configurations.

Dig Deeper on Microsoft Windows hardware, including laptop and notebook reviews

A complete guide to troubleshooting Windows Hello

Past: Gary Olsen
How to fix printer bug after a Windows 10 update

By: Brien Posey
How to utilize and troubleshoot with Device Manager in Windows ten

By: Stephen Bigelow
Troubleshoot Bluetooth connexion problems in Windows 10

By: Stephen Bigelow