Default Printers using GP RDP Via Terminal Servers

(0) Share

Report

Posted on by Community Member

We recently migrated the gp2010 to a new virtual 2012 R2 Server and have the following End User Issues , it looks like it is really in a MS unsupported environment so any help or idea on how to solved the following is really appreciated. 1- When Users login they always have to go to the Printer Setup within GP so that they can select their printer. Anyway on default the end user printer. 2- Printer speed is slow compared to how it prints using a CITRIX server 3- GP Windows Pop-up hidden in the background

*This post is locked for comments

All responses (11)

Answers (0)

Community Member on at

Like (0)

Report

RE: Default Printers using GP RDP Via Terminal Servers

ThinPrint is a print management solution for Citrix / VMWarre environments. It takes the hassle out of dealing with print drivers in these types of environments.
Community Member on at

Like (0)

Report

RE: Default Printers using GP RDP Via Terminal Servers

What is a thin print client?
Jonathan Fear on at

Like (0)

Report

RE: Default Printers using GP RDP Via Terminal Servers

1. If you are using GP as a Published application this is happening because GP is loading before the Windows default printer is determined. To resolve this you can use a delay.

Create a batch file that creates a delay. Here is a link that has this information:

2624437 Frequently Asked Questions about RemoteApp and Dynamics GP

mbs.microsoft.com/.../KBDisplay.aspx

2. Unfortunately I cannot offer much on the performance issue as that isn't something I know too much about.

3. This issue sounds a lot like the previous issues we saw with 2008 R2 like you noted. There was bugs that were fixed from the RemoteApp side for R2 but you could be running into a similar bug with Server 2012 R2. I would say if you cannot reproduce the issue when you do a full remote desktop connection then this would be a similar bug that the RemoteApp team had with Server 2008 R2. It is important to remember that this is not a GP bug but rather a problem with how RemoteApp handles the 'scraping' process for certain applications.

Hope this helps.
kpw 935 on at

Like (0)

Report

RE: Default Printers using GP RDP Via Terminal Servers

We use a thin print client for our users on terminal services or citrix
Community Member on at

Like (0)

Report

RE: Default Printers using GP RDP Via Terminal Servers

The Pop Up window hidden solution is for 2008 R2 server not 2012 R2 server.
Community Member on at

Like (0)

Report

RE: Default Printers using GP RDP Via Terminal Servers

Thanks David, I just confirmed that we don't even have a printer server , all our printers are local so will start the project next week, the dex.ini idea is good, we can perhaps start with a few users and them test.

Regards,

Tony
Community Member on at

Like (0)

Report

RE: Default Printers using GP RDP Via Terminal Servers

No worries. I make the assumption that in the environment the end users have a print server which each person gets their printers from. To check what type of drivers they have installed you can open Control Panel > Devices and Printers. Then right click on the printer in question and select Printer Properties. Then if the user has the right admin privileges click on the 'Advanced" tab and it should list the driver being used.
davidf. on at

Like (0)

Report

RE: Default Printers using GP RDP Via Terminal Servers

Here is a link to the hotfix regarding the "Pop Under" problem.

support.microsoft.com/.../2580346
davidf. on at

Like (0)

Report

RE: Default Printers using GP RDP Via Terminal Servers

Don't give up! I went to Terminal Server Remote Apps exclusively for GP client about 4 years ago. You just have to keep hacking away to get the settings right.

I have no clue how your server environment is set up but this is what worked for me.

Printers: this is the biggest issue...

1: Use networked printers instead of local printers. Even if the printer is physically attached to a desktop, add the printer to your PDC as a shared printer.

2: Install the exact same printer driver to the workstation and TS ( terminal server). Log in to the TS desktop as each user to create the local user profile and set the Default Printer on the TS to be the same as the Local Default Printer.

3: For each user on the TS, make a directory in their Users folder called "DynamicsGP2010" or something like that and save a copy of the Dex.ini file in that folder. This ensures that each user has their own Dex.ini.

4: Create a batch file to launch GP instead of the regular "dynamics.exe dynamics.set" method. This way you can specify where to pick up the dex.ini for each user. Since our ole notes are on a share drive, my batch file first maps the share, then launches GP.

net use z: \\storage\gpshare /persistent:yes

start "" "C:\Program Files (x86)\Microsoft Dynamics\GP2010\Dynamics.exe" "C:\Program Files (x86)\Microsoft Dynamics\GP2010\Dynamics.set" "%userprofile%\DynamicsGP2010\Dex.ini"

5: Use this batch file to create your Remote App for your GP users.

What this does is since the dex.ini stores some printer info, each user having their own dex.ini will help GP "remember" each users settings. This has worked pretty consistently for my users. Sometimes it still gets "off" and the wrong printer driver pops up but I'd say this works about 95% of the time.
Community Member on at

Like (0)

Report

RE: Default Printers using GP RDP Via Terminal Servers

Jonathan , thanks for your input , where do I check the , should I check under the Terminal Servers , the environment is that they really go to a website 1st and from there they login or click into an ICON that lets them RDP to the Server that has GP.

We have a broker server them two Servers under the load balance.

If you can guide me better, my background is really CPA but trying to troubleshoot some IT stuff in order to help our end users.

Elant