The following list shows things to consider before you enable Driver Verifier Manager. Be sure to evaluate the information and include other contingencies that are unique to your environment. If you suspect a driver is causing a problem, Microsoft recommends that you stress the computer in a test environment.
- Review the following Microsoft Knowledge Base articles:235496 How to enable a Memory.dmp file capture using the graphical user interface or the registry148954 How to set up a remote debug session using a modem216206 Blue screen or STOP error message troubleshooting before you call Microsoft Support
- Create an Emergency Backup Disk (EBD) and a full backup of the server.
- Create a contingency plan for production servers for extended down time.
- Notify users when you test the production server. You may want to tell them to save their data locally and frequently, and that performance may be slower.
- Do not verify all the drivers on the computer at the same time. Only test drivers that you suspect.
- When you run Driver Verifier wait at least 30 minutes to log on to the computer, especially if you are troubleshooting domain or network issues. After the user presses CTRL+ALT+DELETE, the recovery process used in LastKnownGood is updated with all of the registry settings, and you are then unable to utilize LastKnownGood as a recovery process to back out of Driver Verifier settings.
- If you need to contact Microsoft Product Support Services, advise the Support Professional that you are running Driver Verifier in your environment and also advise the Support Profession of any relevant case numbers.
- Force domain replications on domain controllers prior to starting, and then perform a backup, which includes system state.
رقم الموضوع: 251233 - آخر مراجعة: 07/01/2008 - المراجعة: 1