Hey Everyone
I am having a problem at the moment that I cant quite understand and hope someone out there can help. The way we have our Citrix farm setup is that we have a 1st Tier of Desktop servers that users log into directly, we then have a 2nd Tier of servers from which we publish apps to the the 1st Tier via PN Agent.
The problem I'm having at the moment is that when a user starts up a published app (happening with MS Publisher & MS Project, not all 2nd Tier servers) they cannot print (error comes up saying that no printers are installed) To troubleshoot this I created a copy of that published app and modified it so the users could log onto the server via a published desktop and the printers work fine. After that their printers work fine whether they start up the published desktop or app.
Can anyone shed some light on this? I didnt think there was but there seems to be a difference in how the profiles work whether you login to the desktop as opposed to a published app.
Our servers are running Windows 2003 R2 with SP2 & PS4 (PSE400W2K3R05) and users printers are stored in their profile and are not scripted.
Cheers
Do you map the printers for the pulished applications using the Start Menu\Startup folder? If so this does not run in Citrix for Published Applications only for full Desktops.
--Emil
Hi Emil
No, we let users pick their own printers and they manually add them themselves.
cheers
So users launch a citrix desktop, then from within that desktop they launch applications that are configured to connect to a different server farm.
Your users are manually adding the printers.
Could the problem be that a user is launching the application that connects to the second server farm prior to adding the printers in their desktop so no session printers are being created in that application session?
So if they check in the Printers folder and there are printers but go into the app there are none avail, or they go into the app then add printers and none are avail?
No, when they go into the published app and choose to print they can see the printers that they have chosen,just when they select the printer in the list it then comes back with the error to install a printer. Another thing to mention is that when they select the printer they want to use, MS Office doesnt come back with any information about the printer (MS Office apps show the status, location, model of the printer in the print section)
Installing the printer driver will be controlled by a GPO (No Kernel/Unsigned/etc drivers) and then the NTPrint.inf/installed drivers combination. The printer drivers on the Print Servers will probably not match the drivers available/allowed on the Citrix Server, therefore the user will not be allowed to connect to the queue and recieve an error (a bit ambiguous).
Also in Office if you do not have a default printer or you add one after the app is started it is not displayed correctly, therefore it is better to select printers beforehand.