Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Long logon time when you use the AddPrinterConnection VBScript command to map printers for users during logon process in Windows

Long logon time when you use the AddPrinterConnection VBScript command to map printers for users during logon process in Windows

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2 Service Pack 1 (SP1)-based terminal server.
  • The terminal server is configured to use the AddPrinterConnection VBScript command to map printers for users during the logon process.
  • You try to log on to the terminal server.
In this scenario, it takes longer than expected to log on to the terminal server. Additionally, the terminal server experiences high CPU usage.

Notes
  • When this issue occurs, the terminal server is unresponsive until the printers are mapped.
  • The expected logon time is within one minute.

↑ Back to the top

Cause

This issue occurs because the following operations are performed redundantly after the AddPrinterConnection VBScript command is called to create network printer mappings during the logon process:
  • Redundant registry keys are populated.
  • A printer driver is downloaded and reinstalled every time that a printer connection is added. This occurs even though the driver exists on the terminal server.

↑ Back to the top

Resolution

To resolve this issue, we have released a hotfix for Windows Server 2008 R2 and Windows Server 2012, and we have released an update rollup for Windows Server 2012 R2 and Windows Server 2012.

Shall I choose hotfix or update rollup?
The update rollup fixes many other issues in addition to the issue that the hotfix fixes. We recommend that you use the update rollup. The update rollup is larger than the hotfix. Therefore, the update rollup takes longer to download.

Get the update rollup for Windows Server 2012 R2 and Windows Server 2012

To resolve this issue, install the May 2014 update rollup for Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2.

To resolve this issue, install the December 2014 update rollup for Windows RT, Windows 8, and Windows Server 2012.

Get the hotfix for Windows Server 2012 and Windows Server 2008 R2

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 the problem described in this article. 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 website:
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

To apply this hotfix, you must install Service Pack 1 for Windows Server 2008 R2.

Registry information

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

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

↑ Back to the top

More Information

File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies to" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    1.17xxx    		Windows Server 2008 R2SP1GDR
    6.1.760
    1.22xxx    		Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Localspl.dll6.1.7601.22502965,63205-Nov-201310:48x64
Winprint.dll6.1.7601.1751439,42420-Nov-201013:27x64
Win32spl.dll6.1.7601.22502756,22405-Nov-201310:49x64
Win32spl.dll6.1.7601.22502756,22405-Nov-201310:49x64
Win32spl.dll6.1.7601.22502497,15205-Nov-201309:56x86
Win32spl.dll6.1.7601.22502497,15205-Nov-201309:56x86
Localspl.dll6.1.7601.22502776,70405-Nov-201309:54x86
Winprint.dll6.1.7601.1751430,20820-Nov-201012:21x86
For all supported IA-64–based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Localspl.dll6.1.7601.225022,079,23205-Nov-201309:47IA-64
Winprint.dll6.1.7601.1751490,62420-Nov-201010:28IA-64
Win32spl.dll6.1.7601.225021,527,80805-Nov-201309:49IA-64
Win32spl.dll6.1.7601.22502497,15205-Nov-201309:56x86

Windows Server 2012 file information notes

Important Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.2.920 0.16xxxWindows Server 2012RTMGDR
    6.2.920 0.17xxxWindows Server 2012RTMGDR
    6.2.920 0.21xxxWindows Server 2012RTMLDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Compstui.dll6.2.9200.16384308,73626-Jul-201203:05x64
Dafprintprovider.dll6.2.9200.2115855,80825-Jun-201404:20x64
Findnetprinters.dll6.2.9200.1638466,04826-Jul-201203:05x64
Printui.exe6.2.9200.1638462,97626-Jul-201203:08x64
Puiapi.dll6.2.9200.16384187,39226-Jul-201203:07x64
Puiobj.dll6.2.9200.21283458,24004-Nov-201423:25x64
Localspl.dll6.2.9200.171691,024,51205-Nov-201406:39x64
Winprint.dll6.2.9200.1645139,93606-Nov-201204:19x64
Localspl.dll6.2.9200.212831,039,36004-Nov-201423:25x64
Winprint.dll6.2.9200.2055539,93606-Nov-201204:25x64
Win32spl.dll6.2.9200.17169733,18405-Nov-201406:40x64
Win32spl.dll6.2.9200.21283733,18404-Nov-201423:26x64
Compstui.dll6.2.9200.16384288,76826-Jul-201203:18x86
Dafprintprovider.dll6.2.9200.2115845,05625-Jun-201404:05x86
Findnetprinters.dll6.2.9200.1638453,76026-Jul-201203:18x86
Printui.exe6.2.9200.1638461,95226-Jul-201203:20x86
Puiapi.dll6.2.9200.16384162,30426-Jul-201203:19x86
Puiobj.dll6.2.9200.16384339,96826-Jul-201203:19x86

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File propertyValue
File nameAmd64_541004444788cae44ca1182575f71090_31bf3856ad364e35_6.1.7601.22502_none_10f12962507b274b.manifest
File versionNot applicable
File size722
Date (UTC)05-Nov-2013
Time (UTC)14:42
File nameAmd64_a37afca7131fd37a7bcd6ac1dbb3a57c_31bf3856ad364e35_7.1.7601.22502_none_4216a0669766fbff.manifest
File versionNot applicable
File size1,086
Date (UTC)05-Nov-2013
Time (UTC)14:42
File nameAmd64_ab558592de6b9e805d35a8e10046b36e_31bf3856ad364e35_6.1.7601.22502_none_85bb5f25976e9a9d.manifest
File versionNot applicable
File size720
Date (UTC)05-Nov-2013
Time (UTC)14:42
File nameAmd64_ac00991b52acc3b71061711509c5c069_31bf3856ad364e35_6.1.7601.22502_none_06dcfd978501edb7.manifest
File versionNot applicable
File size722
Date (UTC)05-Nov-2013
Time (UTC)14:42
File nameAmd64_ddf061c2565bcb8890cfe596cab13e47_31bf3856ad364e35_6.1.7601.22502_none_a3976213d291bbad.manifest
File versionNot applicable
File size722
Date (UTC)05-Nov-2013
Time (UTC)14:42
File nameAmd64_microsoft-windows-p..ooler-core-localspl_31bf3856ad364e35_6.1.7601.22502_none_8ed3b6dfc26510c1.manifest
File versionNot applicable
File size4,845
Date (UTC)05-Nov-2013
Time (UTC)14:48
File nameAmd64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.1.7601.22502_none_982b939da0a0fbd8.manifest
File versionNot applicable
File size10,428
Date (UTC)05-Nov-2013
Time (UTC)11:18
File nameAmd64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_7.1.7601.22502_none_899c0fe32b87a4a7.manifest
File versionNot applicable
File size6,373
Date (UTC)05-Nov-2013
Time (UTC)11:16
File nameWow64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.1.7601.22502_none_a2803defd501bdd3.manifest
File versionNot applicable
File size10,426
Date (UTC)05-Nov-2013
Time (UTC)10:08
File nameWow64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_7.1.7601.22502_none_93f0ba355fe866a2.manifest
File versionNot applicable
File size6,371
Date (UTC)05-Nov-2013
Time (UTC)10:09
File nameX86_microsoft-windows-p..ooler-core-localspl_31bf3856ad364e35_6.1.7601.22502_none_32b51b5c0a079f8b.manifest
File versionNot applicable
File size4,844
Date (UTC)05-Nov-2013
Time (UTC)14:48
Additional files for all supported IA-64–based versions of Windows Server 2008 R2
File propertyValue
File nameIa64_cae9194819158f3202802d15e7007074_31bf3856ad364e35_6.1.7601.22502_none_05cb7eda36e5d4e2.manifest
File versionNot applicable
File size1,084
Date (UTC)05-Nov-2013
Time (UTC)14:42
File nameIa64_e5da294de1b3bfb9270e8f6cfdc7a006_31bf3856ad364e35_6.1.7601.22502_none_0f040e0b29f82613.manifest
File versionNot applicable
File size720
Date (UTC)05-Nov-2013
Time (UTC)14:42
File nameIa64_microsoft-windows-p..ooler-core-localspl_31bf3856ad364e35_6.1.7601.22502_none_32b6bf520a05a887.manifest
File versionNot applicable
File size4,844
Date (UTC)05-Nov-2013
Time (UTC)14:42
File nameIa64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.1.7601.22502_none_3c0e9c0fe841939e.manifest
File versionNot applicable
File size10,426
Date (UTC)05-Nov-2013
Time (UTC)10:23
File nameWow64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.1.7601.22502_none_a2803defd501bdd3.manifest
File versionNot applicable
File size10,426
Date (UTC)05-Nov-2013
Time (UTC)10:08

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012
File propertyValue
File nameAmd64_1cf00af93011299470a578cf1edd997d_31bf3856ad364e35_6.2.9200.21285_none_1e68384bc16bcbfb.manifest
File versionNot applicable
File size1,453
Date (UTC)06-Nov-2014
Time (UTC)01:45
File nameAmd64_230613d6959e7b0c667b8401a0b27950_31bf3856ad364e35_6.2.9200.17169_none_d4aa7bcea18139f9.manifest
File versionNot applicable
File size722
Date (UTC)06-Nov-2014
Time (UTC)01:45
File nameAmd64_4a350bbc9e19155bd6ec0b64b4bddb9e_31bf3856ad364e35_6.2.9200.21285_none_940e08ea10b9c165.manifest
File versionNot applicable
File size1,092
Date (UTC)06-Nov-2014
Time (UTC)01:45
File nameAmd64_4bd39a8ada497a3644df3d439f5f6a19_31bf3856ad364e35_6.2.9200.17169_none_e58d30e96c21b020.manifest
File versionNot applicable
File size1,086
Date (UTC)06-Nov-2014
Time (UTC)01:45
File nameAmd64_676a0482eeb209e6b9c74b44754d8fbc_31bf3856ad364e35_6.2.9200.21285_none_8d3657d269e0d8d6.manifest
File versionNot applicable
File size1,450
Date (UTC)06-Nov-2014
Time (UTC)01:45
File nameAmd64_7fce218e8f243a613e8d41405d004694_31bf3856ad364e35_6.2.9200.17169_none_82efc7f7ac8e7a13.manifest
File versionNot applicable
File size722
Date (UTC)06-Nov-2014
Time (UTC)01:45
File nameAmd64_98e6fa70b1fa90bf3d7e37917e8c1d5e_31bf3856ad364e35_6.2.9200.21285_none_512d27d068e9218a.manifest
File versionNot applicable
File size1,089
Date (UTC)06-Nov-2014
Time (UTC)01:45
File nameAmd64_d49fd0d306eeb935b082fedf7719e093_31bf3856ad364e35_6.2.9200.17169_none_a257248b1c0c0ea5.manifest
File versionNot applicable
File size722
Date (UTC)06-Nov-2014
Time (UTC)01:45
File nameAmd64_microsoft-windows-p..installerandprintui_31bf3856ad364e35_6.2.9200.21285_none_2fa8698598cd5957.manifest
File versionNot applicable
File size24,894
Date (UTC)06-Nov-2014
Time (UTC)01:45
File nameAmd64_microsoft-windows-p..ooler-core-localspl_31bf3856ad364e35_6.2.9200.17169_none_88ff8c161c5db4f6.manifest
File versionNot applicable
File size5,205
Date (UTC)06-Nov-2014
Time (UTC)01:45
File nameAmd64_microsoft-windows-p..ooler-core-localspl_31bf3856ad364e35_6.2.9200.21285_none_896f87e1358f2746.manifest
File versionNot applicable
File size5,205
Date (UTC)06-Nov-2014
Time (UTC)01:45
File nameAmd64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.2.9200.17169_none_925768d3fa99a00d.manifest
File versionNot applicable
File size10,489
Date (UTC)05-Nov-2014
Time (UTC)07:43
File nameAmd64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.2.9200.21285_none_92c7649f13cb125d.manifest
File versionNot applicable
File size10,489
Date (UTC)05-Nov-2014
Time (UTC)02:21
File nameWow64_microsoft-windows-p..installerandprintui_31bf3856ad364e35_6.2.9200.21285_none_39fd13d7cd2e1b52.manifest
File versionNot applicable
File size24,148
Date (UTC)06-Nov-2014
Time (UTC)01:45
File nameWow64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.2.9200.17169_none_9cac13262efa6208.manifest
File versionNot applicable
File size9,276
Date (UTC)05-Nov-2014
Time (UTC)05:52
File nameWow64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.2.9200.21285_none_9d1c0ef1482bd458.manifest
File versionNot applicable
File size9,276
Date (UTC)05-Nov-2014
Time (UTC)00:26

↑ Back to the top

Status

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

↑ Back to the top

References

See the terminology that Microsoft uses to describe software updates.


↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2896881
Revision : 1
Created on : 1/7/2017
Published on : 12/9/2014
Exists online : False
Views : 208