Thank you for your feedback

Markvision Enterprise 2.1 New Features (October 2014)

Document ID:HOT136

Usergroup :External
01/22/14 Properties  


New Features and Release Notes.


What's new

MVE 2.1 

  • Additional products supported
  • Encryption and encryption removal capabilities pertaining to system credentials
  • Administrator usernames/password entry during Firebird and MVE during installation
  • Ability to prevent the redisovery of devices. A configured variable settings data file containing the device's hostname and Bonjour (zero configuration) name provides this capability.
  • Security management improvements

Security vulnerabilities addressed:


  • Firebired database built-in accounts
  • Legacy Markvision Professional import capability
  • Ship-with administrator accounts

Additional fixes:

  • Serial numbers not displayed in Data Export CSV file
  • Tray 3 was prevented from being selected as a fax paper source
  • Menu Setting's Lock Pin value was not being saved



Release History

MVE 2.0

Policies have been replaced by configurations; a term that more closely resembles their actual function.

These new configurations also provide more functionality, such as: 

  • App application management. ( Applications and application license dissemination.)
  • Licensed option support.
  • Apps can now be deleted from devices if the solution resides within the MV E library.
  • Configurations can be imported and exported from one MV E installation to another, or exported and imported within the same MV E installation to obtain a copy of a Configuration.


Migrating from Policies to Configurations

Issue or behavior... What does this mean...
Only Policies that are assigned to devices will be migrated (during the upgrade process) to Configurations.

Merged policy settings can cause errors or failures.

To prevent configuration settings from mixing and conflicting with each other, only active and assigned policies get migrated or carried over to MVE 2.0.

Policies will not be migrated into Configurations if more than one Variable Settings Data file is used.

You will have to combine all tokens into one Variable Settings Data file before upgrading to MVE 2.0.

Scheduled enforcement and conformance actions will not be migrated.

Scheduled enforcement and conformance actions will not be migrated. You will have to reconfigure or reschedule these actions.



Some known issues

  • Devices that utilize a cloned configuration will show out of conformance if you install any apps that force any changes to Function Access Controls. Since the original FAC settings are part of original Configuration clone, you must install the solution(s) before attempting to clone Configurations with MVE 2.1.
  • Using firmware policies with the MS 610
  • Certificates used for SISAL will need to be reimported when upgrading from 1.8.x to 1.9.x
  • Upgrading from version 1.5.x to 1.6.x
  • Error#:2032 when accessing MVE client

Possible suggestions to alleviate some of these issues can be found in MVE 2.1 Full Release Notes 

 Additional resources



Please enter the email address you would like to send a copy of this page to.