Ensure that Client Printers Autocreate Within ICA Sessions

If your printer does not autocreate, verify the following:

1. In Citrix Connection Configuration double click the ICA listener port. Select the Client Settings button, ensure "Connect client printers at logon" is checked.

2. Also, ensure that the following boxes are not checked under the Client Settings Area:

Disable Windows Client Printer Mapping
Disable Client LPT Mapping

3. If "Inherent User Config" is checked in step 1, ensure that "connect client printers at logon" is selected in the UserConfig button for each user account within User Manager for Domains or the Environment Tab within Active Directory Users and Computers/Computer Management-Local Users and Groups.

4. From client machine, make custom ica connection directly to server desktop, logon, open printer folder inside ICA session, then add printer - network printer - expand client network - select client printer and try to add. What is the result? It may indicate a suitable driver needs added, it may say access is denied (rights issue), you may not see the printer under client network (is the printer defined in the local client print folder), can you expand a microsoft server with a shared printer (this may indicate an OS issue), or not see the client network at all (*1).

5. Ensure the latest compatible driver for its operating system is installed on the client computer. On the Citrix Server install the latest compatible driver for the base operating system (NT 3.51, NT 4.0 Terminal Server or Windows 2000). This is easily accomplished by installing a "phantom" printer on the server console. After the printer has been created it can be deleted from the print manager. The driver itself and registry references to the driver will remain. Verify what drivers have been installed on the server in step 6.

Note: Because a printer driver is NT 4.0/ Windows 2000 compatible does not necessarily mean the driver is compatible with NT 4.0 Terminal Server Edition or Windows 2000 Terminal Server.

6. Verify what drivers have been installed ( in WinFrame, Windows NT 4.0 Terminal Server, and Windows 2000) on your Citrix server by checking the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments \Windows NT x86\Drivers\Version-1 (WinFrame)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments \Windows NT x86\Drivers\Version-2 (Terminal Server)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments \Windows NT x86\Drivers\Version-3 (Windows 2000)


7. Verify that administrators can autocreate client printers. If administrators can autocreate and regular users cannot, confirm that users have at least Read, Write, and Execute permissions to the following files and directory:

%SystemRoot%\System32\spool
%SystemRoot%\System32\printer.inf

9. For Terminal Server 4.0 Installations, check to see if the following registry entry exists:

HKEY_LOCAL_Machine/Software/Microsoft/WindowsNT/CurrentVersion/Winlogin

Key Name: Userinit

Value: CTXLOGON.EXE

For Windows 2000 Terminal Server Installations, check to see if the following registry entry exists:

HKEY_LOCAL_Machine/Software/Microsoft/WindowsNT/CurrentVersion/Winlogin

Key Name: AppSetup

Value: Cmstart.EXE

10. Because WinFrame and MetaFrame base autocreation of printers on client name and printer driver name, it is recommended that each client has a unique name.

11. Be advised Hewlett-Packard has introduced a new architecture targeted for the home market called Print Performance Architecture (PPA). Microsoft is not supporting the PPA architecture on all it's operating systems therefore PPA will not be supported in a Citrix environment. Please refer to Microsoft article Q153958 for more information.

12. After verifying all of the above, if your printer still does not autocreate, confirm that the driver names are identical on the client and the server. Sometimes driver names differ marginally for Windows 95 and Windows NT 3.51/4.0. In such an instance, you need to map the names in the Ctxuprn.inf file, Wtsuprn.inf on a MetaFrame 1.8 server (This file resides in the %SystemRoot%\System32 folder), and through the Citrix Management Concole or via the QPrinter.exe command on MetaFrame XP.

*1.) USERS UNABLE TO SEE CLIENT NETWORK

However, you can see the Print Providers listed in the Control Panel\Network\Networks Provider list and in File Manger when connecting to a drive or share point.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.



1. Use the Registry Editor to go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Control\Print\Providers.

2. Click on the Providers subkey and then in the value listing on the right, double-click on
Order. This brings up the Multi-String Editor.

3. The strings in the editor have to match the three subkeys under the Providers subkey.

4. The three subkeys are:

A. Client Printer
B. LanMan Print Services
C. NetWare or Compatible Network

5. These keys must appear the same in the Multi-String Editor. If they are different, make them the same syntax.

6. Ensure cdmprov.dll resides in the correct path shown under the Name value within the Client Printer subkey located under the Providers key.

Explanation

This problem is caused by the multistring values changing in the editor. For example, instead of saying Client Printer, the editor will say Client Network; instead of saying LanMan Print Services, the editor will say Microsoft Print Services

These values sometimes get changed for unknown reasons. When in Print manager, you cannot see the networks whose values got changed or corrupted.