Windows 2000 Server
You install and run a third-party 32-bit application named Application on your Windows 2000 Server computer. After several days, the application stops responding. You open Task Manager and find that the CPU usage is at 100 percent. The normal range of CPU usage on the server is from 20 percent to 30 percent You end the application. However, you see that the CPU on the server is still at 100 percent. Task Manager shows no other applications running. You then examine the Processes page in Task Manager and confirm that the Application.exe process is no longer running. You want to return the CPU usage to its normal range. What should you do?
Use Computer Management to stop and restart the Workstation service
Use Task Manager to end and automatically restart the Explorer.exe process
None of above
Use Computer Management to stop and restart the Server service
Use Task Manager to end any related child processes
Create an Unattend.txt file by using Setup Manager. Create a UDF file that identifies the names of the new computers
Install Windows 2000 server on the computers. Use Sysprep.exe to create the Unattend.txt file, place file on the root of the drive
Create a UDF file by using setup manager. Create an Unattend.txt file that identifies the names of the new computers
Install Windows 2000 server on the computers. Use Setup Manager to create a sysprep.inf file for use with sysprep.exe Place the sysprep.inf on the computers and run sysprep -noidgen
Configure a Group policy for the Domain that blocks all unsigned drivers
Do nothing, this is the default setting
Configure a Group policy for the Default Domain Controller to block all unsigned drivers
Configure the Windows 2000 file servers, Windows 2000 print servers, Windows 2000 professional computers and Windows 2000 file servers to block unsigned drivers
Ensure that the third disk is attached to the server and has power. Use Disk Management to reactivate the disk
Replace the third disk and restart the server. Use disk Management to repair the volume
Ensure that the third disk is attached to the server and has power. Use Disk Management to repair the volume
Install a new disk and create a single extended partition on the new disk. Restart the computer and allow Windows 2000 to automatically repair the volume on the extended partition