Category Archives: Uncategorized
Common Pitfalls when Setting up a NetScaler for the First Time
Here are some basics on NetScaler setup and some mistakes that are frequently repeated while implementing NetScalers
Citrix XenApp 6.5 – Register a MIME type extension
This document is intended to explain how a new file type could be registered on Windows Server 2008 R2 and delivered via XenApp 6.5.
There are a few ways you can associate a file in Windows Server 2008 R2. You can choose manually select the program to open and select always open this type of file with this program, or you can associate the file type under default programs in the Control Panel. Since we are using roaming profiles, these user settings are immediately lost upon log off. Attempting to associate the file under the administrator account will not apply to all users either.
Furthermore, under the Citrix console you can associate files for published applications within the Content Redirection properties in the published application. This useful feature applies specific file types to always open with the published application. The only downside to this is Citrix searches the registry of your XenApp servers to determine what file extensions can be associated. The resolution is to manually associate the file type using the assoc and ftype commands on the XenApp server.
File type Registration process
Logon to the Windows Server 2008 R2 machine and open a cmd prompt in Administrator mode.
The assoc command allows you to associate the file type with a description:
assoc .dwg=Drawing Files
ftype Drawing Files=”Program file path\program.exe” “%1”
SYNTAX
Assoc <extension>=<description of the file>
Ftype < description of the file>=”<Install path or network Location of the file>” “%1”
Once these commands are entered, update your farm with the new file types. Right click on the XenApp server > Other tasks > Update file types from the registry. The file type will then show up under Content Redirection for the published application and you can apply it to all servers publishing this application.
Qfarm/load does not Return any Server Load Information
Symptoms
When the command Qfarm/load is carried out, the server load information is not returned.
Cause
This issue is leaked because of the invalid zones that are associated with the servers in the farm. The issue is usually caused by zones being created and deleted, servers moving in and out of zones and not immediately being rebooted which can leave the servers with the old information.
Resolution
To resolve the issue, complete the following steps:
- Run the following command from the command prompt of the Zone data Collector. This gathers the dynamic store information of Zone Data Collector:
Queryds /table:LMS_ServerLoadTable > c:\loadtable.txt
(The c:\ can be replaced by any local drive on the XenApp server)
- Run a CDF trace for 30 seconds on all modules from the Zone Data Collector and simultaneously run the command Qfarm /load from the command prompt of the zone data collector.
- Upload both the queryds output log and the cdftrace .etl file to the automatic support site for analysis.
To find the servers that have issues, open the queryds log in Notepad and look for any servers that are listed in a zone that does not exist.
In the cdf trace, look for the following errors:
- “IMA_BUF_BinBuffer::ReadStringObject size<=0 00B895E4 0 00B88CBC 00B895E4 20
and
- Read fetch Errored Uid: 1796-000c-00006692 (the Uid will be different as it a unique identifier for the XenApp server)”
There must be a matching host ID in the queryds output log that shows the server that has the issue.
name : 1796-000c-00006692
host : XenAppServerName
zone : Zone 5
Once the server or servers have been identified, remove them from the server farm and run the command dscheck /full servers to ensure that the servers are no longer part of the farm.
Once that has been verified, the command qfarm /load must now run without issues, and then add the problem servers back to the farm, and the command qfarm /load must continue to work.
The issue can also occur if the server was removed from the farm but XenApp was not removed from the server. The XenApp might still contact the ZDC causing the issue. If yes, just turn off the machine to resolve the issue. The command queryds in the preceding section will not show the server.
Note: The local host cache must be recreated on all servers or on the zone data collector of the farm if the dscheck command shows the servers in the database after removal, and run the command dscheck with the clean switch to remove them.
More Information
Queryds utility is located on the XenApp install media under the support > debug folder.
CTX134966 – Citrix Diagnostics Toolkit – 32bit Edition
CTX135075 – Citrix Diagnostics Toolkit – 64bit Edition
CTX111961 – CDFControl
CTX130147 – Citrix Scout
CTX124406 – DSCHECK – XenApp Data Store Checker Tool Commands
CTX133983 – IMA Helper Tool
This document applies to:
How to Change the Default Settings on the Citrix Generic Universal Printer
Summary
This article describes how to change the default settings for the Citrix Generic Universal Printer by overriding the hard-coded default settings of the Citrix Generic Universal Printer with registry keys of the manual setting.
Background
The Citrix Universal Printer in XenApp was originally created with static default printer settings. For examples, paper size, paper width, number of copies, and so on.
Requirements
- XenApp 5.0 for Windows 2008
- XenApp 6.x for Windows 2008 R2 include the fix
Procedure
Caution! This procedure requires you to edit the registry. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Back up the registry before you edit it.
Use the following registry values to override the default settings:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Print\UPDDevmode
Name: see the following table
Type: REG_DWORD
Data: see the following table
The following table provides information about the Registry Chart:
|
Name |
Data |
|
dmOrientation |
1 = portrait |
|
dmPaperSize |
1 = letter |
|
dmPaperLength |
1 – 65535 |
|
dmPaperWidth |
1 – 65535 |
|
dmScale |
1 – 1000 |
|
dmCopies |
1 – 9999 |
|
dmDefaultSource |
1 – 15 |
|
dmPrintQuality |
1 = draft |
|
dmColor |
1 = monochrome |
|
dmDuplex |
1 = simplex |
|
dmYResolution |
32 – 65535 |
|
dmTTOption |
1 = bitmap |
|
dmColate |
0 = false |
|
dmLogPixels |
0 – 65535 |
|
dmBitsPerPel |
0 – 65535 |
|
dmPelsWidth |
0 – 65535 |
|
dmPelsHeight |
0 – 65535 |
|
dmFormName |
Form name, such as letter, A4, tabloid, or other available form options |
Note: The Citrix Generic Universal Printer uses the preceding defined registry settings to override the default settings. Any changes to these settings using the printer preferences of the Citrix Universal Printer might be retained.
More Information
CTX089874 – Troubleshooting and Explaining the Citrix Universal Print Driver
CTX106812 – How to Auto-Create the Generic Citrix Universal Printer in User Sessions
CTX119690 – The Printing Jobs Take More Time When Using the Citrix Universal Printer
Citrixology 