Troubleshooting MetaFrame XP Imported Network Print Servers

Citrix states in their article: CTX881017

CTX881017 - Troubleshooting MetaFrame XP Imported Network Print Servers

This document was published at: http://support.citrix.com/kb/entry.jspa?externalID=CTX881017

Document ID: CTX881017, Created on: Sep 30, 2002, Updated: Oct 29, 2003

Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2000, Citrix MetaFrame XP 1.0 for Microsoft NT 4.0 Server Terminal Server Edition, Citrix MetaFrame XP 1.0 for Microsoft Windows 2003

This article describes the basic issues with imported network print servers and their possible resolutions.

Overview

Imported network print servers make the shared printers available to configured users when they connect to servers in the MetaFrame XP farm. This is an automated process, similar to the manual process of having a user add the printer through the Printer Folder > Add Printer > Network Printer> Microsoft Network wizard in a Terminal Server desktop session.

Troubleshooting this issue can be significantly different than the auto-creation of locally defined, this includes locally attached and network printers, workstation printers as outlined in Troubleshooting Citrix ICA Printer Autocreation.

Importing Print Servers

Use the Network Print Servers tab when you want to import a network print server to make its printers available to the users of the server farm. When you select the tab, you can choose Import Network Print Server from the toolbar or the Actions menu. The command and toolbar button are not available when other tabs are selected.

1. Ensure the driver for the print server is installed on all of the MetaFrame XP servers by checking the following registry key:

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

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

Use the MetaFrame XP feature of Printer Driver Replication to help with this process. See the MetaFrame XP Administrators Guide or the Citrix Knowledgebase Article Printer Driver Replication Failed for Certain Printers and Printer Drivers for more information about printer driver replication. For Windows NT 4.0 print servers imported to a Windows 2000 MetaFrame XP farm, right click in the white space inside the Printers folder and go to Server Properties > Drivers Tab > Add > Choose the driver. The driver defaults to Windows 2000. Change the check box to reflect both Windows NT 4.0 and Windows 2000.

The mere existence of the driver does not guarantee this process will work. The driver may be corrupted. Citrix Support may ask that the driver be removed and re-added.

2. Novell NDS printer are not supported as Imported Network Print Servers. For additional information, see page 70 of the MetaFrame XP Administrators Guide.

3. Assigning, a user, permission to the Imported Network Print Server(s) does not automatically ensure the user the right to actually print to the printer. These permissions merely allow the user to autocreate the object within the users profile. This information is in the following registry keys:

HKEY_CURRENT_USER\Printers\Citrix\NetworkPrinters

HKEY_CURRENT_USER\Printers\Connections

Additionally, because the object is created within the context of the users profile, the administrator cannot view these objects from the Citrix Management Console or through the Printers folder. It may be necessary to shadow a user in a desktop session to further troubleshoot this issue.

4. Citrix does not recommend importing a print server that is also a MetaFrame XP server as a permanent solution. It may be required as a quick troubleshooting step. By design this is so that users will not be confused. Because the object is created on the MetaFrame XP server, the user, upon logon, sees the object as created on the server and not as it would when created in the users profile. Many users will most likely log on to many different MetaFrame XP servers and those servers will not be acting as print servers. Attempting to import the print server by NetBIOS name gives the error message: "Failed to Add Network Print Server . The server is part of the farm. Error Code:0130001/c0138015." The server will import if the IP address is used.

5. Imported Network PrintServer(s) are not subject to alternate print driver mappings as is the case with a locally defined printer object on the client device.

6. Imported Network PrintServer(s) information is written to the data store. This information can be viewed by running Dsview.exe. The locations are: ServerNeighborhood >FarmName > PrinterRoot > NWPrintServers, AutoCreate, and Printers. Examining these locations may help analyze the more complex Imported Network Print Server(s) issues.

7. With Feature Release 2, Printing Preferences can be set per printer in the Citrix Management Console for autocreated network printers. The preference options are papersize, copy count, print quality, and orientation.

8. With Feature Release 2, you can choose to inherit user-defined network printer properties at each logon. This permits you to ignore the saved user profile data, which causes the common properties to be set for the subsequent logon.

9. When importing or updating a print server with a large number of printers, Error: Failed to refresh print server data for . Operation timed out. C0130006/C0138006. should be applied.

10. Imported Network PrintServer(s) are not subject to the usage of the Universal Print Driver, UPD, as outlined in Troubleshooting and Explaining the Citrix Universal Print Driver, UPD.

Network Print Servers Tab

Use the Network Print Servers tab to view the names of network print servers whose printers can be configured in the server farm. When you create a new MetaFrame XP server farm, the tab lists nothing until you import one or more network print servers. After you import print servers, the Network Print Servers tab displays the name of each print server and the date and time when the console last updated the print server information. The tab uses the time zone of the machine to which the console is connected for the date and time display.

Updating Server Information

If you add printers to or remove them from a network print server, update the print server information to be sure that the console displays the available printers on the Printers tab. To do this, select a print server and use the Update Network Print Server command from the right-click menu, the toolbar, or the Actions menu. You must do this because updating print server information does not take place automatically.

When changing the driver (the actual drive name or OS platform type is changed) on the print server, it is advisable to remove the object from the print server, refresh the printer node within the Citrix Management Console, and ensure the printer is removed. Logon a user and then logoff the user after verifying the printer is
successfully deleted. Add the printer with the new driver to the print server, refresh the print server within the Citrix Management Console, add the user to the imported print server, and retest with the previous logged on/off user.

Changing the share name of a network printer deletes all user names entered in the autocreation list for the printer in Citrix Management Console. These assignments are written to the datastore and associated with the share name of the network printer. When you make changes to the printer on the network print server, make sure the user names are reassigned to the printer in the Citrix Management Console.

Error: Failed to refresh print server data for . Operation timed out. C0130006/C0138006.

Removing Print Servers

Removing a print server removes all of its printers from the farm. This is the opposite of importing a network print server. If you remove printers, ICA Client users cannot print to them. If you want to do this, select the print server to remove, and then choose Discard Network Print Server from the right-click menu, the console toolbar, or the Actions menu. After you confirm the command, the printer server no longer appears on the Network Print Server tab and its printers do not appear on the Printers tab.

This process also removes the object from the users profile upon the next logon attempt. Ensure users are not reconnecting to a disconnected session when troubleshooting this issue.

Known Issues

MetaFrame XP Feature Release 1 had one issue. If a user had access to the Printers folder and deleted the Imported Network Printer object from their profile, the object would not be recreated unless the entire users profile was deleted and a new profile was created. This issue is fixed in Service Pack 2 for MetaFrame XP.



Primary links

Custom Search

Who's new

  • Cachleferah
  • Weedbacuupe
  • vororourn
  • vDonellaCandrah
  • SnnaSusi

Who's online

There are currently 0 users and 3 guests online.

KrissysCorner.com RuthSwensonLaw.com CreativeLizardProductions.com

DISCLAIMER:

None of this has anything to do with us, someone else is responsible for the entire thing, and we have no idea who or why. We do not know anything about it. It may be alien life forms for all we know: we haven't a clue. You cannot blame us for anything that may result from your visit. That was entirely your own personal choice, made by you of your own volition, and without our knowledge. We do not, after all, have any control over you and cannot by any stretch of the imagination be expected to accept or acknowledge, be it legally or morally, any accountability for decisions made by you on an independent basis, utilizing your own free will, and without our intervention. We are therefore in no way, shape, or form answerable to anyone for any consequences arising from the aforementioned or indeed any other actions, similar or otherwise, because it was not us that did, or did not do anything. It is not even remotely our fault, and we are in no way prepared or willing to accept any liability, not even slightly, ever. We are, in fact completely and utterly blameless, in that it is definitely not our concern, and no blame can possibly be laid at our doorstep, even if we had one, the possession of which we hereby reserve as being entirely our own free choice. The onus is not on us at all, and furthermore, never has been. The entire matter is wholly beyond our control, and completely out of our hands, each of which are washed scrupulously clean of the whole business. We are not accountable for anything at all, and we hereby categorically deny all responsibility for all that has ever, or will ever happen. Our innocence is therefore wholly beyond doubt and absolutely unimpeachable, and so cannot, under even the remotest or unlikeliest circumstances, be brought into question. By clicking either on a link on this site, clicking on a link that leads to this site, or by arriving at this site by natural or supernatural means, you are in effect accepting responsibility for the fact that it is all entirely your own fault, down to the most miniscule detail, and that you are wholly accountable for whatever outcome may arise as a consequence of the aforementioned action or actions insofar as they were undertaken personally by you on an entirely voluntary basis and without any persuasion, coercion or influence from any party or parties other than yourself. Don't come sniveling to us, we are only figments of your imagination. I also agree that if I am ever with a contributor to this website during mealtimes I agree to pay for any super-sizing of their meal, or at least a nice dessert or one of those foo-foo drinks with an umbrella or a monkey. By admitting to have seen the worthless spineless drivel on this website (also known as content)

I Agree Wholeheartedly and Without Reservation to the above. (Except maybe for that part about the monkey.)

All Your Base Are Belong To Us.

Soylent Green Is People!

Never make a bet with a Sicilian when Death is on the Line!

No. Really, I do agree.