|
|
|
Exporting and Importing an NFS XML Settings File
Technical Note 1816
Last Reviewed 13-May-2004
Applies To
Reflection NFS Client version 11.0 or higher
Summary
Technical Note 1816
Last Reviewed 13-May-2004
Applies To
Reflection NFS Client version 11.0 or higher
Summary
Reflection NFS Client settings are stored in the Windows registry. After configuring a Reflection NFS Client installation, the settings can be exported to an XML settings file that can be used to configure Reflection NFS settings on other computers. This technical note explains how to create, export and import an NFS XML settings file.
Customizing Reflection NFS Client
To customize Reflection NFS Client settings, follow the steps below to install and configure an instance of Reflection NFS Client.
- Install Reflection NFS Client on one computer.
- Restart the computer and logon to Windows using an account that is a member of the Window's Administrators group.
- Open the Reflection NFS Utility from the Reflection > Utilities menu.
- Click View > Settings.
- In the Reflection NFS Client Properties dialog box, configure the NFS Client as you want it to be when you deploy it to your end users.
- Click OK to save the Reflection NFS Client Properties modifications.
Exporting Settings to an XML file
Exported settings are saved to a file called Wrqnfs.xml, which is saved to your Windows My Documents folder.
- On the computer where you have customized Reflection NFS Client, open the Reflection NFS Utility from the Reflection > Utilities menu.
- In the Reflection NFS Client Utility, click File > Export Settings to XML. The settings file is saved to \Documents and Settings\<user>\My Documents\wrqnfs.xml.
Importing the Settings File
To import the NFS settings file, copy the configured wrqnfs.xml file to the common (shared) Application Data\Reflection folder on each user's workstation. The default location is \Documents and Settings\All Users\Application Data\Reflection.
The NFS Client checks this location for a settings file each time Windows starts up. If you have added or updated the file, the NFS settings configured in the XML file are imported automatically.
Note: The imported NFS settings overwrite existing NFS Client settings.
You can manually copy the customized NFS XML settings file to the \Application Data\Reflection folder, use a third-party installation product, such as SMS, to push the file out, or use the Reflection Customization Manager to create a Reflection installation or Companion Package that contains the file.
Deploying Reflection NFS Client Using the Customization Manager
System Administrators can use the Reflection Customization Manager (called Reflection Deployment Manager in versions earlier than 12.0) to create a Reflection installation that includes the customized NFS XML settings file.
Note: The Customization Manager enables administrators to include a customized NFS XML settings file as part of a Reflection NFS Client installation package. No other customization or profiling options are available for Reflection NFS Client.
For information about preparing to deploy Reflection using Reflection Customization Manager, see the Preparing to Deploy Reflection guide at http://www.attachmate.com/docs/reflection/14.0/deploy.pdf. Details about attaching settings files to a deployment can be found in Phase 2, under "Add Files to the Installation" and under "Make Additional Files Available for Your Users with Companion Packages." For ease of updating, we recommend that you use a companion package to make these files available to your users.
Add Files to the Installation: Using this feature, when users run the custom installation, the NFS Client is automatically configured using the settings in the XML file. If you want the file to remain after upgrading or uninstalling the product, select the "Make this file permanent" check box in the Add File to Installation dialog box.
Make Additional Files Available for Your Users with Companion Packages: A companion package is a standalone MSI file that is independent of any Reflection installer package. It is highly recommended that you create a companion package if you wish to retain customizations across one or more upgrades of Reflection. By putting added files, such as settings files, into a companion package instead of adding them to the Reflection product installation, you can later remove or update the settings files without removing or reinstalling Reflection.
