Incorrect ica32web.msi size when trying to download client
File size was smaller than actual size when trying to download ICA32WEB.msi. Fix as follows:

1. Stop IIS.


2. Open c:\windows\system32\inetsrv\metabase.xml in notepad.


3. Search for aspbuffer or aspbuffering and up the limit to whatever size your .msi file is.


4. Restart IIS.

Web Client Install

1. copy ica32web.msi (from the Citrix website) into C:\program files\citrix\Web Interface\4.6.0\Clients\ica32


2. Open the Access Suite Console, highlight your web site and on the right select the deploy clients option.


3. Under deploy clients under client detection check "perform client detection" and under Display client detection bullet "whenever a client is needed".

Fix client detection and java fallback in WI4.6 when using it with AAC


1. Open the \inetpub\wwwroot\Citrix\AccessPlatform\conf\WebInterface.conf file in Notepad.
2. Add the following setting to the file:

EnableClientDetectionForAG=On

If using Access Gateway 4.5 Advanced Edition, complete the following procedure in addition to the above:
1. Open the \inetpub\wwwroot\Citrix\AccessPlatform\auth\login.aspx file in Notepad.
2. Add the text below in bold to line 50 (line number may differ if other customizations were made to this file):

if ( isWizardModeSupported(Mode.SILENT) &&
clientsAvailableForDetection() &&
Request.QueryString[QSTR_MSG_KEY] == null) {
if (runWizardSilently() && Session[SV_WIZARD_SILENT_FINISHED_KEY] != VAL_TRUE){
Session[SV_WIZARD_SILENT_FINISHED_KEY] = VAL_TRUE;
callWizardSilently();
} else if (!sWizardInfo.isInitialized()){
initializeWizardStateFromCookies();
}
}
3. Press CTRL+S to save the file.
4. Open the \inetpub\wwwroot\Citrix\AccessPlatform\auth\clientDetectionVariablesForPost.aspx file in Notepad.
5. Add the text below in bold to line 67 (line number may differ if other customizations were made to this file):

<input type="hidden" name="<%=WizardConstants.PARAMETER_ALLOW_LOGOUT%>" value="<%= logout %>" />
<% if (sWizardInfo.getMode() != Mode.SILENT){ %>
<input type="hidden" name="<%=WizardConstants.PARAMETER_MASTER_PAGE%>" value="~/app_data/auth/include/WIWizardLayout.master" />
<% }
if (showWelcomeScreen){ %>

6. Press CTRL+S to save the file.

Licensing Issues with Edgesight caused me a real hassle lately.

Violatoins kept appearing in the console and the agent log was reporting that it could not find valid licenses. The customer was using Edgesight for Presentation Server along with the Platinum licenses.

The docs for Edgesight are a little threadbare to say the least so troubleshooting problems can be difficult.

After speaking with Citrix for a few days the fix was to apply SP2 on the server and the agent. At the time SP2 was in BETA!

Anyway it worked.


The one problem I have with Edgsight is that you can only force some things to run immediately.
I think it essential that they build this functionality into the product, especially where licensing is concerned.

It would have taken me a 1/4 of the time to figure out what this problem was if i could run a remote worker that attempted to get a new license, but as it stands you make a change and then wait however long the next recursion is on the agent for it to try get a license.

Had an issue recently where a certain application was causing issues alongside other apps on a Citrix Server.
The only option was to isolate the app on its own server but I wanted to make this as seamless as possible.
The customer was using a published locked down desktop, i looked at PNAgent but i was probably going to hit problems with the locked down desktop so avoided it.
I instead wanted to have .ica files on the desktop that used pass-thru to launch the dodgy app on the isolated ctx server and also would accept command parameters so in effect creating my own content redirection.
Heres what i had to do... a little messy but you will get the idea.

Webica.ini add the following to prevent prompt for client security:
[Access]
GlobalSecurityAccess=405


Add the following to get rid of full screen mode prompt:
[HKEY_CURRENT_USER\Software\Citrix\ICA Client\Keyboard Mapping\Tips] "In full screen mode"=dword:01324326

Heres the template for the ICA FILE
[WFClient]
Version=2

[ApplicationServers]
Client Desktop=

[Client Desktop]
Address=nameofctxserver
InitialProgram=#publishedappnamegoeshere
ClientAudio=Off
Compress=On
DesiredColor=2
TransportDriver=TCP/IP
WinStationDriver=ICA 3.0
TWIMode=On
DesiredWinType=8
DesiredHRES=800
DesiredVRES=600



For single sign on:
1. In the Appsrv.ini file of the users profile, add the following lines at the bottom of the [wfclient] section:
···SSOnUserSetting=On
···EnableSSOnThruICAFile=On

2. In the .ica file you want to use, add the following line in the [Application] section (this is the section where all the settings like resolution or encryption are stored):
···UseLocalUserAndPassword=On

3. Delete %appdata%\ica client folder if required and md new one.
4. Create new appsrv.ini that contains the following and copy to %appdata%\ica client:
[WFClient]
LogFileWin32=C:\Documents and Settings\agreen\Application Data\ICAClient\wfcwin32.log
PersistentCachePath=C:\Documents and Settings\agreen\Application Data\ICAClient\Cache
DesiredColor=2
ScreenPercent=0
DesiredHRES=640
DesiredVRES=480
PNCacheVersion=1
EnableSSOnThruICAFile=On
SSOnUserSetting=On
SSOnCredentialType=Any

Error: EdgeSight has detected a problem with the Licensing configuration.

Symptoms

The following message is displayed on the top of the EdgeSight Server Console:

"EdgeSight has detected a problem with the Licensing configuration. Click here for more information."

When you click the link in the error message, the Current Licensing Status is reported as In Violation. Refer to the following screen shot:

-And-

The EdgeSight server sends the following operational email:

"The EdgeSight for Presentation Server license status is EdgeSightAgentForPresentationServer, and this device (10.20.6.6) has additional violations in the payload. The payload will be deleted. Reflectent.Core.Loader HandleLicenseExceeded"

Background

The SYS_EVENT_TXT.txt agent log file is critical in determining the exact cause of the license violations. Investigating this file may help isolate the specific cause.

Cause 1

The EdgeSight License file may not be in place or is not recognized. The following message in the SYS_EVENT_TXT.txt file may indicate this is the problem:

2007-06-19 15:55:22 Ctrx Licensing No suitable licenses are present on the license server CTX-LIC-SERV:27000

Resolution 1

1. Install the EdgeSight license file on the license server.

2. If the license file has been installed on the license server but is still not recognized, try to "re-host” the license file by using your MyCitrix account to check the license back in and then re-creating the license file.

3. Double-check the name of the EdgeSight server name for case sensitivity while re-creating the license file.

Cause 2

The EdgeSight product requires version 4.5 of the Citrix license server or later. If you have an earlier version of the license server in place you may see the following messages in the SYS_EVENT_TXT.txt agent log file:

2007-08-12 21:20:04 Ctrx Alerts Saved immediate operational alert. Alert text is: Your version of the license server on CTX-LIC-SERV is older than the version of the Citrix EdgeSight for Presentation Server agent. Please upgrade your license server or specify a license server location
2007-08-12 21:20:04 Ctrx Licensing Detected incompatible license server CTX-LIC-SERV:27000

Resolution 2

Upgrade the Presentation Server production license server to version 4.5 and install the EdgeSight license file on it. By default, the EdgeSight for Presentation Server agents use the same license server that the server running Presentation Server uses.

Cause 3

A 4.5 license server has been installed to service just the EdgeSight agents but is not being used by the agents. There is a problem in the base EdgeSight 4.5 product (no service packs applied) that may prevent a new license server configuration from being deployed correctly to all agents.

Messages in the SYS_EVENT_TXT.txt file similar to the ones listed above may indicate that the agent is still trying to contact the wrong license server.

Resolution 3

1. If the production license server cannot be upgraded, install a 4.5 license server on the EdgeSight Server.

2. Create a custom Agent Configuration containing the settings (name, port, and so on) for this new license server.

3. If you are running the EdgeSight 4.5 Service Pack 1 software, navigate to Company Settings > Server > Device Management > Departments and assign the new Agent Configuration to all the departments containing servers running Presentation Server.

4. Complete the following procedure if you are running the base EdgeSight 4.5 software (no service packs applied):

Important: If you are running the base EdgeSight 4.5 server software, you must perform additional steps to force the agents to recognize the new license server. If the custom Agent Configuration is in place before an agent reports up to the server for the first time, it is not picked up properly.

For new installations:

1. Deploy all of the agents and let them all report up to the server once.
2. Navigate to Company Settings > Server > Device Management > Departments and assign the new custom Agent Configuration to the departments containing the servers running Presentation Server.

For existing installations with all agents currently deployed:

1. Navigate to Company Settings > Server > Device Management > Departments and identify the Agent Configuration assigned to the departments containing the servers running Presentation Server.
2. Navigate to Company Settings > Agent > Agent Configurations.
3. Select to edit the configuration from the drop-down menu.
4. Do not make any changes; simply click the finish button. This causes the agents to detect a change to this configuration (even though none was made), allowing it to be downloaded and applied correctly.

For existing installations with some new agents still being deployed:

After each (or a group of) new agent reports up to the server, you MUST complete the following procedure on the EdgeSight Server:

1. Identify the department that this new device belongs to.
2. Identify the agent configuration assigned to this department.
3. Navigate to the Company Settings > Agent > Agent Configurations page.
4. Select to edit the configuration from the drop-down menu.
5. Do not make any changes; simply click the finish button. This causes the agents to detect a change to this configuration (even though none was made), allowing it to be downloaded and applied correctly.

After completing this procedure, the new configuration changes should propagate to all the agents within about 24 hours. The agents can also be forced to use the new configuration by running the remote configuration worker using the Company Settings > Agent > Workers > Run Remotely page. Some license violation messages may occur until the configuration fully propagates to all agents.

Cause 4

There are no more available licenses.

Resolution 4

Using the License Management Console, check the license usage over time to determine the license utilization. If all licenses are in use on a regular basis and violations are still occurring, this means you are regularly exceeding your limit.

To resolve this issue, either acquire more EdgeSight licenses or remove the EdgeSight Agent from enough servers running Presentation Server to use fewer licenses than the license limit.

AGGC Print Mapper now includes AGGC Printer Selector...

This app sits in the systray and allows users to quickly seletc their default printer without having to open the printers folder.

Eventually it will integrate totally with AGGC Print Mapper and map printers as well as allow setting the default.