Rollup of Fixes for File and Print Services for NetWare (FPNW) Version 5.0

Microsoft has released an update that corrects the following problems in Microsoft File and Print Services for NetWare (FPNW) version 5.0:

• When you use the Active Directory Users and Computers snap-in to configure a user account with the NetWare-compatible logon option enabled and include any characters from the double-byte character set (DBCS) in the home directory path, the home directory path is not stored correctly.
• If the logon script contains DBCS characters, you may receive the following error message if you try to close (by clicking OK or Apply) the user's properties in the Active Directory Users and Computers snap-in:
  Windows cannot update the login scripts file due to error:
  
  The data area passed to a system call is too small.
• When you use the Active Directory Users and Computers or Local Users and Groups snap-in to create a new user in FPNW version 4.0, a subfolder (named with the user's object ID) is created in the Sysvol\Mail folder. In FPNW 5.0, this subfolder is not created until the user's logon script is edited in the NetWare-compatible user's logon script editor page of the Active Directory Users and Computers or Local Users and Groups snap-in.
• When you change an account that is not NetWare-enabled to become NetWare-enabled and simultaneously force password expiration, the account becomes NetWare-enabled but the password expiration setting is not saved.
• If you change the Grace Logins Remaining option in the NetWare Services properties dialog box to 0 and click OK, the 0 value is accepted. If you click Accept, the 0 value is automatically changed to 1. The minimum allowable value for Grace Logins Remaining should be 0.

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: The English-language version of this fix should have the following file attributes or later:

Microsoft has confirmed that this is a problem in Microsoft Windows 2000. This problem was first corrected in Windows 2000 Service Pack 2.

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base: