FIX: Applications that are written for Windows Services for UNIX 3.5 or for Windows Services for UNIX 3.0 cannot retrieve data from Active Directory on a domain controller that is running Windows Server 2003 R2

Article translations Article translations
Article ID: 921599 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You have two or more domain controllers in an Active Directory directory service forest that are running Microsoft Windows Services for UNIX 3.5. Additionally, the domain controllers have Server for NIS or the Password Synchronization component installed.
  • You upgrade one or more of the domain controllers to Microsoft Windows Server 2003 R2. However, you do not upgrade all the domain controllers to Windows Server 2003 R2.
  • The new Windows Server 2003 R2 schema will be disseminated throughout the forest, even on the domain controllers that have Services for UNIX 3.x installed.
In this scenario, Server for NIS on the domain controllers that have Windows Services for UNIX installed cannot retrieve all the required data from Active Directory. This problem occurs because the data is stored in separate attributes on the Windows Services for UNIX domain controller that has Server for NIS installed, compared to a Windows Server 2003 R2 domain controller that has Identity Management for UNIX’s Server for NIS component installed.

CAUSE

This problem occurs because Active Directory data is stored differently on a domain controller that is running Windows Services for UNIX 3.5 or Windows Services for UNIX 3.0 compared to a domain controller that is running Windows Server 2003 R2.

On a domain controller that is running Windows Services for UNIX 3.5 or Windows Services for UNIX 3.0 and has Server for NIS installed, data is stored in attributes that are defined by the Windows Services for UNIX schema. When you upgrade the domain controller to Windows Server 2003 R2, the newer RFC 2307 compliant Windows Server 2003 R2 schema is installed on the domain controller. When you upgrade the Windows Services for UNIX 3.5’s Server for NIS to Identity Management for UNIX’s Server for NIS component on this Windows Server 2003 R2 domain controller, the domain controller starts saving the NIS data in the newer RFC 2307 compliant attributes.

The Windows Services for UNIX’s Server for NIS component that is installed on other Windows Server 2003 domain controllers in the Active Directory forest continues to store data in attributes that are defined by the Windows Services for UNIX schema. Because the data is saved in the older schema attributes, Server for NIS on these Windows Services for UNIX domain controllers may not respond correctly to the NIS clients.

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Windows Server 2003 R2 installed to apply this hotfix.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Nis2ad.exe8.0.1969.462,122,75219-Jul-200621:53x86
Nisadmin.exe8.0.1969.46219,13619-Jul-200621:53x86
Nismap.exe8.0.1969.462,122,75219-Jul-200621:53x86
Nisprop.dll8.0.1969.46112,64019-Jul-200621:53x86
Nissvc.exe8.0.1969.46187,39219-Jul-200621:53x86
Pswdsync.dll8.0.1969.46109,56819-Jul-200621:53x86
Regini.exe5.0.2134.135,60019-Jul-200621:53x86
Yppush.exe8.0.1969.4676,28819-Jul-200621:53x86

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

After you apply this hotfix, the Server for NIS component and the Password Synchronization component of Windows Services for UNIX 3.5 can correctly integrate with the newer Windows Server 2003 R2 schema.

You must install this hotfix on the Windows Server 2003 domain controllers where Windows Services for UNIX 3.5 or Windows Services for UNIX 3.0 Server for NIS or the Password Synchronization component is installed.

REFERENCES

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
912309 How to upgrade Windows Server 2003 with Service Pack 1 to Windows Server 2003 R2
For more information about how to install the Password Synchronization component and UNIX side components for Identity Management for UNIX, visit the following Microsoft Web site:
http://www.microsoft.com/windowsserver2003/R2/unixcomponents/idmu.mspx
For more information about how to set up the Server for NIS component, visit the following Microsoft Web site:
http://technet2.microsoft.com/WindowsServer/en/Library/43d83e6f-c1fb-48de-88df-4cb5adbe6ebd1033.mspx?mfr=true
For more information about how to extend the schema in Windows Server 2003 R2, visit the following Microsoft Web site:
http://technet2.microsoft.com/WindowsServer/en/library/84445c1b-a418-4a09-a50c-5f3258cfc5b51033.mspx?mfr=true

Properties

Article ID: 921599 - Last Review: October 9, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Services for UNIX 3.5
  • Microsoft Windows Services for UNIX 3.0 Standard Edition
Keywords: 
kbautohotfix kbexpertiseadvanced kbHotfixServer kbqfe KB921599

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com