web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / PDF Printer defaulting...
Microsoft Dynamics GP (Archived)

PDF Printer defaulting on GP2010 on Terminal Server

(0) ShareShare
ReportReport
Posted on by Olaf Laos 1,890

Adobe Acrobat was deployed onto a Terminal Server and now we find that all Terminal Server users get the PDF printer as default within Dynamics GP 2010 - even though their Terminal Server profiles have a different default Windows printer.

We would be interested to know what is making GP override the windows default printer with the PDF printer.

Could it be related to the DEX.ini file?

We see a lot of references, as per example below, on the DEX.ini file of the GP2010 client running on the Terminal Server - and we see an reference to "pdfwinspool" also:-

TS072winspool=0;0

TS066winspool=0;0

TS094winspool=0;0

TS195winspool=0;0

TS208winspool=0;0

TS265winspool=0;0

TS330winspool=0;0

WSD-4f9010f3-3ed8-423e-aea8-92a8675d619e.003cwinspool=0;0

TS384winspool=0;0

192.168.6.13winspool=0;0

TS343winspool=0;0

TS023winspool=0;0

Documents\*.pdfwinspool=0;0

TS406winspool=0;0

Any help would be appreciated.

*This post is locked for comments

I have the same question (0)
  • L Vail Profile Picture
    L Vail 65,271 on at

    Hi,

    I can't help with the printer, but I can help with the mess it's making in your dex.ini file. You need to install the support debugging tool and use the Dex.ini configuration management so all of those winspool items are not allowed to be added. They are junk in the .ini file. Set the support debugging tool as is explained in the first section of the manual that comes with it and you will be very pleased with the results.

    Kind regards,

    Leslie

  • Community Member Profile Picture
    Community Member on at

    It could be a problem with GP grabbing a printer a bit too early. If GP gets fired before the completion of the terminal server printer mappings it is known to grab the last installed printer.

    Perhaps it might be worth to login to the terminal server, wait for few minutes and launch notepad or an MS Office app if available. Take note of the default printer. Launch GP and take note of the default printer.

    I am sure if you post the results here, senior experts will be able to point you in the right direction.

     

     

     

  • Community Member Profile Picture
    Community Member on at

    Olly

    Mariano does say you can control the pesky entries using support debugging tool.

    community.dynamics.com/.../40065.aspx,

    but the discussion stops there with a reference and not the solution.  

    In this blog post Andrew Cooper struggling with winspool, thanks Mariano for this post

    dynamicsgpblogster.blogspot.com/.../retrieving-windows-registry-key-values.html

    which I think was written in Latin or Greek - we also have same problem, as of now our procedure is clean up the dex.ini as maintenance task every week in the mean while trying to get into the thoughts of Mariano.

    Happy Halloween!

    Sanjay

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans