The following Windows NT tip comes from the vast TechRepublic archives. It was featured in our Windows NT TechMail dated November 15, 1999. Will it still work today in Windows Server 2003? Yup! Check it out.
The following Windows NT tip comes from the vast TechRepublic archives. It was featured in our Windows NT TechMail dated November 15, 1999:
Today’s Windows NT Tip
Hunt down problem drivers with remote registry editing
Looking for a quick way to deal with a driver that’s hanging your NT system? This tip won’t help you if you’re faced with a Blue Screen of Death, but if Windows NT is running and only the user interface isn't functioning, chances are that Windows NT's 32-bit network services are still functioning. If this is the case, you can edit the registry from another computer.
To do so, first log on to another computer within the domain as the administrator. Next, open the Registry Editor using the REGEDIT command. When the Registry Editor starts, select Connect Network Registry from the Registry menu. When you do, you'll see the Connect Network Registry dialog box. Specify the name of the malfunctioning computer and click OK. If the network services are functional, you should now be able to edit the malfunctioning computer's registry. When you finish, close the Registry Editor and restart the malfunctioning computer.
This tip actually still works in Windows Server 2003. The only major difference is that when you click Connect Network Registry, you'll see the Select Computer dialog box which will allow you to search Active Directory for the target computer.