NOTE: Incorrectly installed Microsoft Visual C++ 2017 Redistributable Package (x64) may break current mdm installation

Prior to the installation or update of mdm, Microsoft Visual C++ 2017 Redistributable Package (x64) (or newer versions) must have been successfully installed on the Win­dows system.

Download: https://aka.ms/vs/16/release/VC_redist.x64.exe

NOTE: It is possible that the specified link is no longer valid. In any case make sure that the correct version is used!

Precondition: All current Windows Update Packages must have been installed first.

Make sure that the package has been installed without warnings or error messages.

If the package has been installed unsuccessfully or incomplete, the mdm installation may fail and break existing mdm installations.

NOTE: All current Windows Update Packages must have been installed

Prior to the installation or update of mdm or Windows components, all available update packages for the Windows operating system must have been successfully installed.

Caution: It might be necessary to re-check several times that all necessary packages have been installed. Sometimes some of the packages will not be installed during the first or even second Windows Update session.

mdm Client

mdm Server

mdm CA

Supported operating system

–Windows Server 2016

–Windows Server 2012 R2

–Windows 10 (mdm client only)

–Windows 7 (mdm client only)

Hardware

–A minimum of 512 MB RAM

–500 MB free hard disk space

–Color monitor with at least 1280 x 1024 res­olution

–A minimum of 4 GB RAM

–100 GB free hard disk space

–A minimum of 512  MB RAM

–5 GB free hard disk space

Software components

–Third-party components (PostgreSQL 10.14, Apache Webserver 2.4.46, OpenJDK 11.0.9, Python 3.8.3, and OpenSSL 1.1.1g) will automatically be installed via the mdm 1.12.x Installer for Win­dows.

–Apache Web Server requires Microsoft Visual C++ 2017 Redistrib­utable Package (x64) (or newer) to be installed.

Download: https://aka.ms/vs/16/release/VC_redist.x64.exe

NOTE: It is possible that the specified link is no longer valid. In any case make sure that the correct version is used!

–mdm clients, independently run on systems other than the “server system“, require the Java platform OpenJDK 11 to be installed.

Precondition

–If not installed via mdm Installer for Windows:

OpenJDK 11 

–mdm not installed (or mdm 1.11.0 or lat­er installed).

–PostgreSQL not installed (or installed by previous mdm installations).

–Apache Web Server not installed 

–(or installed and listening to a port other than 443),

–(or installed by previous mdm instal­lations).

–Microsoft Visual C++ 2017 Redistribut­able Package (x64) (or newer) installed.

mdm Client

mdm Server

mdm CA

Operating system

–Ubuntu Desktop 18.04 LTS

–Ubuntu (Server) 18.04 LTS

Hardware

–A minimum of 512 MB RAM

–500 MB free hard disk space

–Color monitor with at least 1280 x 1024 res­olution

–A minimum of 4 GB RAM

–100 GB free hard disk space

–A minimum of 512  MB RAM

–5 GB free hard disk space

Software components

–Third-party components (PostgreSQL 10, Apache Webserver 2.4, OpenJDK 11, Python 3.8, and OpenSSL 1.1.x) will automatically be installed via the package management of Ubuntu.

Precondition

–If not installed via Ubuntu‘s pack­age managing tools:

OpenJDK 11 

–mdm not installed (or mdm 1.11.0 or lat­er installed).

–All components of previous mdm installa­tions < 1.7.0 must have been removed.

The PostgreSQL database does not support the FAT32 file system. In this case it is strongly recommended to convert the file system to NTFS by using the convert.exe com­mand before installing PostgreSQL. For more information on the convert-tool please enter help convert on the command line.

If you do not specify a license file during installation, the mdm server will start in evalua­tion mode (Evaluation License) with an allowed number of 10 devices and 2 concurrently connected clients.

Run the installation program as the Local Administrator of the Windows system. The in­stallation by another user with (only) administrator rights may lead to an error.

If you do not specify a license file during installation, the mdm server will start in evalua­tion mode (Evaluation License) with an allowed number of 10 devices and 2 concurrently connected clients. To purchase a license, visit the PHOENIX CONTACT  Webshop at phoenixcontact.net/product/2981974.

Privacy notice: Access to the mdm software repository server is logged to ensure the se­curity and stability of the service. Only anonymized data is retained for statistical analysis.

mdm-all-server

Meta package to install all mdm server components.

mdm-common

Contains basic components required to in­stall mdm.

mdm-server

Contains the server component of mdm.

Starts as systemd service.

mdm-client

Contains the client components of mdm.

Starts as systemd service.

mdm-ca

Contains the CA components of mdm (CA server).

mdm-configpull

Sets up the apache2 server to provide the mdm configuration pull feature (see “Up­load configurations to mGuard devices” on page 131).

mdm-clientdownload

Sets up the apache2 server to allow the mdm client download.

mdm-webbase

Configures apache2 for mdm and allows it to be used as firmware server (see “Man­age firmware upgrades with mdm” on page 147).

You need administrator rights to install mdm and components.

Make sure, that the correct repository has been successfully added to the file /etc/apt/sources.list. Check the integrity of the provided repository key.

If mdm 1.12.x is installed via the command line, the variable DEBIAN_FRONTEND must be used with the value readline to install the package mdm-common. This is obligatory to display and accept the Software License Terms (SLT).

Copy your mdm license file mdmlic.lic to the directory /etc/mdm/mdm-server/ (default set­ting in preferences.xml) before you install mdm.

NOTE: Backup important files and databases

Keep backup copies of the following files and databases to avoid data loss during the up­grade process of mdm:

–current mdm server and mdm CA server databases

–preferences.xml and ca-preferences.xml
These files usually contain individual parameters that are to be taken over again after the upgrade.

–mdm license file

You need the license file to use the mdm to its full extent.

NOTE: Incompatibility of PostgreSQL databases

To upgrade from an older version to mdm 1.12.x, it is necessary to make irreversible changes to the backing PostgreSQL database. Once these changes have been made, the database can no longer be accessed with an older version.

Migrating mdm installations with the provided batch files/shell scripts restores only the da­tabase(s) dumped and imported. Any other installation data (e.g. pull server certificate and config files) must be manually copied to the new installation as explained below.

The provided batch files/shell scripts will only work in case of standard mdm installations (check default database names, ports, and user names in the provided preferences.xml and ca-preferences.xml files).

mdm server (and CA server) will be stopped and restarted during the dump generation process.

Consider the General notes in Section 2.3 “Upgrade mdm installations to mdm 1.12.x” on page 22

From mdm 1.11.0 or later

To upgrade mdm version 1.11.x on supported Microsoft Windows systems, use the mdm 1.12.x Installer for Windows (see “mdm 1.12.x Installer for Windows” on page 14)

It is not necessary to uninstall mdm version 1.11.x and components.

The mdm Installer for Windows will automatically create database dumps of the current mdm installation 1.11.x.

From mdm < 1.11.0

To upgrade installed mdm version 1.5.2 or later on supported Microsoft Windows sys­tems, there are two options:

1.mdm Installer for Windows: Upgrade the current mdm installation stepwise to the next minor version, using the corresponding mdm Installer for Windows, until mdm 1.11.x is installed (e.g. from mdm 1.5.2 >> 1.6.2 >> 1.7.0 >> 1.8.0 >> 1.9.x >> 1.10.x >> 1.11.x to mdm 1.12.x) or

2.Database dumps: create, export and import database dumps of the mdm sever and CA server databases as described below:

–dump and backup the databases

–remove the complete mdm installation,

–install mdm 1.12.x via the mdm 1.12.x Installer for Windows,

–import the dumped databases.

To dump and backup the databases, proceed as follows:

A)Make database dumps of the mdm and mdm CA server database

1.Copy the required batch files to the Windows system where mdm is installed.

2.Execute (as administrator) the batch file export_mdm_server.bat .

3.Provide the path where the database dump shall be saved
(default: C:\Users\username\Documents\mdm-server.sql).

4.Provide the path to your current mdm installation directory
(default: C:\Program Files\mGuard device manager).

5.Provide the password of the database user innomms if required.

6.Press any key to close the command prompt when the database dump generation has finished.

7.(If necessary) Repeat 1–6 but execute the batch file export_mdm_ca.bat to dump the mdm CA server database (default: mdm_ca_server.sql, database user = mdm­ca).

B)Keep a backup copy of the database dumps

1.Open the directory where the database dumps have been saved.

2.Copy the database dump(s) created at (A) to a secure place (e.g. a secure backup folder at another company server).

C)(If necessary) Backup the pull server configuration

1.To backup the web server configuration file, copy the following file to a secure place:

<path to mdm installation>\apache\conf\extra\httpd-mdm.conf

–Search for the following entries (your entries may differ from the default settings of the mdm Installer given below) and write down the aliases of the pull config server:

# Verzeichnis für ATV-Profile (wie in preferences.xml eingestellt).

# Alias /atv/ /var/apache-data/atv/

# <Directory /var/apache-data/atv/>

Alias /atv/ “C:/Program Files/mGuard device manager/apache-data/atv/"

Alias /atv “C:/Program Files/mGuard device manager/apache-data/atv/"

–If you have configured a service to send the pull feedback to mdm, search for and write down the following entries (CustomLog) as well:

# Pull Config-Feedback an den mdm-Server (derzeit auskommentiert).

# CustomLog "| /bin/nc -u -i1 127.0.0.1 7514" common

<your feedback configuration>

2.To backup the certificate and private key, copy the following files to a secure place:

<path to mdm installation>\apache\conf\server.crt

<path to mdm installation>\apache\conf\server.key

D)Remove the complete mdm installation from the Windows system

1.Remove the mdm installation by using its own unistaller or Microsoft Window‘s stan­dard uninstall procedures (e.g. Control Panel\Programs\Programs and Features).

E)Install mdm 1.12.x and desired components via the mdm 1.12.x Installer for Windows.

1.Use the mdm 1.12.x Installer for Windows as described in Chapter 2.2.1.

F)Import the dumped databases (mdm server and mdm CA server)

1.Make the dumped databases available on the system where mdm 1.12.x has been installed.

2.Execute (as administrator) the batch file import_mdm_server.bat .

3.Provide the path to the database dump
(default: C:\Users\username\Documents\mdm-server.sql).

4.Provide the installation path of mdm 1.12.x 
(default: C:\Program Files\mGuard device manager).

5.Provide the password of the database user innomms if required.

6.Press any key to close the command prompt when the database import has finished.

7.(If necessary) Repeat 1–6 but execute the batch file import_mdm_ca.bat to import the dumped mdm CA server database (default: mdm_ca_server.sql, database user = mdmca).

8.mdm will restart automatically and connect to the imported databases.

G)(If necessary) Update the firmware upgrade/pull server configuration

1.Open Apache HTTP Server Monitor (included in the mdm installation) and stop the service ApacheMDM.

2.Compare the web server configuration file, with the backup file copied and stored in step (C):

<path to mdm installation>\apache\conf\extra\httpd-mdm.conf

–Compare the aliases of the pull config server. If your former settings differ from the default settings of the mdm Installer (given below), replace the default set­tings accordingly to your settings (e.g. Alias /my_company_atv/ ):

Alias /atv/ “C:/Program Files/mGuard device manager/apache-data/atv/"

Alias /atv “C:/Program Files/mGuard device manager/apache-data/atv/"

–Update the pull configuration feedback to the mdm server, if it must be config­ured:

# Pull Config-Feedback an den mdm-Server (derzeit auskommentiert).

# CustomLog "| /bin/nc -u -i1 127.0.0.1 7514" common

<your feedback configuration>

3.Copy the certificate and private key, backed up and stored in step (C) to

<path to mdm installation>\apache\conf\server.crt

<path to mdm installation>\apache\conf\server.key

4.Open Apache HTTP Server Monitor and start the service ApacheMDM.

All mdm versions

mdm versions installed on unsupported Windows systems cannot be upgraded to mdm 1.12.x.

To reuse the databases of these mdm versions on supported Windows systems, you have to:

–dump and backup the databases,

–install mdm 1.12.x via the mdm 1.12.x Installer for Windows on a supported system,

–import the dumped databases.

To dump and import the mdm server database and mdm CA server database, proceed as described above (“From mdm < 1.11.0” on page 23).

All mdm versions

To reuse the databases of mdm versions, installed on Linux systems, on supported Win­dows systems, you have to:

–dump and backup the databases,

–install mdm 1.12.x via the mdm 1.12.x Installer for Windows on a supported system,

–import the dumped databases.

Proceed as follows:

A)Make database dumps of the mdm and mdm CA server database

1.Copy the required shell script files to the Linux system where mdm is installed.

2.Execute (as sudo) the shell script export_mdm_server.sh .

3.Provide the path where the database dump shall be saved
(default: /tmp/mdm-server.sql).

4.Provide the password of the database user innomms if required.

5.(If necessary) Repeat 1–4 but execute the shell script export_mdm_ca.sh to dump the mdm CA server database (default: mdm_ca_server.sql, database user = mdm­ca).   

B)Keep a backup copy of the database dumps

1.Open the directory where the database dumps have been saved.

2.Copy the database dump(s) created at (A) to a secure place (e.g. a secure backup folder at another company server).

C)(If necessary) Backup the pull server configuration

1.To backup the web server configuration file, copy the following server configuration file to a secure place. E.g. if you are using Apache 2.x, your configuration file may be stored in: /etc/apache2/sites-available/your-server.conf .

–If your server configuration defines any aliases for the pull configuration directo­ry, write them down. They may look like:

Alias /atv/ “/var/www/mdm-pull/"

Alias /atv “/var/www/mdm-pull/"

2.To backup the certificate and private key, proceed as follows:

–Check the configuration file from step (1.) (e.g. /etc/apache2/sites-avail­able/your-server.conf) and look for the certificates used by your server. E.g. if you are using Apache 2.x, the entries may look like:

SSLCertificateFile /etc/mdm/mdm-pull-server/cert.pem

SSLCertificateKeyFile /etc/mdm/mdm-pull-server/key

–Copy those files to a secure place, using the following file names:

<path to certificate>/server.crt

<path to certificate>/server.key

D)Install mdm 1.12.x and desired components via the mdm 1.12.x Installer for Windows.

1.Use the mdm 1.12.x Installer for Windows as described in Chapter 2.2.1.

E)Import the dumped databases (mdm server and mdm CA server)

1.Make the dumped databases available on the system where mdm 1.12.x has been installed.

2.Execute (as administrator) the batch file import_mdm_server.bat .

3.Provide the path to the database dump
(default: C:\Users\username\Documents\mdm-server.sql).

4.Provide the installation path of mdm 1.12.x 
(default: C:\Program Files\mGuard device manager).

5.Provide the password of the database user innomms if required.

6.Press any key to close the command prompt when the database import has finished.

7.(If necessary) Repeat 1–6 but execute the batch file import_mdm_ca.bat to import the dumped mdm CA server database (default: mdm_ca_server.sql, database user = mdmca).   

8.mdm will restart automatically and connect to the imported databases.

F)(If necessary) Update the firmware upgrade/pull server configuration

1.Open Apache HTTP Server Monitor (included in the mdm installation) and stop the service ApacheMDM.

2.Compare the web server configuration file, with the backup file copied and stored in step (C):

<path to mdm installation>\apache\conf\extra\httpd-mdm.conf

–Compare the aliases of the pull config server. If your former settings differ from the default settings of the mdm Installer (given below), replace the default set­tings accordingly to your settings (e.g. Alias /my_company_atv/ ):

Alias /atv/ “C:/Program Files/mGuard device manager/apache-data/atv/"

Alias /atv “C:/Program Files/mGuard device manager/apache-data/atv/"

–Update the pull configuration feedback to the mdm server, if it must be config­ured:

# Pull Config-Feedback an den mdm-Server (derzeit auskommentiert).

# CustomLog "| /bin/nc -u -i1 127.0.0.1 7514" common

<your feedback configuration>

3.Copy the certificate and private key, backed up and stored in step (C) to

<path to mdm installation>\apache\conf\server.crt

<path to mdm installation>\apache\conf\server.key

4.Open Apache HTTP Server Monitor and start the service ApacheMDM.

Versions mdm 1.11.x and 1.12.x can only be installed on Ubuntu (Server) 18.04 LTS.

To upgrade an older version of mdm to mdm 1.12.x, you must first upgrade Ubuntu 16.04 LTS to Ubuntu 18.04 LTS via Ubuntu‘s package management tools. See also:

“Quick Guide: Upgrade Ubuntu 16.04 to 18.04” on page 37

“Quick Guide (Ubuntu): Upgrade mdm 1.11.x to 1.12.x” on page 38

Consider the General notes in Section 2.3 “Upgrade mdm installations to mdm 1.12.x” on page 22

From mdm 1.11.0 or later (installed on Ubuntu 18.04 LTS)

To upgrade mdm versions 1.11.0 or later, installed on Ubuntu Server 18.04 LTS, you have to:

–upgrade mdm to mdm 1.12.x via Ubuntu‘s package management tools:

see “Quick Guide (Ubuntu): Upgrade mdm 1.11.x to 1.12.x” on page 38

For further information see “Minor release updates” on page 40 and “Ubuntu‘s package management tools” on page 19.

From mdm 1.10.0 or later (installed on Ubuntu 16.04 LTS)

To upgrade mdm versions 1.10.0 or later, installed on Ubuntu Server 16.04 LTS, you have to:

–upgrade Ubuntu Server 16.04 LTS to Ubuntu Server 18.04 LTS:

see “Quick Guide: Upgrade Ubuntu 16.04 to 18.04” on page 37.

–upgrade mdm stepwise via Ubuntu‘s package management tools:

Upgrade the installed mdm version in two steps via the package management tools of Ubuntu 18.04 LTS first to version mdm 1.11.x and then to version mdm 1.12.x (see “Quick Guide (Ubuntu): Upgrade mdm 1.11.x to 1.12.x” on page 38)

For further information see “Minor release updates” on page 40 and “Ubuntu‘s package management tools” on page 19.

From mdm 1.7.0 or later (installed on Ubuntu 16.04 LTS)

To upgrade mdm version 1.7.0 or later, installed on Ubuntu Server 16.04 LTS, you have to proceed stepwise:

1.Upgrade the installed mdm version in several steps via the package management tools of Ubuntu 16.04 LTS to the next possible version (mdm 1.7.x >> 1.8.x >> 1.9.x >> 1.10.x).

2.Upgrade mdm 1.10.x to mdm 1.11.x as described above (From mdm 1.10.0 or later).

From mdm < 1.7.0

mdm versions < 1.7.0, installed on supported and unsupported Linux systems, cannot be upgraded to mdm 1.12.x.

To reuse the databases of these mdm versions on supported Linux systems, you have to:

–dump and backup the databases,

–install Ubuntu Server 18.04 LTS,

–install mdm 1.12.x via Ubuntu‘s package management tools on Ubuntu Server 18.04 LTS,

–import the dumped databases.

Proceed as follows:

A)Make database dumps of the mdm and mdm CA server database

1.Copy the required shell script files to the Linux system where mdm is installed.

2.Execute (as sudo) the shell script export_mdm_server.sh .

3.Provide the path where the database dump shall be saved
(default: /tmp/mdm-server.sql).

4.Provide the password of the database user innomms if required.

5.(If necessary) Repeat 1–4 but execute the shell script export_mdm_ca.sh to dump the mdm CA server database (default: mdm_ca_server.sql, database user = mdm­ca).

B)Keep a backup copy of the database dumps

1.Open the directory where the database dumps have been saved.

2.Copy the database dump(s) created at (A) to a secure place (e.g. a secure backup folder at another company server).

C)(If necessary) Backup the pull server configuration

1.To backup the web server configuration file, copy the following server configuration file to a secure place. E.g. if you are using Apache 2.x, your configuration file may in:

/etc/apache2/sites-available/your-server.conf .

–If your server configuration defines any aliases for the pull configuration directo­ry, write them down. They may look like:

Alias /atv/ “/var/www/mdm-pull/"

Alias /atv “/var/www/mdm-pull/"

2.To backup the certificate and private key, proceed as follows:

–Check the configuration file from step (1.) (e.g. /etc/apache2/sites-avail­able/your-server.conf) and look for the certificates used by your server. E.g. if you are using Apache 2.x, the entries may look like:

SSLCertificateFile /etc/mdm/mdm-pull-server/cert.pem

SSLCertificateKeyFile /etc/mdm/mdm-pull-server/key

–Copy those files to a secure place, using the following file names:

<path to certificate>/cert.pem

<path to certificate>/key

D)Install mdm 1.12.x and desired components via Ubuntu‘s package manage­ment tools

1.Use Ubuntu‘s package management tools as described in Chapter 2.2.2.

E)Import the dumped databases (mdm server and mdm CA server)

1.Make the dumped databases available on the system where mdm 1.12.x has been installed.

2.Execute (as sudo) the shell script import_mdm_server.sh .

3.Provide the path to the database dump (default: /tmp/mdm-server.sql).

4.(If necessary) Repeat 1–3 but execute the shell script import_mdm_ca.sh to import the dumped mdm CA server database (default: mdm_ca_server.sql, database user = mdmca).

5.mdm will restart automatically and connect to the imported databases.

F)(If necessary) Update the firmware upgrade/pull server configuration

1.Stop (as sudo) the Apache Web Server: service apache2 stop

2.If your previous configuration defined aliases for the pull configuration directory (check files backup up and stored in step (C)), edit the Apache configuration file of your new mdm installation:

/etc/mdm/mdm-webbase/30-configpull.conf

–Add the aliases of your previous configuration (do not change the real export di­rectory: /var/www/mdm/). E.g.:

Alias /atv/ “/var/www/mdm/"

Alias /atv “/var/www/mdm/”

3.Copy the certificate and private key, backed up and stored in step (C) to

/etc/mdm/mdm-webbase/cert.pem

/etc/mdm/mdm-webbase/key

4.Start (as sudo) the Apache Web Server: service apache2 start

All mdm versions

To reuse the databases of mdm versions, installed on Windows systems, on Ubuntu Server 18.04 lTS, you have to:

–dump and backup the databases,

–install Ubuntu Server 18.04 LTS,

–install mdm 1.12.x via Ubuntu‘s package management tools on Ubuntu Server 18.04 LTS,

–import the dumped databases.

Proceed as follows:

A)Make database dumps of the mdm and mdm CA server database

1.Copy the required batch files to the Windows system where mdm is installed.

2.Execute (as administrator) the batch file export_mdm_server.bat .

3.Provide the path where the database dump shall be saved
(default: C:\Users\username\Documents\mdm-server.sql).

4.Provide the path to your current mdm installation directory
(default: C:\Program Files\mGuard device manager).

5.Provide the password of the database user innomms if required.

6.Press any key to close the command prompt when the database dump generation has finished.

7.(If necessary) Repeat 1–6 but execute the batch file export_mdm_ca.bat to dump the mdm CA server database (default: mdm_ca_server.sql, database user = mdm­ca).

B)Keep a backup copy of the database dumps

1.Open the directory where the database dumps have been saved.

2.Copy the database dump(s) created at (A) to a secure place (e.g. a secure backup folder at another company server).

C)(If necessary) Backup the pull server configuration

1.To backup the web server configuration file, copy the following file to a secure place:

<path to mdm installation>\apache\conf\extra\httpd-mdm.conf

–Search for the following entries (your entries may differ from the default settings of the mdm Installer given below) and write down the aliases of the pull config server:

# Verzeichnis für ATV-Profile (wie in preferences.xml eingestellt).

# Alias /atv/ /var/apache-data/atv/

# <Directory /var/apache-data/atv/>

Alias /atv/ “C:/Program Files/mGuard device manager/apache-data/atv/"

Alias /atv “C:/Program Files/mGuard device manager/apache-data/atv/"

2.To backup the certificate and private key, copy the following files to a secure place:

<path to mdm installation>\apache\conf\server.crt

<path to mdm installation>\apache\conf\server.key

D)Install mdm 1.12.x and desired components via Ubuntu‘s package manage­ment tools

1.Use Ubuntu‘s package management tools as described in Chapter 2.2.2.

E)Import the dumped databases (mdm server and mdm CA server)

1.Make the dumped databases available on the system where mdm 1.12.x has been installed.

2.Execute (as sudo) the shell script import_mdm_server.sh .

3.Provide the path to the database dump (default: /tmp/mdm-server.sql).

4.(If necessary) Repeat 1–3 but execute the shell script import_mdm_ca.sh to import the dumped mdm CA server database (default: mdm_ca_server.sql, database user = mdmca).

5.mdm will restart automatically and connect to the imported databases.

F)(If necessary) Update the firmware upgrade/pull server configuration

1.Stop (as sudo) the Apache Web Server: service apache2 stop

2.If your previous configuration defined aliases for the pull configuration directory (check files backup up and stored in step (C)), edit the Apache configuration file of your new mdm installation:

/etc/mdm/mdm-webbase/30-configpull.conf

–Add the aliases of your previous configuration (do not change the real export di­rectory: /var/www/mdm/). E.g.:

Alias /atv/ “/var/www/mdm/"

Alias /atv “/var/www/mdm/”

3.Copy the certificate and private key, backed up and stored in step (C) to

/etc/mdm/mdm-webbase/cert.pem

/etc/mdm/mdm-webbase/key

4.Start (as sudo) the Apache Web Server: service apache2 start

Migrating mdm installations with the provided batch files/shell scripts restores only the da­tabase(s) dumped and imported. Any other installation data (e.g. pull server certificate and config files) must be manually copied to the new installation as explained below.

The provided batch files/shell scripts will only work in case of standard mdm installations (check default database names, ports, and user names in the provided preferences.xml and ca-preferences.xml files).

export_mdm_server.bat

Windows batch file to dump the mdm server database

export_mdm_ca.bat

Windows batch file to dump the mdm CA server database

import_mdm_server.bat

Windows batch file to import the dumped mdm server database

import_mdm_ca.bat

Windows batch file to import the dumped mdm CA server database

export_mdm_server.sh

Linux shell script file to dump the mdm server database

export_mdm_ca.sh

Linux shell script file to dump the mdm CA server database

import_mdm_server.sh

Linux shell script file to import the dumped mdm server database

import_mdm_ca.sh

Linux shell script file to import the dumped mdm CA server database

This will not change the real directory structure in the system, but will make it possible for already configured mGuard s which expect the directories atv, and crl to download pull configurations, and CRL files successfully.
If you additionally want to have the same directory structure in the system, you have to create the corresponding directories and define the access permissions of each in mdm-webbase-ssl.conf.

NOTE: Data loss during the upgrade process

Backup your files before you upgrade the system.

If mdm 1.12.x is installed via the command line, the variable DEBIAN_FRONTEND must be used with the value readline. This is obligatory to display and accept the Software Li­cense Terms (SLT).

Do not update your mdm installation until the upgrade from Ubuntu 16.04 LTS to Ubuntu 18.04 LTS has successfully been completed (see “Quick Guide: Upgrade Ubuntu 16.04 to 18.04” on page 37).

If mdm 1.11.x is installed via the command line, the variable DEBIAN_FRONTEND must be used with the value readline. This is obligatory to display and accept the Software Li­cense Terms (SLT).