This version of the software is currently available only to customers in the Controlled Availability (CA) program.

Windows UNC file paths

In Windows environments, you can use the universal naming convention (UNC) to simplify the connectivity to shared file systems. An example UNC file path is as follows:

\\MACHINE_NAME\SHARE

See https://www.lifewire.com/unc-universal-naming-convention-818230 for details of the UNC format.

Remote network-mounted file systems are rarely the most efficient option for data migration. However, they can provide a convenient solution where data migration performance is not the primary consideration.

UNCFilePath.png

When using UNC file paths to connect to a remote file system, the user running the Windows Service must have permission to access the file system. This applies to the BMC Helix Data Manager Engine Service.

Unless the remote file system is publicly available for read/write operations and Windows authentication is not in place, you must configure the Windows service to run as a particular user. See the example illustrated below:

Properties.png


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*