• Description
• Renewing Subscription customers
• Activating the Core Server Online
• Manually Activating the Core Server

Description

LANDESK Management Suite and Security Suite licensing is managed using online activation.  A Core Server must be activated using this online activation before it will be functional.

Also, different features of LANDESK can be enabled or disabled with simple activation.  Installation of additional software is not usually needed.

Renewing Subscription customers

For renewing subscription Customers, simply reactivate your core.

Start | All Programs | LANDesk | Core Server Activation and clicking the Activation button.

Activating the Core Server Online

Complete an online activation of the Core Server using the following steps:

1. Run the Core Server Activation from the Start menu LANDesk Management group.
2. Enter valid credentials and click 'activate'.
3. The Licensing server will be accessed and the Core Server will be activated.

Note: Clicking on the Licenses... button will display the licenses received through the activation process.

Manually Activating the Core Server

Complete a manual core server activation by:

1. Run the Core Server Activation from the Start menu.
2. Enter valid credentials and click 'activate'.
3. The Licensing server will be accessed and the Core Server will be activated.
4. An error box will appear specifying a file has been created that must be e-mailed to licensing.
   
     A *.txt file is created in \program files\LANDesk\Authorization Files
   
   
5. Obtain the .txt file and e-mail the file to licensing@landesk.com.
6. When the new activation e-mail is returned a .AUTH file will be attached to the email. Place the attached .auth file in \Program Files (x86)\LANDesk\Authorization Files.  Ensure the file does not have a .TXT extension, it must have a .AUTH extension.

No further action is needed.  The core is activated upon placing a valid .auth file in the above folder.

Note: Clicking on the Licenses... button will display the licenses received through the activation process.

Important! If you run the core server activation and it appears to be successful, but you are unable to log into the console check to make sure that your license is valid for the product you are trying to use.  For example, if your credentials are valid for Management Suite 8.8 but you are trying to use Management Suite 9.0, the console login will fail.

Exception! ParseLocalConnectionString Parameter name: local_connection_string

stuck while checking database pre-requisites or error may occur any time the database is accessed via coredbutil.exe

This document will cover a few different things that can contribute to getting this error message. The very first step to confirm this error message is to launch coredbutil.exe located here:

"C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe"

or

%LDMS_HOME%CoreDbUtil.exe 

This communication works with SSL and Microsoft's Internet Information Services ( IIS ) to complete the connection. Here is the error message that you will most likely get while launching CoreDbUtil.exe

Now that we have identified that the utility CoreDbUtil.exe is unable to launch, let's proceed with some of the easier steps to correct this issue first.

Solution #1 Check bindings in IIS for https / port 443

Here are the steps to check the bindings on 443.

1. On the Core Server open IIS manager
2. Right-click on a Default Web Sie
3. Select Edit Bindings...
   
4. Select the binding for https / port 443 and then go to Edit...
   
5. On the next screen, we will want to make sure that the hostname field is blank.

Solution #2   Check Configure LANDESK Software Services and the Windows registry key HKLM\Software\LANDesk\ManagementSuite\Core\Connections\Local

1. For this step, we will be checking the Windows Registry key to make sure it is not blank, and matches what is seen under “Configure LANDESK Software Services”. Let's go ahead and launch “SvcCfg.exe”. Usually you can launch this application by clicking on start then searching for Configure Services. If your system is unable to find it, here is the full path: "C:\Program Files\LANDesk\ManagementSuite\SvcCfg.exe" or %LDMS_HOME%SvcCfg.exe
   
   Take note of the Server,  Username and Database. While we have Configure Services open, we should test the login for the Database
2. Put a space after the password and then delete the space
3. Click apply.  Afterward, you should get a prompt telling you to restart the service if everything is accurate. ( You must restart the services that use the database before your changes will take effect. )
   
4. Next we need to open Regedit then browse to:  HKLM\Software\LANDesk\ManagementSuite\Core\Connections\Local
5. Make sure that the name of the Database, name of the Server, and User all match the information found in step 1
6. Check to make sure that the value of IsNTLM is set to false

Solution #3   Check to make sure TLS 1.0/1.1 is enabled

The easiest way to enable TLS 1.0/1.1 is going to be with a tool named IIScrypto. Click here to download the tool IIScrypto. When you first launch the tool IIScrypto, everything might be grayed out. Double click on TLS 1.1 to enable it.

Click apply and then restart the Windows Server / Core Server. Now follow the same steps on the SQL Server. Once both Windows Servers come back up, let's go ahead and try to launch CoreDbUtil.exe one more time.

If CoreDbUtil.exe launched successfully, you should now be able to proceed with your upgrade or login.

Solution #4 Check that IIS Application Pools are using the correct  .NET CLR Version.

On the Core Server open IIS Manager. Application Pools should look as follows:

Solution #5 Check that ISAPI and CGI Restrictions are allowed at the IIS Server level

Solution #6 Check if any proxy server is used in IE - Options - Connections

Supported languages for Ivanti Endpoint Manager

Description

EPM Tool was originally started in order to remove Landesk (LDMS) from remote consoles and cores. Since then, other features have been added.

EPMTool is capable of the following and listed in the menu structure below:

          MAIN MENU

             Uninistall/ Install Utilities

               A.) Agent Uninstall                    How To: Uninstall the LANDESK Agent

               B.) Console Uninstall                How to remove a 9.6 and 9.6 SP1 console from client machines when the uninstall or reinstall fails

               C.) Remove IIS (in progress)

             Inventory Utilities

               A.) Mini to Miniscn                    .MINI Scan Files In LDSCAN Folder

             Failed Core Install Utilities

               A.) Fix Strong Name                 Strong Name Verification Errors

               B.) Fix .Net for DA                    Issue: Data Analytics Install Fails With .NET 4.7

               C.) Run Streams                      Troubleshooting Failed installs.

             Support Utilities

               A.) Fetch Logs

               B.) Diagnostics

               C.) Network Tests

                         A.) Core to Agent

                         B.) Core to db

                         C.) Custom Host and Port

                         D.) DEP IOS Test

                         M.) MDM Check from Core

               D.) Remove Auth Files               Issue: Unable to Build Core Server Activation File

               E.) COM+ Rebuilder                   How to rebuild the LANDesk COM+ Objects

               F.) EPM Mail (in progress)

               G.)Enumerate Programs

             Service Control

               A.) Stop LANDesk Services

               B.) Start LANDesk Services

               C.) Restart Landesk Services

               D.) Delete ASP .Net Files

Note: If you have issues uninstalling.

Try Microsoft's FixIt tool https://support.microsoft.com/en-us/help/17588 "Fix problems that block programs from being installed or removed"

Current version: 11-28-2017

This batch file is known to work on:

• 9.5SP3
• 9.60 - 9.6SP3
• 2016.0 - 2016.3 Service Update 4
• 2017.1 - 2017.1 Service Update 1
• 2017.3

Note: Attached you will find a batch file and an exe. The exe is the batch file converted so it will use less space.

Issue

Remote console install fails during install with error "The Strong name verification system contains exclusion entries in the registry. Blocking access."

Resolution

1. Launch regedit on the computer that the console is being installed on.
2. Navigate to these two locations and delete additional folders beneath these keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\StrongName\Verification

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\StrongName\Verification

LANDESK Architecture

There are several distinct services or functionalities that may be required or used with LANDESK Management Suite (LDMS). These can include some or all of the following:

• LANDESK Core Server
  • This server includes IIS which provides many key web services
• Database Server (MS SQL)
• LANDESK Cloud Services Appliance (CSA)
• Remote Management Console
• Preferred Servers
• PXE Representatives

There are other services or servers that can be used depending on the requirements, such as a Terminal Server to allow access to the Remote Management Console or a dedicated reporting server for custom reports and so forth.

Considerations for Upgrade and Install

When upgrading or installing LANDESK, the demands on the system may be higher than during normal use. This can be due to increased activity that can occur during an upgrade. For example, installing a new agent may cause that device to perform several scans to ensure it is up-to-date. Additionally adoption of new features can lead to increased load on the system, so an environment that was meeting expectations before, may begin to not meet expectations as the demand or feature adoption increases.

Software Requirements

Core Server

The LANDESK Management Suite Core Server is now fully 64-bit, so it cannot be run on any 32-bit systems.

• Microsoft Windows Server 2008 R2 with Service Pack 1, 64-bit (Supported for in-place upgrades only)
• Microsoft Windows Server 2012 R2 with Update 1, 64-bit

The install language of the Microsoft Windows Server should match the LANDESK install language and the language of all Remote Consoles.

Database Server

The following database systems are supported:

Microsoft SQL Server

• Microsoft SQL Server 2008 Express (Free to use, but limited)
• Microsoft SQL Server 2008 Standard/Enterprise
• Microsoft SQL Server 2012 Express (Free to use, but limited)
• Microsoft SQL Server 2012 Standard/Enterprise
• Microsoft SQL Server 2014 Standard/Enterprise

Oracle 11g

Oracle is not a supported database server for LDMS 2016

Remote Console

The LANDESK Managment Console is installed as part of the Core Server installation. Additional Remote Consoles can be installed as well to provide access to the LANDESK Management Suite/Security Suite tools and features. For LANDESK Management Suite 2016, the Remote Console can only be installed and run on 64-bit systems.

Supported Operating Systems:

• Windows 7 Professional, Business, Enterprise and Ultimate Editions x64
• Windows 8 Enterprise x64
• Windows 8.1 x64
• Windows 10 x64
• Windows Server 2008 R2 SP1
• Windows Server 2012 x64
• Windows Server 2012 R2 x64

Supported Client Platforms

Hardware Recommendations

Generic Guidelines

Additional Guidelines by Environment Size

Up to 750 Devices

All LANDESK Services on a single server

• Dual-core, 64-bit processor
• 4GB RAM
• 100/1000 Mb Network Adapter
• 72 GB of free disk space on 10K RPM or faster drives or arrays.
  • Drive/Array configuration
    • One drive or array for the operating system, LANDESK Management Suite application, and database application
    • One drive or array for the database and database logs

750 to 1,500 Devices

All LANDESK Services on a single server

• Quad-core, 64-bit processor. (Preferably two physical quad-core processors)
• 4+ GB RAM
• 100/1000 Mb Network Adapter
• 72 GB of free disk space on 10K RPM of faster drives or arrays
  • Drive/Array configuration
    • One drive or array for the operating system, LANDESK Management Suite application, and database application.
• One drive or array for the database and database logs. RAID 0, 5, 10, or an equivalent/faster redundant storage technology is recommended.

1,500 - 3,000 Devices

All LANDESK Services on a single server

• Two Quad-core, 64-bit processors (8 CPU cores total)
• 8 - 12+ GB of RAM or more
• Gigabit network adapter
• 3 storage arrays with 72 GB of free space each on 15K or faster drives
  • One array for the Operating System. RAID 0, 1, 5 or faster
  • One array for LANDESK Management Suite software. RAID 0, 5, 10 or an equivalent/faster technology
  • One array for the database and database logs. RAID 0, 5, 10 or an equivalent/faster redundant storage technology

A LANDESK system for 1,500 to 3,000 devices all running on a single server could see performance issues with disk I/O depending on the use and configuration of both LANDESK and the storage arrays. Some tuning may be needed. As noted above, the arrays should be on separate spindles (physical disk) to reduce any resource conflicts.

3,000 to 5,000 Devices

LANDESK Core Server and Database Server on separate servers

The Core Server

• Two quad-core, 64-bit processors (8 CPU cores total)
• 4 - 8 GB RAM
• Gigabit Network Adapter
• 2 arrays with 72 GB of free space per array on 15K RPM or faster drives
  • The operating system should be on an array of RAID 0, 1 or an equivalent/faster technology
  • LANDESK Management Suite software should be on an array of RAID 0, 5, 10 or an equivalent/faster redundant storage technology

The Database Server

• Quad-core, 64-bit processors (4 CPU cores total)
• 8+ GB of RAM
• Gigabit Network Adapter
• Three arrays with 72 GB of free space per array on 15K RPM or faster drives
  • The operating system array should be RAID 0, 1 or an equivalent/faster technology
  • One array for the database. RAID 0, 5, 10 or an equivalent/faster redundant storage technology
  • One array for the database logs, RAID 0 or an equivalent/faster redundant storage technology

5,000 to 8,000 Devices

LANDESK Core Server and Database Server on separate servers

The Core Server

• Three - four quad-core, 64-bit processors (12 - 16 CPU cores total)
• 4 - 8 GB RAM
• Gigabit Network Adapter
• 2 arrays with 72 GB of free space per array on 15K RPM or faster drives
  • The operating system should be on an array of RAID 0, 1 or an equivalent/faster technology
  • LANDESK Management Suite software should be on an array of RAID 0, 5, 10 or an equivalent/faster redundant storage technology

The Database Server

• Two quad-core, 64-bit processors (8 CPU cores total)
• 12+ GB of RAM
• Gigabit Network Adapter
• Three arrays with 72 GB of free space per array on 15K RPM or faster drives
  • The operating system array should be RAID 0, 1 or an equivalent/faster technology
  • One array for the database. RAID 0, 5, 10 or an equivalent/faster redundant storage technology
  • One array for the database logs, RAID 0 or an equivalent/faster redundant storage technology

8,000 to 12,000 Devices

LANDESK Core Server and Database Server on separate servers

For more recommendations and guidelines for an environment of this size, see Recommendations for tuning LDMS and MS SQL for large enterprise Core Servers

The Core Server

• Four quad-core, 64-bit processors (16 CPU cores total)
• 16+ GB of RAM
• Gigabit Network Adapter
• 2 arrays with 72 GB of free space per array on 15K RPM or faster drives
  • The operating system should be on an array of RAID 0, 1 or an equivalent/faster technology
  • LANDESK Management Suite software should be on an array of RAID 0, 5, 10 or an equivalent/faster redundant storage technology

The Database Server

• 3+ quad-core premium 64-bit processors (12+ CPU cores total)
• 24+ GB of RAM
• Gigabit Network Adapter
• Three arrays with 72 GB of free space per array on 15K RPM or faster drives
  • The operating system array should be RAID 0, 1 or an equivalent/faster technology
  • One array of four or more disks for the database. RAID 0, 5, 10 or an equivalent/faster redundant storage technology
  • One array for the database logs, RAID 0 or an equivalent/faster redundant storage technology
• Microsoft SQL Server Enterprise Edition is recommended for environments of this size. Consult Microsoft for a detailed SQL Server Edition comparison.

12,000 to 16,000 Devices

LANDESK Core Server and Database Server on separate servers

For more recommendations and guidelines for an environment of this size, see Recommendations for tuning LDMS and MS SQL for large enterprise Core Servers

The Core Server

• Four quad-core, 64-bit processors (16 CPU cores total)
• 16+ GB RAM
• Gigabit Network Adapter
• 2 arrays with 72 GB of free space per array on 15K RPM or faster drives
  • The operating system should be on an array of RAID 0, 1 or an equivalent/faster technology
  • LANDESK Management Suite software should be on an array of RAID 0, 5, 10 or an equivalent/faster redundant storage technology

The Database Server

• Four quad-core premium, 64-bit processors (16 CPU cores total)
• 32+ GB of RAM
• Gigabit Network Adapter
• Three arrays with 72 GB of free space per array on 15K RPM or faster drives
  • The operating system array should be RAID 0, 1 or an equivalent/faster technology
  • One array of four or more disks for the database. RAID 0, 5, 10 or an equivalent/faster redundant storage technology
  • One array for the database logs, RAID 0 or an equivalent/faster redundant storage technology
• Microsoft SQL Server Enterprise Edition is strongly recommended for environments of this size

More than 16,000 Devices

For LANDESK Management Suite installations of this size, additional tuning and design assistance from LANDESK Professional Services or from a valued Expert Solution Provider (ESP) is strongly recommended.

• • 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 Microsoft Windows 2012 Server
  • VI. Install Microsoft SQL Server 2012
  • VII. Create, configure your new database and restore your old one
  • VIII. Import your certificates
  • IX. Install LANDesk Management Suite 9.6 (or 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 LANDesk Management Suite Core Server and your future Core 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.

Environment tested:

• LANDesk Management Suite 9.5 SP2 to LANDesk Management Suite 9.6        [30.07.2014]

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 LANDesk Management Suite 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 Management Suite 9.6 installation files is an updated CoreDataMigration.exe and it may be better to use the Management Suite 9.6 version instead of the version that is currently on the Core Server.

NOTE: The Ivanti 2017.1 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 Management Suite 9.6 version of CoreDataMigration.exe can be found in the Management Suite 9.6 installation media under the:

    \LANDESK\PF\LD\MS\_non

If Management Suite 9.6 was downloaded, extract LANDESKSoftware.exe to access this file, situated in the Resourcesfolder:

Once you have copied the folder Resources on your 9.5 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 9.6\

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 9.6 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 Microsoft Windows 2012 Server

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

• LANDESK Management Suite 9.6 Architecture - Overview

• Supported Platforms and Compatibility Matrix for LANDESK Management Suite/Ivanti Endpoint Manager

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 2012

    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:

• Best Known Methods for installing 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 LANDesk Management Suite 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 LANDesk Management Suite 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 LANDesk Management Suite 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 LANDesk Management Suite 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 LANDesk Management Suite 9.6 (or 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 our 9.6 Core Server installation package from this page:

• LANDesk Management Suite / Security Suite 9.6 Download

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 LANDESK configure your database: Upgrade an existing 9.5 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:

• Best Known Methods for Installing LANDESK Management Suite 9.6

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 LANDesk Management Suite 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:

Description

This is a simple chart designed to quickly reference what the minimum required version a core needs to be on in order to upgrade.

Note: It is recommended to be on the latest service pack or service update level for each version before upgrading. Being on the latest service pack will help reduce problems during upgrade.

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

The attached document covers the installation process for Ivanti Endpoint Manager 2018.1.

The document is provided in PDF and DOCX format for your convenience.

Applies to Ivanti Endpoint Manager 2018 (The information here may also generally apply to other versions of Ivanti Endpoint Mananger. Verify before planning any architecture)

Ivanti Endpoint Manager, Endpoint Security for Endpoint Manager and Patch for Endpoint Manager provide essential IT services to many organizations from simple "kiosk" machines to the CEO's laptop; from mission-critical servers to smartphones. It is often a keystone to many services provided by the IT department. Because of this, it is important that Ivanti perform well and be able to accomplish the tasks the each organization needs to get done in a manner that they can plan for and expect. Ivanti Software is constantly working to make sure that we can deliver a product that can do all of this for our customers. A critical component in the overall solution is the architecting of the Ivanti "environment". The servers, equipment and software that provide various services or functionality key to a smooth running Ivanti solution. When architected properly things go much smoother and you avoid the headaches that can come when every task requires careful consideration to not upset the balance that is just barely holding together.

Ivanti Architecture

There are several distinct services or functionalities that may be required or used with Ivanti Endpoint Manager. These can include some or all of the following:

• Ivanti Core Server
  • This server includes IIS which provides many key web services
• Database Server (MS SQL)
• Ivanti Cloud Services Appliance (CSA)
• Remote Management Console
• Preferred Servers
• PXE Representatives

There are other services or servers that can be used depending on the requirements, such as a Terminal Server to allow access to the Remote Management Console or a dedicated reporting server for custom reports and so forth.

Considerations for Upgrade and Install

When upgrading or installing Ivanti, the demands on the system may be higher than during normal use. This can be due to increased activity that can occur during an upgrade. For example, installing a new agent may cause that device to perform several scans to ensure it is up-to-date. Additionally adoption of new features can lead to increased load on the system, so an environment that was meeting expectations before, may begin to not meet expectations as the demand or feature adoption increases.

Software Requirements

Core Server

The Ivanti Endpoint Manager Core Server is now fully 64-bit, so it cannot be run on any 32-bit systems.

• Microsoft Windows Server 2012 R2 with Update 1, 64-bit
• Microsoft Windows Server 2016, 64-bit

The install language of the Microsoft Windows Server should match the Ivanti install language and the language of all Remote Consoles.

Important: Upgrading the Core Server Operating System over an existing Windows installation is not supported. A "clean" installation is required

Database Server

The following database systems are supported:

Microsoft SQL Server

• Microsoft SQL Server 2012 Express (Free to use, but limited)
• Microsoft SQL Server 2012 Standard/Enterprise
• Microsoft SQL Server 2014 Standard/Enterprise
• Microsoft SQL Server 2016 Express/Standard/Enterprise
• Microsoft SQL Server 2017 Express/Standard/Enterprise

Ivanti has not performed testing with Microsoft SQL Server on Linux. Initial examination seems to indicate that it should work, as it provides the general SQL functionality necessary, however customers should use it at their own risk until further notice. Ivanti welcomes feedback from customers with experience or need to run Ivanti Endpoint Manager using MSSQL on Linux.

Important Note: Microsoft SQL Express editions are severely limited in CPU usage, memory usage and total database size. This can cause performance problems and even complete failure if those limits are exceeded. It should only be used in very small environments or test labs.

Remote Console

The Ivanti Managment Console is installed as part of the Core Server installation. Additional Remote Consoles can be installed as well to provide access to the Ivanti Manager/Endpoint Security tools and features. For Ivanti Endpoint Manager 2018, the Remote Console can only be installed and run on 64-bit systems.

Supported Operating Systems

• Windows 7 Professional, Business, Enterprise and Ultimate Editions x64
• Windows 8.1 Update 1 x64
• Windows 10 x64
• Windows Server 2008 R2 SP1
• Windows Server 2012 R2 x64
• Windows Server 2016 x64

Supported Platforms

For additional information on supported client platforms see: Supported Platforms and Compatibility Matrix for LANDESK Management Suite

Hardware Recommendations

Generic Guidelines

The following are some generic guidelines to get started. More details based on environment size listed below.

Virtualization Considerations

Ivanti Endpoint Manager can be run in physical or virtual environments. Ivanti Software does not certify any virtualization platform or hypervisor, nor any specific hardware vendor for the Core Server as the software does not interact at a such a low level. Virtualization of the Core Server, and other components is supported on-premise, co-located or in a private cloud, assuming all requirements are met. For co-located and private cloud installations, it is important to ensure that the network configuration allows for all necessary communications between the Core and other systems.Special consideration should be given to virtualized systems in regard to CPU Cores. Most hypervisors present a single hyperthreaded CPU as 2 separate CPU cores to guest operating systems. This can lead to confusion as a single hyperthreaded CPU core does not provide the same performance as two separate CPU cores. This can lead to performance bottlenecks as well as licensing complications for supporting software, such as Microsoft Windows and SQL. It is advised to check with an appropriate licensing specialist to ensure systems are licensed appropriately and costs are optimized to the best outcomes. Ivanti Endpoint Manager is licensed based on endpoint devices and/or users, and does not have any CPU licensing restrictions. All guidelines assume a standard full CPU "Core", not a "thread".

Discovery Services and Elasticsearch

Ivanti is constantly innovating and introducing new functionality to our customers. Discovery Services is a new and developing functionality intended to help customers better understand their environment and changes that may occur in the environment. Discovery Service is currently a beta product and not recommended for general production use. Discovery Services uses Elasticsearch as a backend data store. A basic installation is included with the install of Ivanti Endpoint Manager 2018 and can provide limited functionality. This document does not include information about Elasticsearch architecture or sizing. Ivanti also has a Discovery Services product that will be available in the cloud, and customer interested in the additional functionality are recommended to reach out to Ivanti for more details.

Additional Guidelines by Environment Size

Up to 750 Devices

All Ivanti Services on a single server

• Dual-core, 64-bit processor
• 8GB RAM
• 100/1000 Mb Network Adapter
• 100 GB of free disk space on 10K RPM or faster drives or arrays.
  • Drive/Array configuration
    • One drive or array for the operating system, Ivanti Endpoint Manager application and database application
    • One drive or array for the database and database logs

750 to 1,500 Devices

All Ivanti Services on a single server

• Quad-core, 64-bit processor. (Preferably two physical quad-core processors)
• 8+ GB RAM
• 100/1000 Mb Network Adapter
• 100 GB of free disk space on 10K RPM of faster drives or arrays
  • Drive/Array configuration
    • One drive or array for the operating system, Ivanti Endpoint Manager application and database application.
• One drive or array for the database and database logs. RAID 0, 5, 10, or an equivalent/faster redundant storage technology is recommended.

1,500 - 3,000 Devices

All Ivanti Services on a single server

• Two Quad-core, 64-bit processors (8 CPU cores total)
• 12 - 16+ GB of RAM or more
• Gigabit network adapter
• 3 storage arrays with 100 GB of free space each on 15K or faster drives
  • One array for the Operating System. RAID 0, 1, 5 or faster
  • One array for Ivanti Endpoint Manager software. RAID 0, 5, 10 or an equivalent/faster technology
  • One array for the database and database logs. RAID 0, 5, 10 or an equivalent/faster redundant storage technology

An Ivanti system for 1,500 to 3,000 devices all running on a single server could see performance issues with disk I/O depending on the use and configuration of both Ivanti and the storage arrays. Some tuning may be needed. As noted above, the arrays should be on separate spindles (physical disk) to reduce any resource conflicts.

3,000 to 5,000 Devices

Ivanti Core Server and Database Server on separate servers

For more recommendations and guidelines for an environment of this size, see Recommendations for tuning LDMS and MS SQL for large enterprise Core Servers

The Core Server

• Two quad-core, 64-bit processors (8 CPU cores total)
• 8 - 12 GB RAM
• Gigabit Network Adapter
• 2 arrays with 50 GB of free space per array on 15K RPM or faster drives
  • The operating system should be on an array of RAID 0, 1 or an equivalent/faster technology
  • Ivanti Endpoint Manager software should be on an array of RAID 0, 5, 10 or an equivalent/faster redundant storage technology

The Database Server

• Quad-core, 64-bit processors (4 CPU cores total)
• 16+ GB of RAM
• Gigabit Network Adapter
• Three arrays with 50 GB of free space per array on 15K RPM or faster drives
  • The operating system array should be RAID 0, 1 or an equivalent/faster technology
  • One array for the database. RAID 0, 5, 10 or an equivalent/faster redundant storage technology
  • One array for the database logs, RAID 0 or an equivalent/faster redundant storage technology

5,000 to 8,000 Devices

Ivanti Core Server and Database Server on separate servers

For more recommendations and guidelines for an environment of this size, see Recommendations for tuning LDMS and MS SQL for large enterprise Core Servers

The Core Server

• Two - three quad-core, 64-bit processors (8 - 12 CPU cores total)
• 8 - 12 GB RAM
• Gigabit Network Adapter
• 2 arrays with 50 GB of free space per array on 15K RPM or faster drives
  • The operating system should be on an array of RAID 0, 1 or an equivalent/faster technology
  • Ivanti Endpoint Manager software should be on an array of RAID 0, 5, 10 or an equivalent/faster redundant storage technology

The Database Server

• One - two quad-core, 64-bit processors (4 - 6 CPU cores total)
• 16+ GB of RAM
• Gigabit Network Adapter
• Three arrays with 75 GB of free space on 15K RPM or faster drives
  • The operating system array should be RAID 0, 1 or an equivalent/faster technology
  • One array for the database. RAID 0, 5, 10 or an equivalent/faster redundant storage technology
  • One array for the database logs, RAID 0 or an equivalent/faster redundant storage technology

8,000 to 12,000 Devices

Ivanti Core Server and Database Server on separate servers

Important: For Ivanti Endpoint Manager installations of this size, further tuning and design assistance from Ivanti Professional Services or from a valued Expert Solution Provider (ESP) may be required.

For more recommendations and guidelines for an environment of this size, see Recommendations for tuning LDMS and MS SQL for large enterprise Core Servers

The Core Server

• Three - four quad-core, 64-bit processors (12 - 16 CPU cores total)
• 24+ GB of RAM
• Gigabit Network Adapter
• 2 arrays with 75 GB of free space per array on 15K RPM or faster drives
  • The operating system should be on an array of RAID 0, 1 or an equivalent/faster technology
  • Ivanti Endpoint Manager software should be on an array of RAID 0, 5, 10 or an equivalent/faster redundant storage technology

The Database Server

• 2+ quad-core premium 64-bit processors (8 - 12 CPU cores total)
• 32+ GB of RAM
• Gigabit Network Adapter
• Three arrays with 100 GB of free space on 15K RPM or faster drives
  • The operating system array should be RAID 0, 1 or an equivalent/faster technology
  • One array of four or more disks for the database. RAID 0, 5, 10 or an equivalent/faster redundant storage technology
  • One array for the database logs, RAID 0 or an equivalent/faster redundant storage technology
• Microsoft SQL Server Enterprise Edition may be beneficial for environments of this size. Consult Microsoft for a detailed SQL Server Edition comparison.

12,000 to 16,000 Devices

Ivanti Core Server and Database Server on separate servers

Important: For Ivanti Endpoint Manager installations of this size, further tuning and design assistance from Ivanti Professional Services or from a valued Expert Solution Provider (ESP) may be required.

For more recommendations and guidelines for an environment of this size, see Recommendations for tuning LDMS and MS SQL for large enterprise Core Servers

The Core Server

• Four quad-core, 64-bit processors (16 CPU cores total)
• 36+ GB RAM
• Gigabit Network Adapter
• 2 arrays with 75 GB of free space per array on 15K RPM or faster drives
  • The operating system should be on an array of RAID 0, 1 or an equivalent/faster technology
  • Ivanti Endpoint Manager software should be on an array of RAID 0, 5, 10 or an equivalent/faster redundant storage technology

The Database Server

• Three - four quad-core premium, 64-bit processors (12 - 16 CPU cores total)
• 48+ GB of RAM
• Gigabit Network Adapter
• Three arrays with 100 GB of free space on 15K RPM or faster drives
  • The operating system array should be RAID 0, 1 or an equivalent/faster technology
  • One array of four or more disks for the database. RAID 0, 5, 10 or an equivalent/faster redundant storage technology
  • One array for the database logs, RAID 0 or an equivalent/faster redundant storage technology
• Microsoft SQL Server Enterprise Edition may be beneficial for environments of this size

16,000 to 25,000 Devices

Ivanti Core Server and Database Server on separate servers

Important: For Ivanti Endpoint Manager installations of this size, further tuning and design assistance from Ivanti Professional Services or from a valued Expert Solution Provider (ESP) may be required.

For more recommendations and guidelines for an environment of this size, see Recommendations for tuning LDMS and MS SQL for large enterprise Core Servers

The Core Server

• Four - five quad-core, 64-bit processors (16 - 20 CPU cores total)
• 48+ GB RAM
• Gigabit Network Adapter
• 2 arrays with 75 GB of free space per array on 15K RPM or faster drives
  • The operating system should be on an array of RAID 0, 1 or an equivalent/faster technology
  • Ivanti Endpoint Manager software should be on an array of RAID 0, 5, 10 or an equivalent/faster redundant storage technology

The Database Server

• Four - six quad-core premium, 64-bit processors (16 - 24 CPU cores total)
• 64+ GB of RAM
• Gigabit Network Adapter
• Three arrays with 150 GB of free space on 15K RPM or faster drives
  • The operating system array should be RAID 0, 1 or an equivalent/faster technology
  • One array of four or more disks for the database. RAID 0, 5, 10 or an equivalent/faster redundant storage technology
  • One array for the database logs, RAID 0 or an equivalent/faster redundant storage technology
• Microsoft SQL Server Enterprise Edition may be beneficial for environments of this size

More than 25,000 Devices

For Ivanti Management Suite installations of this size, additional tuning and design assistance from Ivanti Professional Services or from a valued Expert Solution Provider (ESP) is strongly recommended.

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

Issue

Core Server Activations can fail for a number of reasons, below is a list of some of the main things to check when activation is failing. This is not an all inclusive list but should cover most known issues.

Solution(s)

1. Verify that you can ping license.landesk.com from your core server; (ip address may vary)
   Ensure the registry key for Provider is set to LEGACY on the core.HKLM\software\LANDesk\managementsuite\licensing\provider OR HKLM\software\wow6432Node\LANDesk\managementsuite\licensing\provider)
   
2. Disable any AV that you may have running when attempting to activate.
3. Delete the contents in the LANDESK\Authorization files folder.
4. Locate the current windows temp folder using the %temp% command, then delete the contents in that folder.
5. Verify the "CertName" value under [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite\Setup] matches the value of the certificate file name under Landesk\Shared files\keys
   
6. Open the .0 file with notepad, verify the key=CertName
   
7. In the Shared Files\Keys folder on the core, be sure that the hash.0 file (that is bound to IIS) matches what is in the protect.ini file.
   
8. Verify that the LANDesk Management Usage Service is running on the core. Restart if you suspect an issue.
9. Check to see if you can activate the license on another core. This will prove or disprove an issue with the license itself. If an issue with the license is found then you should work with licensing.landesk.com to resolve.
   
   
   If your core activates successfully but you are still unable to login, you should check the verification date and grace period for your license to make sure it has not expired. Also verify the Product Name(s) and Product Version(s) for your license are correct.
   
10. Verify that the activating user belongs to the core's Built-in Administrators group.
11. Check the ldpgp files - Best Known Method for Troubleshooting Remote Console Activation Error
12. If these steps still don't work, reinstall the version of LANDESK that you are currently on. If on a flat of 9.5 or 9.6, just reinstall the flat version. If on a service pack, reinstall of the service pack is all that's needed.

Problem:

1. LDMS setup creates a SA user with a random password if you select SQL Express database during installation. The password can't be recovered. It has to be changed.

2. Unable to log into the SQL Express server because of a lost SA password.

Solution / Workaround:

Follow the steps below to reset the lost SA password. You may need domain admin access on the Core.

1. Login to the server as the default user who installed the core
2. Locate SQL Management Studio in the start menu
3. Login with Windows Authentication
4. Once you are logged into the SQL Server use the Object Explorer and locate the SA user. (Security > Logins)
5. Right-click on the SA user and select properties.
6. In the Login Properties update the "Password" and "Confirm Password" fields and click OK

If that doesn't work or if you don't have access to the account that installed LDMS on the core server, try the following steps:

1. Turn off all LANDesk Services (Here is a document that has a PS script to quickly disable all LANDesk services: How to Stop/Start all LANDesk Services at Once? (now with PowerShell)
   
2. Open an admin CMD prompt and Stop IIS (Very important step)
3. Open the Registry and navigate to "HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode"
4. Change the value of LoginMode from 2 to 1
   
5. Open the "Services" applet in the Control Panel
6. Locate the “SQL Server (LDMSDATA)” entry and open its properties
7. Enter “-m” into the “Start parameters” field
   
8. Start the service
9. Open a Command Prompt as an administrator
10. Enter the command:
    
    osql -S CORENAME\LDMSDATA -E
    
    *Note* Be sure to change CORENAME to whatever your server name is or you will get a big long message saying you messed up.
    
    
11. At the next prompts enter the following commands:
    
    1> alter login sa enable
    2> go
    1> sp_password NULL,'new_password','sa'
    2> go
    1> quit
    
    
12. Stop the “SQL Server (LDMS)” service
13. Remove the “-m” from the Start parameters field
14. Open the Registry and navigate to "HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode"
    

    Depending on the SQL install version, the path may be different. You can try searching for "LoginMode" in regedit to find this key as well.

15. Change the value of LoginMode from 1 to 2
    
16. Start the service
17. At this point you should be able to login to Management Studio using the SA user account and the new password you gave it.
18. Once you confirm that you can log into SQL Server with the new SA password, launch LANDesk Configure Services and update the SA password on the General Tab

Description

It is advised to run these steps prior to running any Ivanti installer (Full install or Service Update). There can be instances where an Ivanti EPM installer will fail or run into issues after installation. Below are best practices to follow when installing or updating the Core Server.

Prerequisites

1. Backup or snapshot your core server and your applicable databases (including the Core Server Database and the Workspaces Database).
   • With these backups available, you can quickly restore to a functional state if you run into errors.
     
     
2. Verify that your C drive and the drive you intend to install LANDESK onto have plenty of free space. For full specs, please visit: Ivanti Endpoint Manager 2017 Architecture - Overview
   
   
3. If upgrading to a new full release, verify Licensing for that version is listed in your product license.
   • You can verify this by opening the Core Server Activation and clicking on Licenses. This will show all the version assigned to your credentials.
   • Please contact support if you are missing any versions.
     
     
4. If having to use RDP to connect to your core server when running the install, use the admin switch for the RDP session.
   • This is done by running the RDP application with the admin switch "mstsc /admin".
     
     
5. Disable UAC, anti-virus, malware, and EPS software on the machine for the install.
   
   
6. Download the installer to the computer locally. Do not run from a network drive.
   
   
7. Before extracting the installer, right-click the file and go to Properties to Unblock the installer.
   • In the bottom right-hand corner of the properties window for the installer package there may be an Unblock button or check box. If this is there, unblock the file and then click Apply and OK.
   • It is critical to have the file be unblocked prior to running the LANDesk installer.

     8. Check version of Microsoft .NET that is installed and take actions appropriate for the version of EPM/LDMS that you are installing/updating to.

• You can use this document to check the version you have installed on your core server: How To: Tell What Version of .NET Framework Is Installed
• The following document goes over version specific .NET information and considerations .NET Considerations for EPM/LDMS on the Core and Remote Consoles

     9. DO NOT install the IIS role prior to installing your core. Ivanti will do this for you as part of the installer.

• LANDESK will incur problems during install if IIS is already installed and will not be able to proceed.
  
  

     10. Once the installer has been unblocked and extracted, run Microsoft Streams against the extracted location and install destination folders using the switches -s and -d.

• See the following document for information on how to run Microsoft StreamsStreams; and why you should remove them.
• Additional information on Streams can be found here - Streams
  
  

     11. Check to make sure the boot.wim is not mounted on the Core server.

• Follow this document if it is: How To: Cleanup WIM Images Before Upgrading/Patching Core

     12. Right-click the installer and click "Run as Administrator", even if logged on as an admin on the machine.

Conclusion

Thanks for taking the time to read through these best practices steps. If you have any suggestions to add to this list, please add a comment to this document so we can internally vet those suggestions and update this document as needed.

Overview

This document goes over supported minimum TLS levels for currently supported versions of Endpoint Manager. Minimum assumes that any higher level versions are also enabled.

TLS 1.2 support requires that the operating system and SQL server are properly configured to use TLS 1.2. Ivanti Support will not assist with the configuration of TLS 1.2.

Due to the amount of configuration necessary for TLS 1.2 only to function correctly, restricting your environment to TLS 1.2 only is generally not recommended unless you have a specific compliance need.

Supported TLS Versions

Issue

Remote console install fails during install with error "The Strong name verification system contains exclusion entries in the registry. Blocking access."

Resolution

1. Launch regedit on the computer that the console is being installed on.
2. Navigate to these two locations and delete additional folders beneath these keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\StrongName\Verification

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\StrongName\Verification

Issue

• During the LANDESK Management Suite installation, the Core certificate install to IIS fails
• A pop up window appears, reporting that SecureWebSiteInstall.exe has stopped working
• The installation process stops

Solution

SecureWebSiteInstall.exe runs successfully when the environment variable RANDFILE is not set.

If for some reason (for example because some third party application already set the variable) the environment variable is already set, the executable fails to install the Core certificate to IIS.

• From the Start menu, right click Computer and select Properties, then click on Advanced system settings.
  
• Select Environment variables and remove the RANDFILE variable, verifying both the User and System variables sections.
• Restart the LANDESK Management Suite setup.

When the setup installs successfully the Core certificate to IIS, you will see the following entries in the installation log file names LANDesk.Install.LDMS_yyyy-mm-dd hh_mm_ss.log in the directory %ProgramData%\LANDesk\ManagementSuite\Install\Version#\Log:

INFO: Executing: C:\Program Files (x86)\LANDesk\ManagementSuite\SecureWebSiteInstall.exe "LANDesk_1391606962" landesk/managementsuite/core/ssl landesk/managementsuite/core/ssl/information     (Launcher.ExecuteXmlCommand())

INFO: Notifying ProcessBegin: C:\Program Files (x86)\LANDesk\ManagementSuite\SecureWebSiteInstall.exe     (Launcher.ExecuteXmlCommand())

INFO: Execution of SecureWebSiteInstall_Core completed. Return code: 0, State: Success     (SetupController.ExecuteNextCommand())

Problem:

Error: "Unable to Build Core Server Activation File" when activating the core server.

Solution / Workaround:

Delete all temporary files

1. Check That you have plenty of disk space available for the drive that hosts "\Program Files\LANDesk\Authorization Files".
2. Navigate to "\Program Files\LANDesk\Authorization Files" and delete all the files in this location.
3. Navigate to "%temp%" and delete all the files in this location.
4. Navigate to "C:\Windows\Temp" and delete all the files in this location.

Make sure correct certificate is being used.

1. Check this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\ManagementSuite\Setup - Certname
2. Verify if the "Certname" from above matches the certificate name in "\Program Files\LANDesk\Shared Files\Keys". If not, adjust the registry to show the proper name. NOTE: The certificate name will not have the file extension in the registry
3. Check that "protect.ini" is referencing the correct <hashname>.0 file and that .0 file has the correct core server name.

Replace ldpgp

1. There are 2 files that you would replace; ldpgp.exe and ldpgp.sig. These files are used to encrypt the license files and can sometimes become corrupt.
2. Replace these two files with the ones from the installer. Here is the location from the 9.6 flat installer: "\LANDeskSoftware960\LANDESK\LDMS\Program Files 64\LD\MS\_non"
   1. ldpgp.exe - \Program Files (x86)\LANDesk\Shared Files, \Program Files\LANDesk\ManagementSuite
   2. ldpgp.sig - \Program Files\LANDesk\ManagementSuite

More Helpful links:

Unable to Build Activation File

Error "Unable to build the core server activation file" when attempting to activate the LDMS Core Server

Troubleshooting Core Server Activation

Questions:

• When will LANDESK Support Windows Server 2016 as a Core Server?

  • This is supported in the 2017.1 and newer releases.
    
    

• When will LANDESK Support Windows Server 2016 as a remote console?

  • This is available in the 2017.1 SU1 update
    
    

• When will LANDESK Support Windows Server 2016 as a client?

  • This is available in the 2017.1 and later releases
    

  • This is available in the 2016.3 SU3 release

For further Supported Operating System Information: Supported Platforms and Compatibility Matrix for LANDESK Management Suite/Ivanti Endpoint Manager