Install Guide

Contents

Introduction .................................................................................................................................................. 3
Scope ............................................................................................................................................................. 3
Installing/Upgrading to Ivanti® Endpoint Manager 2018.3 .......................................................................... 4
Planning the Installation/Upgrade ............................................................................................................ 4
Performing a backup of the existing core server ..................................................................................... 4
Preparing the Core Server for Installation/Upgrade ............................................................................... 5
Installing/UpgradingI ................................................................................................................................ 5
Post-Installation Configuration ................................................................................................................ 5
Assumptions.................................................................................................................................................. 6
Planning the Installation/Upgrade ................................................................................................................ 6
Documenting All Decisions when planning ............................................................................................... 6
Gathering Network Information................................................................................................................ 6
Choosing the Ivanti Endpoint Manager Components to Implement ........................................................ 7
Microsoft Server 2012 R2 Platforms and Software Requirements ........................................................... 8
Virtualizing the Core Server....................................................................................................................... 8
Selecting the Database Software: MS SQL 2012, 2014, 2016 or 2017 ...................................................... 8
Workspaces Installation......................................................................................................................... 8
Choosing the Installation/Upgrade Procedure.......................................................................................... 8
Certified Ivanti® Deployment .................................................................................................................... 9
New Installation ........................................................................................................................................ 9
Clean Core Server Installation with an Upgraded Database ................................................................... 10
In-Place Upgrade (Same Server).............................................................................................................. 10
Side-by-Side Migrations (Separate Server) ............................................................................................. 10
Backing-up the Existing Core Server ........................................................................................................... 11
Backing-up the Core Server ..................................................................................................................... 11
Backing-up the Core Server to Media ..................................................................................................... 11

www.ivanti.com | 801.208.1500
 – Ivanti Document

Backing-up the Core Server with ImageW.exe........................................................................................ 11

1.1. https://community.Ivanti.com/support/docs/DOC-32296.............................................................. 11
Backing-up the Database......................................................................................................................... 11
Backing-up Critical Core Server Files ....................................................................................................... 11
Backing-up Critical Files with CoreDataMigration.exe ............................................................................ 11
Backing-up Other Needed Files and Information.................................................................................... 13
Other Needed Files .............................................................................................................................. 13
Other Needed Information .................................................................................................................. 13
Preparing for the Ivanti® Endpoint Manager 2018.3 Core Server Installation ........................................... 14
Obtaining Licensing ................................................................................................................................. 14
Upgrading Licenses.................................................................................................................................. 14
45-Day Trial ............................................................................................................................................. 15
Preparing Microsoft Server 2016 for a new Ivanti® Endpoint Manager 2018.3 Installation...................... 15
Installing Microsoft Windows Server from DVD ..................................................................................... 15
Applying Updates to Windows Server..................................................................................................... 15
Naming the Core Server .......................................................................................................................... 15
Obtaining a Domain Account for the Scheduler Service and Com+ Applications ................................... 15
Preparing an Endpoint Manager Database on the Database Server ...................................................... 15
Selecting the Database Software: MS SQL 2012, 2014, 2016 ............................................................. 16
The Installation/Upgrade Procedure .......................................................................................................... 17
Downloading the Installation Media ....................................................................................................... 17
Avoiding Unforeseen Errors ........................................................................................................................ 17
Reading the Release Notes...................................................................................................................... 17
Rebooting the Core Server ...................................................................................................................... 17
Verifying All Ivanti Services and Processes Are Stopped......................................................................... 17
Stopping non-Ivanti Services and Processes ........................................................................................... 18
Read-only Files ........................................................................................................................................ 18
Extracting Ivanti2018-3.exe..................................................................................................................... 18
Performing a New Installation ................................................................................................................ 19
Install the Core Server Software .......................................................................................................... 19

Page | 2
 – Ivanti Document

Introduction

The purpose of this guide is to cover the Best-Known methods for installing or upgrading a LANDESK Management
Suite Core Server to Ivanti Endpoint Manager 2018.3. In this guide, we will discuss considerations when
performing a clean install, an in-place upgrade, and an upgrade on a new server (side by side). Once the Ivanti
Endpoint Manager core server has been installed the final steps for configuration are the same. Find the section
that matches what method will be used and then review the common configuration section.

■ Method 1 – New Installation

■ Method 2 – In-place Upgrade

■ Method 3 – Clean Core Server Install with an Upgraded Database

■ Method 4 – Test or Lab Core Becomes Production

■ Method 5 – Side-by-side Migration

Scope

This guide is designed to provide an experienced Ivanti® Administrator with the information needed to make
choices during a Core Server install or upgrade. It should help in the choices concerning the database, Operating
System, and the Endpoint Manager application.

When preparing to install Ivanti® Endpoint Manager decisions must be made about the memory, storage and
network cards, all of which will affect the performance of the Core Server. Decisions must also be made on how
many Core Servers and when to separate the database server from the Core Server.

Page | 3
 – Ivanti Document

This guide will cover the following:

■ Step 1 – Planning the Installation/Upgrade Procedure

■ Step 2 – Backing-up the Existing Core Server

■ Step 3 – Preparing for the Ivanti® Endpoint Manager 2018.3 Core Server Installation

■ Step 4 – Implementation the Installation/Upgrade Procedure

Installing/Upgrading to Ivanti® Endpoint Manager 2018.3

The following pages contain a check list you can print out to help make sure that all the tasks involved in
installation of or upgrade to Endpoint Manager 2018.3 are completed and to log who performed and accomplished
each task. Your tasks will vary based on whether you are newly installing the product or if you are performing an
upgrade from the prior version.

Planning the Installation/Upgrade Initials

Reviewed Installation/Upgrade options and planned installation procedure

Documented decisions here __________________________________________

Gathered necessary network information

Selected the Ivanti® features and components to implement

Selected the Core Server Hardware and Operating System (Server 2016 now supported)

Selected the database hardware, Operating System, and Database software

(SQL Server 2017 is now supported)

Selected the installation/upgrade procedure (in-place upgrade vs. side-by-side, etc.)

Determined the Domain Policies and other security requirements that apply to the core

Performing a backup of the existing core server Initials

Backed up the Core Server

Backed up the Ivanti® Database

Backed up the Core Server critical files (Most importantly the Certificates and keys)

Backed up any other needed files or information

Page | 4
 – Ivanti Document

Preparing the Core Server for Installation/Upgrade Initials

Obtained licensing for Endpoint Manager 2018.3 or plan to evaluate with the 45-day trial

The Core Operating System has been installed and patched

All the necessary pre-requisites applied

The name of the core server ______________________________________

Obtained the Ivanti Endpoint Manager 2018.3 installation software

Obtained Domain Credentials to be used for the Scheduler Service and Com+ accounts

Unicode database instance prepared and ready for the Endpoint Manager 2018.3 install

Installing/UpgradingI Initials

Installed Ivanti® Endpoint Manager 2018.3 and any other feature sets needed

Post-Installation Configuration Initials

Configured the LANDESK® Scheduler Service with a domain account

Configured the LANDESK Com+ application identities with a domain account

Configured Local Intranet and Trusted sites in Internet Explorer as needed

Added proper users to the LANDESK Management Suite local group and LANDESK Administrators
group

Windows Firewall is properly configured or disabled

Flash Player is properly installed on the Core Server (Even with the Windows console, such
features as Reporting and Alerting will require flash to be installed)

A database maintenance plan has been implemented

A plan for consistent Core Server and Database backups has been implemented

Page | 5
 – Ivanti Document

Assumptions

1. The reader is knowledgeable in Microsoft Server 2012 and/or Microsoft Server 2016, and Microsoft Internet
Information Server (IIS) management.

2. Microsoft SQL Server 2012, 2014, 2016 or 2017 database is installed and configured using the Ivanti® Database
installation guides found in the community. https://community.ivanti.com/docs/DOC-61785

Planning the Installation/Upgrade

Before beginning, a plan should be made to determine the best installation procedure for your environment.

This should be based on the following items:

■ Documenting All Decisions when Planning

■ Gathering Network Information

■ Choosing the Ivanti® Components to Implement

■ Choosing the Core Server Operating System

■ Choosing the Core Server and Database Hardware

■ Selecting the Database software: Microsoft SQL - 2012, 2014, 2016 or 2017

■ Choosing the Installation/Upgrade Procedure

Documenting All Decisions when planning

Necessary documentation should be gathered and/or created for the steps listed above. In addition, prior to
implementing any of the installation steps, prepare a methodology to have all decisions documented. For
upgrading, the best practice would be a screen capture of all Database and Core Server installation selections that
provide a visual diagram of the original installation.

Gathering Network Information

There are many network concerns that must be addressed including but not limited to the following:

■ Determine the IP address, Hostname, and FQDN of Core Server and other servers

■ Important: Once the Core Server is installed, the name cannot be changed.

■ Estimate of total number of devices on which the Ivanti Endpoint® agent will be installed

■ A diagram of the network and all sites involved

■ Gather the type of Operating Systems that will have the Ivanti agent installed (Windows, MAC, Linux, etc.)

■ Noting any network appliances that may exist between the Core Server and agent workstations such as
firewalls and caching appliances.

■ Noting any network appliances that may exist between the Core Server and the Internet.

Note: Some of these network appliances may need to have exceptions added or be bypassed all together for
traffic between the Core Server and the agent workstations.

Page | 6
 – Ivanti Document

■ Speed of network connections between the Core Server and the agent workstations

■ Proxy server configuration (The Core Server must be configured to bypass the proxy to communicate with
itself and other local sites)

■ Core and Clients should be in the same domain (recommended) or all in the same workgroup (not
recommended). If core and clients are not in the same domain, they need to have a trust relationship between the
domains.

There may be other concerns that are not listed above that are specific to your environment and these should be
noted as well. If you are working with Professional Services, this information should be immediately brought to
their attention.

Choosing the Ivanti Endpoint Manager Components to Implement

Ivanti® solutions have many features that can be implemented. Each feature may lead to different requirements.

When installing Ivanti® Endpoint Manager, all features are installed but the license you purchase will determine
the features that are activated and those that are not. There are many features some of which, though not all, are
listed below.

Ivanti® Endpoint Manager (Formerly LANDESK Management Suite)

 Inventory and Software License Monitoring

 Software Distribution / Application Virtualization
 Remote Device Management through the Management Gateway
 Operating System Deployment / Provisioning
 Remote Control

Ivanti® Endpoint Security for Endpoint Manager (Formerly LANDESK Security Suite)

 Patch Management
 Antivirus / Spyware
 Host Intrusion Protection System (HIPS)

Different features may lead to different hardware requirements.

For example, a server that will be used for all features of both Ivanti® Endpoint Manager and Ivanti® Endpoint
Security for Endpoint Manager will utilize more memory and processor resources than one that is used for
Inventory only.

Another example is if Software Distribution and Operating System Deployment are going to be implemented, a
share server may be needed to store the images and software packages. This may be an existing server, a new
server, or even a separate drive on the Core Server.

Choosing the Core Server Operating System

The Core Server can be installed on the following platforms:

 Microsoft Server 2012 R2

 Microsoft Server 2016

It is expected that any new installation will use Microsoft Server 2016.

Page | 7
 – Ivanti Document

Note: If Microsoft has released a new service pack for any of these operating systems, check with Ivanti Support
before applying it.

It is also expected that the Operating System is installed clean just prior to the Core Server installation and is not
already running other third-party applications.

Microsoft Server 2012 R2 Platforms and Software Requirements

 Microsoft Server 2012 R2 or Microsoft Server 2016 (Standard or Enterprise Editions)

 A clean installation of the Operating System is recommended.
 The servers should be dedicated to hosting Ivanti Endpoint Manager

Important: The following configurations are NOT supported for the Core Server Installation.

As any type of domain controller

A server that has been upgraded from a previous version of Windows
Servers running other third-party applications as their primary server (example: Sharepoint)

Virtualizing the Core Server

One of the main reasons for virtualization is to fully utilize your hardware. If multiple servers are hardly used, then
they could potentially be handled by one physical server. The Core Server, however, typically fully utilizes the
hardware allocated.

There are some other benefits of virtualization, such as backup features, snapshot features, etc., that may lead you
to put the Core Server inside a virtual environment. While the Core Server can be installed in a virtual
environment, remember that the hardware requirements listed still apply and that the hardware allocated should
not be shared with other virtualized servers.

Selecting the Database Software: MS SQL 2012, 2014, 2016 or 2017

The hardware requirements have already been covered and any of the listed database software is fully supported.
One way to determine which database software to use is to look at 1) what database software you are currently
using and 2) Is there already an SQL administrator that has strong skills in MS SQL. The cost and/or the ability to
hire a database administrator should also be evaluated.

Oracle database servers are no longer supported, even in an upgrade scenario.

Ivanti Endpoint Manager 2018.3 also requires a second database for Workspaces. This second database can also
be used for Ivanti Configuration Center. This database is used to store custom charts, user information, and
Workspaces specific information.

Workspaces Installation
Ivanti Endpoint Manager no longer installs Workspaces, and no longer provides separate install media for
Workspaces. Please review the community for more information: https://community.ivanti.com/docs/DOC-67417

Choosing the Installation/Upgrade Procedure

When it is time to upgrade, there are multiple choices that must be considered and the pros and cons of each
should be analyzed to see what best works for your environment.

The following table lists some of the various choices that can be made when upgrading a Core Server. These are
not all the possible combinations but a general overview of command types.

Page | 8
 – Ivanti Document

Install/Upgrade Method Core Server Database

New Installation Clean install on the same or on New clean database instance
new server hardware

In-Place Upgrade Upgrade existing server. Backup Same database upgraded during
server prior to upgrade. install. Backup database prior to
upgrade.

Clean Core Server Installation with Clean install on the same or on Upgraded Database instance
an Upgraded Database new server hardware

Test or Lab Core Becomes Upgrade existing server. Backup Same database upgraded during
Production server prior to upgrade. install. Backup database prior to
upgrade.

Side-by-side Migration New server hardware that will be Multiple options: new database
configured while the current instance, upgraded database.
server hardware is hardware
running.

Certified Ivanti® Deployment

Because each environment has different needs, it recommended that you contact your reseller or IVANTI Partner
about the Certified IVANTI® Deployment. If you are unsure who your reseller is, go to this site to find an IVANTI
inside sales manager who can direct you to your reseller:

http://www.ivanti.com/partners/find/

For more information visit the following web site:

http://www.ivanti.com/support/

Ask your Ivanti® Solution Provider which option is best for your environment or contact Ivanti Worldwide
Professional Services by emailing ProServices@IVANTI.com.

New Installation

A new installation is where the Core Server is built starting with a new clean install of the Windows Server
environment from the install media, a new empty database, and a new installation of Ivanti® Endpoint Manager
2018.3.

A new installation is always the solution for new customers who are not upgrading from a previous version.

A new installation is rarely the preferred option for existing customers who already have Management Suite in
their environment. However, a new installation may be the best option for an existing customer if they wish to
make a migration from a legacy version, such as 9.x or prior, to Ivanti® Endpoint Manager 2018.3 as the database
upgrade from legacy version are not tested.

If there is a concern about the stability of both their existing Core Server Operating System and their database, this
option may be desired to eliminate such concerns.

Page | 9
 – Ivanti Document

Clean Core Server Installation with an Upgraded Database

A clean Core Server installation with an upgraded database is when an existing Core Server and database exist, but
the Core Server needs to be rebuilt.

This may occur if the existing Management Suite Core Server is running Microsoft Server 2012 R2 and it is desired
to move to Windows 2016 before moving to Endpoint Manager 2018.3. Since it is not supported to upgrade the
Core Server Operating System, the Core Server should be rebuilt. The database should be upgraded if it is running
version SQL Server 2008. However, the database is still intact, valid, and can be upgraded. In this situation, the
Core Server files should be backed up, (see backup section) and then the server can be rebuilt from a clean Core
Server installation with an upgraded database is a good option when the database is working well but the stability
of the Core Server is in question.

Renaming the Core Server is an example of something that would cause the Core Server to be in an unstable and
unsupported state and a reinstallation using the clean Core Server installation with an upgraded database is
required.

In-Place Upgrade (Same Server)

An in-place upgrade is when a server already has a previous version of Management Suite and Ivanti® Endpoint
Manager 2018.3 is going to be installed on the same server. The installation processes will handle uninstalling the
previous version, installing the new version, and upgrading the existing database.

An in-place upgrade is a good choice when little has been done to customize the installation of Ivanti® software
and when moving forward only one or two releases. See https://community.ivanti.com/docs/DOC-48704 for
compatible upgrade paths.

An in-place upgrade is a good choice when the Core Server and the database are currently functioning properly
and there is no concern of Operating System or database stability.

An in-place upgrade is not a good option if the Core Server or database may already be considered unstable. An
upgrade will not resolve the instability but instead such instability will simply cause the upgrade to fail or leave the
upgraded Core Server in the same state of instability.

Side-by-Side Migrations (Separate Server)

A side-by-side migration is most common when it is needed to have both the old and new Core Server running and
functioning at the same time.

A side-by-side migration is a good choice when wanting to upgrade the Core Server’s Operating System to a newer
version, major hardware upgrade, moving forward several versions i.e. Management Suite 9.5 to Ivanti® Endpoint
Manager 2018.3, or for a clean Operating System environment to start with before installing the new Ivanti®
Endpoint Manager version.

A side-by-side migration is also a good choice if the installation of the previous version is highly customized,
because such customization may not be upgradeable in-place. Instead, a new server should be built with the new
version and these customizations should be documented and then applied to the new server.

A side-by-side migration is also a good choice if there is a concern about the stability of both their existing Core
Server Operating System and database. Using a side-by-side migration can eliminate such concerns.

A side-by-side migration is the only choice when deciding to increase certain hardware or when upgrading the
Operating System. For example, if you need to purchase a more powerful server that would be a separate server
and use the side-by-side migration method. If you need to migrate from Microsoft Server 2008 to Microsoft Server
2012 R2 or Microsoft Server 2016 then a side-by-side migration is recommended, as upgrading from Microsoft
Server 2012 R2 to Microsoft Windows 2016 is not supported.

Page | 10
 – Ivanti Document

Backing-up the Existing Core Server

Before upgrading or otherwise modifying the current Core Server, it is important to back-up all the critical files as
well as any other customized files. This step can be skipped if this is a new installation where a Core Server is being
installed for the first time.

Backing-up the Core Server

There are multiple options to backing-up the Core Server. It is important that the Core Server is backed- up, so use
a trusted backup method.

Backing-up the Core Server to Media

Many companies have a backup policy to backup servers to a specific external media type such as tape drive, DVD,
or even external drives.

If your company has a backup policy, this policy should be implemented before upgrading the Core Server.

Backing-up the Core Server with ImageW.exe

The Core Server drives or partitions can be backed up using Ivanti‘s imaging tool, ImageW.exe. The system drive,
and the drive the Core Server is installed if different, should be backed-up.

For information on backing-up the Core Server with ImageW.exe, see the following document: Manually Capturing
an Image with ImageW.exe

1.1. https://community.Ivanti.com/support/docs/DOC-32296

Backing-up the Database

Back up the database. This document does not include the steps for backing up the database on the database
server. Work with the database administrator to create a backup of your database.

Important: Backing-up the database is critical. There are many reasons a database may fail to upgrade. If
the Core Server successfully upgrades, but the database does not, then without a backup database, you may have
to start with a new database and lose your data. If you have a backup of the database it can be restored, the
upgrade problem can be resolved, and the database can then be upgraded to maintain your data.

Backing-up Critical Core Server Files

Even though we have a backup of the entire Core Server and database, it is still a good idea to have the critical files
backed-up and accessible. If the only backup is on a tape drive, the critical files are not necessarily accessible
without restoring the tape. It is better to have these files backed-up to a share for accessibility.

Ivanti has a created a tool to backup critical files to a share. This tool is called CoreDataMigration.exe.

Backing-up Critical Files with CoreDataMigration.exe

Newer versions of CoreDataMigration.exe may backup files that were not backed-up in previous versions.

One of the Ivanti® Endpoint Manager 2018.3 installation files is an updated CoreDataMigration.exe and it may be
better to use the Ivanti® Endpoint Manager 2018.3 version instead of the version that is currently on the Core
Server.

Page | 11
 – Ivanti Document

The new Ivanti® Endpoint Manager 2018.3 version of CoreDataMigration.exe can be found in the Ivanti® Endpoint
Manager 2018.3 installation media under the directory (Extracted Folder\LD\MS\PF\LD\MS\_non). If Ivanti®
Endpoint Manager 2018.3 was downloaded, extract Ivanti2018-3.exe to access this file.

It is recommended that the critical files be backed-up to a secure share on separate server. The following steps
explain how to use CoreDataMigration.exe for side-by-side migrations.

You can also find more information here: http://community.Ivanti.com/support/docs/DOC-6970

Recommended Method:

1. On the new core server (Ivanti® Endpoint Manager 2018.3) run CoreDataMigration.exe with no
parameters to launch it in GUI mode.

2. Check the boxes Ivanti® Endpoint Manager Core and Web Console) and fill out the other required info and
click OK. In this mode, the tool has been updated to create temporary network shares on the remote
system to get to the Shared Files folder and the ManagementSuite folder. It copies over the necessary
files and then removes the temporary network shares. It handles registry values in WOW6432Node.

Optional Method:

1. Create a directory called IvantiBackup on a share on a separate server that is not the Core Server.

2. Open a command prompt on the Core Server by going to Start | Run and launching CMD.EXE.

Page | 12
 – Ivanti Document

3. In the command prompt, change to the ManagementSuite directory. By default the ManagsementSuite
directory is located at %ProgramFiles%\LANDESK\ManagementSuite but it may have been installed to a
different location.

4. Run the following command:

coredatamigration.exe GATHER \\ServerName\Share\IVANTIBackup

Note: The word GATHER must be all capital letters, but the rest is not usually case sensitive.

Backing-up Other Needed Files and Information

There are many other files and information that may be necessary to backup. Not everything is backed-up by
Ivanti‘s CoreDataMigration.exe. Many of these other files are files that only you know about and only you can be
responsible for making sure they are backed-up properly.

In the previous section a share was already created and this share can be used to backup any other needed files or
information.

Other Needed Files

■ Distribution Package installation files, if stored on a package share on the Core Server

■ The Patch directory, if it is stored on the Core Server

■ \ldlogon\ldappl3.template, if modifications have been made to it.

■ \ldlogon\AgentWatcher\*.ini files

Other Needed Information

There is other information that may be needed. This information usually includes items that are not stored in the
database but are only stored on the Core Server. This information is especially important to backup if performing a
side-by-side Migration or a clean Core Server installation with an Upgraded Database because in both cases the
Core Server will be new and not have that information.

Export the users and groups added to the LANDESK® ManagementSuite group on the Core Server to a file and then
backup the file by copying it to a share. The file can be create by running these commands:

net localgroup “LANDESK Management Suite” > “LANDESK Groups.txt”

net localgroup “LANDESK Reports” >> “LANDESK Groups.txt”

Note: Domain users and groups may not show up when running these commands if the Domain Controller is not
accessible at the time the command is run (for example if the Core Server is moved to a lab environment for
upgrading).

Page | 13
 – Ivanti Document

If migrating to a new database, many items can be exported from the existing database, including the following:

 Queries

 Distribution Packages

 Delivery Methods

 Software License Monitoring

 Custom Vulnerabilities

 Patch status (which patches are set to autofix)

If migrating to a new database, many items cannot be exported. Screen shot such configurations so that they can
be applied to the new Core Server. Examples of these include but are not limited to:

 RBA configuration for the IVANTI® users and for the Template user

 Preferred Server settings

 Unmanaged Device Discovery configurations

 Settings under Configure | Services

 PXE Boot Menu

 Security and Patch settings

Document any custom changes made for your environment. Many companies have made custom alterations or
changes for reasons specific to their environment. Most of these changes are only known to you.

Preparing for the Ivanti® Endpoint Manager 2018.3 Core Server Installation

Now that the Core Server is backed-up, it is time to prepare it for installation or upgrade. Some preparation steps
may already be done on the existing Core Server and do not need to be done again if doing an in-place upgrade.

Obtaining Licensing

The Management Suite Activation user name and password is obtained once you have purchased licensing from
Ivanti. To find where to purchase licenses, go to the following web site.

http://www.Ivanti.com/wheretobuy/default.aspx

Upgrading Licenses

An existing customer who is upgrading should verify with their sales representative that their existing username
and password will activate with licensing for 2018.3 and any other features they have purchased.

Tip: Activate the existing Core Server again, and then look at the Product Licensing to see if the Ivanti®
Endpoint Manager 2018.3 licensing is appearing. The list of licenses shows up even though you are on a
previous version of the Core Server.

Page | 14
 – Ivanti Document

45-Day Trial

New installations can use the 45-day trial and a license can be purchased after installation before the trial period
ends.

Preparing Microsoft Server 2016 for a new Ivanti® Endpoint Manager 2018.3 Installation

Before installing the Ivanti® Endpoint Manager software, Windows should be properly configured and prepared. To
prepare a Core Server for installation, the following must be done:

 Installing Microsoft Server 2016

 Applying Microsoft Updates to the server

Installing Microsoft Windows Server from DVD

The best-known method for a new installation is to install Microsoft Windows Server from DVD (or a scripted
install from a network share) and not from an already existing image. As we cannot determine what is already on
an image we cannot recommend using an image as a best-known method, though the image may work fine.

It is up to you to decide if you want to use a corporate image for the Windows Server. Use it only if you are
confident that your image does not have any changes or installed software that will prevent the Core Server from
installing and functioning correctly. It is recommended that the image be tested in a lab environment before using
it in production for the Core Server.

Applying Updates to Windows Server

Windows Update Service needs to be enabled or at least set to "Manual". Ivanti makes every effort to support the
latest patches and updates. As of the date this document was written, all Microsoft Server 2016 Service Packs and
other Microsoft updates found by going to Windows Update can be applied.

If a new major update such as a new service pack or a new version of .NET Framework is released, check the
Ivanti® community at http://community.Ivanti.com or contact Ivanti® support to verify that it is currently
supported before applying it.

Naming the Core Server

The Core Server name should have already been decided. If the Core Server does not have the proper name, this
name must be assigned now.

Important! Once installed a Core Server cannot be renamed.

Obtaining a Domain Account for the Scheduler Service and Com+ Applications

In a Domain or Active Directory environment, the Scheduler service and the Com+ applications will need to run as
a domain account. A domain account should be created for this purpose.

Schedule Service account should be a domain administrator or an account that is a local administrator on all agent
workstations. It should also have access to all packages servers via UNC or HTTP.

Preparing an Endpoint Manager Database on the Database Server

If using the Microsoft SQL Express 2016 that is installed with Management Suite 2018.3, no configuration needs to
be done here.

Page | 15
 – Ivanti Document

If performing an upgrade, verify that the database version is a supported version, the database service must be
upgraded before installing Ivanti® Endpoint Manager 2018.3. For information on supported database software see
the previous section titled

Selecting the Database Software: MS SQL 2012, 2014, 2016 or 2017

If doing an in-place upgrade Server that is already pointing to a database, that database is used. If the database
software is supported, no changes are required here. This included MSDE. If the current Core Server is running an
earlier version of MS SQL Express, MS SQL Express 2016 will not be installed, but instead the existing SQL Express
database will be used.

If a new database is needed, a database instance must be created before the installation of Ivanti® Endpoint
Manager 2018.3 can occur. To set up the database follow the guides documented in the section titled Database
Documentation.

Page | 16
 – Ivanti Document

The Installation/Upgrade Procedure

Now that the Core Server and the database are backed up and the server is ready for installation/upgrade, it is
now time to begin the installation of Ivanti® Endpoint Manager 2018.3.

Downloading the Installation Media

The Ivanti® Endpoint Manager 2018.3 installation source can be downloaded from the following locations:

New customers must use this

http://www.ivanti.com/company/trials/
IVANTI trial page

Ivanti Product Downloads

A login is required. Only existing http://community.ivanti.com/support/community/product_downloads

customers and partners can see
the downloads section.

Service Packs and updates http://community.ivanti.com/support/docs/DOC-1001

The file that is downloaded is a self-extracting executable, Ivanti2018-3.exe.

Avoiding Unforeseen Errors

This section gives tips on avoiding unforeseen errors that could be impossible to duplicate.

Reading the Release Notes

Many installation caveats are in the Release Notes. When the installation is started, there is a link to the Release
Notes and these should be read. They describe known issues that should be avoided and other important
information.

Rebooting the Core Server

A server reboot can be extremely helpful just before an upgrade. Remember, your Core Server has been under a
heavy load handling several hundred or thousands of clients and requests on many different services. To make
sure that the Core Server, the Operating System, and all supporting software are running smooth and won’t
interfere with the upgrade, a reboot is recommended.

Verifying All Ivanti Services and Processes Are Stopped

The installer will stop all services and processes. Ivanti® services, as well as IIS and other services, may be under
very heavy use and may have been under heavy use for a long time. If you just rebooted, as mentioned previously,
the Management Suite installer should stop all services and processes without error.

The Endpoint Manager installation needs all the LANDESK services and all other IVANTI® processes to be stopped
in order for the upgrade to complete. If you see a process that fails to stop, please contact Ivanti® Support.

Page | 17
 – Ivanti Document

Important! IIS must be running and should not be stopped.

Stopping non-Ivanti Services and Processes

There are many processes that could get in the way of installing Ivanti® Endpoint Manager 2018.3 and not all of
them are known or can be predicted.

 Stop any antivirus programs if already installed, especially real-time antivirus services.

 Stop the Indexing Service.

 Disconnect any Console and Web Console connections.

Read-only Files

If performing an in-place upgrade, make sure that no Ivanti files are marked as read-only that should not be. Some
people have marked files such as the NTSTACFG.IN# or their agent configuration files as read-only to prevent them
from being modified. This may lead to an error upgrading as these files cannot be renamed to .bak and replaced
because they are read only.

Stop all real-time scanners during the install to improve install time and to ensure services and other critical files
get updated correctly.

Ensure that there are no .WIM files already mounted

If you use .WIM files and mount them to view or manipulate the contents it is essential to ensure there are no
.WIM files currently mounted. The following document details this process.

https://community.ivanti.com/docs/DOC-39927

Extracting Ivanti2018-3.exe

If the software was downloaded, it comes in a self-contained executable called Ivanti2018-3.exe. If the installation
is available already, skip this section.

1. Double-click on Ivanti2018-3.exe.

Warning: Do not try to extract the software with a third-party zip utility as some files may not be extracted.

2. The default path of C:\Ivanti2018-3 will be displayed. This can be changed to your desired location.

Important! Notice the default location is a temporary directory. This will serve as the installation media
location. Choose and enter a permanent location where these files can be extracted and kept. The best-known
method is to store this installation media on the package server that supports UNC shares, so the Remote
Console can be deployed.

3. Once you have chosen the location, click Install and the files are extracted.

Once extracted the Ivanti Setup window will automatically open.

Page | 18
 – Ivanti Document

Performing a New Installation

Install the Core Server Software

To perform the installation of Ivanti® Endpoint Manager, follow these steps:

1. Run Setup.exe from the installation files to open the Ivanti Setup window.

2. Click Continue after selecting the appropriate language.

Page | 19
 – Ivanti Document

3. Read the Terms and Conditions, then if you agree, then Select Continue

4. Click the appropriate installation option.

 Core Server

 Remote Console

 Rollup Core Server

To include Ivanti® Endpoint Manager, choose Core Server.

Page | 20
 – Ivanti Document

The next screen checks to make sure that the server has passed the prerequisites. If the prerequisite
checker detects that it is missing a required feature, the screen shows a button with Install Prerequisites.

5. Select Install Prerequisites

Page | 21
 – Ivanti Document

6. Once the prerequisites are done installing select Continue.

7. You will be prompted for the database information. (This guide assumes that Configure a new 2018.3
database is selected.)

Page | 22
 – Ivanti Document

8. Select the desired option and click Next.

Page | 23
 – Ivanti Document

(This guide assumes that Microsoft SQL Server is chosen.)

9. Enter the following SQL Server information:

a. Server Name of the Database Server in the “Server” field.

b. Enter the Name of the database in the Database field.

c. Enter the Username and Password in the User name and Password field.

d. The Port field can be left blank, unless you have changed the default port from 1433.

Page | 24
 – Ivanti Document

10. Once the data is entered, click Test Connection to test database connectivity or Select Continue.

Page | 25
 – Ivanti Document

11. Next, you are prompted for the location where you would like LANDESK® Management Suite installed.
Choose the default location or if desired, change it and select Continue.

Page | 26
 – Ivanti Document

12. Secure Client Management: In LDMS 2016 we introduced a new feature called Secure Client
Management. If you are doing a brand-new install and will not be managing ANY clients with a pre-
LANDESK 2016 Agent installed now would be a good time to enable this feature. However, if you are
migrating and will be managing some older agents for a while then you can enable this feature later from
the Ivanti Console. You can find more information here: http://community.Ivanti.com/support/docs/DOC-
39948

Page | 27
 – Ivanti Document

13. Click Continue and the Management Suite 2018.3 software summary is shown.

Page | 28
 – Ivanti Document

14. Click Install and the Ivanti® Endpoint Manager software installs

Page | 29
 – Ivanti Document

15. When the installation finishes, select Reboot.

Page | 30
 – Ivanti Document

16. Once your core server has rebooted the activation utility will pop up. Go ahead and enter your
credentials and run the Core Server activation utility.

Page | 31
 – Ivanti Document

1. Location and Troubleshooting

With 2018.3, the install logging is in C:\ProgramData\LANDESK\ManagementSuite\Install\11.0.1\Log. These logs

are also linked within the GUI of the install if a failure occurs. When looking through the MSI log, look for “Return
Value 3”. This information right before it and right after this contains the last step the installation attempted to
perform. When contacting IVANTI Support this information will help the Support representative resolve any
installation in a more quickly. It would also be recommended to zip up this directory and attach to the case.

Page | 32