Move Riva to a Different Folder on the same Windows System

If required, Riva can be moved to a different folder on the same Windows system. Most moves are required to satisfy one of two requirements:

• The system drive (C:\) that Riva is installed on is running out of disk space. Moving Riva to a different volume will free disk space.
• Riva is being run from a user's personal desktop or other non-system folder that is causing UAC and file/folder permissions errors.

Procedure to Move Riva Folders

For this procedure, refer to the following terms:

• Current parent folder refers to the Windows folder where Riva is currently installed.

• New parent folder refers to the Windows folder where the Riva folder structure will be moved to.

The proper procedure to move Riva to a different Windows system is:

1. Determine the current parent folder holding the Riva server files.
2. Stop the Riva sync service.
3. Move the Riva folders and files to the new parent folder.
4. Reinstall the Riva sync service.
5. Reset desktop shortcuts for Riva.

For the purposes of this article, the move discussed in this article includes moving Riva from a user's desktop to the recommended default "Program Files" system folder.

Step 1: Determine the current parent folder holding the Riva server files

To determine the source parent folder currently containing the Riva folder structure:

1. Log on to Windows using the user normally used to run the Riva Manager application.

2. Start the Riva Manager application.

3. In the top left corner, select the Riva logo.

4. In the About Riva window, in the top right corner, double-click the Riva version number.

   Result: Windows Explorer displays the contents of the Riva folder where Riva is installed. The parent folder above the Riva folder is the source parent folder, for example, C:\Documents and Settings\<Username>\Desktop\riva-latest\Riva .

5. Start the Windows Services applet (Start > Run > services.msc).

6. Start the properties for the Omni Riva (Sync Service). (In older versions of Riva, the service was called Omni Riva CRM Agent (for Exchange).) Check the path for the service. It should match the path determined at step 4.

7. Verify which user the service logon uses.

Step 2: Stop the Riva sync service

• Use the Windows services applet (services.msc) to stop and disable the Riva sync service.
  
  OR

• Use the Riva Service Monitor application to stop the service.

Step 3: Move the Riva folders and files to the new parent folder

1. In Windows Explorer, move the Riva folder to the new location, for example, D:\Riva.

2. Right-click the new folder, for example D:\Riva, and select Properties.

3. On the Security tab, select Advanced.

4. Ensure that the local Administrators group has Full Control permissions assigned to This folder, subfolders and files.

5. Ensure that this check box is selected: Allow inheritable permissions from the parent to propagate to the object and child objects.

6. Select OK twice.

Step 4: Reinstall the Riva sync service

1. Edit the Riva\Application\ClientInfo.config file, and confirm the version that Riva is configured to run.

2. Open a CMD prompt window.

3. Use the CD command to navigate to the Riva\Application\<version> folder.

4. Type Omni.Riva.CrmAgentEx.exe --reinstall [Enter].

   Result: The command reinstalls the Riva sync service so that it runs from the new folder location and retains the properties previously configured, including the logon settings.

Step 5: Reset desktop shortcuts for Riva

1. Remove the existing desktop shortcuts for Riva Manager and the Riva Service Monitor applications.

2. From the new location of the Riva folder, create desktop shortcuts for the Riva Manager and Riva Service Monitor applications.

3. Use the desktop shortcut to start the Riva Manager application. Confirm that you can see the email and CRM connections and the sync policies.

4. Use the desktop shortcut to start the Riva Service Monitor application. Start the service, and confirm that you can see the users appear in the user list. Open a few user monitor activity windows, and confirm that the users are syncing correctly.