Today I started working on a new XenApp 6 installation. I started with a fresh install of Windows Server 2008 R2 and then went to town installing XenApp 6. Once the license server was installed as well as the web interface I installed Microsoft Office 2007 as we don’t have Microsoft Office 2010 volume licensing yet. After all of that was installed I wanted to publish a desktop. I published the desktop with pretty standard settings and tried to access my published application, oops can’t connect to the server. Let’s try the web interface, nope that didn’t work either. When trying to connect to my new published application via the web interface I got

An error occurred while making the requested connection and there was an error in the application log for each time I tried to connect.

The Citrix servers reported that they are too busy to provide access to the selected resource. This message was reported from the XML Service at address <http://servername:xml_port>

Let’s call Citrix Technical Support, oh wait we don’t have support so let’s figure it out. Everywhere I looked people were saying it was a licensing issue. I tried everything I read

Add one or more servers to the Worker Group assigned to the published application.

If no applications are published to a Worker Group, check to see that logins are not disabled to the server. If they are, re-enable logins.

The server the application is published on does not have a load evaluator assigned. This can be seen in QFARM:

From the Citrix Delivery Services Console:

- Right click on the server and select Other Tasks | Assign Load Evaluator from the context menu.

The load will go to 10000, and then settle after a couple of minutes:

SURE

Running the qfarm / load command I was seeing 20000 as all of the posts say is BAD.

Checking HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\ProductFeature like one article I read and it was blank. Now what?

I had to modify the unfiltered XenApp policy for License Server Host Name

1.       In the Delivery Services Console, navigate to the Policies node and select the Computer tab and Unfiltered policy.

2.       Click the Settings tab in the lower pane.

3.       In the Search All Settings search field, type License.

4.       Add or Edit the License server hostname or License server port or both settings.

5.       Run GPUPDATE /FORCE.

6.       Restart Independent Management Architecture service.

7.       Run QFARM /LOAD.

8.       Verify that the server load reverts back to zero.

Mine didn’t, there was one more thing that did it for me. I then had to duplicate the default load evaluator and then assigned the new copy of the default load evaluator to the XenApp Server.

Run QFARM /LOAD.

Wait for a few seconds and you should be in business. My new XenApp 6 Farm is now accepting connections.

When a user connects to a Windows Server 2003 running MetaFrame Presentation Server 3.0 and tries to use an RDP connection, the connection is denied and the following messages appear:

“The desktop you are trying to open is currently available only to administrators. Contact your administrator to confirm that the correct settings are in place for your client connection.”

“You do not have access to logon to this Session.”

These messages appear even though the user is a member of the Remote Desktop Users group.

The user does has not have problems connecting with a MetaFrame Presentation Server Client for 32-bit Windows.

Cause

Installing MetaFrame Presentation Server 3.0 on a Windows Server 2003 creates a new RDP-TCP listener. The default properties of this listener allow only the launching of published applications.

Resolution

To allow users to connect with an RDP connection, clear Only launch Published Applications under the Advanced Connection settings of the RDP-TCP listener.

How can I reduce the size of my desktop icons if the video resolution is already on the highest setting?

To resize desktop icons
• Right-click the desktop, point to View, and then click Large Icons, Medium Icons, or Classic Icons. (Classic icons are the smallest size.)

You can also use the scroll wheel on your mouse to resize desktop icons. On the desktop, press and hold CTRL while you scroll the wheel to make icons larger or smaller.

Consider the following scenario:

This issue occurs because the non-administrator user account cannot access the %WINDIR%\System32 folder. By default, WPF writes the output file to the %WINDIR%\System32 folder. The %WINDIR%\System32 folder requires administrator permissions. When the non-administrator account tries to access this folder, the WPF caching code is triggered. This code causes the screen to flicker. 

In 32-bit versions of the Windows Server 2003 operating system, the output file is D3d9caps.dat. In 64-bit versions of the Windows Server 2003 operating system, the output file is D3d9caps64.dat.

To resolve this problem, install the following hotfix. After you install this hotfix, WPF applications write the output file to the current user profile instead of to the %WINDIR%\System32 folder.

See http://support.microsoft.com/kb/955692 for more details

• You use a non-administrator user account to connect to a Windows Server 2003-base terminal server by using a third-party terminal client, such as a Citrix ICA client.
• You run Windows Presentation Foundation (WPF) applications in the terminal server session.

In this scenario, you may notice that your screen flickers. You do not encounter this issue when you use Remote Desktop Connection (RDC) to create the terminal server session

If you were unable to install the Integrated Smart Scan Server component during OfficeScan 10 server installation, you can still install the component afterwards.