How to Hide the Messages Button in Web Interface 5.4

This article describes how to hide the Messages button on the Web Interface toolbar.

Note: Use this procedure carefully. Be aware that the Messages button provides useful information to the end users.
Requirements
Web Interface 5.4
Procedure
Follow the steps below to hide the Messages button from Web Interface 5.4 toolbar:

1. On the Web Interface server, go to C:\Inetpub\wwwroot\Citrix\<site name>\app_data\include\ folder and look for a file called header.inc.


Go to around line #70, and comment out the following line by putting <!-- and -->:

Before:

After:

Save the file.


Run IISRESET on the Web Interface server.


Clean up your browser history on the client workstation and test.

Read More

Force Terminal Services Clients to Disconnect when Idle

When you administrate servers running Windows Server 2000 or 2003, one of the most frustrating experiences is when sessions get cut off but the server still thinks they are active. You’ll get this error message, which you are sure to encounter at some point:

The terminal server has exceeded the maximum number of allowed connections.

You can help prevent this from happening by setting a policy on the server to automatically disconnect when idle. To change this setting, go to Administrative Tools \ Terminal Services Configuration.



Click on Connections in the left hand pane, and then right click RDP-Tcp and select Properties. In the resulting window select the Sessions tab.

Check the boxes for “Override user settings” and change the idle session limit to something reasonable, like an hour. You can set it lower if you’d like.
Change the radio button to “Disconnect from session” when session limit is reached. This will make all sessions automatically mark as disconnected on the server. The session will be saved exactly as it was, but the server will mark it as disconnected so that you can log back into the session again.
Cannot Suppress the Idle Timer Expired Dialog Box in an ICA Session  
When an idle session limit is set in Terminal Services, users are presented with the following idle timeout dialog box stating that sessions will be disconnected in two minutes if they are left idle for the specified amount of time.



Idle timeout message:
"Session has been idle over its time limit. It will be disconnected in 2 minutes. Press any key now to continue session."
The idle session timeout logic is part of Microsoft's Terminal Services architecture and is hard-coded to two (2) minutes. Currently there is no way to change this value or disable the notification.

Read More

Data Collector and its features

Data Collector:


Every Zone in a MetaFrame farm consists of one data collector. If a new MetaFrame server joins the zone or the current data collector is unavailable then an election is triggered to determine a data collector. When a zone elects a new data collector, it uses a preference ranking of the servers in the zone. Each zone has four levels of preference for election of data collectors and every server is assigned a preference level. The preference levels, in order from highest to lowest preference, are:
       Most Preferred
       Preferred
       Default Preference
       Not Preferred
By default, a MetaFrame server is set to the Default Preference setting. This is the case for all server except the for the first server added to the zone, in which it is set to Most Preferred and it is set to be the zones initial data collector.

To designate a specific server as the data collector you will want to set the election preference for the server to Most Preferred and all other servers to something lower.
If you do not want a server to be a data collector then you will need to set the preference to Not Preferred.
If you create a new zone, the first server that you move to the new zone becomes the zones data collector, and its preference level is set to Most Preferred.
Note: As discussed in the design phase, when the server farm exceeds five or more servers or it is experiencing high session traffic, you can reduce the possibility of data collector performance issues and sluggish farm enumeration by setting up MetaFrame XP server as a data collector or what I like to call a Control Server. This server will be dedicated for acting as the data collector so you will NOT want to publish any applications to it.


New Data Collector Election Process


When a communication failure occurs between a member server and the data collector for its zone or between data collectors, the election process begins in the zone. Here are some examples of how ZDC elections can be triggered and a high level of summary of the election process. A detailed description of this process and the associated functions used is further below in this document.
1. The existing data collector for Zone 1 has an unplanned failure for some reason, that is, a RAID controller fails causing the server to blue screen. If the server is shutdown gracefully, it triggers the election process before going down.
2. The servers in the zone recognize the data collector has gone down and start the election process.
3. The member servers in the zone then send all of their information to the new data collector for the zone. This is a function of the number each server has of sessions, disconnected session and applications.
4. In turn the new data collector replicates this information to all other data collectors in the farm.
Important: The data collector election process is not dependent on the data store.
Note: If the data collector goes down, sessions connected to other servers in the farm are unaffected.
Misconception: “If a data collector goes down, there is a single point of failure.”
Actual: The data collector election process is triggered automatically without administrative intervention. Existing as well as incoming users are not affected by the election process, as a new data collector is elected almost instantaneously. Data collector elections are not dependent on the data store.


Detailed Election Process:


As we know, each server in the zone has a ranking that is assigned to it. This ranking is configurable such that the servers in a zone can be ranked by an administrator in terms of which server is most desired to serve as the zone master. “Ties” between servers with the same administrative ranking are broken by using the HOST IDs assigned to the servers; the higher the host ID, the higher-ranked the host.
The process that occurs when an election situation begins is as follows:
1. When a server comes on-line, or fails to contact the previously-elected zone master, it starts an election by sending an ELECT_MASTER message to each of the hosts in the zone that are ranked higher than it.
2. When a server receives an ELECT_MASTER message, it replies to the sender with an ELECT_MASTER_ACK message. This ACK informs the sender that the receiving host will take over the responsibility of electing a new master. If the receiving host is not already in an election, it will continue the election by sending an ELECT_MASTER message to all of the hosts that are ranked higher than itself.
3. If a server does not receive any ELECT_MASTER_ACK messages from the higher-ranked hosts to which it sent ELECT_MASTER, it will assume that it is the highest ranked host that is alive, and will then send a DECLARE_MASTER message to all other hosts in the zone.
4. When a server that has previously sent an ELECT_MASTER message to the higher-ranked host(s) in the zone receives an ELECT_MASTER_ACK from at least one of those hosts, it enters a wait state, waiting for the receipt of a DECLARE_MASTER from another host. If a configurable timeout expires before this DECLARE_MASTER is received, the host will increase its timeout and begin the election again.
At the conclusion of the election, each host will have received a DECLARE_MASTER message from the new zone master.

Read More

VMXNET 3: Supported Guest Operating Systems

VMXNET 3 is the newest NIC driver for VMs (requries VM HW v7). It should be chosen as default for all supported guest operating systems. Windows Server 2000, however, is not supported. Here's link to VMware KB with more info. Remember, that when you delete the old NIC and add a new one, then all IP info is wiped and should be reconfigured (mostly relevant for static IPs).

Read More

Farm Metrics Server

The Farm Metric Server is a MetaFrame CPS(Citrix Presentation Server) server that is selected to correlate all farm metrics and server events as it relates to the entire farm. Currently, the only farm metric that is available is the application count for applications. Valid server events that are identified by the Farm Metric Server are server down, server up, metric green, metric red and metric yellow. Every time a server goes down or comes up, the Farm Metric Server is notified. The Farm Metric Server is notified anytime that a server metric changes thresholds.
The Farm Metric Server is also considered a CPS member server. It has the same responsibilities to the summary database functionality as other member servers. The only difference is that it also has the responsibility of the tasks associated with a Farm Metric Server.

On XenApp 5 it's possible to configure farm metric servers in resource manager (xenapp advanced configuration console).In Xenapp 6, we can find this feature in Edge sight

Read More

Cyclic Boot Presentation Servers

When the IMA Service starts after restarting the server, it establishes a connection to the data store and performs various reads to update the local host cache. 

These reads can vary from a few hundred kilobytes of data to several megabytes of data, depending on the size and configuration of the farm.
To reduce the load on the data store and to reduce the IMA Service start time, Citrix recommends maintaining cycle boot groups of no more than 100 servers. 

In large farms with hundreds of servers, or when the database hardware is not sufficient, restart servers in groups of approximately 50, with at least a 10 minute interval between groups.
 

Note: If the Service Control Manager reports that the IMA Service could not be started during a cycle boot of a Presentation Server but the service eventually starts, ignore this message. 

The Service Control Manager has a time-out of six minutes. 

The IMA Service can take longer than six minutes to start because the load on the database exceeds the capabilities of the database hardware. 

To eliminate this message, try rebooting fewer servers at one time.

Read More

DSN and Details

DATA SOURCE NAME

A DSN stores the data source information  necessary for the Driver Manager to connect to the database. This can be configured either through the ODBC Administrator or in a DSN file. On Windows, the information is called a system or user DSN and is stored in the Registry.
Open Run and type the following command to open Microsoft ODBC Manager:
%SystemRoot%\system32\odbcad32.exe.
Or it is available under Control Panel--> Administrative Tools-->Data Sources(ODBC).

 What’s a DSN ?

According to Microsoft documentation, it means "The name that applications use to request a connection to an ODBC data source." In other words, it is a symbolic name that represents the ODBC connection. It hides the connection details like database name, directory, database driver, UserID, password, etc. So when making a connection to the ODBC, you don’t have to remember the database name, where it resides, etc.

Before we discuss this, let me the list the various types of DSNs.

• System DSN: This is the DSN used through out the system, no matter which user logs in. Meaning, all users on the system can see this DSN and use it (as long as they know the user ID and password). The connection parms are stored in the registry.
• User DSN: This is a DSN created for a specific user. Only the user who created the DSN can see this and use it. Like System DSN, the information is stored in the registry.

In both these two cases, DSN details are stored in the system registry.

With that, let me explain what a file DSN is. Instead of storing the DSN details in registry, you store it in a file - simple ?! Yes, it is. The file is a simple text file, with a .DSN extension.

Although it sounds simple, you need to know the parameters that make up a DSN. But again, it is not all that difficult, as you can look this up in any ODBC reference, or online help that comes with Visual Basic or Access.

Shown below is a generic file DSN for an MS Access database.

------------- file.dsn -------
[ODBC]
DRIVER=Microsoft Access Driver (*.mdb)
ReadOnly=0
UserCommitSync=Yes
Threads=3
SafeTransactions=0
PageTimeout=5
MaxScanRows=8
MaxBufferSize=512
ImplicitCommitSync=Yes
FIL=MS Access
DriverId=25

I call the file file.dsn, you may rename it appropriately.

Creating this file is half work done. The next step is creating a connection. When using a system DSN, you create a connection by simply using the system DSN name, something like

Conn.Open "MyDSN"

While using the file DSN shown above, you need a few more parameters I purposely left out so that you could reuse the file DSN. The final connection string will look like

"filedsn=c:\webdir\file.dsn;DBQ=c:\database\mydb.mdb;UID=admin;PWD=admin;"

c:\webdir is the directory where file DSN resides. This requires a physical path to the file. On an ISP, you could use Server.mapPath method to determine this directory. Something like

Server.MapPath("/mysite/file.dsn")

the same holds for DBQ parameter. UID and PWD are optional.

In summary, to create a reusable file DSN

1. Create a text file with DSN parameters. This file has a .dsn extension
2. Create the connection string, with the filedsn and DBQ parameters. You can determine physical paths using Server.MapPath method
3. Use the DSN for as many databases you want, by changing just the DBQ, UID and PWD parameters

Note that databases other than MS Access require different values for parameters and also some additional parameters.

Read More