- #Citrix receiver local printer not mapping how to#
- #Citrix receiver local printer not mapping drivers#
- #Citrix receiver local printer not mapping driver#
Stop the print spooler and Ctx_CpSvc services. Using the following method is the easiest way to remove a problematic print driver:Ĭaution! Refer to the Disclaimer at the end of this article before using Registry Editor.
#Citrix receiver local printer not mapping drivers#
Note: Sometimes print drivers can be problematic to remove from servers since they are loaded once the spooler is running. This might cause the Citrix Print Manager service to crash, not be able to restart, or even to stop functioning.
#Citrix receiver local printer not mapping driver#
If the driver does not respond in time, it begins to leave orphaned printers in the registry in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers hive, eventually causing a traffic jam. Drivers must respond to the AddPrinter(), XcvData(), and DeletePrinter() API function calls. In the following example of the 5x5 setup for testing, 5 concurrent AddPrinter() events are created and repeats it 5 times:Īfter you remove the drivers from the server, you should check what contents are left behind from the bad drivers. For more information, refer to the Knowledge Center article CTX109374 – StressPrinters 1.3.2 for 32-bit and 64-bit Platforms.Īfter you have tested the drivers and found the drivers that failed to pass the stress test in the normal amount of time in a 5x5 test, (that is an average of 12 to 30 seconds), then you should remove these drivers from the server.
#Citrix receiver local printer not mapping how to#
For more information, refer to the Knowledge Center article CTX126093– How to Distinguish Native/Inbox Print Drivers from Non-native/Manufacturer Print Drivers in Windows Server 2008 R2Īt this point use the Citrix Print Driver Stress Test tool to see if this driver is causing the issues. If it reads 0.0.0.0, then it is a non-native driver. If this version is 6.x, then it is a native driver. Note: Check for a version number in MinInboxDriverVerVersion. The best way to identify non-native print drivers is to observe the registry.Ĭonsider a 64-bit computer as an example: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows 圆4\Drivers\Version-3\ Restart the Citrix Group Policy Engine service, and you will now notice that new sessions populate the registry hive with the correct policies applied.Įnsure that the non-native print drivers are not causing issues on the server. This ensures that all new sessions receive the new group policies on the server. This is a dynamic key and does not affect any existing sessions on the server. Open the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix folder, and remove all hives with a session number. Open a Command window and run the gpupdate /force command to add contents to the folder with the new Group Policy information from Active Directory and Citrix. Open the C:\ProgramData\Citrix\Group Policy folder and delete all items in the Group Policy folder. If the policy is still not applying, complete the following tasks: If you do not see the policies applied to the user, verify if the policy is applied to the correct user group. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix\(session#)\PrintingPolicies You can check this by browsing to the following policy registry hive:
XenApp 6.5 Recommended Hotfixes - GeneralĮnsure that you apply the auto-creation policy to the appropriate group of users. XenApp 6.0 Recommended Hotfixes - General XenApp 5.0 2008(64) - Hotfix Rollup Pack 1 for Citrix XenApp 5.0 for Microsoft Windows Server 2008 64-bit Edition XenApp 5.0 2008 - Hotfix Rollup Pack 1 for Citrix XenApp 5.0 for Microsoft Windows Server 2008 32-bit Edition
To troubleshoot the issue, complete the following steps:Įnsure that you have all the available hotfixes for your environment:ĬTX129229 – Recommended Hotfixes for XenApp 6.0 and later on Windows Server 2008 R2 Non-native print drivers are the main cause for the failure of auto-creation causing a slew of other issues that must be considered after identifying the drivers to remove from the server.
0 kommentar(er)
