360 Sync Requirements

We often get asked, “What are the minimum requirements for setting up 360 Sync?” This document will walk you through the best practices for your 360 Sync Setup.

Suggested workflow
360 Sync can be installed on any computer with Windows – whether it's a desktop, server or virtual machine. We suggest installing 360 Sync on a Virtual Machine (VM) because it will not affect the processing speed of your personal computer or server when transferring files between data sources.

We suggest you setup a VM with the computer requirements below:

Computer requirements

• Windows Version: Windows Server 2012 or later (or recent version of Windows)
  Suggested: Windows 10 or later

• Processor: Minimum: 1.4 GHz 64-bit Processor
  Suggested: 2 GHz or faster

• RAM: Minimum: 1 GB
  Suggested: 4 GB or greater

• Disk Space: Minimum: 250 MB for application plus requirements for .NET installation and enough storage for the files you intend to synchronize.
  Suggested: 40 GB or greater

Installation notes

• A computer with Windows Server 2012 or later. (You don’t need to install 360 Sync on a server.)

• Install on any computer, as long as the version of Windows is more recent than 2012.

• Install .NET Framework v 4.7 and a C++ redistributable. Download using the links below:

  • If you don’t have .NET Framework of 4.7 or later, try installing it from here:  https://dotnet.microsoft.com/download/dotnet-framework/net472

  • Download this C++ redistributable: https://aka.ms/vs/15/release/vc_redist.x64.exe

• Install 360 Sync. Download the most recent version of 360 Sync by following this link: http://evolvemep.com/resources/downloads/360-sync. Make sure to have your Enterprise License code or Trial License code available. Navigate to https://foresite.evolvemep.com to find your license key.

Internet Explorer Internet Options

1. Open Microsoft Internet Explorer.

2. In the top right corner, click the gear and select Internet Options.

3. Select the Delete button and check all boxes.

4. Scroll to the bottom and check TLS 1.2 in the Advanced tab.

5. Finally, click the Privacy Tab and make sure that Turn on Pop-up Blocker is unchecked.

Reference the images below:

Pre-Installation & Setup

1. Download the latest version of 360 Sync from here: http://evolvemep.com/resources/downloads/360-sync

2. Get your license code from https://foresite.evolvemep.com

3. Steps to unblock the file:

   • Prior to unzipping the file, right-click on the zip file and select Properties at the bottom.

   • When the window pops up, check the Unblock button in the bottom right corner. Click Apply and OK.

   • If the Unblock button doesn’t show up, then you don’t need to do anything.

Reference the image below:

Install 360 Sync on your C: drive, as shown below:

Scheduled Tasks Requirements

1. The user will need admin + read/write/edit permissions for folders and files on the computer/server or virtual machine that 360 Sync is installed on.

2. The user will need admin or read/write/edit/run permissions for Scheduled Tasks with the Windows Task Scheduler.

3. The user will need to be a member of the Local Security Group Policy: Log on as a batch job.
   (Local Security Policy > Local Policies > User Rights Assignment > Log on as a batch job)

Reference the image below.

User Profile Requirements  

1. User needs to have Modify, Read & execute, List folder contents, Read and Write permissions for the following folders: C:\360 Sync for Windows
   
   Reference the image below:

   

   
   

2. Steps to check or modify:

   • Click on 360 Sync for Windows folder.

   • Right-click and select Properties at the bottom.

   • Click on the Security tab.

   • Choose the group or user name that you want to modify.

3. You may need to get help from your IT professional to do this.

4. The user will need read/write/modify access to any other folders on the computer or server that they want to sync.

User Group Policy Requirements

A user that is utilizing 360 Sync may need to have their IT Group Policy settings changed to allow the following:

Run Batch Jobs

1. Make sure Log on as a batch job is added to the user or the user is added to a Group Policy that can do that. Reference the image below.

2. Edit files and folders on the C: Drive.

3. Edit files and folders in the 360 Sync for Windows folder.
   
   

   

   
   

Vault Requirements

1. User will need to have Vault Professional Client 2019 installed on the computer that 360 Sync is installed.

2. User must know Server Name, Vault name, username and password.

   • Ask your Vault Admin and they can help you find this information.

3. You can only connect to Vault 2019, 2020, 2021.

   • If there is another version that you would like to connect to, please contact: forgedev@evolvemep.com

4. Suggested: Setup your files or folders to follow a Lifecycle status prior to setting up 360 Sync. This will allow you to customize which files are moved between Vault and other data sources based on the status of the file in your workflow.
   
   

360 Sync Security

While security for 360 Sync is mandated by the solution we are connecting to, keeping our clients files and data safe and secure is of utmost importance to us.

Here are some notes regarding security within 360 Sync:

• TLS 1.2 is enabled for all of our vendors.

• However, not all of our vendors support TLS 1.2 (they still use TLS 1.1).

• 360 negotiates the highest allowed version by the solution you’re connecting to, with the goal being TLS 1.2.

• All files are encrypted. We encrypt everything going to the cloud (including SharePoint). SharePoint encryption depends on SharePoint cloud hosted vs. On Premise (On Premise is subject to the individual company’s setup).

• 360 Sync doesn’t require elevated permissions to run, but it does require elevated permissions to install.

• If you’re syncing to a File Share / Azure, there must be a domain account that has appropriate permissions to access that file server.

• All usernames and passwords saved in 360 Sync are encrypted.

Encryption Info: Data never leaves the client’s firewall.

Data at Rest: AES/Rijndael symmetric encryption.

Data in Transit: Transport Layer Security (TLS) 1.2 when supported by the remote connection; Fallback to 1.1 and 1.0 may occur depending on what the remote end (Procore, Viewpoint, etc) supports.