Don't get lost when your Windows 2000 Server's GUID overloads

by Jim Boyce | Feb 26, 2007 8:00:00 AM

Tags: Servers, Jim Boyce, Microsoft Windows 2000, Microsoft Windows 2000 Server, GUID, Microsoft Windows, server, Windows 2000 Server Tips Newsletter

Takeaway: Windows 2000 Server's globally unique identifier (GUID) can wreak havoc when it runs out of memory. Find out how you can avoid the problem by creating a backup in case the GUID gets overloaded.

There's a bug in Windows 2000 Server that makes the system unable to read the globally unique identifier (GUID) when it's all out of memory—virtual and otherwise. When that happens, the system thinks there isn't one and rewrites a completely new one right on top of the old one.

If this has happened to you, you know how bad it can be—it's the equivalent of the machine losing its identity and becoming unrecognizable by its pals. Here's how to avoid this problem before it befalls you.

1. Open your registry editor and navigate to
   

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography

2. Save the key as a text file and name it something useful like guid_fix.txt. The first item in the long list is the actual GUID, so you may safely delete all of the other key blocks.
3. Save a copy to three or four different places just to be safe.
4. Save it to a disc for safekeeping.

Note: Please remember that editing your registry can be risky, so always have a verified backup before you begin.

Miss a column?

Check out the Windows 2000 Server archive, and catch up on the all the W2K Server columns.

Want more Win2K tips and tricks? Automatically sign up for our free Windows 2000 Server newsletter, delivered each Tuesday!

Print/View all Posts Comments on this article

No real info provided!bmagurn@...  | 03/02/07