CAST Console - How to move an AIP Console deployment from the default location to a custom location

This page provides information about moving an AIP Console deployment from the default location (on the C: drive) to a custom location

For more information, refer to:



Platform or <Sub Platform Version>


1.16 (tick)
1.15 (tick)



The following steps were needed to move AIP Console deploy and other folders from a default C: installation drive to a custom D: drive location:

1.'Logically' remove all applications from the Console using the Console CLI with the following syntax. See here for more on the CLI documentation:  Delete an Application via CLI 

deleteApplication.bat -apiHost "http://host:<port>" -appName "<application>" -keepData -token "<token>"

2. Update file to point to D .  See here for related documentation:   Configure AIP Node storage folder locations - optional

# =============================
# Storage folders location
# -----------------------------

3. Update castGlobalSettings.ini . See here for related documentation:   Appendix - Modifying default CAST data storage locations  

; Set the default deploy folder location

4. Bring up each application in CMS and Verify that the Platform Settings (in Windows->settings) look good and all point to Drive D

5. In CMS, start DMT and verify if the DMT packages (upload folder) point to C Drive. If they do, then do the following. See the following for related documentation:   Validate and Accept the Delivery 
- Reject package and update to D
- Set as 'Current Version' and update the Deploy paths to Drive D

6. In PGAdmin: Update the 'deploypath' in the table CMS_PortF_application on the management schema (no results returned by this query):

set search_path= xxx_mngt;
Update CMS_PortF_application set deploypath='D:\CAST_ANALYSIS\deploy/<application>';

7. Import Application into AIP console using the CLI below . See here for related documentation: Import an Application managed with CAST Management Studio into AIP Console

importApplication.bat -apiHost "http://<host>:<port>" -appName "<application>" -mngtSchemaName "xxx_mngt" -token "<token>"

8. In Console: make sure that all analysis units are present and all point to drive D. Make sure that all configuration files are located on drive D such as Dynamic Link filter files.


 Ticket # 23558





Have more questions? Submit a request


Powered by Zendesk