The Citrix Receiver (XenApp plugin / Online plugin / ICA Client / WinFrame client) has a with the.ICA extension. This means that each time you open a file with the.ICA extension the Citrix Receiver is launched to interpret the file (and act upon the content of the file). In this article I’ll explain how the.ICA file is constructed, what sections and properties are commonly used and how you can create the file. ICA – Independent Computing Architecture To start at the beginning, ICA stands for Independent Computing Architecture. It is a protocol used in Citrix / (or previously Presentation Server, MetaFrame, WinFrame) to separate the application logic (which runs on a remote system, usually in a datacenter) and the presentation (on the client). In a nutshell what this protocols does is sending input from the client (like keyboard, mouse, audio, etc.) to the remote system and receive the output (like video, sound, etc.) from the remote system via the network.
On the client (a workstation, laptop or thin client) a piece of software is used to handle this traffic. At the moment of this writing the is used. Files with the extension.ICA contain information required to connect to the remote system, including session properties and (optionally) authentication.ICA File File Type Association (FTA) Files with an.ICA extension are associated with a Citrix ICA client. This is done via a (or FTA).
Sep 24, 2007 CNET's Forum on Mac hardware is the best source for finding help, troubleshooting, and getting buying advice from a community of experts. Discussion topics.
In the registry hive HKEYCLASSESROOT a key with the name.ica specifies the name of the file type and the content type. Name: Citrix.ICAClient.2.7.
ContentType: application/x-ica The name is correlated to the key HKEYCLASSESROOT and describes how the file is handled, what icon to show, what items should be visible in context menu etc. In the shell open command key the default value shows what executable to run when a file with the.ICA file extension is launched. % ConnectionName% Each section has properties (or settings) assigned, some of there are mandatory but most are optional.
In the next sections I’ll explain the most common settings and the not-so-common settings that are available. Properties per section Each section contains a list of properties (or settings) that can be set. I’ll describe the most common settings per section, a larger (not complete) list of properties can be found in the on Citrix eDocs. Encoding (Optional) This section contains setting(s) that describe how the file is encoded. InputEncoding = ISO88591 In the example the.ICA file is stored in the default encoding, ISO88591. Settings. InputEncoding.
Description: Describes the character encoding type of the.ica file. This information is used by the client to convert and understand the.ica file if the Web server that created it used an encoding type that is different from that of the the client. Possible values: Value Description ISO88591 is a joint ISO and IEC series of standards for 8-bit character encodings (Default, according to Citrix eDocs) SJIS is a character encoding for the Japanese language EUC-JP is a multibyte character encoding system used primarily for Japanese, Korean, and simplified Chinese. UTF8 is a variable-width encoding that can represent every character in the Unicode character set (Default for WebInterface launch.ica) WFClient In this section the client is configured.
WFClient stands for client, so it goes way back Example. ConnectionBar = 1 In the example a server with the name server01.domain.local is contacted on port 80 to supply details about the server or published application / desktop that is supplied in the ApplicationServers section. During the connection the Desktop Viewer is used and a Connection Bar is shown. After the connection is broken the.ICA file is removed. Settings.
AlwaysSendPrintScreen. Description: Enables or disable using the Print Screen key on the keyboard while the ICA session is running with seamless application. Possible values: Value Description On Print Screen key can be used Off Print Screen key cannot be used (Default).
CDMAllowed. Description: Specifies whether Client Drive Mapping (CDM) is allowed or not. Possible values: Value Description True Allow Client Drive Mapping (Default) False Disallow Client Drive Mapping. ConnectionBar.
Description: Enables or disable the use Desktop Toolbar (and the Desktop viewer) for all connections in the.ICA file. More details can be found. Possible values: Value Description 0 The ICA Client (wfcrun32.exe) is used instead of the Desktop viewer (cdviewer.exe) (Default) 1 The desktop viewer (cdviewer.exe) is used instead of the ICA client (wfcrun32.exe). EnableSSOnThruICAFile.
Description: Specifies whether or not to use the same user name and password the user used to log on to the client device for authentication through.ica files. For security reasons, users cannot be authenticated to the server unless this parameter is present and its value set to On, even if UseLocalUserAndPassword and SSOnUserSetting are specified in the.ica file. Possible values: Value Description On / True / 1 / Yes Use same username and password Off / False / 0 / No Do not use same username and password (Default). HttpBrowserAddress. Description: Specifies the location of the browser server (usually the data collector since it holds the most accurate information of the farm).
Possible values: Value Description: The (for instance server01.domain.local) of the browser server followed by a colon and the port where the XML service is located (default port is 80): The IP address of the browser server followed by a colon and the port where the XML service is located (default port is 80). RemoveICAFile. Description: Specifies whether or not the ICA file should be deleted after the session is finished.
The setting is set either by Off, False, no or 0 (or the opposite value). Possible values: Value Description Off / False / no / 0 Does not remove ICA file (Default) On / True / yes / 1 Removes ICA file. Version. Description: The version of the ICA file structure. Possible values: Value Description 2 Version two of the ICA file structure.
No other version is known? (Default) ApplicationServers Contains one (or more) connections that are stored in the file. The “more” connections is a legacy option used in the Program Neighborhood that has been removed in version 11.1 – (june 2009), the connections where stored in the appsrv.ini which had the same structure as the ICA file.
Desktop = In the example a connection with the name Desktop is present. When the.ICA file is executed by the client software, the properties are read in Desktop. Settings.%ConnectionName%. Description: The name of the connection, the properties of this connection are located in the section with the name name (%ConnectionName%).
Depending on the version of the client this name is (shortly) visible for the user during the connection phase. Possible values: None %ConnectionName% The section has the name of the connection that is supplied in the ApplicationServers ‘list’. In this section the properties are set for the connection. This is the most extensive list and therefore segregated in separate areas. EncryptionLevelSession = Encrypt In the example the settings for the connection Desktop are supplied.
A seamless connection will be made to the published application Desktop with a connection bar (and the Desktop Viewer) visible. Both Session Reliability as Client audio are enabled. The connection is made with compression and encryption enabled whose details are specified in section Compress and Encrypt.
Settings – General This area describes the general properties of the connection. Address. Description: Specifies where the Citrix client should connect to. Possible values:. Connect directly to server: The FQDN of the Citrix XenApp / XenDesktop server. Connect to published application / desktop: The name of the published application / desktop. Connect via WebInterface / CloudGateway: A semicolon (;) separated string containing the application / desktop to connect to, the secure ticket authority (STA) and the secure ticket (or token).
The user can click an application / desktop and will effectively download a launch.ica which will be processed by the Citrix client (receiver). CGPAddress. Description: Enables or disables Session Reliability.
Possible values: Value Description.:2598 Session Reliabilty is used (connection is made on port 2598) (empty) Session Reliability is not used (connecion is made on port 1494). Compress. Description: Specifies whether the ICA traffic needs to be compressed before its transported. Possible values: Value Description On ICA traffic is send compressed. The driver used to compress is specified in section Compress Off ICA traffic in send uncompressed.
InitialProgram. Description: Specifies what application to launch. Possible values:. Connect directly to server: The location to the executable to launch. If the value is empty the default shell is loaded. Connect to published application / desktop: A hash-sign (#) followed by the name of the published application / desktop.
Launcher. Description: Specifies the name of launch mechanism (that is, the client launcher name). This parameter is used to launch multiple ICA windows from the startup folder at logon time. Possible values: Value Description ICA Client Launched using the ICA client (default) WI Launched through the Web Interface PN Launched through the Program Neighborhood client (deprecated) PNAgent Launched through the Program Neighborhood agent MSAM Launched through the Metaframe Secure Access Manager Custom Launched through a custom client.
LaunchReference. Description: Reference token for a specific session on a Citrix XenApp server. This enables the Citrix feature, it directs the user to the same server as it has an existing session.
Possible values: Reference token for a specific session on a server (generated by the WebInterface). LogonTicket. Description: Specifies client authentication token for web interface. The client handles an authentication token in the form of an opaque LogonTicket with an associated interpretation defined by the LogonTicketType. This functionality can be disabled by clearing the Web Interface 4.5 and above check box. Possible values: A token in the form of a serialized string provided by the WebInterface.
LogonTicketType. Description: Specifies the logon ticket type for 'Web interface authentication ticket'. Use this policy to control the ticketing infrastructure used when authenticating through the Web Interface. The client handles an authentication token in the form of an opaque LogonTicket with an associated interpretation defined by the LogonTicketType. Citrix STA versions are described in. Possible values: Value Description 0 No ticket (default) 1 Secure Ticket Authority (STA) version 1 ticket 2 Secure Ticket Authority (STA) version 4 ticket CTXS1 Secure Ticket Authority (STA) version 4 ticket (?).
PersistentCacheEnabled. Description: This parameter specifies whether or not to use the persistent disk cache. The persistent disk cache stores commonly used graphical objects such as bitmaps on the client device’s hard disk. Possible values: Value Description On The persistent cache is enabled Off The persistent cache is disabled (Default). SessionSharingKey. Description: Specifies the session sharing key.
The sharing key is a combination of all attributes that allows you to reuse an existing session: colors, encryption, audio, credentials and farm. If any of these attributes are different (not 100% identical), a new session is created. For more information read the about this topic. Possible values:. Web Interface 4.6 and before: colors – encrypt – audio – domain – user farm. Above Web Interface 4.6: A serialized string containing the same information. SSLEnable.
Description: Specifies whether or not SSL is enabled. When SSL is enabled all ICA traffic (1494 or 2598) is tunneled via a secure socket layer (SSL) tunnel via port 443 (by default). Possible values: Value Description On ICA traffic is tunneled via SSL Off ICA traffic is not tunneled via SSL (Default). SSLProxyHost. Description: Specifies the hostname of the SSL proxy when SSLEnable is set to ‘On’.
This value is not present when traffic is not tunneled via SSL. The name on the certificate has to match the hostname (FQDN).
Possible values: Value Description.:443 It is assumed that all Citrix server in the farm have their own SSL relay, the SSL relay is the same as the Citrix server. (Default):443 An explicit server is specified as the SSL relay server (for instance an Citrix Access Gateway). TransportDriver. Description: This parameter specifies the transport protocol to use to connect to the specified connection or application set. This name must correspond to one of the transport drivers specified in the TransportDriver section of Module.ini. Possible values: Value Description TCP/IP The protocol is used to transport the ICA traffic (Default) IPX The protocol is used to transport the ICA traffic SPX The protocol is used to transport the ICA traffic NetBIOS The protocol is used to transport the ICA traffic. UseAlternateAddress.
Description: This parameter is useful in performing Network Address Translation (NAT). If set to 1, it defines whether to use the alternate address for ICA connectivity across a firewall or a router. Possible values: Value Description 0 Do not use the alternate address for firewall connection option (Default) 1 Use alternate address for firewall connection option. WorkDirectory. Description: Specifies the working directory for the InitialProgram. Possible values:.
Connect directly to server: The working directory of the program to execute (instead of the default shell). Connect to published application / desktop: Not used. WinStationDriver. Description: Specifies what winstation driver to use, the driver where all ICA (including virtual channels) traffic flows through. Possible values: Value Description ICA 3.0 The only valid value is ICA 3.0. Previous versions where used before WinFrame (Windows NT 3.5). (Default) Settings – Audio This area describes the settings that relate to audio HDX.
AudioBandwidthLimit. Description: Specifies the audio bandwidth limit and, by extension, the audio quality for the connection. Higher audio quality requires more bandwidth. Possible values: Value Description 0 High quality (1.4 Mbps) 1 Medium quality (64 Kbps) (Default) 2 Low quality (4 Kpbs). ClientAudio.
Description: Specifies whether or not to enable client audio mapping. Possible values: Value Description On Enables client audio mapping Off Disables client audio mapping (Default). EnableAudioInput. Description: Enable access to audio capture devices. Use this policy to enable and restrict the remote application or desktop access to local audio capture devices (like microphones).
Possible values: Value Description True Allow the use of audio capture devices False Disallow the use of audio capture devices. EnableRtpAudio. Description: Enables or disables the real-time transport of audio over UDP. Possible values: Value Description True Enables Rtp Audio (Default) False Disables Rtp Audio. SpeedScreenMMAAudioEnabled.
Description: Specifies whether or not audio playback will occur through HDX MediaStream Multimedia Acceleration. Possible values: Value Description True Audio playback will occur through HDX MediaStream Acceleration (Default) False Audio playback will not occur through HDX MediaStream Acceleration Settings – Display This area describes the settings that relate to display like color depth, resolution and video HDX. DesiredColor. Description: Specifies the preferred color depth for a session. Possible values: Value Description 1 16 colors (Default) 2 256 colors 4 High color (16 bpp) 8 True color (24/32 bpp). This is 32bpp, unless the administrator explicitly prohibits a server from supporting a 32-bit session. In that case, the session is downgraded to 24bpp.
DesiredHRES. Description: This parameter defines the horizontal window size in pixels. For Citrix Receiver and up: If TWIMode is set to Off / False, this parameter is used. For older Citrix clients: If DesiredWinType is set to Custom, this parameter is used. Possible values: The horizontal window size in pixels (Default: 640). If you set both DesiredHRES and DesiredVRES to the session will always launch in full screen (thanks ).
DesiredVRES. Description: This parameter defines the vertical window size in pixels. For Citrix Receiver and up: If TWIMode is set to Off / False, this parameter is used. For older Citrix clients: If DesiredWinType is set to Custom, this parameter is used. Possible values: The vertical window size in pixels (Default: 480.) If you set both DesiredHRES and DesiredVRES to the session will always launch in full screen (thanks ). DesiredWinType.
Description: This parameter specifies the default desired window size for custom connections. This setting is ignored by the Citrix Receiver. Possible values: Value Description 1 640×480 2 800×600 3 1024×768 4 1280×1024 5 Custom size defined by DesiredHRES and DesiredVRES 6 Percent 7 Full Screen 8 Seamless. SpeedScreenMMA. Description: Specifies whether or not to enable the HDX MediaStream Multimedia Acceleration.
Possible values: Value Description On The remote video option allows the server to directly stream certain video data to the client (if the client has the appropriate codecs). (Default) Off The video is always rendered on the client. TWIMode.
Description: Specifies whether or not to use seamless mode for the connection. Possible values: Value Description On / True Enables the seamless mode for the connection Off / False Disables the seamless mode for the connection (Default) Settings – Security This area describes the settings that relate to security.
ClearPassword. Description: The parameter specifies the password for the supplied credentials in clear text. This is less safe than the encrypted Password setting. Possible values: A password. EncryptionLevelSession. Description: Specifies the encryption level of the ICA connection (SecureICA).
Since the Citrix Receiver a section with the corresponding name should be provided including the drivers. Possible values: Value Description Basic Basic (Default) EncRC5-0 RC5 (128 bit – Logon Only) EncRC5-40 RC5 (40-bit) EncRC5-56 RC5 (56-bit) EncRC5-128 RC5 (128 bit) Encrypt Basic. Domain.
Description: This parameter specifies the user domain for the supplied credentials. Possible values: The name of the domain for the supplied credentials. Password. Description: This parameter specifies the password for the supplied credentials. The password must be encrypted. Possible values: An encrypted password.
Remko Weijnen has written a tool to Encode (and decode) Citrix Passwords, you can find the tool. UseLocalUserAndPassword. Description: Specifies whether or not to use the same user name and password the user used to log on to the client computer for authentication to the Citrix server. SSOnUserSetting must be set to On. Possible values: Value Description On Use pass-through authentication.
Off Does not use pass-through authentication (Default). Username.
Description: This parameter specifies the username for the supplied credentials. Possible values: The username for the supplied credentials. Compress Contains the name of the drivers use for compression as specified in the Compress setting in the%ConnectionName% section. DriverNameWin32 = PDCOMPN. DLL In the example the default drivers used for compression are specified. Settings.
DriverName. Description: This parameter specifies the name of the DOS driver file to load. Possible values: Value Description PDCOMP.DLL The default driver file for used for compression (Default). DriverNameWin16. Description: This parameter specifies the name of the Win16 driver file to load. Possible values: Value Description PDCOMPW.DLL The default driver file for used for compression (Default).
DriverNameWin32. Description: This parameter specifies the name of the Win32 driver file to load. Possible values: Value Description PDCOMPN.DLL The default driver file for used for compression (Default) Encryption Contains the name of the drivers use for encryption (SecureICA) as specified in the EncryptionLevelSession setting in the%ConnectionName% section.
The name of the section equals the value of the EncryptionLevelSession setting. DriverNameWin32 = PDC128N. DLL In the second example the drivers for each encryption level (SecureICA) are specified in a separate section. Settings. DriverNameWin16.
Description: This parameter specifies the name of the Win16 driver file to load. Possible values: Value Description PDCRYPTN.DLL The default driver file used for used for encryption (Default) PDC0W.DLL The driver file used for RC5 (128 bit – Logon Only) encryption. PDC40W.DLL The driver file used for RC5 (40-bit) encryption. PDC56W.DLL The driver file used for RC5 (56-bit) encryption. PDC128W.DLL The driver file used for RC5 (128 bit) encryption.
DriverNameWin32. Description: This parameter specifies the name of the Win32 driver file to load. Possible values: Value Description PDCRYPTW.DLL The default driver file used for used for encryption (Default) PDC0N.DLL The driver file used for RC5 (128 bit – Logon Only) encryption.
PDC40N.DLL The driver file used for RC5 (40-bit) encryption. PDC56N.DLL The driver file used for RC5 (56-bit) encryption. PDC128N.DLL The driver file used for RC5 (128 bit) encryption.
When are.ICA files used?.ICA files are used in many applications that allow you to connect to a Citrix XenApp / XenDesktop environment. Most common used are the and the, but third party applications like use.ICA files as well.
Usually the use of.ICA files is temporarily and hidden for the end user, which is a good thing. Web portal default configuration When you launch a published application / desktop via the web portal supplied by Citrix (WebInterface, StoreFront or VDI in a box) a default configuration is applied. You can alter the default configuration to meet your needs, if it isn’t available in the management console (most settings are not configurable via the management console). The default configuration is stored in a default.ica file. The location of the default.ica depends on the platform you’re using and the name of the site. Since both WebInterface and StoreFront are integrated in Microsoft Internet Information Services (IIS) the configuration is stored in a directory in the%SystemRoot% inetpub (default location). For each site a directory is created which you specified when you created the site.
Assuming you’ve used the default site name, these are the locations where the default configuration is stored: Platform Version Type Location Web Interface 5.x XenApp inetpub wwwroot Citrix XenApp conf 4.5 / 4.6 XenApp inetpub wwwroot Citrix AccessPlatform conf 4.0 XenApp inetpub wwwroot Citrix MetaFrame conf All XenApp services / PNAgent inetpub wwwroot Citrix PNAgent conf StoreFront All All inetpub wwwroot Citrix Store AppData VDI in a box All All /home/kvm/install/servletcontainer/webapps/ dt/WEB-INF/etc/proto.ica (not default.ica!) Thanks for locating the default configuration for. Change specific published application / desktop If you want to change the setting / behavior of a specific published application / desktop you need to add the published resource in the ApplicationServers section and add a %ConnectionName% section with the required settings. It is important that the name of the connection (%ConnectionName%) is exactly as it is shown in the application set of the management console. DesiredVRES = 800 How can I create an.ICA file?
Well, there are a number of options:. Manual. Citrix ICA File Creator –.
Citrix Quick Launch – The first option, manual, is of course an option but it’s quite some work for an easy task. Keep in mind that the Citrix Receiver (or older clients) are rather restrictive with the information it returns. If there’s an (syntax) error in the ICA file well, in most cases you need to sort that our yourself.
The second option, the Citrix ICA File Creator, is a less time consuming option than creating it manually but is a bit clunky. It works, but it’s not the best tool (and unsupported). The third option is the Citrix Quick Launch tool,which is also provided by Citrix (and unsupported, btw), and is built to offer some features of the deprecated Program Neighborhood. IMHO this is the best way of building ICA files Not only because it offers the most features (it is recently updated) but also because you can connect and test the connection immediately! PS: The Citrix Quick Launch works even on desktops with 125% DPI (default with a resolution of 1920×1080 on my laptop)!
So kudos to the developers who where willing to build a version that supported 125% DPI (and James Denne – – for contacting them). Comments Did I miss anything or do you have a suggestion? Let me know in the comments.
Hi ingmar, Great article. Not sure when it was posted as it only lists the day and month at the top of article so not sure if you will respond to this. ? Our users run a seamless full desktop session to our citrix server – but when they press the print screen key, or alt Print screen, nothing in the seamless desktop session is captured to the full desktop clipboard.instead, if you press print screen then log off the citrix session then paste into paint.exe from the local client, it will paste a copy of what was on the seamless desktop at the time you pressed print screen.so the print screen is capturing the correct data (i.e. What is happening in the citrix session) but it is storing it in the local PCs clipboard memory and not the clipboard that is avaliable to the citrix session. Can we make it so the citrix session can have access to the local clipboard memory or is there another way to get print screen functionality happening inside our citrix sessions?
Issue at the moment is, when we press paste in side the citrix session after pressing print screen, nothing pastes into word/paint.but log out of the citrix session and paste into paint/word on the local PC and our print screen appears. At the moment we are using PS4.5 and ICA client v10.
We are using this reg key as a work around at the momentit turns the f12 key into a print screen key and that is working for us. Thanks in advance and hopefully you can point me in the right direction. Hey Ingmar, I tried setting the “AlwaysSendPrintScreen” key with a new string value with the data value of “On” – that is in HKLM-software-citrix.WFClient.
I restarted PNA and tried connecting to the seamless desktop again but the print screen key still was not pasting from the clipboard into the citrix session. Howerver it seems that the print screen key is working and being passed to the citrix session but the print screen image is being placed in the local computers clipboard.because when i minimise down to the local machine and paste into wordthe print screen of the seamless session is shown. It seems that the print screen functionality is working.but the seamless session cannot get access to the local clipboard.how can i enable that? How can i allow the seamless full desktop session to access the local machines clipboard.or make the citrix session pass the print screen key into the citrix session so that the full desktop/server clipboard is used to store the print screen image. Not sure why this is not working or what others have done to resolve this print screen functionality.
Hi Ingmar, Sorry – i applied your setting to the ICA file as you explained (from the web interface, i right clicked the ‘desktop’ app then saved to desktop to get an ICA file that i can modify) – i added the key you mentioned AND IT DID WORK!!! Now when the user presses the print screen or alt print screen key the correct thing is pasted INSIDE the citrix session! THANK YOU:).but wondering if you can explain or tell me how i can make this ‘key’ a permanent part of the published desktop app? Can i modify the ICA file on the servers that are given out to the clients when they access the published app list? Reason being is that when i save a copy of this ICA file, i have to modify the server IP address – we have 3 citrix servers to i dont want to direct all sessions to the one server – i want the citrix server to manage the load.i also dont want to have to maintain this separate ICA file as users connect to us from different computers all the time.so getting them the ICA file is a pain. How can i add this key to the ICA file that is given out by the citrix servers?
Where is the ICA file that the server gives out constructed from? Does it just build the ica file at the time the user clicks the published desktop and bases the contents off the settings i apply when i created the app with the citrix management console? Can i set this key anywhere in the CMC so that it applies to the ICA file that the server gives out for this full desktop? Thanks Ingmar. Hi Ingmar, I found the ICA files you mentioned – the default.ica files and made the changes in there.
The settings were then successfully applied to sessions that were started from the Citrix Web Interface.HOWEVER, the settings did not apply to sessions launched via the PNA! I did a little more digging around and just in case someone else stumbles upon this issue, i did manage to get it working. In order for the sessions launched via PNA to correctly use the print screen and other windows keys, i had to edit the config.xml file of the PNA in the CMC. Access the CMC – expand web interfaces – find your PNA site – expand that to get your config.xml file – right click it and choose change session options – in here choose client resources and then under ‘targets of windows key combinations’ make sure the only one that is ticked is ‘in full screen desktop’. Our problem all along was that all of these tick boxes were selected, the PNA clients were all set to choose the default setting and because all of these were ticked here, i assume it just selected the first item in this list as the default which is ‘on the local desktop’!! So i have now modified the ica file to include the key you mentioned – that fixed the problem for sessions launched from the web interfaceand i have also modified the PNA config file to fix the issue for sessions launched internally via PNA.
Thanks again for your input, assistance and fast response Ingmar ?. Hi, Is it possible to create an ICA file that connects a web interface requesting for published application resource from another Farm (added to the WI) and then connects to provisioned XenApp server?
I can only get this working with a specific server or dynamically within the servers of the farm that provides the WI. But if I add another farm to the WI, I cannot create a working ica file which would connect the WI requesting the published app on this other farm. I am using the Citrix Linux receiver. In the wfcmgr I can see all apps from both farms in the XenApp view. But with the Connection view I only see the apps from the farm that provides the WI. Same issue when trying with the Citrix Quick Launch – I only see applications from the first farm, not from the second farm that is added to the WI (note: for both the XenApp Web Sites and the XenApp Services Sites).
Note: I can see all the applications from both farms when logging in with the browser to the XenApp web site. Dear Ingmar, I Want to make icaclient.visible = tr ue as like as ie.visible =true; please let me know; which property I have to use in icaclient? I have written one small script to login to the server using ica client; manually script is working fine; when i schedule script in task scheduler and enabled user is loged in or not option in task scheduler; could not able to connect to the system. If i enabled; user is loged only option ica client is connecting to the system. Please give your valuable ideas; Thanks in advance; Adarsha.
Hello Ingmar, Thank you for your useful post!! I want to manipulate the ICA encryption level. After I “Enable SEcureICA” on the delivery group, use a policy applied to that delivery group to set the encryption at RC5-56 (for example), the encryption level on the client (as seen by Citrix Connection Center) is still RC5-128 (not RC5-56 like I want) so it seems like the policy isn’t working. We want to do testing with all the encryption levels. Article below suggests there may be 128 bit encryption on the client that’s overriding the 56 bit encryption? Do you know how I would address this and properly manipulate the encryption?
In the section “If you want to change the setting / behavior of a specific published application / desktop you need to add the published resource in the ApplicationServers section and add a %ConnectionName% section with the required settings. It is important that the name of the connection (%ConnectionName%) is exactly as it is shown in the application set of the management console.” Is there a way to use a wildcard for the application name? If i have a bunch of applications launching and each new user gets assigned a number, lets say “Windows 7 User-0001” the next “Windows 7 User-0002”. Can I use a wildcard to say “Windows 7 User-.=” then create a section called Windows 7 User-.
Is there a specific port that an XML broker users to enumerate applications? I have an ICA file that runs just fine on an environment in the same LAN as the XML broker, web interface server, etc., but it fails when I try to run the same file from a satellite office that has a site to site VPN configured. When running the Citrix Quick launch utility on the main network, I can select “to published applications” and see the full list of published applications enumerated in the drop down menu. When I’m on a workstation at the satellite office, however, and try to use the quick launch utility pointed at the same XML broker IP address, I get an error message stating “Error: could not get the list of published applications” when I select the ‘to published application’ radio button.
I can telnet to the IP address I’m using in CQL from the satellite office over port 80– which is what is being used as the XML port for the farm on the web interface– and can also launch applications using the online plug-in from the satellite workstation. I can also get a published desktop session by checking the ‘to XenApp’ radio button in the Choose connection type section of the quick launcher. Is there an additional route that needs to be configured on the VPN perhaps, a specific port that needs to be opened on either side, or is there something else going on?
The answer that fits into the scheme of things. For what its worth, the poster posted a PC question in a Mac forum.
I supplied a google that finds replacement programs that will cure the issue. If you feel my answer is not right, supply what you think is the right answer.
If you want the forum to be full of members flaming each others answers, keep it up. This is not how these forums work. Give your answer and let them choose. Do however butt in if you find an answer to cause other issues such as total data loss.
On the Mac and keyboard: Hold down the Apple command key plus the shift key and press the numeral #4. After that you will get a marquie with cross hairs on it. Place the crosshair marquie and drag over the image.
You will hear a faint click, like a camera shutter. The Image will be placed to your desktop as a PDF file in OSX 70DPI. And on the hard drive in OS9. Hold down the Apple command key plus the shift key and press the numeral #3. That will get you a full screen shot that is saved to your hard drive.
Usually listed as a Picture file and so forth. That's how it's done on a Mac. May be more difficult on the PC with a Mac keyboard. Nice question! Why would you use a Mac keyboard on a PC in the first place! Doesn't the PC have a pull-down menu to print the screen? Why use the keyboard at all?
By MasterOfNone - 26/09/06 10:56 In reply to: How do i print screen on a PC with a Mac Keyboard?? By cfagan Go to Accessories/Accessability in the start menu and select the On-Screen Keyboard.
That will give you a print screen button you can click with your mouse. (Using the On-Screen Keyboard will not change the active window, so you can even grab just the window you want). I tried what you suggested, which worked fine, except that it captured the on-screen keyboard as well! I also tried the 'active window' capture, by clicking on the alt key, but that didn't work at all.
I know the other work-around is to use the screen capture feature of a paint package program, which is what I'm doing at the moment, but it's a little long-winded. I never thought I'd miss that simple but very effective key combination! It was so much quicker and easier. I think I must be doing something wrong. By the way, I'm using a MacBook, which may or may not make a difference to anything, but I thought I'd mention it anyway.
If there are any other suggestions, or any pointers as to where I might be going wrong, I'd be extremely grateful to try them. January 22, 2003 Todd Miller is using an Apple Pro USB keyboard on a Windows machine, and found a way to remap the F13, F14, and F15 keys so that they act as the Windows Print Screen, Scroll Lock, and Break functions. His method involves creating a text with registry information. I use my Apple brand USB keyboard with a USB KVM switch to control both my Macs and a PC.
It works great, except I was missing the Print Screen key because the Mac sends an F13 instead of Print Screen. I came across this registry edit that will map the F13-F15 to their PC counterparts. I have tested this on my Windows 2000 machine and I think it should also work on XP. This allows the user to press F13 on the Mac keyboard and have Windows receive a Print Screen command instead of F13.
Follow these instructions In order to map the F13-F15 keys on an Apple USB keyboard to the functions, Print Screen, Scroll Lock, and Break commonly found on PC keyboards: 1. On your PC, copy the following lines into a text file. REGEDIT4 HKEYLOCALMACHINE SYSTEM CurrentControlSet Control Keyboard Layout 'Scancode Map'=hex:00,00,00,00,00,00,00,00,04,00,00,00,46,E0,5F,00,46,00,5E,00,37,E0,5D,00,00,00,00,00 2. Rename the text file remap.reg. Double click on the file remap.reg and answer yes to the question about adding the information to the registry.
Function keys are now remapped to their PC equivalents.