Sep 062011
 

If you happen to “just” start seeing this logon warning > “You do not have the proper encryption level to access this session” chances are you have recently been smacked with a group policy update that has recently been pushed down to your servers.  This error can yield an array of issues from shadowing to icons not launching that do not have the proper encryption level.

First have a quick look at the following registry key – HKLM\Software\policies\Windows NT\Terminal Services\MinEncryptionLevel.  If the key is present and set to 3 you will either have to correct the group policy (not good) or update the encryption level of the icons linked to the server with issues (best option)

To change the icons encryption level – simply launch the Citrix Access Management Console and navigate to the icon in question, then right-click and select properties. Next, click on Advanced, then click on Client Options and click the dropdown arrow under “Encryption”. Change the value from “Basic” which is the default to 128-Bit(RC-5).  Then test the icon with a non administrative account. At that point you should be good to go.

You may want to consider changing the rest of the icons in your farm to 128-Bit(RC-5) as soon as you can.  It honestly is not a good idea to have basic encryption, even if your server is behind firewalls and on a lan with no internet facing exposure.  Think about it. Do it do it! Pies up!

 

XenApp 6 launch error

 Server, XenApp  Comments Off
Aug 012011
 

Note: In XenApp 6 – you need to configure the ICA Listener Configuration application (CtxlCACfg.exe), which is located in “C:\Program Files (x86)\Citrix\system32\CtxICACfg.exe”.  To not use tsconfig.msc or you will see the following error.  The server hosting this environment is a Server 2008 R2 enterprise [w/o sp1]. The server is an IBM System X3550 M2 with Xeon5570 processors and 64 GB of Ram. Users are receiving the following message while attempting to launch a published icon hosted on this specific server:

Unable to launch your application. Contact your help desk with the following information: Cannot connect to the Citrix XenApp server. There is no Citrix Xenapp server configured on the specified address.

Recommended actions and remediations:
1.) Load up SP1 for Server 2008 R2 enterprise ASAP
2.) Check the event log for any anomalies [side by side errors and such].
3.) Publish a desktop and attempt to launch.
4.) Make sure you can telnet over port 1494 to the server to assure IMA is working properly. Example >> telnet servername1 1494. If you see a response similar to “ICAICAICAICAICAICAICA” then assume IMA is working correctly.
5.) confirm you are getting the endless “connection in progress” message followed by “There is no Citrix XenApp server configured on the specified address” prompt with a test account.

6.) Check if the ICA listener is broken/or having issues >> start > run > tsconfig.msc and press enter. Right-click on ICA-TCP under connections and select properties. Click on the “network adapter” tab and see where the ICA listener is bound. If you get an error indicating “Remote Desktop Session Host Configuration tool is not able to obtain the properties for this connection. The connection has either been deleted or the internal state of this connection has been corrupted. Please close all property pages and select refresh from the menu”

7.) If you happen to get the following, break the team – chances are its a broadcom team [BACS]. at Microsoft.TerminalServices.Configuration.SnapIn.BaseSetting.SettingHandler(Boolean fSet, REQUESTID rid, Object& objectType, UInt64& errorStatus)
   at Microsoft.TerminalServices.Configuration.SnapIn.BaseSetting.getSetting(REQUESTID rid, Object& objectType, UInt64& errorStatus)
   at Microsoft.TerminalServices.Configuration.SnapIn.TSSettings.getSetting(REQUESTID rid, Object& objectType, UInt64& errorStatus)
   at Microsoft.TerminalServices.Configuration.SnapIn.NetworkPropPage.OnInit()
   at Microsoft.TerminalServices.Configuration.SnapIn.BasePropPage.OnInitialize()
   at Microsoft.ManagementConsole.SnapInBase.ProcessNotification(Notification notification)
   at Microsoft.ManagementConsole.NamespaceSnapInBase.ProcessNotification(Notification notif)
   at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)
   at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)
   at Microsoft.ManagementConsole.Executive.SnapInNotificationOperation.ProcessNotification()
   at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)
8.) Check your NIC teaming configuration – chances are they are busted and you have the wrong network listening on the wrong interface! Break the team and manualy attempt. A reboot may be necessary!

 

Apr 262011
 

Is it possible to retrieve the hostname of the Xenapp client as they connect to the farm?

There is in fact several different things you can do to retrieve a users Hostname.

  1. you can read the value of CLIENTNAME [REG_SZ] which is located in the following key HKEY_CURRENT_USER\Volatile Environment.
  2. you can use the following variable which also displays the hostname:  %CLIENTNAME%.
  3. If you want to use VBScript to pull in the variable use the following
    1. dim oShell
    2. dim iValue
    3. dim SessName
    4. dim SpltSess
    5. dim strKeyPath
    6. set oShell = CreateObject(“WScript.Shell”)
    7. SessName = oShell.ExpandEnvironmentStrings(“%TEMP%”)
    8. SpltSess = split(SessName, “\”)
    9. strKeyPath = “HKCU\Volatile Environment\” & SpltSess(6)
    10. iValue = oShell.RegRead(strkeypath & “\Clientname”)
    11. myHostName = ivalue
    12. msgbox (myHostName)
© 2012 random technology [RT] technology documentation

Optimized by SEO Ultimate