Scenario

If RayVentory (RVS) 11.0 RTM was installed via its automated routine, its warehouse directory is created on the same drive as its application. 

If a different drive is desired for the warehouse, the following steps are currently required. 

WARNING  This process is ONLY for RVS 11.0 RTM (11.0.0.3661) due to the various MSI component GUIDs referenced within the registry files.  If this process should be used against a different version then its registry will need to be searched in order to gather the correct GUIDs. 

Note:  This process could also be used for RMSi 11.0 RTM (11.0.0.3661); however, it will most likely need to be modified as certain Deployment Manager items maybe missing, and all relevant OS Deployment Manager and Security Patch Manager items will need to be added. 

Preparation

1. Download & extract the attached 'Warehouse move.zip' file:   
2. Check if RVS has been installed on a x64 or x86 system. 
3. Check if the warehouse directory is called ManageSoft or Rayventory. 
4. If the new drive for the warehouse will not be 'E:', modify the relevant CMD & reg files so that they will target the required drive letter. 
5. Take note of ALL disabled scheduled tasks within the ManageSoft folder and its RemoteExecution sub-folder (RMSi may also have additional sub-folders):
      

Implementation

1. Stop the 'Deployment Manager connection agent' service. 
2. Disable ALL enabled tasks within the ManageSoft folder and its sub-folders. 
3. Detach the RVS database (default name is either ManageSoft or RayVentory).  Note:  This is ONLY required if the RVS install also installed SQL Server Express Advanced edition, and ONLY if RVS is still using this SQL environment. 
4. Move the warehouse directory to its new drive (This action will delete its existing shares).  
5. Open an administrative command window (Run as Administrator). 
6. CD into the extracted 'Warehouse move' directory. 
7. Merge the relevant reg file with the servers registry via the command window.   
8. Run the relevant CMD file via the command window. 
9. Attach the RVS database IF required (Database location = <drive letter>:\RayVentory\Repository\Database\). 
10. Enable ALL scheduled tasks that were NOT disabled beforehand. 
11. Start the 'Deployment Manager connection agent' service. 
12. Reboot the server. 

Verification

1. Open the RVS console and check that its dashboard displays its expected values. 
2. Check that the various tiles switch to their associated snapins. 
3. Navigate through each snapin to make sure that it still functions. 
4. Check that both pack and distribute actions work. 
5. Review the Application, ManageSoft and system event logs to see if any errors or warnings pertaining to the RVS environment have been recorded since the reboot.
    

 Appendix

The registry files update values within the following keys: 

• [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders]
• [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\<GUID>]
• [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\*]

The CMD files do the following: 

• Create the shares associated with the warehouse. 
• Update the physical paths associated with warehouse IIS virtual directories.