| NFuse is the focal point to any MetaFrame installation and in return one of the most important. A good friend of mine taught me that perception is reality and NFuse is the first impression the users will have of their new Citrix environment. Keeping to this philosophy a custom branded NFuse 1.71 site accomplishes all of this while giving you simplified installation, configuration, and management. Not to mention it looks very professional. In order to implement a full featured NFuse web site, follow the following three steps. Install the NFuse 1.71 Web Extensions (standalone web server only) Configure NFuse 1.71 through the Citrix NFuse Classic Administration Web pages Brand your NFuse web portal. You will also want to make sure you follow the security recommendations for the particular Web Server that you are using. Note: NFuse Classic 1.71 is a security update to NFuse Classic 1.7. It can be downloaded from the http://www.mycitrix.com. Important: If you install NFuse 1.71 on MetaFrame XP Service Pack 2/Features Release 2 or earlier server with remapped server drive letters, change every instance of C:\ in the NFuse.properties file to the new %SystemRoot% drive letter. This operation is performed automatically if you are upgrading the server to Feature Release 2/Service Pack 2. Stop and restart the WWW Service for the changes to take effect. Note: NFuse Classic 1.71 gives you the ability to add considerable enhancements and integration in to your existing environments with experienced programmers and or professional services.
In order to run NFuse on a standalone web server you will be required to install the NFuse web extensions. By default, setup will install NFuse in to the C:\Program Files\Citrix\NFuse directory. Note: When using NFuse Classic 1.71 with ticketing you will want to make sure that all the MetaFrame servers are configured to use the same Citrix XML port number. Note: If you are going to be running NFuse from a MetaFrame server then you will want to skip this step) 1. Insert the MetaFrame XP Componects CD and when the followings pops up click the NFuse Classic button. 
2. Click Next to continue. 
3. Click the I accept the license agreement radio button and click Next to continue. 
4. Click the OK to restart IIS radio button and click Next 
5. Click Next to accept the default location for the NFuse files. Make note of this directory for this is the directory that NFUSE.TXT and NFUSE.CONF file resides. 
6. Enter the name of a MetaFrame server in your farm that is running the XML service and the port that the XML server is listening on and click Next Note: If you are unsure of the port XML is listening on, you will be able to obtain that information through servers properties - MetaFrame Settings tab in the CMC. 
7. The next screen asks you if you would like to install the latest ICA client CD to the ICAWEB directory for use in your NFuse portal. I highly recommend it! Enter the location of the ICAWEB folder and click Next Note: If you do not have access to the latest version (6.31) of the Citrix ICA Clients CD then you will need to download them from: www.citrix.com/dowloads. Click on Download NFuse 1.61 Click Yes to accept the license agreement click Generic Web-based ICA Client Install Package Once downloaded you will want to extract the ICAWEB620.EXE file to C:\ICACLIENT then click Browse and select C:\ICACLIENT\ICA620\ folder and click OK Click Next 
8. Click Next to continue. 
9. Click Finsh 
You have a successfully installed NFuse and are ready to proceed in configuring your NFuse Web site. First, you will want to test your NFuse installation. To do this you will need to open your web browser and in the address box type: http://nfuse_webserver/citrix/nfuse17 enter a username, password and domain and verify that you are able to launch a published application.
If you are currently running NFuse 1.61 or below and want to take advantage of the new features of NFuse Classic 1.71. The following details how to upgrade a stand along web server to the NFuse Classic 1.71 Web Extensions. 1. Insert the MetaFrame XP Components CD and when the followings pops up click the NFuse Classic button. 2. Click Next to start the installation. 3. Click the I accept the license agreement radio button and click Next. 4. Click to select the OK to restart IIS radio button and Click Next. 5. Click Next to accept the default location for the NFuse Classic 1.71 program files. 6. You are now prompted to select a location for setup to backup the previous NFuse version. Accept the default location and click Next to continue. 
7. Click Next to install the ICA Clients from the Components CD. 8. Click Next to install NFuse Classic 1.71 9. Click Finish You have now successfully upgraded your web server to NFuse Classic 1.71 and are ready to configure it for use. Important! Your previous NFuse web sites might now work correctly. You will find the new NFuse Classic 1.71 site located at http://nfuse_webserver/citrix/nfuse17.
23. 3. How to Configure NFuse 1.71 through the Web Administration Tool NFuse 1.71 introduces a new easy to use GUI administration tool to configure such items as the MetaFrame Servers, Authentication, Server-Side Firewall, Client side firewall, ICA Client Deployment and ICA Customization. The NFuse web admin tool is a GUI interface for making changes to the NFUSE.CONF file located in \Program Files\NFuse\Citrix\conf folder. After you have made changes using the Web Administration tool, you save and apply them so your configuration takes effect. The Web Admin tool is only for Windows/IIS machines, and requires Internet Explorer version 5.0 or later. You can browse to the NFuse Classic Administration tool via: http://nfuse_servername/citrix/nfuseadmin. 
In the MetaFrame Servers section of the NFuse Classic Web Administration tool you have the ability to configure how NFuse to deal with multiple MetaFrame servers and their XML services, what ports are the XML services listening on the desired SSL server port. 
Server List In this section, you will configure how NFuse will communicate with the MetaFrame XML service of every MetaFrame server. By doing this you will not only configure how NFuse will talk with the Farm but you can also accomplish a bit of load balancing to guarantee high availability and which goes to the goal of high user perception. Note: Currently NFuse 1.71 does not support aggregation of multiple farms in one application set. In order to accomplish that you will need to use Project Columbia with the NFuse 1.61 server extensions. As documented in Methodology in a Box 1.1. (http://www.dabcc.com/projectinabox/) The following defines how to configure how NFuse Classic will communicate with the MetaFrame farm. 1. Click MetaFrame Servers in the panel on the left of the page. 2. Under Serve List, you will need to type the name of a MetaFrame server that is running the XML service in the Server address text box and click Add to add it to the list of server addresses. Repeat for every MetaFrame server in the farm. The servers are processed from the first server in the list down. You will want to prioritize the MetaFrame server with the data collectors being at the top of the list and then to organize the rest if the order of most available server. 
3. Check the Use the server list for load balancing check box to enable load balancing of the MetaFrame server in the server addresses listbox. NFuse will start with the first server in the list and then move to the next until the end of the list and then back to the beginning. 
4. The Bypass any failed server for X minutes (applies to all servers in the list) setting lets you set the amount of time that a failed server is hidden from the list of available servers. When NFuse fails in connecting to a MetaFrame XML service of a server listed in the Server addresses listbox it will removes it from the list for X amount of minutes. When the specified time limit is meet then the Server in placed back in the list. 
5. In the XML service port text box you can specify the TCP/IP port used by the Citrix XML Service on the MetaFrame servers specified in the Server addresses list. By default, this is the value of the port number entered during NFuse Classic installation. This port number must match the port number used by the Citrix XML Service. 
6. In Transport type - you can specify the protocol used to transport NFuse Classic data between the Web server and MetaFrame server. 
q HTTP - Select this to send data over a standard HTTP connection. Use this option when you have made other provision for the security of this link. q HTTPS - Select this to send data over a secure HTTP connection using SSL. You must ensure that the Citrix XML Service is set to share its port with IIS, and that IIS has been configured to support HTTPS. q SSL Relay - Select this to send data over a secure connection that uses the Citrix SSL Relay running on the MetaFrame server to perform host authentication and data encryption. 7. If you are using SSL Relay, specify the TCP port of the SSL Relay in the SSL server port field (the default port is 443), and the directory containing the certificate authority root certificates in the SSL key store path field. NFuse Classic uses root certificates when authenticating a Citrix SSL Relay server. Ensure all the servers running Citrix SSL Relay are configured to listen on the same port number. 
8. Click Save. The Overview page appears. Click the Apply Changes link. The Apply Changes page appears click the Apply Changes button for the changes to take place.
In the Authentication section you can configure the ways in which users can authenticate to NFuse Classic and, subsequently, to MetaFrame. Authentication to NFuse Classic takes place when a user accesses NFuse Classic using the Login dialog page or via another authentication method. If authentication is successful, NFuse Classic returns the users application set. You can configure explicit authentication, guest logins, Desktop Credential Pass-Through (Single Sign On), and smart card authentication to NFuse Classic. Use the Methods for authenticating to NFuse Classic section to configure user authentication to NFuse Classic. You can also configure how users authenticate to MetaFrame. Authentication to MetaFrame takes place when a user clicks on a hyperlink in their application set to launch an application. If authentication is successful, an ICA session is initiated in which the application runs. You can configure pass-through authentication and smart card authentication to MetaFrame. Use the Authentication for launching applications section to configure authentication to MetaFrame 
Methods for Authenticating to NFuse Classic In this section, you will configure what methods of authentication NFuse Classic will use to login and authenticate users. Note: The type of authentication you specify does not affect the method used for ICA Program Neighborhood Agent Clients. You must edit the Config.xml file to change the authentication method used by the Program Neighborhood Agent Clients. For more information, please refer to the ICA Win32 Client Administrators Guide. I will be adding a How to Configure the Config.xml file in the next release of this document. You can specify the following methods of authentication: 
Smart card By selecting this checkbox, users can authenticate to NFuse Classic by inserting a smart card into a smart-card reader attached to the client device. The user is prompted for a PIN. Desktop Credential Pass-Through By selecting this checkbox, users can authenticate to NFuse Classic using the credentials they provided when they logged into their Windows desktop. Users do not need to re-enter their credentials at the NFuse Classic Login page and their application set is automatically displayed. By combining Desktop Credential Pass-Through with pass-through authentication, you provide users with single sign-on. Pass-through authentication is a feature provided by the Win32 ICA Client. Security Issue - If the pass-through authentication feature is enabled on the Win32 ICA Client, an attacker could send the user an ICA file that causes the users credentials to be misrouted to an unauthorized or counterfeit MetaFrame server. Therefore, I do not recommend you enable the pass-through authentication feature. Guest login By selecting this checkbox, you will enable Guest users access through NFuse Classic without supplying a username and password and launch applications published for anonymous use on the MetaFrame server. Explicit authentication By selecting this checkbox, users are required to log into NFuse Classic by supplying a username and password. Microsoft domain-based authentication and Novell Directory Service (NDS) authentication are available. 
The following defines how to configure explicit login: 1. Click Authentication in the panel on the left of the page 2. Click to select the Explicitly login check box. 3. Click to select Use NT authentication radio button to specify Microsoft domain-based authentication. To force users to log in to a specific domain, select the with force login domain check box and enter the name of the domain.
4. If the users will be logging in to a Novell Netware environment then select the Use NDS authentication radio button. Specify an NDS tree in the with tree name field and a context name in the Context name field and click Add. The context name is displayed in the Context list. If you specify more than one context name, highlight a context name in the list and use the Up and Down buttons to place these in the appropriate order. The order you specify determines the order that context names are displayed to users in the user Login dialog box. 
5. In the Allow user to change password section you have the ability to specify whether users can change their login passwords within an NFuse Classic session using the Allow user to change password field: 
q Yes Click the Yes radio button to give users the ability to change their password through NFuse Classic. When you enable this option, the change password icon is displayed on users pages. When users click on this icon, a dialog is displayed, in which users can enter a new password. q No Click the No radio button to prevent users from changing their login password within NFuse Classic. Users must log in to MetaFrame to change their passwords. q On Expiry Click the On Expiry radio button to let users change their login password only when the password has expired, select On expiry. When you enable this option, if a user fails to log into NFuse Classic due to an expired password, the user is redirected to the change password dialog. After changing the password, the user is automatically logged into NFuse Classic using the new password. The time of expiry is an operating system setting.
Authentication for Launching Applications In this section, you can also configure how users authenticate to MetaFrame. Authentication to MetaFrame takes place when a user clicks on a hyperlink in their application set to launch an application. If authentication is successful, an ICA session is initiated in which the application runs. You can configure pass-through authentication and smart card authentication to MetaFrame. 1. To enable pass-through authentication of the users credentials, set Enable ICA Client pass-through authentication to one of the following options: 
q Auto. This is the default. If the user authenticated to NFuse Classic using Desktop Credential Pass-Through, NFuse Classic attempts to authenticate to MetaFrame using pass-through authentication, and the ICA Client passes the captured credentials to the MetaFrame server. If the user authenticated to NFuse Classic using a smart card, the ICA Client does not pass the captured PIN to the MetaFrame server, and the user is prompted for their PIN. q Yes. NFuse Classic always attempts to authenticate to MetaFrame using pass-through authentication. The ICA Client passes the captured credentials or PIN to the MetaFrame server. q No. NFuse Classic never attempts to authenticate to MetaFrame using pass-through authentication. 2. To enable smart card authentication to the MetaFrame server, set Use smart card to log in to MetaFrame to one of the following options: 
q Auto. This is the default. If the user authenticated to NFuse Classic using a smart card, NFuse Classic attempts to authenticate to MetaFrame using this method. q Yes. NFuse Classic always attempts to authenticate to MetaFrame using smart card credentials. q No. NFuse Classic never attempts to authenticate to MetaFrame using smart card credentials. 3. To change the expiry time for the ticket generated by the MetaFrame server. Ticketing provides enhanced authentication security for explicit logins by eliminating user credentials from the ICA files sent from the Web server to the client devices. By default, each NFuse Classic ticket has an expiry time of 200 seconds, but you can change this. To configure the expiry time of tickets 
Enter a value in seconds in the MetaFrame ticket time to live field. By default, the expiry time is 200 seconds. 4. Click Save. The Overview page appears. Click the Apply Changes link. The Apply Changes page appears click the Apply Changes button for the changes to take place.
In the Server-Side Firewall section, you can configure NFuse Classic to include the appropriate IP address in .ICA files, depending upon how you have configured your firewall and your MetaFrame servers. 
Default Address Translation Setting If you are using a firewall in your MetaFrame installation, you can use the Server-side firewall settings page to configure NFuse Classic to include the appropriate IP address in .ICA files, depending upon how you have configured your firewall and your MetaFrame servers. The following defines how to configure the default address translation settings of addressing within NFuse Classic: 
1. Click Server-Side Firewall in the panel on the left of the page. 2. In the Default address translation setting section, select the default method of address translation: q Normal address - the IP address given to the client is the actual address of the MetaFrame server specified in the MetaFrame Servers page. This is the default setting. q Alternate address - the alternate address is given to the client. The MetaFrame server must be configured with an alternate address and the firewall configured for network address translation. q Translated address - the address given to the client is determined by the address translation mappings set in NFuse Classic. q Citrix Secure Gateway - enables Citrix Gateway support. 3. One of the new features of NFuse Classic 1.71 is that it allows you to specify specific address translation settings per IP network. If you would like to set a specific IP network to utilize a different address translation than the default then you will need to enter the IP network number in the Client address prefix text box select the address translation Option radio button and click Add 
4. Click the Save button to save the above changes. 5. Click Server-Side Firewall in the panel on the left of the page. 6. If you will be using translated addresses then you will need to configure the MetaFrame server address translation map section of the page. 
7. Enter the IP address of the MetaFrame server in the server address text box. 8. Enter the TCP port number that the MetaFrame server is listening on in the server port text box. 9. Enter the public IP address that translates to the MetaFrame server address in the translated address text box. 10. Enter the TCP port number that the public address is listening on in the translated port text box 11. Click Add. You have the ability to add multiple translations and then select the priority order. 12. Click Save. The Overview page appears. Click the Apply Changes link. The Apply Changes page appears click the Apply Changes button for the changes to take place. 13. If you will be using Citrix Secure Gateway (CSG) you will need to click the Server-Side Firewall link and scroll down to the Secure Gateway server section of the page. 
14. Enter the FQDN address of the server running the CSG component in the Address (FQDN) text box. 15. Enter the port the CSG component is listening on in the Port text box. 16. If you have a firewall configured to perform network address translation between the CSG box and the MetaFrame server then you will need to check the Use alternate addresses of MetaFrame servers checkbox. An Alternate Address is required to be added to the Citrix Server if NAT is being used on the firewall between the Metaframe Server and the CSG/NFuse server. The IP Address that is assigned on the external interface and that is NATd to the IP Address of the Metaframe Server on the Local LAN, must be added to the Metaframe Server, from the command prompt by typing:- C:\altaddr /set [alternate address eg. 192.168.5.1] To delete the Alternate Address use C:\altaddr /delete 17. In the Secure Ticket Authorities URL text box enter the NETBIOS name of the server running the STA component in place of <server> and click the Add button. 18. Repeat step 10 in order to add STA server for high availibility. If you will be using multiple STAs then I recommend to check the Use the Secure Ticket Authority list for loal balancing checkbox to enable round robin load balancing. 19. Click Save. The Overview page appears. Click the Apply Changes link. The Apply Changes page appears click the Apply Changes button for the changes to take place.
If the Client-Side Firewall If you are using a SOCKS proxy server at the client side of your NFuse Classic installation, you can configure whether clients must communicate with the MetaFrame server via the proxy server or not. From the Client-side firewall settings page, you can: Specify default SOCKS proxy rules for clients, or specify that proxy behavior be controlled by the ICA Client. Configure exceptions to the default behavior by associating client addresses or partial addresses with a particular SOCKS proxy server address. 
Default Settings If you are using a SOCKS proxy server at the client side of your NFuse Classic installation, you can set default SOCKS proxy rules for clients. Alternatively, you can specify that the proxy behavior be controlled by the ICA Clients. The following defines how to configure default SOCKS proxy settings 
1. Click Client-Side Firewall in the panel on the left of the page. 2. Under Default setting set Use SOCKS proxy to 3. In the Use SOCKS proxy section of the default setting sections of the page select one either yes or no. If you select Yes then you will maunally configure the client to use a set Proxy server. I dont recommend this setting. I recommend selecting no and having the ICA Client configure proxy settings automatically. q Enter the address of the SOCKS proxy server, as the ICA Client sees it, in the Proxy address field. This can be an IP address or DNS name. q In the Proxy port field, type in the port number of the SOCKS proxy server. By default, the port number is 1080. If you select No then the local ICA Client will use the client proxy settings defined in the local browser. (Internet Explorer and or Netscape Navigator) 4. Click Save. The Overview page appears. Click the Apply Changes link. The Apply Changes page appears click the Apply Changes button for the changes to take place.
Specific SOCKS proxy settings The following details how to control SOCKS proxy behavior via ICA Client proxy settings. 
1. Click Client-Side Firewall in the panel on the left of the page. 2. Under Specific SOCKS proxy settings, enter the client address in the Client address prefix field. You can enter the IP address of the client or the partial address of the client subnet. Note: If Web browsers connect to NFuse Classic through a proxy server or firewall that hides the client's IP address, the Client address prefix must specify the client address, as NFuse Classic sees it. For example, if a web browser connects through a SOCKS proxy, specify the external address of the SOCKS proxy in the Client address prefix. This does not apply to Program Neighborhood Agent users. 3. Enter the address of the SOCKS proxy server in the Proxy address field. You can specify an IP address or a DNS name. 4. If necessary, specify the port number of the SOCKS proxy server in the Proxy port field. By default the port number is 1080. 5. Click Add. The mapping is displayed in the Mapping list. You can control the order in which multiple mappings are applied. Highlight a mapping and use the Up and Down buttons to place the mappings in order of priority. 6. Click Save. The Overview page appears. Click the Apply Changes link. The Apply Changes page appears click the Apply Changes button for the changes to take place.
In the ICA Client Deployment section of the NFuse Classic administration tool you have the ability to define if and how the ICA Client will be deployed, if the application will be an embedded application and what client the end-user will use (local ICA Client or Java Client). 
Client Download Setting In this section, you can configure how NFuse Classic will deploy the ICA Clients. You have three options: one to deploy by displaying a link under the NFuse Classic Message Center and two to try to automatically deploy the ICA Clients to Win32 devices or three, to do nothing. You can configure NFuse Classic to automatically deploy the ICA Win32 Web Client to your Windows users. This installs the ICA Web Client (ica32t.exe) which is smaller and easier to download, so it may be more suitable for users on low bandwidth connections. The following defines how to configure automatic client download settings. 
1. Click ICA Client Deployment in the panel on the left of the page. 2. Under Client download setting, select one of the following options: Auto - This is the default setting. On Windows platforms, if the user does not have an appropriate ICA Client installed, a link to the recommended ICA Client is displayed. On other platforms, the installation caption is always shown. Yes A link to the recommended ICA Client is always displayed, on all platforms. No A link to the recommended ICA Client is never displayed. Note: If a user clicks on the link to the recommended ICA Client, but a client already has the latest ICA client installed then nothing happens. To use Web-based ICA Client installation, you must ensure your Web server contains the appropriate ICA Client installation files. 3. Click the Enable automatic download of ICA Win32 Web Client check box if you want to allow NFuse Classic to analyze the users client device and Web browser and if the user is on a Windows platform and he or she does not have an ICA Client, or their current client is not up to date, NFuse Classic attempts to automatically install the ICA Win32 Web Client on the users client device. Specify the version of the ICA Win32 Web Client to deployby default NFuse Classic 1.71 configures this setting to the 6,30,1000 version. To stay current with latest and greatest ICA Client I recommend changing this setting to 6,31,1051 and then copy the newly downloaded ICA Client(s) to the \\wwwroot\citrix\icaweb\en\ica32\ directory. 
Note: the commas, rather than decimal points, are used as separators. 4. Click Save. The Overview page appears. Click the Apply Changes link. The Apply Changes page appears click the Apply Changes button for the changes to take place.
Embedded Applications In this section, you can control whether applications run as seamless sessions or are embedded into HTML pages using the ICA Client deployment page. If you choose to embed applications, you can specify the ICA Client that is used to launch the embedded application. You can deploy the ICA Win32 Client or the ICA Java Client, depending on the users platform, or you can use the ICA Java Client for all users. Alternatively, you can enable users to decide how their applications are launched using their Settings page. The following defines how to configure how applications are launched and embedded. 1. Click ICA Client Deployment in the panel on the left of the page. 2. Under Launch application as embedded applications (within a Web browser window), select one of the following options: 
No To launch applications in a seamlessly on the local desktop, select No in the Embedded applications section. Yes - To embed applications into Web pages, select Yes in the Embedded applications section. Specify the ICA Client that will be used to launch the embedded application: q Auto Choose Auto to automatically detect the users client device and Web browser and deploy the appropriate ICA Client. If a Windows platform is detected, the ICA Win32 Web Client or Netscape plug-in is deployed, depending on the users Web browser. NFuse Classic deploys the Java Client if it detects that the user is not on a Windows platform, or it is unable to detect the users client device and Web browser. q Java Client - Choose Java Client to force deployment of the ICA Java Client, regardless of the users platform. The ICA Java Client can be configured to be a small download, so this option is best for users on low bandwidth connections.
3. If you would like to give the end-users the ability to decide how their applications are launched then select the User decides radio button in the Embedded applications section. When you enable this option, users can choose how their applications are launched in their Settings page. You can also specify what happens by default if a user does not decide how their applications are launched, as follows: 
To embed applications into Web pages by default, select the By default launch applications as embedded applications radio button. Specify the ICA Client that will be used to launch the embedded application. To launch applications in a separate window on the local desktop by default, deselect the By default launch applications as embedded applications radio button. q Auto - Select Auto to automatically detect the users client device and Web browser and deploy the appropriate ICA Client q Java Client - Select Java Client to force deployment of the ICA Java Client, regardless of the users platform. 4. You can configure the components included in the deployment of the ICA Java Client in NFuse Classic. You can configure the ICA Java Client to be a small download (as small as 300K) by removing unwanted functionality. For example, if you want to reduce the size of the download for users on low bandwidth connections, you can configure NFuse Classic to deploy only a minimum set of components. Alternatively, you can enable your users to control which components are required. To customize ICA Java Client deployment, select the Java Client packages you want to include in the deployment. To allow users to control which Java Client packages are enabled from their Settings page, select the Allow user to choose packages check box. 
The options that you can set are: Audio - Enables applications running on the MetaFrame server to play sounds through a sound device installed on the client computer. You can control the amount of bandwidth used by the client audio mapping on the server. Clipboard - Enables users to copy text and graphics between server-based applications and applications running locally on the client device. Legacy server support - Allows users to connect to MetaFrame for Windows servers prior to MetaFrame XP (such as MetaFrame 1.8 and MetaFrame 1.0) and prior to Feature Release 1 of MetaFrame for UNIX Operating Systems. Local text echo - Accelerates the display of the input text on the client device. SSL/TLS - Secures communication using Secure Sockets Layer (SSL) and TLS (Transport Layer Security). SSL/TLS provides server authentication, encryption of the data stream, and message integrity checks. Important: If you will be using the ICA Java client to traverse Citrix Secure Gateway or the Citrix SSL Relay Service, NFuse Classic 1.71 must be configured to include the SSL/TLS Java client package. Encryption - Provides strong encryption to increase the privacy of ICA connections. Client drive mapping - Enables users to access their local drives from within an ICA session. When a user connects to the MetaFrame server, their client drives are automatically mounted, such as floppy disks, network drives and CD-ROM drives. Users can access their locally stored files, work with them during their ICA sessions, and save them again on a local drive or on a drive on the MetaFrame server. In order to enable this setting your users must also configure client drive mapping in the ICA Java Client Settings dialog box. COM port mapping - Allows devices attached to the client computers COM ports to be used during an ICA session on the MetaFrame server. These mappings can be used by applications in the same way as other network mappings. This feature requires third party software to be installed on the client device. Printer mapping - Enables users to print to their local or network printers from within an ICA session. Configuration UI - Enables the ICA Java Client Settings dialog. This dialog can be used by users to configure the ICA Java Client. 5. Click Save. The Overview page appears. Click the Apply Changes link. The Apply Changes page appears click the Apply Changes button for the changes to take place.
You can specify the settings that users have access to adjust in their Settings page, using the ICA Customization page. You can specify whether users can adjust the: Window size of ICA sessions Color depth of ICA sessions Audio quality of ICA sessions The following defines how depicted what features the end-users will have the option to configure. 
1. Click ICA Customization in the panel on the left of the page. 2. To control what ICA settings that end-users have access too select any of the following: Window Size: Allows users to adjust the window size. By default, users can adjust the window size of ICA sessions. If you prevent users from adjusting a setting, the setting is not displayed in the Settings page in the users presentation and the settings specified for the published application in the Citrix Management Console are used. Window Color: Allows users to adjust the color depth. Audio Quality: Allows users to adjust the audio quality. 3. Click Save. The Overview page appears. Click the Apply Changes link. The Apply Changes page appears click the Apply Changes button for the changes to take place. When users configure settings such as window size, their settings are stored as cookies on their client device. These settings are therefore remembered for all future applications launched via NFuse Classic. Depending on the operating system and Web browser used, these cookies may be specific to each user or all users will have the same settings. Customized settings made by guest users (logged in using the Guest User option) are not saved to the client device.
NFuse 1.61 and 1.71 has the ability to be branded with custom text and graphics to customize the out of the box web site. The following sections describe how to make for settle changes that will gave far in creating a better, much richer end-user experience. The following is an example of a custom NFuse Classic 1.71 login page. 
The following is an example of a custom NFuse Classic 1.71 application list page. 
The ability to customize the text found on the NFuse Classic web pages are configured through a single file, the NFUSE.TXT file located in the default NFuse directory. (C:\program files\Citrix\NFuse\) In order to change the verbiage of the NFuse screens all you need to do is change the text behind certain sections. i.e., LoginTitle, Welcome, PleaseLogin. After making changes to the nfuse.txt file you will need to restart the IIS services. 1. Click Start click Run type: iisreset and click OK. 2. Verify that all the nesacary services started. IMPORTANT! Be VERY careful when editing this file. For disaster recovery purposes, make a copy of the NFuse.txt file before editing. The following is the default nfuse.txt file. 
Customizing graphics is a little harder than text as you really dont have a lot to work worth unless you customize the .asp code of the default NFuse 1.71 web site, however we do have a one option. In the \Citrix\NFuse17\media folder found under your web root of the NFuse Web Server, you will find all the graphics found on the default site. The two key files are as follows: citrix.jpg This graphic is the Citrix logo found on the button right hand side of the default web site. 
nfusehead.jpg This graphic is the Citrix NFuse Classic banner found over the login box and list of enumerated applications. 
Important! Be very care when editing the above graphics or any graphic found in the media folder. If you change the size of it might adversely affect the NFuse Classic 1.71 web site. You will want to make a backup copy of any file you will edit for disaster recovery purposes. 1. In order to change the graphics on the default NFuse Classic web site just edit the graphic file located in the \Citrix\NFuse17\media folder found under your web root of the NFuse Web Server with you favorite graphic editor. Be very careful not to change the size of the graphic. 
2. Click Start click Run type: iisreset and click OK. 3. Verify all necasary secives started sucessfully.
In case you experience problem with NFuse then the following details how to repair NFuse Classic 1.71 1. Click Start click Settings click Control Panel click the Add/Remove Programs applet. 2. Highlight Citrix NFuse Classic from the list of installed programs and click the Support information link. 
3. Insert the Citrix MetaFrame XP with Feature Release 2 Component CD in the CDROM and click repair. 
Setup reinstalls NFuse Classic 1.71 while keeping all the previous custom settings. If you need to rollback to the default settings then you will need to uninstall NFuse Classic 1.71 and delete the default NFuse folder. (c:\Program Files\Citrix\NFuse) |