Moving user account on the same or new edit workstation

If you need to move to a new user account on the same computer or to a brand new computer the steps are the same. In the new user account, you will need to recreate you Zoom account settings to connect with the Zoom server and setup a new project store/folder with it’s own server checkout location/folder. For example, you are using a Mac account ‘sandy’ right now and need to move to a new Mac user account ‘brandy’ on the same or a new laptop.

Choose a move plan

Please choose your move plan:

  • Option1: New Checkout location: You can start a new Checkout location from scratch and are willing to checkout projects, links & proxies from the Zoom Server again. This is the easiest option and the least error prone.
  • Option 2: Preserve Checked-out files & folders: You wish to preserve or keep the same checkout location for project store on the new user account or wish to preserve all the files you have check-out at another folder on the new user account. This requires careful planning, and is more error prone.

Before the move

  • It is recommended but not required to ensure all modified files are checked-in/synced into the Zoom server repository from the old user account. To confirm, you can check the bread crumb trail of red/green dots in the Visual Asset Browser (VAB) or in your Mac Finder/Windows Explorer. Red dot means modified files exist in the folder. This is recommended but not essential as long as you have access to the old user account to copy any new or modified files later to your new user account. Note a plain copy may change the modification time stamp of the file on the new user account making them appear as modified.
  • If using the Zoom Hub to transfer large media files, please ensure all native media transfers from your External Store to Zoom have been completed. You can check this on the Zoom client hub dashboard:
  • Write down or take a screenshot of the current settings in your Z -> Settings dialog on your old user account:


    Make a note of: Server URL, Location, Server Alias. You will need these on the new user account when you setup new Zoom server setting.

Option 1: New Checkout location

Changing the Checkout location: This article assumes you will be setting up a new Checkout location for your Project Store. That means the project files, links, proxies etc will need to be checked out again from the Zoom server at the new checkout location. For example, if the old checkout location was /Users/sandy/Documents/ProjectStore, the new checkout location can be /Users/brandy/Documents/ProjectStore.

Steps:

  1. Reboot your computer and sign-in into the new user account
  2. On the new user account, open Z -> Settings from the Z menu. There shouldn’t be any new settings. The Zoom client proxy may prompt you to create a new Zoom server.
  3. Click Add and enter the Server URL, Location, Server Alias you copied or saved from the old user account:


    Make sure to select the correct location in order to sync your desktop Zoom properties correctly from the Zoom server
  4. Make sure to select the checkbox marked Default (first column) after adding the server; Also select Always Use Default checkbox below. This will ensure that the Zoom client always connects with the given server implicitly which is essential for the Hub to perform its data transfer activities.
  5. Enter a new default Server checkout location for your Project Store as you do not plan to preserve existing checkout location
  6. Restart the Zoom Client proxy from the Z menu:
    This will auto sync all the properties for your location.
  7. Now you are ready to continue with your desktop apps or plugins to connect to Zoom

Option 2: Preserve existing Checkout Location

Keeping existing Checkout Location: If you want to avoid checking out proxies and other files and reuse an existing checkout location such as a shared folder /Volume/ProjectStore or /Users/sandy/Documents/Evolphin Zoom/ProjectStore that is mounted at the same folder on the new user account, then follow the steps below. It will require familiarity with running terminal commands.

Steps:

  1. Reboot your computer and sign-in into the new user account such as Brandy
  2. Using a terminal, copy or move the old user account’s .zm/ to the new user account. For example, to copy /Users/sandy/.zm to /users/brandy/.zm, first sign-in into Brandy’s user account and then execute a copy command such as:
    sudo cp -pr /users/sandy/.zm /Users/brandy/
    sudo chown -R brandy /Users/brandy/.zm
  3. Alternatively, you can also use the mv command instead of cp to speed it up:
    sudo mv /users/sandy/.zm /Users/brandy/
    sudo chown -R brandy /Users/brandy/.zm
  4. This will ensure all your settings are copied over to the new user account $HOME/.zm with correct permissions
  5. Update the ownership of the existing Checkout location to allow new user account write access:
    sudo chown -R brandy /Volume/ProjectStore/ or
    sudo chown -R brandy /Users/sandy/Documents/Evolphin Zoom/ProjectStore
  6. Reboot your computer
  7. If the default server checkout location is the same on the new user account, then you are all set
  8. If the default server checkout needs to change, but the checked out files still need to be preserved, that would require rebasing your current checkout location. Follow this help article: rebasing your current working copies to the new user account
  9. Validate & test everything is working as expected, after that you can delete the old .zm folder such as /Users/sandy/.zm to save space

Copying Hub Data

In addition to preserving checked-out files, if you are running the AWS S3 Archive Hub, you should also copy the S3 archive hub folder from your old account to new. Please execute the steps below:

sudo cp -pr /users/sandy/Library/Application\ Support/Evolphin/ejh /Users/brandy/Library/Application\ Support/Evolphin
sudo chown -R brandy /Users/brandy/Library/Application\ Support/Evolphin/ejh

Alternatively, you can also use the mv command instead of cp to speed it up:

sudo mv /users/sandy/Library/Application\ Support/Evolphin/ejh /Users/brandy/Library/Application\ Support/Evolphin
sudo chown -R brandy /Users/brandy/Library/Application\ Support/Evolphin/ejh