The below chart can be consulted to determine best practices for each .NET version.

	Supported: The version of .NET should not exhibit unstable and intermittent behaviors when installed on the corresponding Core version. Please contact Ivanti support if you experience issues specific to an supported version of .NET.
	Unsupported:The version of .NET has exhibited unstable and intermittent behaviors when installed on the corresponding Core version. Please take the listed steps below if if experience issues with this version of .NET installed.

Core Version	.NET 4.5	NET 4.6	.NET 4.7
LDMS 9.5
LDMS 9.6
LDMS 2016.0
LDMS 2016.3
EPM 2017.1
EPM 2017.3

We use Ivanti2017.3_SU5 - can we install on the Core .NET Framework 4.7.2
and will that be supported?
(We also have an Ivanti agent installed on the core ...)

At the time of installation (Ivanti2017.1 ...) no .NET Framwork 4.7.2 was allowed on the core.

• • DESCRIPTION
  • PROCESS OVERVIEW
  • WARNINGS
  • I. Backup Your Existing Core Server
  • II. Backup Your Existing Database
  • III. Backup Critical Core Server Files
  • IV. Backup Other Needed Files and Information
  • V. Prepare Your New Core Server
  • VI. Install Microsoft SQL Server
  • VII. Create/Configure Your New Database and Restore Your Old One
  • VIII. Import Your Certificates
  • IX. Install Ivanti Endpoint Manager (the most current version)
  • X. Migrate Your Clients by Deploying a New Agent
  • Additional Considerations
  • Creating a Core DNS Redirect

DESCRIPTION

A side by side migration consists in having both your existing Ivanti Endpoint Manager Core Server and your future CoreHo Server running at the same time.

You can either use a new clean database or use your current database and have it upgraded to the new version.

I will cover here the second choice: migration using the current database.

    ATTENTION:Please note that this article covers a basic side by side migration, which means that if you have other LANDESK products like a CSA, then you will first have to think or ask about how to migrate it as well.

PROCESS OVERVIEW

1. Backup your existing Core Server (This is not covered in this article, you may want to have an image of your Core server copied on a media/server)
2. Backup your database
3. Backup Critical Core Server Files
4. Backup Other Needed Files and Information
5. Prepare your new Microsoft Windows 2012 Server for your future Core server (Installation and configuration of the server are not covered in this article as it depends on the infrastructure you manage)
6. Install your Microsoft SQL Server 2012
7. Create and configure your database
8. Restore your database to the new server
9. Install Ivanti Endpoint Manager on the new server
10. Import your certificates
11. Migrate your clients by deploying a new agent
12. Additional Considerations
    1. Core Server DNS Redirect
       

WARNINGS

This article is not supposed to get you through the issues you may fix, but to give you a good starter guide if you want to do a side by side migration.

If you actually encounter any error, please contact us through the support portal or our community web site.If you have any customized settings, queries or files, please be aware that you should take screenshots of these configurations, and save the files that may not be saved by our CoreDataMigration tool.

If you plan on changing corenames, then you will need to use the DNS alias for MDM devices to still communicate to the core. Please see doc: Using a Core server DNS alias with the Cloud Service Appliance.

I. Backup Your Existing Core Server

You should have a snapshot/image of your Core Server in order to be able to roll back.

II. Backup Your Existing Database

    VIDEO:Backup your LANDesk Management Suite 9.5

From Microsoft SQL Server Management Studio, go to Databases, Tasks, Back Upand check where this backup goes to copy it to your future Core Server.

In this case, it goes to:

    C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup\

    Remember to copy this ".bak" file as it is your future database.

III. Backup Critical Core Server Files

    VIDEO:Core Data Migration LDMS 9.5

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

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

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

NOTE: The Ivanti 2017.x CoreDataMigration.exe will not work on previous versions. Instead, just use the CoreDataMigration.exe that is in the \landesk\managementsuite folder on the current core server. Please refer to the CoreDataMigration.exe document for further details. 

The new Ivanti Endpoint Manager version of CoreDataMigration.exe can be found in the EPM installation media under the:

    \LANDESK\PF\LD\MS\_non

If Ivanti Endpoint Manager was downloaded, extract LANDESKSoftware.exe to access this file, situated in the Resourcesfolder:

Once you have copied the folder Resources on your old Core server, create a folder named CoreBackup, in this example:

    C:\CoreBackup\

Then open a Command Prompt (CMD) and browse to the folder where you extracted the Resources folder, in this example:

    cdC:\Resources extracted from old server\

And type the following command (in this example):

    CoreDataMigration.exe GATHER C:\CoreBackup\

It may be necessary in some situations to use a local backup directory to work around NTFS and share permissions.

You will be able to find in your CoreBackup folder the critical files you will need for your migration (your scripts, certificates, ldlogon folder with your application packages, etc.), if you want to use them in your new environment, you can copy/paste them from this folder to your future Core Server once the full installation is done.

IV. Backup Other Needed Files and Information

    Some files will not be automatically saved, you must be careful in order to be sure you will have a backup of everything:

• Distribution Package installation files, if stored on a package share created 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

V. Prepare Your New Core Server

In order to be sure that your Windows Server installation is going to match your infrastructure needs, please check the following articles:

• Supported Platforms and Compatibility Matrix for LANDESK Management Suite/Ivanti Endpoint Manager
• About the LANDESK Management Suite 2016 Architecture - An Overview
• About the Ivanti Endpoint Manager 2017 Architecture
• Ivanti Endpoint Manager 2018 Architecture Guidelines

Ensure that your server has the latest updates.

    Then do not forget that the following items are NOT SUPPORTED for the Core Server installation:

• A Primary Domain Controller (PDC), Backup Domain Controller (BDC), or an Active Directory
• A Domain Controller
• A server that has been upgraded from a previous version of windows
• Servers running other third-party applications as their primary server function such as a SharePoint server

VI. Install Microsoft SQL Server

    VIDEO:Install SQL Server 2012 for a Side by side migration of LMDS 9.5 to 9.6

The installation and configuration of Microsoft SQL Server 2012 is described in this document:

• How to install Microsoft SQL Server 2012 for LDMS

You may also find these links useful:

• SQL Tuning and Performance
• Reindexing LANDESK Databases

VII. Create/Configure Your New Database and Restore Your Old One

    VIDEO:Database creation, configuration and restore for Side by side migration 9.5 to 9.6

    An important point here is not to install Ivanti Endpoint Manager on the new server before you restore your old database as the installation process has to convert your old database into the new version.

First you will need to create a new database, so right click on Databases,New Database and put these settings:

Then create your database administrator by going into Security, right click Logins,New Login:

Now you need to restore your old Database into this new database we just created, to do so, right click your new database, Tasks, Restore, Database

• In the General tab, check Device and indicate the path of your old database backup file (*.bak) we made in the previous steps, after that double-check that the Destination Database is the one you created earlier
• In the Files tab, check the Relocate all files to folder option
• In the Options tab, check the Overwrite the existing database (WITH REPLACE) option

Then validate and you are now ready to install Ivanti Endpoint Manager to the new server. Here is a good article as well about this Backup / Restore process:

• Backup and Restore Database: How to move the LANDesk database to another server

VIII. Import Your Certificates

    VIDEO:Import LDMS 9.5 certificates to your 9.6 Server for a side by side migration

In order to use some features on your new Ivanti Endpoint Manager server with your old clients, you will need to have a certificate they already trust.

The files you will need have normally been saved during our CoreDataMigration done earlier except the keys directory.You will need to manually copy core certificate files. These files must be handled securely and should only be placed in a secure location. You can copy them into the CoreBackup folder, but they must be handled with care. You must copy the following files shown below.

You will find these files in the CoreBackup folder you created, in:

    C:\CoreBackup\landesk\Shared Files\keys\

You must copy the following files:

• C:\Program Files\LANDesk\Shared Files\Keys\*.key
• C:\Program Files\LANDesk\Shared Files\Keys\*.crt
• C:\Program Files\LANDesk\Shared Files\Keys\*.0  
• C:\Program Files\LANDesk\Shared Files\Keys\ldcryptoconfig.xml
• C:\Program Files\LANDesk\Shared Files\Keys\Compatible\*.xml(These files will only exists if client security mode is enabled)

Copy them into your new keys folder on your new server, it may look like this:    C:\Program Files\LANDesk\Shared Files\KeysYou also have to copy the *.0 file to your new ldlogon folder, which should be there:    C:\Program Files\LANDesk\ManagementSuite\ldlogon Once this is done, your new Ivanti Endpoint Manager Server will be able to directly remote your clients, with the highest security features enabled. Please note that side by side migrations from 9.6 to 2017.3 requires a full agent reinstall due to the certificate changes in 2017.3. Copying the certificates from the old core to the new one will not allow remote control to function.

Here is an article that might be interesting:

• Moving a Core server to another Domain/Forest - Scenario

IX. Install Ivanti Endpoint Manager (the most current version)

Before starting the install on the new core, you should first create the C:\Program Files\LANDesk\Shared Files\Keys directory and copy ldcryptoconfig.xml into it from your CoreBackup.  This will ensure data that was encrypted and written in the database will be decrypted properly.

If files were copied from C:\Program Files\LANDesk\Shared Files\Keys\Compatible, then they must also be restored back into this directory

    VIDEO: Install LANDesk Management Suite 9.6 for Side by side Migration from 9.5

First, download the latest version of Ivanti Endpoint Manager from this page:

• Downloads for Endpoint Manager (formerly LANDESK Management Suite and Security Suite)

Then extract the files on your server and the installation will begin.

    For this installation, you will only have to be careful with the following settings:

• How should Ivanti configure your database: Upgrade an existing database
• Database information: Enter your Server name, Database name we created earlier, User we created earlier as well and its Password

Here are the articles you may find useful as well for this process:

• How to install Ivanti Endpoint Manager 2017.3
• Ivanti Endpoint Manager 2018.1 Install Guide

X. Migrate Your Clients by Deploying a New Agent

After having done all of this, you should have your infrastructure looking like this:

What we want now is to have our clients directly reporting to our new Server. In order to do that properly, you will have to create new agents (similar to your previous settings if you want) and deploy them gradually with pilot groups/computers.

    Keep in mind that once you have deployed an agent to your client, it may not be manageable anymore from your old server.

Once all of your infrastructure has been "moved" to your new Ivanti Endpoint Manager Server, you can shut down your old server, which will look like this:

    You must be aware as well that a side by side migration can be pretty long and complex as you will have to manage both your old and new server until you are sure of your new settings.

Additional Considerations

Creating a Core DNS Redirect

Some administrators after following this document may encounter some issues where existing agents/agent functions are attempting to communicate with the old core rather than the new, despite the old core having already been removed from production. To avoid such issues, it is recommended as a best practice that administrators after performing a side-by-side migration setup a DNS redirect that will take all traffic intended for the previous core name/fqdn and route it to the new core. This can help to avoid complications and ensure that agent functions remain functional through the migration.

ATTENTION:Please note that DNS redirection is problematic for devices behind CSA (Cloud Services Appliance), reinstallation of the agent on these devices will be required to avoid communication issues.

You will need to manually copy core certificate files. These files must be handled securely and should only be placed in a secure location. You can copy them into the CoreBackup folder, but they must be handled with care. You must copy the following files:

Hello,

Does anyone have any experience or have an idea on how to properly package and distribute Eclipse IDE for Java Devs? Link: Eclipse Packages | The Eclipse Foundation - home to a global community, the Eclipse IDE, Jakarta EE and over 350 open so… I've looked and looked and it doesn't seem like they have an msi or a way to perform silent installs.

Thanks

Trying to upgrade to 9.6 SP2 - failing with:

----------

Pending file rename operations...

ERROR: UpdateComputers exiting with 4 Error(s)

ERRORSUMMARY_BEGIN

The process cannot access the file because it is being used by another process.

  Console.inf: (0x00000020) IMAGE\,,log4net.dll

  Console.inf: (0x00000020) Langs\enu\IMAGE\,,enuitran64.dll

  Console.inf: (0x00000020) Langs\enu\IMAGE\,,enuitnmp64.dll

  CommonCore.inf: (0x00000020) Langs\enu\IMAGE\,,enusched.dll

ERRORSUMMARY_END

Silent Reboot: A REBOOT is required.

Exiting with Return Code: 4

End Done

------------------

I've rebooted and ran upgrade as admin.  Any idea?

Issue

When installing the Core or Remote Console on a device with .NET 4.7 installed, the Data Analytics install fails.

Resolution

This has been fixed in installers for 2017.3 and beyond.

Workaround

A defect has been opened for this issue internally. However, as a workaround, customer can use the powershell shell script attached to this document to modify the registry keys the DA Installer checks, so the install can proceed.

This script has a few parameters:

Install - Backs up the .NET registry keys to the directory the script is launched from, then changes the Version values to 4.6.01586

Restore - Checks for regkey backups and restores them

Ivanti is not responsible for any damages caused by this script, direct or otherwise. This is NOT an official Ivanti script, and is not supported. This script is provided as-is, with no guarantee or warranty of any kind.

Instructions

1. Save the attached .zip file and extract the contents to a directory of your choice
2. Launch an elevated powershell prompt
3. Change directory to directory of ChangeNetVersion.ps1 (ex. "cd "C:\Scripts\ChangeNetVersionRelease")
4. Run the following command: ./ChangeNetVersion.ps1 + parameter

     Ex: ./ChangeNetVersion.ps1 Install

Updated versions of this script may be attached as issues are reported, if necessary

If this script does not work, perform the manual workaround below:

1. Backup the following registry keys:

     HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client

     HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client\1033

     HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full

     HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\1033

     2. Right click each key and select Permissions > Advanced then change the owner to yourself. THIS IS REQUIRED.

     3. Right click each key and select Permissions, and give yourself full control.

     4. Change the "Version" string to 4.6.01586 once the keys are backed up.

     5. Continue with the install.

After the Remote Console is installed, double click on your backed up .reg files to restore the old values.you

******* If you still get the same Error after running this script and restarting the computer.  Delete C:\programdata\landesk and then try the Installer again.*********

History

2.0:

• Script now accepts parameters rather than prompting the user, allowing for non-interactive use (deployment package, scripted use, etc)
• Output changed to write-output instead of write-host so output can be piped to a log

1.0:

• Release. Nothing special.

Description

LANDESK Management Suite has the option to deploy a Remote Console that looks and acts very similar to the Admin Console on the core server. This console is 64-bit and can only be installed on 64-bit operating systems. Users can install the Remote Console to their own machines using the same install files that are used to install the LANDESK Management Suite Core Server. When deploying multiple Remote Console's in an environment it is helpful to deploy it silently to certain users with LANDESK's Software Distribution tool to automate the install process for users.

This document will discuss what command-line parameters are necessary to install the console with no user interaction, and also how to setup a Windows Actions package in LANDESK Management Suite to automate the deployment to multiple users.

Solution

Command line for silent install

Some of you may only be here to find the command line switches necessary to run the install silently. Here... take it and leave if you must! But you may learn something if you read on.

• C:\LANDESKSoftwareXXXX\Setup.exe /s Feature=RemoteConsole

Obtain a copy of the installer

• First things first, we need the install media. If you do not already have this downloaded please get the information here: Where to download LANDesk Management Suite / Security Suite products

Preparing the install files

To run a silent install we need to first unpack the install files out of the EXE format and put them into a ZIP format. This is necessary so that we can pass the proper command line switches

The EXE that you download is a self-extracting executable, and not the EXE used to install the client although it will automatically launch the Setup.exe once it finishes unpacking the files.

1. Run the LANDESKSoftwareXXXX.exe that was downloaded from the LANDESK website.
2. This will extract all the install files to the C:\LANDESKSoftwareXXXX directory by default.
3. Once the extraction is complete Setup.exe will automatically launch providing you with the install GUI that you can follow through to install the Remote Console if desired. But, we want to set this up to run silently...
4. Cancel out of the setup.exe installer to close it.
5. Navigate to C:\ so that you can see the C:\LANDESKSoftwareXXXX folder.
6. Right click on the folder and select "Send to... - Compressed (zipped) Folder", this will create a ZIP of the "LANDESKSoftwareXXXX" directory.
7. You should now have a ZIP file called LANDESKSoftwareXXXX.zip.
8. Copy this file to your Software Distribution share on your network.

Configure your deployment package

As of LANDESK 2016 we have a new package type that makes this process much easier called the Windows Actions Package. This is the package type we will be using to deploy the Remote Console. Below I have attached an export of the a Windows Actions Package that is already configured for deployingthe Remote Console, and only needs to know where to download the ZIP we just created, and the file path to find it once it is on the client.

Import the package

1. Download the attached "LANDESK Remote Console.ldms", move that file over to the device you are using to run the LANDESK Management Suite Console.
2. In the Management Suite Console go to Tools - Distribution - Distribution Packages.
3. Right click on the My Packages folder, and select the "Import..." option.
4. Navigate to the "LANDESK Remote Console.ldms" file and select "Open"
5. On the Import Options screen we recommend using the "Insert items into selected group or owner" this is usually the second option. Nevertheless, use the option that works best for your environment.
6. Click Import.
7. Once the import completes, click close.
8. Locate the package under the My Packages folder.

Modify the package

1. First, we need to add the ZIP we created to the package so that it will get downloaded to the client.
   1. Open the LANDESK Remote Console distribution package.
   2. In the view on the left side of the window, select "Additional Files"
   3. In the field with the file path listed, change that to either the UNC or HTTP path where you would like clients to download the ZIP file from.
   4. Click the blue arrow button to the right to update the directory listing under "Available Files"
   5. Locate the LANDESKSoftwareXXXX.zip that was created earlier, then click the ">>" button to add it to the "Additional Files" list.
   6. Take note of the whole path used for the ZIP.
   7. The ZIP is now added to the package, and will automatically be downloaded to the client when the package is deployed.
   8. Click Save.
2. Next, we need to figure out the file path the client will initially find the ZIP file at after it has been downloaded. Although LANDESK downloads files to the "sdmcache" folder by default, the location under that directory can vary from one environment to the next.
   1. On step 1.6 you noted down the path to the ZIP file, it should look something like this:
      • http://FileServer/PackageShare/PackageFolder/LANDESKSoftwareXXXX.zip
      • \\FileServer\PackageShare\PackageFolder\LANDESKSoftware.zip
   2. When LANDESK downloads files to the agent it will place them in "C:\Program Files (x86)\LANDesk\LDClient\sdmcache\..."
      
   3. The "..." at the end of that path is the part we have to work out to update the package so that the "Unzip Action" in the package knows where to find the ZIP to be unpacked.
   4. Files in the "sdmcache" folder are organized according to the file structure on the share they were downloaded from. So, based on the examples above the ZIP will be downloaded to:
      • C:\Program Files (x86)\LANDesk\LDClient\sdmcache\PackageShare\PackageFolder\LANDESKSoftwareXXXX.zip
   5. For the sake of simplicity we can use the %LD_CLIENT_DIR% variable for the first part of the file path. So the path we will plug into the package becomes:
      
      • %LD_CLIENT_DIR%\sdmcache\PackageShare\PackageFolder\LANDESKSoftwareXXXX.zip
3. Finally we need to add this updated file path into the package.
   
   1. Open the LANDESK Remote Console distribution package.
   2. In the view on the left side of the window, select "Actions"
   3. In the Actions box, select the "Unzip File" action.
   4. Below in the Arguments box, on the "Source File" line, you will see a path that resembles the path we resolved on step 2.5.
   5. Replace that path, with the path resolved on step 2.5.
   6. Click Save.
4. We now have the package prepared to deploy. Right click on it and schedule out to a test client to ensure it is functional before trying to deploy it to a larger audience.
   
5. Also it is important to take into consideration the size of the ZIP file that this package will download to machines, it is at a minimum 2.5 GB, and possibly larger. Plan accordingly.

Conclusion

If you run into any problems, please review the package in detail and ensure that you have made the proper changes. Feel free to comment below with any issues or suggest updates to the document.

After I install the application server of Landesk service desk, console, touchpaper , I restore the default database manually and then go to http://localhost/touchpaper.framework.web/config.aspx to configure the datasource for touchpaper. I can connect the datasource with the sa account (I press test , it shows succeed). But when I keep on the process, I get the error:

Invalid object name 'datatbl'.. Please check the metadata manager log file for further details (time elapsed: 9 seconds)

Below is the metadata manager log file, could anyone help me to solve this problem?

Hi all,

I am upgrading my LANDesk core server from LANDesk 2016 to Ivanti 2017.01 and it has failed at Installing Identity Server. Rather than do the upgrade on our production environment I decided to be safe and do it on a Development environment first. The environments weren't setup by myself and I haven't used our development environment before, I am fairly new to the business. I did all the necessary pre-checks and made sure pre-requisites were met beforehand using the forums and product documentation. Upon doing the upgrade the wizard stopped at the step "Installing Identity Server". I checked the logs and found the following error message in:

2018-10-23 12:58:31 INFO: Execution of CreateWebsite completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2018-10-23 12:58:31 INFO: Executing command CreateCertificate (SetupController.ExecuteCurrentCommand())

2018-10-23 12:58:31 INFO: Executing: D:\Ivanti2017-1 folder\LD\IdentityServer\Resources\LANDesk.Common.RunMethod.exe assemblyFile="LANDesk.Install.Common.Actions.dll" class="CertificateActions" Method="CreateCertificate" commandLine="BouncyCastle;SHA256;My;LocalMachine;TCG-HAY-DEVLD01;LANDESK Secure Token Server"; (Launcher.ExecuteCommandEx())

2018-10-23 12:58:35 ERROR: Execution of CreateCertificate completed. Return code: 1, State: Failure (SetupController.ExecuteCurrentCommand())

2018-10-23 12:58:35 INFO: A required XmlCommand failed (SetupController.CancelInstall())

2018-10-23 12:58:35 INFO: Exiting with Return Code : 3 (SetupController.CancelInstall())

I also checked the setup logs and found this error message:

2018-10-24 11:42:08 INFO: Executing: D:\Ivanti2017-1 folder\LD\IdentityServer\setup.exe /s Feature=Feature1 InstallDir="C:\Program Files\LANDESK\Identity Server" (Launcher.ExecuteCommandEx())

2018-10-24 11:42:10 ERROR: Execution of IdentityServerInstall completed. Return code: 3, State: Failure (SetupController.ExecuteCurrentCommand())

Upon doing some research on the internet, any documentation I could find and the forums here as well as comparing the development environment core server with our production environment core servers I found that in IIS>Server Certificates we are missing the certificate called 'LANDESK Secure Token Server' which might have something to do with this however my experience in LANDesk is somewhere between basic and intermediate and therefore I am not sure what to do next and how to resolve this. I have contacted Ivanti support however despite this server being out of action and this being a SEV 2 they seem to be extremely slow at responding and not much help and so if there is anyone in the community that has had similar issues with the upgrade process and failing on Installing Identity Server and has any ideas of how to fix this it would be much appreciated. I believe this has something to do with ISS, Server Certificates and STS but I don't know how it should be configured or know enough about it to troubleshoot further.

Thanks in advance to anyone who is able to assist with this.

Kind regards,

Luke

Information

Migrating a database is a pretty straightforward process and is well documented on TechNet and other outlets. Here is a list of instructions you can use to migrate a SQL database from one server/host to another.

1. Build or install new SQL server.      Install SQL Server 2012 from the Installation Wizard (Setup)
        http://msdn.microsoft.com/en-us/library/ms143219.aspx
2. Use the following directions to backup your database and restore it on your new SQL server:
        http://technet.microsoft.com/en-us/library/ms187048.aspx
3. If the database is a new install, you'll want to verify that Mixed-mode login is enabled on the SQL server. The how-to for that is found here Change Server Authentication Mode and is posted below in case the link stops working.

Using SQL Server Management Studio to change authentication mode

1. In SQL Server Management Studio Object Explorer, right-click the server, and then click Properties.
2. On the Security page, under Server authentication, select the new server authentication mode, and then click OK.
3. In the SQL Server Management Studio dialog box, click OK to acknowledge the requirement to restart SQL Server.
4. In Object Explorer, right-click your server, and then click Restart. If SQL Server Agent is running, it must also be restarted.
5. Navigate to Start > All Programs > LANDesk > LANDesk Configure Services. Once opened edit the SQL connection information to reflect your new SQL server credentials. Once that is done, you'll want to reboot your core server so all your services start up with the new connection information.

Once this is done your core should now be pointing to your new database server and working as expected. At this point, you may want to consider detaching or deleting your old database from the old SQL Server, though this would be up to your discretion. If you're doing a side by side upgrade I would suggest that you keep a copy of this old database around for a while so you can work out any kinks in your upgrade process and have something to fall back to in case there are problems.

Ivanti Endpoint Manager ( EPM ) version 2017.3 Remote Management Console fails on a step "Installing the Remote Console" - Failed

SOLUTION

Created local Windows account, added the newly created local account to the local group "Administrators" and launched the Ivanti EPM version 2017.3 setup.exe as the newly created local Windows account.

Example:

step 1 of 3 - net.exe user ivanti.install * /add

step 2 of 3 - net.exe localgroup administrators ivanti.install /add

step 3 of 3 - runas.exe /noprofile /user:ivanti.install c:\ivanti2017-3\setup.exe

* assumption is that the Ivanti EPM 2017.3 file Ivanti2017-3.exe has been extracted to c:\ivanti2017-3

Issue

EPM 2018.1 Core Server installation is failing on the step "Configuring Identity Server"

Log file on the Core Server LANDesk.Install.LDMS_%DATE%%TIME%.log reports:

2018-05-25 09:37:54 ERROR: Error running method: ConfigureStandalone Message: Exception has been thrown by the target of an invocation.

2018-05-25 09:37:54 ERROR: Error running method: ConfigureStandalone Message: Configuration file tps.config does not have root <configuration> tag (C:\ProgramData\LANDESK\ServiceDesk\My.IdentityServer\tps.config line 2)

Solution

Modify the following file:

• C:\ProgramData\LANDESK\ServiceDesk\My.IdentityServer\tps.config

And change the <Configuration> </Configuration> tags to <configuration> </configuration>. Then click Try Again and the installation should proceed.

Contact Ivanti Support if these steps don't resolve this issue

Overview

Ivanti Endpoint Manager 2018.1 no longer provides installation media for Workspaces, and does not install Workspaces as part of the install. This move aligns with Ivanti's transition of the End User Workspace to Portal Manager.

If you require Workspaces in 2018.1, you'll need to install it as part of a previous version, and then perform an in place upgrade to 2018.1 The following upgrade paths are supported for Workspaces:

1. Install 2017.3 + Workspaces (separate media in 2017.3 - About Workspaces and Ivanti EPM 2017.3 ), then upgrade to 2018.1
2. Install 2017.1, then upgrade to 2018.1
3. Install 2016.3, then upgrade to 2017.3 + Workspaces (separate media in 2017.3 - About Workspaces and Ivanti EPM 2017.3 ), then upgrade to 2018.1
4. Install 2016.3, then upgrade to 2017.1, then upgrade to 2018.1

The following functions require Workspaces in 2018.1:

• Software Portal for MDM managed devices
• Ivanti Service Desk integration

Description

In EPM 2017.3, the CBA8 Root Certification Authority still uses SHA1 as its signature algorithm.

This certificate is present on clients and may be noticed on communications to the EPM agent. This may be flagged by security scanners, however, it doesn't pose an inherent vulnerability.

This certificate is only used to sign the client's local client certificate, and not to secure any communications. The client certificate does use SHA256, and this is what is used to secure communications sent from the agent, not the CBA8 Root Certification Authority certificate.

Ivanti is looking into addressing this in a future release.

Issue

EPM install reports Failed "Checking database upgrade prerequisites"

Log file reports:

INFO: Executing command CheckIsDatabaseReadyForUpgrade  (SetupController.ExecuteCurrentCommand())

INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\LANDesk.Common.RunMethod.exe assemblyFile=".\Install Only Files\LANDesk.Install.Common.Actions.dll" class="DatabaseActions" Method="IsDatabaseReadyForUpgrade" commandLine="True"  (Launcher.ExecuteCommandEx())

ERROR: Execution of CheckIsDatabaseReadyForUpgrade completed. Return code: -1, State: Failure

Resolution(s)

1. If the SQL Server account password used to access the Ivanti EPM database contains some "special" characters, please temporarily change the SQL Server account's password to be a "simple" password on the Microsoft's SQL Server. Then on the EPM Core Server launch the application "Ivanti Configure Services" / "Configure Software Services" by running %LDMS_HOME%svccfg.exe and change to the new and "simple" password within the tab "General" > "Database". Then click "Try Again".

2. On the EPM Core server, ensure the Windows Registry key HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\ManagementSuite\Core\Connections\local\lsNTLMis set to False. Then click on "Try Again".

1. Run the EPM Tool.  EndPoint Manager (EPM Tool)
   • Option B for Console removal.
   • C to continue the uninstall
   • This will also remove the agent from the machine.
2. Restart the computer.
3. Run the install for the target version again.
   
   If the computer has .NET 4.7 then you will need to run this script: Issue: Data Analytics Install Fails With .NET 4.7
   (This is only for 2017.1 and earlier.  2017.3 and newer will not have this issue)
   
   After running this script you will need to reboot the system to reload the registry.
   
   In some cases some of the software might be left over so you will want to run this tool to double check that there are not any entries for Data Analytics, Landesk or Ivanti:
   
   Microsoft fix it tool (This is just in case something did not get removed.) :https://community.ivanti.com/external-link.jspa?url=https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F17588%2Ffix-pro…
   
   
4. Run the install software.
5. Then apply any Service Updates.
6. Redeploy the Agent for the computer.

Issue

When upgrading core version 9.6 to any later install, it may fail on "Removing Commands website" or "Removing Mobility website"

When looking at the install logs, it appears similar to this:

The key here is: "delete app /app.name: "Default Web Site" /landesk/commands"

The current new upgrade installer is trying to delete a Commands application or Mobility application that is not found in IIS on a core with a current 9.6 install.

Cause

Convert the Commands/Mobility folder in IIS to an application if the folder exists. If it doesn't exist it will need to be created

1. Open IIS> Expand core server > Sites> Default Web Site> landesk> Right click Commands> Convert to Application
   
2. Simply press "OK"
   

At this point, if you have repeated this step for Commands and Mobility, the upgrade of the core console can be continued. If it is still failing because it is found that the Commands or Mobility do not exist, either of those folders will need to be created manually, by right-clicking the "landesk" subpage and selecting "Add Application". Type in the respective folder like the following capture, and then continue the upgrade.

Verifying Ivanti Endpoint Manager ( EPM ) 2017.3 file Ivanti2017-3.exe

c:\windows\system32\certutil.exe -hashfile Ivanti2017-3.exe sha256

SHA256 hash of file Ivanti2017-3.exe:
938c889272e7462460da49b03afaf3487a860b4fcf8f54cd17ae4a44bedf4dbf

c:\windows\system32\certutil.exe -hashfile Ivanti2017-3.exe sha1

SHA1 hash of file Ivanti2017-3.exe:
b70f8ca542c1298721e59633aaa027afcfe51ab2

REFERENCES:

Ivanti Endpoint Manager 2017.3 Download

certutil | Microsoft Docs

Description

When performing core server installation, the user will be given the option to configure a new database or to upgrade an existing database. This article aims at clarifying the supported versions for core server installation with an upgraded database on LDMS 9.6, LDMS 2016.3 and EPM 2017.1.

LDMS 9.6

The options are:

Upgrade an existing 9.5 database

Upgrade an existing 9.0 database

LDMS 2016.3

The options are:

Upgrade an existing 2016 database

Upgrade an existing 9.5 SP3 or 9.6 database

EPM 2017.1

The options is:

Upgrade an existing database (Once clicking on this node pop-up message will show it only supports version 9.6 and above)

Issue

Error displayed during Core Installation: "login failed in user 'sa'.Reason:Server is in single user mode. Only one administrator can connect at this time."

Resolution

1. Install MS SQL Server Management Studio and open the program
2. Expand the object browser Databases and right click on the database named ulddb (this is default name)
3. Right-click the database name select Properties. Then Select the Options page.
4. Scroll down to the State section and change the Restrict Access option from single to multiple (could also be called Multi_user).
5. Once the change has been made click ok.