Multiple users can work on same project by sharing Asset folder on network, below steps will help you configure network folder.
- If you use network folder you have to grant full control to “System” user of all machines connecting to this network folder or as a simplest option grant full access to all users. It can be done via “Security” tab in folder options. Obviously it’s not very safe solution.
- It’s not possible to use mapping drive because of permission level. Mapping drive is available only for user created this drive and it’s not possible to grant access to “System” user. There is a specific way to created mapping drive as a “System” user, you need to write script and schedule it to run on startup using “System” user credentials. We are not sure if it even works. (see it in detail here)
- As a result our suggestion is to use directory symbolic link created via mklink command (more information about this command here: https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/mklink)
- Run command line: Win+R -> cmd -> Enter
- Execute mklink command;
- If you want to point to the destination folder on the same machine you can use /d argument
- If you want to point to the destination folder from some machine in your network you have to use /j argument (more information can be found here https://superuser.com/questions/343074/directory-junction-vs-directory-symbolic-link)
- As a result you run command mklink /j %FOLDER_ON_YOUR_MACHINE% %FOLDER_ON_REMOTE_MACHINE%. For example:
- Then you need to change Controller.config to point AssetsFolder to the path you specified in %FOLDER_ON_YOUR_MACHINE%. Obviously you need to stop Controller service before, then change config, save it and start service again, it can be done via Task Manager or Windows Service. (It is advisable to use four backslash in starting of path \\\\v-files\\ instead of two \\v-files\\ in case it is not working with \\).
For any clarification, please contact our Priority Support.