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.

Slowness and Freezing experienced when theres lots of read/writes to file server

Have bumped into this problem a couple of times now and it is very difficult to troubleshoot.
I saw this recently after a new application went onto a Citrix server with 25 concurrent users.
They had number of applications that were reading and writing to a file share (Lotus Notes data in particular),and they were also using a redirected %appdata% to the file server which meant any apps that use the appdata folder for configuration information (most) were also reading and writing to the file server very frequently.
There is an OS limit of 50 concurrent outstanding network requests between a Server Message Block (SMB) client and server, which can be overrided by a couple of registry settings.

You can use the following performance counters to troubleshoot the issue:
Server\Files Open
Server\Server Sessions
Server\Work Item Shortages


Fix
Create the following DWORD registry keys if they are not already there and set the value to 2048. This should be more than enough for any Citrix Server.

On the file server:
HKLM\SYSTEM\CurrentControlSet\Services\LanamanServer\Parameters\MaxMpxCt

On the client/citrix server:
HKLM\SYSTEM\CurrentControlSet\Services\LanamanWorkstation\Parameters\MaxCmds

See the following MS articles for more info:
http://support.microsoft.com/kb/810886
http://support.microsoft.com/kb/232476


www.aggc.co.uk

AGGC Print Mapper Added Features

- Export Print mappings from file
- Import Print mappings from file

Get it here -> www.aggc.co.uk

Creating Certificate Requests for the Citrix Access Gateway

Sometimes when you get a new cert and try and upload to the Access Gateway it will fail. This is because the cert is not in the correct format/ or maybe corrupt. Heres how to generate the cert and keyfile if it is in the wrong format, from start to finish.

Section 1
To install Cygwin:
1 Use a web browser to navigate to www.cygwin.com and click Install
Cygwin Now.
2 Follow the on-screen instructions to open the setup installer.
3 In the Cygwin Setup dialog box, click Next.
4 Click Install from Internet and then click Next.
5 Accept the default root installation directory settings and then click Next.
6 Accept the default local package directory setting and then click Next.
7 In the Internet Connection screen, click Use IE5 Settings and then click
Next.
8 In the list of Available Download Sites, click ftp://ftp.nas.nasa.gov and
then click Next.
9 In the Select Packages screen, click the View button (upper-right corner).
10 Scroll the packages list to locate in the Package column openssl: The
OpenSSL runtime environment and openssl-devel: The OpenSSL
development environment.
11 In the New column for those two entries, click Skip.
The current version number of Cygwin appears.
12 Click Next to start the installation.
After Cygwin installs, you can generate the CSR.

To generate a CSR using the Cygwin UNIX environment:
1 Double-click the Cygwin icon on the desktop.
A command window opens with a UNIX bash environment.
2 To change to a particular drive, use the command: cd driveLetter:
3 At the $ prompt, type the following to generate a CSR:

openssl req -new -nodes -keyout privateKeyFilename out certRequestFilename

For example:

openssl req -new -nodes -keyout private.key -out public.csr

Status messages about the private key generation appear. You will be
prompted for information such as country name.
4 When prompted for the Common name, enter the DNS name of the AG.
The name that you enter will appear in the certificate and must match the
name expected by PCs that connect to the AG. Thus, if you alias DNS
names, you will need to use the alias name instead.
5 Submit your CSR (public.csr) to an authorized certificate provider such as
Verisign. When asked for the type of server that the certificate will be used
with, indicate Apache.
The certificate provider will return a Signed Certificate to you by e-mail
within several days.

If the cert doesnt upload to the CAG at this stage you need to create a .pem file.
Section 2

1.Create a new file (.pem) with notepad. Copy the contents of private key and signed certificate in the .pem file. Remove the squares in the private key file and use on those positions with your keyboard (those squares are carriage returns). Your .pem file should look something like this:

-----BEGIN RSA PRIVATE KEY-----
KJHGDFIUUGQWFE7FJI3HF897FFHWFEJKAHFAKJFHQIUWYEFUIWEYF898937W2L3JFL33F3ETC ETC
-----END RSA PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
KJHGDFIUUGQWFE7FJI3HF897FFHWFEJKAHFAKJFHQIUWYEFUIWEYF898937W2L3JFL33F3ETC ETC
-----END CERTIFICATE-----

4. Upload this file using the option "Upload private key and cert (pem)".


That should work and if it doesnt then your cert is probably faulty, go follow instructions in section 1 to create the certificate request.

Force Java Settings

Java caching can cause slowness with some Java Applets when using redirected folders.
The default location for java cache is in the appdata folder, so if your redirecting this to a network drive somewhere it can sometimes slow the applet when loading. The fix is to force java settings using a centralised deployment.properties file; create a file called deployment.config and put it in the windows\sun\java\deployment folder. Put the following into the file:

deployment.system.config="c:\JavaCache\deployment.properties"
deployment.system.config.mandatory="true"

This tells Java to use a centralised configuration for Java and to use the config stored in the c:\JavaCache\deployment.properties file.

Heres what I have stored in the deplyment.properties file:

#deployment.properties#Thu Nov 15 13:48:34 GMT 2007
deployment.user.cachedir=e\:\\JavaCache
deployment.user.cachedir.locked
deployment.system.cachedir=e\:\\JavaCache
deployment.system.cachedir.locked
deployment.javapi.jre.1.5.0_11.args=
deployment.javapi.jre.1.5.0_11.osname=Windows
deployment.javapi.jre.1.5.0_11.path=C\:\\Program Files\\Java\\jre1.5.0_11
deployment.javapi.jre.1.5.0_11.osarch=x86
deployment.browser.vm.iexplorer=true
deployment.browser.vm.mozilla=false
deployment.cache.jarcompression=9
deployment.version=1.5.0
deployment.capture.mime.types=true
deployment.system.tray.icon=false