We periodically get issues where when a user launches a published application, it appears to be launched outside of the desktop or for lack of better words “out of focus” and the user is unable to bring or move the application to the foreground. and whats completely interesting is no matter how many times you reset the profile, the application still appears to not be focused properly.

As a result of further research – there are several things you can do to address this issue.

  1. Shadow the users session – when they click accept, the vertical/horizontal resolution will be significantly decreased and the user will be able to properly set the application in a window or monitor that is suitable for them.
  2. Use vbscript or .net to first find the process using objProcess.getowner, then attached to the process name using objProcess.name. then at that point, you will want to grab the process id and use wshshell.appactivate to bring the application to primary monitor 1 and set it to the foreground and then use sendkeys to finish up the process. We have provided a vbscript and a .net example on how to grab an application and set the focus to the foreground. Simply logon and download the example.
  3. If you happen to see the application running in the taskbar – right click on the application, then select move. then hold down the left arrow key for a few seconds followed by using the mouse. you should see the application come to focus and allow you to manually set the position.

Either way you look at it, an administrator needs to simply step in and help the user. At that point the window history should be saved and the user/application settings

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!

 

 

After establishing connectivity for quite some time, we randomly get the following message. I’ve seen this not only on the new WYSE zero footprint devices, but also on the 11x and 12x xenapp clients.

User receives the following prompt:
>> Citrix XenApp connection interrupted.
>> Attempting to reconnect …
>> Network or dial-up problems are preventing communication with the citrix XenApp Server.  If the problem persists. Please contact your network administrator. Number of failed reconnection attempts:

** After quick review, the notification displays not the only the number of failed reconnection attempts but also the Icon name, Server Address and the clients Hostname.

Here is what what was found:
** The server in question hosting this session did not have any information in the event logs (event, system, etc…).
** After checking the end users workstation, no information was logged in the clients event logs (event, system, etc…).

© 2012 random technology [RT] technology documentation

Optimized by SEO Ultimate