You encounter SMS administrator issues after you modify the MaxTokenSize registry entry

After you apply post-Windows 2000 Service Pack 1 (SP1) fixes or Windows 2000 Service Pack 2 (SP2) and modify the MaxTokenSize registry entry to increase the Kerberos token size, various Systems Management Server (SMS) administrator issues may occur. For example, you may encounter the following issues:

• When you create a package from definition, you may receive the following error message:
  Description: Wizard internal error: invalid WBEM ExecMethod result. Please exit the Wizard.
  HRESULT : 0x800706BF-The remote procedure call failed and did not execute.
• When you try to create a new advertisement, you may receive the following error message:
  No properties are available on this object.
• When you enumerate collections, you receive a list of Collection icons, but the collection name may be missing. For example, you may not see the "All Systems" name even though the typical icon is still displayed.
• When you browse collections in the Advertisement Wizard, you may also receive the following error message:
  _com_error exception in MMC Admin UI!

This issue may occur if the value of the MaxTokenSize entry is set too high. The maximum value is FFFF (hexadecimal). This value can also be entered as 65535 (decimal). A common mistake is to set the value to 65535 (hexadecimal), which is equivalent to 415029 (decimal). This value is too high.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: To resolve this issue, set the value of the MaxTokenSize entry as a decimal value. For more information, click the following article number to view the article in the Microsoft Knowledge Base: