What to Expect with the V2 to V3 Migration Process

We’ve recently rolled out our updated version of the Mvix Digital Signage CMS (v3) and we’re hoping you are as excited as we are to be using this new system. 

To prepare our users for this migration from the current version (V2, XhibitSignage) to the new version (V3, CMS.Mvix.com), we have put together a checklist of items to ensure you are using our new up-to-date software.

Checklist

• The migration order is currently determined by your account number and will be handled by the Mvix Client Success Team.
• Once migrated to the V3 environment, the XhibitSignage.com URL will auto-forward you to our V3 URL: cms.mvix.com.
• Once migrated, users will be unable to utilize V2 going forward. 

What do I do with my Players?

• Your existing players will be able to transfer to V3. Additionally, they are still usable with our updated service and new device application. 
• Additionally, all players running Linux OS versions 16.04 and 18.04 are viable for this update but will need to be powered on and online for our Client Success team to install the update.
• Any players offline will be given a short period to be brought online with a notification from the CS team. Players that are unreachable will be skipped.
  • Linux OS ver 14.04 players are not valid for updating to the V3 environment and we will be providing additional instructions to manage players such as these. 
  • Our Team will be able to determine which players are valid or not, and will provide the next steps as necessary.

What will Change in my Account? 

• All media (with the exclusion of several specifics) is expected to transfer to your V3 account and will be usable to your preference. 
  • The following apps will not be transferred to V3 automatically and will have to be manually applied following the migration: 
    • Flash Files
    • Microsoft Power BI 
    • Pinterest
    • Table
    • Facebook
    • Picasa
    • Instagram
    • SocialWall
    • Stock Photos
    • Sports
    • Box Office
    • SFTP Transfer media
    • Announcements
    • Rideshare
    • Queue Management
  • MS Office, Dockets Medias, Event Listings, and Analytics also need a manual update on the V3 CMS as they will be unable to preview without a source file.
  • As a note, some minor style changes may occur in other media, including Alerts, RSS Feeds, and Weather, and should be reviewed following the migration. 
  • Expired Media in the V2 CMS will transfer to V3, but may not be visible without adjusting the Show Expired Media toggle:

• All media of these excluded types will automatically be removed from Media, Playlist, Templates, and Schedules as they are migrated from V2 to V3.  
• Other than this, the changes are largely cosmetic and will look and feel fresh. We hope you enjoy using the updated interfaces and faster load times! 

What if I Have Custom Applications?

Custom applications created by Mvix are not transferrable to v3 and must be reproduced. Signature Care clients are eligible for a discount on reproducing custom applications for migration.

Is There Anything Necessary From My End? 

On the day of the migration, we do not expect any major efforts on your end however, we may need your assistance to ensure all players are accessible over the network. It is of utmost importance that you connect your devices and keep them powered on during the migration process. We will begin the process at your scheduled time through our remote connection tool and will reach out during the migration if we need any on-site assistance with these players.

Please be certain there is the main Point of Contact on-site on the day of Migration to assist with any potential issues.

We will inform you once the migration is completed and will provide you with the next steps via this ticket.

We recommend not adding any additional content following midnight of the day of Migration, as any content not synced at Midnight will not migrate to V3.

Please also be advised that some players and content may not be able to migrate to the V3 environment. A variety of factors (including environmental) may render support for certain hardware and/or features not possible. 

Your Device Requirement Networks

The following outbound ports must be opened in order to allow access to https://cms.mvix.com:

• HTTP – TCP Port 80
• HTTP – TCP Port 8080
• HTTPS – -TCP Port 443
• WebSockets – TCP Port 5001

You will also need to make the following available for outbound connections to our remote troubleshooting tool:

Port 80, 443, or 6568 connects to the remote troubleshooting tool. For standard listening ports, the direct line connection is 7070 (TCP).

The connection should work on all players connected to the Internet. Some networks with additional security may require additional steps to receive support. Further, you may find more information about the network requirements to receive remote support by clicking here.

• Note: TCP port 6568 is not required for BrightSign and Android hardware, only for Mvix and Flex for MiniPC BYOD hardware.

Please allow access to *.ntp.ubuntu.com to ensure your time is correct. You will also need to make the following outbound port available to ensure your device’s time is correct:

• UDP Port 123 

To ensure proper and successful security updates, please allow outbound access to http://archive.ubuntu.com. This is done over:

• TCP Port 80 (HTTP)

The network should allow uninhibited traffic over ports 80 and 443. If the requirements have been met, the devices on your network should communicate with our server.

Problems, Questions, Corrections: If you have any further questions, problems, or corrections you would like to see made, please open a support ticket.