Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm a newbie in AD domain administration. I'd like to deploy our printers to client workstations mostly running WXP. Windows Server 2012, added Print Management feature, followed a tutorial on deploying printers using Group Policies. Printer is connected via a TCP/IP port.

Windows Server 2008/2012 do not contain pushprinterconnections.exe by default. Addded pushprinterconnections.exe from pmcmgmt.exe package from and put it to a new group policy logon script.

When user log in, the error "_ftol2_sse entry point not found in dynamic library msvcrt.dll" is displayed. Printer is visible in Printers/Faxes but does not print (throwing the error above).

Fresh XP installation nor installing Visual C++ redistributable 2010 didn't help.

Thanks in advance for any help.

share|improve this question
There are at least 3 methods to deploy printers via GP. How about telling us what method you're using. In addition, have you installed the GPP CSE for Windows XP on the Windows XP clients? - – joeqwerty Jan 15 '13 at 12:35
Thanks for the link! It helped me with another things (i.e. mapping shares without the script calling net use). However pushprintconnections.exe error is still displayed. I followed the tutorial - starting from 3:00 (related to Windows Server 2008) - in 2012 it was almost the same. – user681768917 Jan 15 '13 at 15:07
I'm thinking that you don't need to use pushprinterconnections.exe with GPP. – joeqwerty Jan 15 '13 at 15:23
But without it the Printers and Faxes in XP are empty. (Tested now on a fresh AD user.) The users who already ran pushprintconnections.exe have the printer installed but not working. (_ftol2_sse entry point... error when trying to print). I'm going to google for other printer deploying methods. Thanks a lot. – user681768917 Jan 15 '13 at 15:36
up vote 1 down vote accepted

There weren't additional 32bit printer drivers installed on the 64bit server.

This was obviously the cause of that strange error - pushprinterconnections.exe ran deployed to 32bit XP and tried to communicate with the printer...

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.