Prepare the Remote Access Host Computer

The remote access host computers must be configured to display the Offline mode commands in the PowerUser client application. They should synchronize changed documents on every Offline command, but use the remote client computers’ Local Workspace for storage. And for best performance, documents should be viewed using AutoVue in a client/server deployment as described in Autovue.

If a pool of remote access host computers will be used, the Local Workspace lock ID, which normally identifies the computer where the client is run, must be set to a common value for all of the remote access host computers.

To prepare the remote access host computers for remote access:

1. If documents that include external references will be edited by remote access client computers, install the documents’ native application on the remote access host computer, which is required to resolve the external references of documents downloaded to the remote access client computers.

2. Install the Meridian client applications that will be used by the remote access client computers, the appropriate application links, and Application Integration components as described in Install the Client Components.

3. Create the following values if they do not already exist and set them.

   As described in HKEY_CURRENT_USER\Software\Cyco\AutoManager Meridian\CurrentVersion\Client\Settings

   • OfflineMode

   • WorkSpaceLocation

   As described in HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\Client

   • RunRemoteApp

   • UseCICO

   • WorkSpaceDB

   • WorkSpaceLocation

   • WorkSpaceLockID for remote PowerUser users, CommonWorkspace on the Meridian web server for remote PowerWeb users as described in HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\WebLink\Published Locations\<ID>.

   The preceding registry values are for 64-bit Application Integration. If only the 32-bit version of Application Integration will be used on a 64-bit PC, set the same values in the Wow6432Node branch as described in HKEY_LOCAL_MACHINE\Software\Wow6432Node. AMHookTray.exe may need to be restarted for the changes to take effect.