Losing print Settings in Citrix

[klewis10367]

We are in a citrix environment running Great Plains v7.5 SP2 and are continually losing users print settings. We use a "Default Printer Setting" program to try and combat this, but it doesn't seem to be very consistant. Does anybody else have this problem and if so have you found a fix?

 

[Luvsql]

We are looking at implementing Uniprint, which actually prints using the local printer settings and sends the print job as a compressed pdf file instead of the large grahpic that GP uses. When you print in Great Plains, it opens the local computer's printer list and you choose which one and what properties (like other applications do normally).

We have so many issues with printing in Great Plains over citrix that we had to look at other solutions. Their website is

http://www.uniprint.net/.

 

[winthropdc]

Guys

This information for Named Printers might help.


What is the best method of setting up Named Printers on a Terminal Server?

Things to note:

1) Named Printers is machine based. It stores a Machine ID in the DEX.INI for each workstation and all settings are for the current workstation only. In a Terminal Server environment it means that all users share the same settings because the are all using the same workstation.

2) It is not recommended to use Wokstation Printers with Named Printers as they can change depending on which machine is used to login to a terminal server session. It is best to only select printers which are permanently visible to the terminal server.

3) Printers can be set up on a user basis which allows different users to have different configurations on the single workstation.

4) If using multiple application folders on the one terminal server or multiple terminal servers, please ensure that each has its own Machine ID. You might need to manually edit the ST_MachineID setting in the DEX.INI. You would then need to configure Named Printers on each each instance individually.


Situation 1: Single Location Access to Server
For a simple site where all users have their printers defined the same, just set up Named Printers as though it is a single workstation, using System or Company class printers.


Situation 2: Multiple Location Access to Server
For the more complex site where there are a number of remote locations accessing the server, you should use User class printers so that each user can have their own configuration defined. However, when you use a user class printer you will find that is MUST be defined for all users and that can be time consuming. Usually, all of the users from a single remote location will want the same configuration. Named Printers has a way of setting this up simply and quickly.

The feature you need to use is Named Printers' Template Users, below is an example with the steps to set this up:

I have 3 remote locations using my terminal Server in Sydney. There are based in London, Paris and Fargo. Each remote location has 30 users.

1) Create a New User ID for each remote location, and assign them access to the lesson company or a test company. These User ID's will not be used to login.

2) Select Setup >> System >> Named Printers. If this is first time you have used Named Printers, you will be asked to set up the Machine ID (normally the Computer's Network Name as this is unique). You would also need to set up the Default Printer ID, this should point to a printer based in Sydney. The Default Printer ID is automatically assigned to the System Default Printer Task.

3) From the Assign Named Printers window, click on the Setup Button and then on the Advanced Button. Using the bottom half of the window enter in the Template User ID as the remote location User ID and using the checkboxes, assign to it all the users from that location. Repeat for each remote location. You now have created your 3 Template Users.

4) From the Setup Named Printers window create all the Printer ID's needed for each location as User Class Printers assigned to the Template User for that location. Repeat for each remote location.

5) Then from the Assign Named Printers window, change the User and Company to one of the Template Users and the assigned company. Set the Company Default Printer to Printer Class: User and select the default Printer ID to be used for that location.

6) Assign other user class printers to other Printer Tasks as required. Repeat 5 and 6 for each location.


In this example, it was possible to complete the Named Printers setup by configuring 3 template users instead of the 90 individual users.

David Musgrave
Senior Development Consultant
Asia Pacific Professional Services

Microsoft Business Solutions

http://www.microsoft.com/BusinessSolutions

mailto:dmusgrav@nospam-microsoft.com

Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.

 

[winthropdc]

I have added this as a FAQ faq632-4834

 

[Luvsql]

This seems like an extreme amount of setup just to have users be able to print in Great Plains? We have 6 citrix servers, 100 users, with over 6 physical locations. Each location doesn't have one printer that each user prints to. When you log into citrix, each users' printer becomes unique ie \\clientname\localprintername. Citrix metaframe creates each of these printers as a separate printer.

 

[Dukester0122]

Here's the solution:
1. Go to each Citrix box then open CMC
2. Right-click on Printer Management then Properties
3. Open the Printers tab then Mark Auto-create client printers when user logs on
4. Choose Use connection settings for each server
5. Open the Drivers tab then choose Use universal driver only if native driver is unavailable
6. Restart all servers in the following order:
a. File/Printer Server
b. SQL Server
c. Citrix Servers

Hope this helps. If you still have problems send me a PM.

 

[madmari]

I just saw this thread when looking for something else in this forum. We have GP 7.0 on Citrix and we have about 60 users connecting this way. All of our users are set up in a way that their default printer becomes the only printer available in GP. We had only one user that constantly wasn't able to print. We were able to figure out that the printer drivers on the printer's server were the culprit. Before we were using PCL drivers for this particular printer(HP LaserJet 4000). When we switched to PS drivers the user stopped having problems.

Mario