cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

The PTC Community email address has changed to community-mailer@ptc.com. Learn more.

Enable UNC paths to be used in CLI command

Enable UNC paths to be used in CLI command

I want to execute a command in the form "si createsandbox --recurse --project=<projectpath> --batch   \<machinename>\<partition>\<directory>" in which the target location is specified via a UNC path.

Latest versions of Integrity (10.8, 10.9) do not allow paths in CLI commands to be specified via UNC, former versions did. Instead newest versions require to mount the target address to the machine on which the Integrity client is executed and specify the target address via the letter the target address is mounted to. Command would be  "si createsandbox --recurse --project=<projectpath> --batch   F:<directorypath>".

I use CLI commands in scheduled tasks/batch jobs in which the executing user is not logged in. The specification of a target address via UNC code never changes, while the specification via mounting and letter depends on several factors.  In my eyes the workaround provided with 10.8/10.9 is counterproductive.

2 Comments
GauravPhadtare
14-Alexandrite

Moving this idea to "Future Consideration" as Official support for UNC paths for Windows Sandboxes is planned.

Siddharth
9-Granite
Status changed to: New Idea