Open Software Solutions

Consider the following scenario. In an Active Directory domain environment, you deploy a user logon script to client computers in the domain. The logon script contains calls to Active Directory Service Interfaces (ADSI), such as Lightweight Directory Access Protocol (LDAP) queries. However, every time that a user logs on to the domain from a Windows Vista-based client computer, the client computer takes a long time (about 10 minutes) to process the logon script. During this time, no other ADSI queries can be executed.

This issue occurs if the ADSI call in the logon script involves downloading a schema cache file.

Back to the top

This issue is caused by an error in ADSI. Because of this error, the schema cache files are downloaded every time that the logon script is processed. However, the schema cache files should be downloaded only the first time that the logon script is processed or when the schema changes.

Back to the top

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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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:

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

To apply this hotfix, you must have Windows Vista Service Pack 1 (SP1) or Windows Server 2008 installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

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.

Windows Vista SP1 and Windows Server 2008, x86-based versions

File name	File version	File size	Date	Time	Platform
Package_1_for_kb952611~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,815	17-Jun-2008	18:01	Not Applicable
Package_2_for_kb952611~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,982	17-Jun-2008	18:01	Not Applicable
Package_3_for_kb952611~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,820	17-Jun-2008	18:01	Not Applicable
Package_4_for_kb952611~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,820	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,367	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_client~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,431	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,421	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_sc~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,423	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,425	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_server~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,431	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,422	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,429	17-Jun-2008	18:01	Not Applicable
Update.mum	Not Applicable	3,077	17-Jun-2008	18:01	Not Applicable
X86_d43262d7360564c9ba9359600e70e9fb_31bf3856ad364e35_6.0.6001.22204_none_b80384513a513063.manifest	Not Applicable	735	17-Jun-2008	18:01	Not Applicable
X86_microsoft-windows-a..terface-ldapc-layer_31bf3856ad364e35_6.0.6001.22204_none_5fc014127f975bc9.manifest	Not Applicable	9,798	17-Jun-2008	04:10	Not Applicable
Adsldpc.dll	6.0.6001.22204	199,168	17-Jun-2008	03:19	x86

Windows Vista SP1 and Windows Server 2008, x64-based versions

File name	File version	File size	Date	Time	Platform
Amd64_cabc2411d50e0ee4dde658ae1eca2dd3_31bf3856ad364e35_6.0.6001.22204_none_a68cee861ef908e4.manifest	Not Applicable	1,118	17-Jun-2008	18:01	Not Applicable
Amd64_fa4ab17d77f8887b3be502aeef9219ee_31bf3856ad364e35_6.0.6001.22204_none_8f1f8f58f57490d0.manifest	Not Applicable	739	17-Jun-2008	18:01	Not Applicable
Amd64_microsoft-windows-a..terface-ldapc-layer_31bf3856ad364e35_6.0.6001.22204_none_bbdeaf9637f4ccff.manifest	Not Applicable	10,134	17-Jun-2008	06:32	Not Applicable
Package_1_for_kb952611~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,825	17-Jun-2008	18:01	Not Applicable
Package_2_for_kb952611~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,247	17-Jun-2008	18:01	Not Applicable
Package_3_for_kb952611~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,083	17-Jun-2008	18:01	Not Applicable
Package_4_for_kb952611~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,083	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,375	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_client~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,439	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,429	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,431	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,433	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_server~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,439	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,430	17-Jun-2008	18:01	Not Applicable
Package_for_kb952611_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,437	17-Jun-2008	18:01	Not Applicable
Update.mum	Not Applicable	3,099	17-Jun-2008	18:01	Not Applicable
Adsldpc.dll	6.0.6001.22204	230,400	17-Jun-2008	03:45	x64

Back to the top

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

Back to the top

For more information about the schema cache, visit the following Microsoft Web site:

For more information about ADSI, visit the following Microsoft Web site:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top