How to Setup Remote Sync with Mediahub

Both server and Mediahub must be running at least Platform v5.7.1.6. Units must have an outside internet connection on both.

1. Log into both the Server and Mediahub's Windows Operating System.

2. Ensure that the Remote Sync is installed on the Server as this is manually deployed.  Please see article here to do so.

3. Have both Remote sync windows open on both units.

mediahub sync

4. Navigate to the Actions-->Advanced and copy the Device ID of each unit.  Take note of each one as they are unique to each device.


5. Copy the Main Server's Device ID.

6. On the Mediahub, click on the 'Add Remote Device' and Paste the Device IP and give that Device a name.  Something like Main Platform Server may help differentiate.  Example below is our Sales Demo.

7. Click on the Sharing tab and Allow Introducer but do not allow Auto-Accept.

8. Give the units about 1-2 minutes.  If there are no prompts appearing, you may restart their services to initialize.

9. The main server should prompt to add device.  Click 'Add Device'.

10. The Device ID should now be populated.  The Device Name will be named if the server has one already but it can be renamed to anything like 'Mediahub01' or something similar to keep track.  Click 'Save' when ready.

11. On the main server to share out a folder, click on 'Add Folder'.  

Keep this window open as we will return to this shortly.

12. Open up a File Explorer Window and Navigate to your StorageGroup and locate the Platform Space you wish to sync.

13. Hold 'Shift' and then right-click on the Platform Space you wish to sync and click on 'Copy Path'.

14. Return to the Sync Window and Paste into the Folder Path.  Be sure to remove the quotations around the path.  Be precise of the name as it is character specific and do not cutr the path shorter or to the root of the path as it will sync all items in the path.  If the name is exact, the folder name will be created just like as it it were on the main platform.

15. Add the Folder name.  It is easiest to keep it the same as the original so there is no confusion down the line. 

16. Go to the Sharing tab and select the servers that you wish to share this out to.  If you have multiple Mediahubs, select the mediahubs that they will sync to. 

17. Go to the Ignore Patterns tab and enter in the following exactly as seen:



It is important that these exact ignore patterns are added as they should not be syncing to either device.  DS_Store files are mac generated files and .pmxignore files hold the permissions information for each platform and will change permissions if they sync.

Save once ready.

18. Wait 1-2 minutes again.  If the servers are not syncing, restart the service.

19. The Mediahub UI should prompt.  Click 'Add'

20. Alter the Folder Path so it's exactly how it appeared on the original platform.  The Drive Letter may differ however the Mediahubs are generally D:\

Note that this example is a different drive letter for this server.

21. Go to Sharing tab and ensure that the source server is checkmarked.  If there are multiple mediahubs that will be syncing the same material of this folder, you may checkmark those as well.  The changes of a file will sync to the others.  When a new server is syncing the material, it will pull the material from the fastest connection.

22. Go to the Ignore Patterns tab and paste the same rules as previous and save when ready.



23. Restart service if needed.

24. Files should be syncing to Mediahub

25. Once files are synced, navigate to the Platform UI.

26. Go to the Settings Screen and 'Reset Cache'.

27. Go back to the Platform Space Screen and once the Space repopulate, use the 'Add Existing Platform Space' function.

28. Select the newly synced space.  Mediahubs will have No size cap on by default.  Add when ready.  A prompt about space larger than the storage will prompt.  You may confirm and go past the screen.

29. The Space is should add to the Platform UI and be ready to mount on the workstation.  If the mount does not work, you may need to reset the permissions if they have not attained admin permissions.  Please see article here.