Getting started

MVE is installed as a web server and can be accessed from a web browser on any computer on the network. MVE also uses a database to store information about the printer fleet. The following lists are the requirements for the web server, database, and user system:

Web server requirements

Processor

At least 2GHz dual core processor that uses Hyper-Threading Technology (HTT)

RAM

At least 4GB

Hard disk drive

At least 60GB


Note: MVE, Lexmark Document Distributor (LDD), and Device Deployment Utility (DDU) cannot be run on the same server.

Supported servers

Database requirements

Supported databases

User system requirements

Supported web browsers

Screen resolution

At least 1280 x 768 pixels

Supported languages

Supported printer models

1 A printer certificate update is required. In this release, the Java platform security and performance update removes support for some certificate-signing algorithms, such as MD5 and SHA1. This change prevents MVE from working with some printers. For more information, see the help information documentation.

2 SNMPv3 support is required.

3 If an advanced security password is set on the printer, then MVE cannot support the printer.

4 MVE cannot communicate with Lexmark Forms Printer 2580, 2581, 2590, and 2591 models that are in the Not Ready state. The communication works only when MVE has previously communicated with the printer in the Ready state. The printer can be in the Not Ready state when there are errors or warnings, such as empty supplies. To change the state, resolve the error or warning, and then press Ready.

Setting up the database

You can use either Firebird or Microsoft SQL Server as the back-end database. The following table can help you decide on what database to use.

 

Firebird

Microsoft SQL Server

Server installation

Must be installed on the same server as MVE.

Can be run from any server.

Communication

Locked down to only localhost.

Communicates over a static port or a dynamic named instance.

Performance

Shows performance issues with large fleets.

Shows the best performance for large fleets.

Database size

Default database sizes are 6MB for FRAMEWORK, and 1MB for MONITOR and QUARTZ. The FRAMEWORK table grows at 1KB for each printer record that is added.

Default database sizes are 20MB for FRAMEWORK, and 4.5MB for MONITOR and QUARTZ. The FRAMEWORK table grows at 1KB for each printer record that is added.

Configuration

Configured automatically during installation.

Requires preinstallation setup.


If you are using Firebird, then the MVE installer installs and configures Firebird with no other configuration required.

If you are using Microsoft SQL Server, then before installing MVE, do the following:

Setting up a run-as user

During installation, you can specify MVE to execute either as a local system account or as a domain user account. Executing MVE as a run-as domain user account provides a more secure installation. The domain user account has limited privileges compared to a local system account.

 

Run-as domain user account

Run-as local system

Local system permissions

  • File write access to the following:

    • $MVE_INSTALL/tomcat/logs

    • $MVE_INSTALL/tomcat/temp

    • $MVE_INSTALL/tomcat/work

    • $MVE_INSTALL/apps/library

    • $MVE_INSTALL/apps/dm-mve/picture

    • $MVE_INSTALL/../mve_truststore*

    • $MVE_INSTALL/jre/lib/security/cacerts

    • $MVE_INSTALL/apps/dm-mve/WEB-INF/ldap

    • $MVE_INSTALL/apps/dm-mve/download

    Where $MVE_INSTALL is the installation directory.

  • Windows privilege: LOGON_AS_A_SERVICE

Administrator permissions

Database connection authentication

  • Windows Authentication with Microsoft SQL Server

  • SQL Authentication

SQL Authentication

Configuration

A domain user must be configured before installation.

Configured automatically during installation


If you set up MVE as a run-as domain user account, then make sure to create the user on the same domain as the MVE server.

Installing MVE

  1. Download the executable file into a path that does not contain any spaces.

  2. Run the file as an administrator, and then follow the instructions on the computer screen.

  3. Notes:

Accessing MVE

To access MVE, use the login credentials that you created during installation. You can also set up other login methods, such as LDAP, Kerberos, or other local accounts. For more information, see Setting up user access.

  1. Open a web browser, and then type https://MVE_SERVER/mve/, where MVE_SERVER is the host name or IP address of the server hosting MVE.

  2. If necessary, accept the disclaimer.

  3. Enter your credentials.

  4. Click Log In.

  5. Notes:

Changing the language

  1. Open a web browser, and then type https://MVE_SERVER/mve/, where MVE_SERVER is the host name or IP address of the server hosting MVE.

  2. If necessary, accept the disclaimer.

  3. On the upper-right corner of the page, select a language.

Changing your password

  1. Open a web browser, and then type https://MVE_SERVER/mve/, where MVE_SERVER is the host name or IP address of the server hosting MVE.

  2. If necessary, accept the disclaimer.

  3. Enter your credentials.

  4. Click Log In.

  5. On the upper-right corner of the page, click your user name, and then click Change password.

  6. Change the password.