The Actual Installation

1. Make the tcms folder

  • On MacOS make a folder at ~/tcms/
  • On Windows make a folder at c://tcms/

2. Make a tcms_data folder in the tcms folder

  • On MacOS you should now have ~/tcms/tcms_data/
  • On Windows you should now have c://tcms/tcms_data/

3. Make an ActiveVersion folder in the tcms_data folder

Into the /tcms_data folder created in step one add the ActiveVersion folder. You should now have:

  • On MacOS you should now have: ~/tcms/tcms_data/ActiveVersion
  • On Windows you should now have: c://tcms/tcms_data/ActiveVersion

3. Load the two client folders into ActiveVersion

Copy the client's two folders (resources and Startup Scripts) into the ActiveVersion folder from Step 2. 

The two folders are in the release folder. You can copy this from your file server's existing installation or you can request the current client by requesting it from a support ticket from

4. Copy your site's servers.jsx file to the tcms_data folder

Unique to each site is a servers.jsx file. This is generally a set once and forget type of file. Copy that file from your servers' tcms_data folder to the tcms_data folder created above on the local computer. The full path would now be:

  • MacOS: ~/tcms/tcms_data/servers.jsx
  • Windows: c://tcms/tcms_data/servers.jsx

5. Copy your Add-ons folder from the file server to the local tcms_data folder

Also unique to each site is a folder of customized scripts and settings files that automate folios and may provide output naming options. The proper path for this folder that you will copy with its contents is:

  • MacOS: ~/tcms/tcms_data/Add-ons/
  • Windows: c://tcms/tcms_data/Add-ons/

6. Create the Alias or Shortcut for Adobe InDesign and/or Adobe InCopy

Adobe InDesign, or if you use Adobe InCopy it too, needs to know where the ActiveVersion folder is. Make a MacOS Alias or a Windows Shortcut of that folder. Place that Alias or Shortcut in either of the Scripts folders for Adobe InDesign and/or Adobe InCopy. That is outlined in a downloadable PDF here. But where it talks about the ActiveVersion on the server, you are going to use the ActiveVersion folder created above. 

File Server or Local Storage

There are two main ways of working remotely:

  • Using your existing file server
  • Using Local Storage

You will need to decide what you are doing before going any further. The storage needs to be configured before testing the local installation.

If you are using your existing file server then you can share pages with users in the main office / design center / etc. But using your existing file server can be very painful if you network bandwidth via VPN isn't sufficient. 

If you are using local storage, all your pages will be local to you. They can't be shared other than in PDF form. And you would traditionally not have access to any of the advertisements. Our Distributed Production product (due late 2021 or early 2022) will support sharing of local documents. 

If you are using your existing file server:

1. Check the browser interface at Desktop > Settings > InDesign > Path configuration

2. That dialog has a Windows and a MacOS tab. Click the one for your OS. 

3. The first option in that dialog is Windows Base Path: or MacOS Base Path:. You MUST be able to reach that location on this local workation. If that means you need VPN, then connect to VPN. Then navigate to that path.

  • If you are a MacOS user that usually means using the Finder's Go > Connect to Server... and logging in and while there mounting the tcms_indesign and tcms_purged shares.
  • If you are a Windows user you can use Windows Explorer and navigate to that. If you don't have access to the DNS, you might need to modify your Windows Host file to spoof the DNS name. If you need help with that we can provide some details. Send a support request to your local IT department or file a support ticket at

4. You will also need to check the Advertising Paths listed on those same Windows and MacOS tabs. They too must be reachable using similar processes as in step 3. 

If you are using local storage:

1. While it could be that the above will point to the local drive, it is exceptionally rare. So you will likely need a fileServerDetails.jsx file added to the root of the tcms_data folder. We can provide such a file, or there is one linked here. If you need one, file a support ticket at

2. Once you have the file it would be installed here:

  • MacOS: ~/tcms/tcms_data/fileServerDetails.jsx
  • Windows: c://tcms/tcms_data/fileServerDetails.jsx

3. Add the Adobe InDesign unique files to the Local Storage. There are host of configuration files, templates, snippets, and other things that will need to be copied to the local machine. This amounts to most of what is in the file server's tcms_indesign share. You can safely copy all of its contents to a folder you will make at:

  • MacOS: ~/tcms/tcms_indesign/
  • Windows: c://tcms/tcms_indesign/

4. Some sites have a series of optional Adobe PDF files in the tcms_data/General Documents share. They can be copied to the local storage at:

  • MacOS: ~/tcms/tcms_data/General_Documents/
  • Windows: c://tcms/tcms_data/General_Documents/

Launch and Log In

Now that you have the client installed and are configured for document storage you are ready to test the launching of the client. Launch Adobe InDesign and/or Adobe InCopy. You should get prompted to log in. Click the correct radio button driven by the options in the servers.jsx file, enter the user's e-mail address and password (or optional login parameters) and click the Log In button.