Issue

The install of LANDESK 2016 fails at the step "Is Database Ready for Upgrade?"

Resolution

There are some prerequisites that will be checked and cause it to fail:

     1. Core Rollup enabled - the upgrade will fail if Core Rollup has been enabled. This needs to be disabled for the upgrade.

     2. DB User Rights - the database user configured in LANDESK Configure Services is the user being used for the upgrade. This user needs to have sys_admin rights in the database itself. Not having these rights will cause the upgrade to fail.

     3. In IIS right click on default website > edit bindings > edit https > ensure that the 'hostname' field is blank

If the upgrade still fails after these prerequisites have been set, there are some troubleshooting steps listed below:

     1. On the core server, open regedit. Navigate to key

          HKLM\Software\LANDESK\ManagementSuite\Core\Connections\Local

          The value for isNTLM needs to be set to "False".

At this point, the install may continue past the database check and fail at the step for "Installing CBA8"

     1. See this document on how to fix this error - Error: Execution of CBA8InstallCommand during inline upgrade from LDMS 9.5 - 9.6 and upgrade to LDMS 2016

          ***Note*** The file location on your machine may vary a little bit, depending on where you extracted the installer to. For the default file location for the 2016 extractor, the folder is C:\LANDESKSoftware2016\LD\MS\PF\LD\MS\_non\ldlogon.

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

Applies to Ivanti Endpoint Manager 2017 (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

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.

Oracle 11g

Oracle is not a supported database server for Endpoint Manager 2017

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 2017, 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 x64
• Windows 10 x64
• Windows Server 2008 R2 SP1
• Windows Server 2012 x64
• 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.

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 2017 and can provide limited functionality. This document does not include information about Elasticseach architecture or sizing. Customers should contact Ivanti Support for additional information if using Discovery Services in production, or using Concorde solutions with Ivanti Endpoint Manager.

Additional Guidelines by Environment Size

Up to 750 Devices

All Ivanti Services on a single server

• Dual-core, 64-bit processor
• 6GB 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)
• 6 - 10 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)
• 12+ 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)
• 6 - 10 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

• Two quad-core, 64-bit processors (8 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

• Four quad-core, 64-bit processors (16 CPU cores total)
• 20+ 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

• 3+ quad-core premium 64-bit processors (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)
• 20+ 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 quad-core premium, 64-bit processors (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 quad-core, 64-bit processors (16 CPU cores total)
• 32+ 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.

This document covers the installation for Ivanti Endpoint Manager 2017.

This product was formerly known as LANDESK Management Suite or LANDESK Security Suite.

Issue

Running any scans from the console result in The request failed with HTTP status 404: Not Found.

IIS logs shows a response of 404 2

Cause

ISAPI and CGI Restrictions are improperly configured.

Resolution

1. Open IIS Manager
2. Click on the server level
3. Double-click on ISAP and CGI Restrictions
4. Make sure all restrictions are set to allowed.
5. From an administrator command prompt, run IISreset
6. Try again

More Info:

You can view HTTP status codes at https://support.microsoft.com/en-gb/help/943891/the-http-status-code-in-iis-7.0,-iis-7.5,-and-iis-8.0

• Overview
• Installation
• Database Setup
  • SQL Management Studio
  • Creating The Database
• General Configuration

Overview

This document goes over how to install SQL Server 2016 for use with Ivanti Endpoint Manager(EPM). This document assumes you have downloaded SQL Server 2016 Standard or above (i.e. not SQL Express).

The examples provided are for an environment where SQL Server and EPM are on different servers. However, the steps apply to when both are on the same server as well.

This guide does not take into account requirements for large enterprises or specific SQL Server configurations such as clustering, high availability, performance tuning, replication, etc.

Installation

The steps below will guide you through installing SQL Server 2016.

1. Mount your downloaded SQL Server .iso file. This can be done by double-clicking on the file.
2. Run Setup.exe as an administrator in the mounted disc.
3. Select Installation > New SQL Server stand-alone installation or add features to an existing installation
4. On the next window, check the box to check for updates if you want, then hit next.
5. Head through the subsequent screens until you get to Feature Selection.
6. Install the Database Engine Services feature at least. You may also want to install Reporting Services - Native if you want to run reports, and SQL Server Replication if you're using a Rollup Core as well, and intend to roll up this database. Hit Next.
   
7. On the next page, you can decide on a name for your SQL instance, or leave it at the default. Unless you have a need to name the instance, it's usually easier to just leave it at the default.
8. On the Server Configuration page, you can leave the Service Accounts and Collation at their defaults. Hit Next.
9. On the Database Engine Configuration Page, enable Mixed Mode authentication and specify an SA password. Use "Add current user" to add your windows user to the SQL Server admins, and add anyone else that should have access using the "Add" button.
11. Head to the "Data Directories" tab and specify Data, log and backup directories if you desire. Refer to this document for recommendations based on your node count.
12. TempDB and FileStream tabs can be left at defaults. Hit next.
13. If you decided to install Reporting Services, you'll now have a Reporting Services configuration page. Leave it at "Install and configure" and hit next.
14. Now you're ready to install. Review this final page to see if anything is missing or incorrect. If everything looks good, hit "Install".

Database Setup

SQL Management Studio

Setting up the database will be easiest using SQL Management Studio. To acquire SQL Management studio, you can have 2 main options:

• Download it from here
• Select the "Install SQL Server Management Tools" option in SQL Server Installation Center.

Creating The Database

1. To create the EPM database, launch SQL Server Management Studio and log in.
2. Right click on "Databases" in your Object Explorer, and select "New Database".
4. Name the database, and hit "Ok". The database should then be created.

You can now specify this database during your install of Ivanti Endpoint Manager. The installation will take care of creating the schema and populating the necessary data.

General Configuration

In addition to the above, the below items should be considered regarding overall configuration.

• EPM uses a SQL account. You may want to create a separate SQL account specifically for LDMS instead of using the SA account.
• By default, when a database is created, it uses the Full recovery model. This can cause excessive transaction log growth. Switching to a Simple recovery model is recommended, as long as you create regular backups.
• Check out our database maintenance schedule recommendations here

Question

Can a Core Server be renamed once installed?

Answer

No. It is not supported to rename the Core Server.  If the Core Server must be renamed, the system should be rebuilt starting with a new installation of the Windows Server operating system the media or from a stable base image.

Problem

During a console install, you may run into a failure installing Microsoft Visual C++. Below is what the install log will show:

2018-09-05 21:59:34 INFO: Executing command VC14Command (SetupController.ExecuteCurrentCommand())

2018-09-05 21:59:34 INFO: Executing: C:\Ivanti2018-1\Microsoft Visual C++ Redistributable\14\vc_redist.x86.exe /q (Launcher.ExecuteCommandEx())

2018-09-05 21:59:36 ERROR: Execution of VC14Command completed. Return code: 1638, State: Failure (SetupController.ExecuteCurrentCommand())

Cause

Machine already has a newer version of C++ installed and we cannot install C++ 2015 because of it. Sometimes this is installed with the latest version of Visual Studio.

Solution

• Uninstall the newer version of C++ (2017) from "add and remove programs"
  • If you are unable to remove this, you may need to reach out to support.
• Reboot
• Run install as admin

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?

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.

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

Issue

Activating the Core Server results in the error:  "Unable to Build Core Server Activation File."

Cause

1. The Core Servers Device ID does not exist in the following registry location. HKLM\Software\LANDesk\Common Api
   NOTE: on Windows 2008 R2 server the relevant keys are under theHKLM\Software\Wow6432Node\LANDesk and the files are under the directory C:\Program Files (x86)\LANDesk\Shared Files

2. The .crt file referenced in the registry of the Core Server does not match the .crt in the Program Files\LANDesk\Shared Files\Keys folder.

3. Through the GPO the group policy "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" has been enabled.

Resolution

1. The Core Servers Device ID does not exist in the following registry location. HKLM\Software\LANDesk\Common Api The device id should be created on install or during an inventory scan of the Core Server.
   If it is not, copy this key from HLKM\Software\Intel\LANDesk\Common Api

   • Browse to the HLKM\Software\Intel\LANDesk\Common Api\UniqueID key.

   • Export the key.

   • Edit it to reflect the new path: HLKM\Software\LANDesk\Common Api

   • Import the modified key.

   • Retry to activate the core server

2. The name of the certificate created on install is referenced in the following registry key: HKLM\Software\LANDesk\ManagementSuite\Setup\CertName This file needs to exist in the C:\Program Files\LANDesk\Shared Files\Keys.

For the activation process to work properly the original .crt and .key file have to be present in the C:\Program Files\LANDesk\Shared Files\Keys folder.

If the server has been reinstalled it needs to be the Cert Created during the most recent install.

It is possible that after the install the user may have deleted or renamed these files. If this is the case the files will need to be renamed back to the original name. If the original .crt, and .key files were deleted the core will need to be rebuilt.

Open the Core Server Activation Utility.  Click the Licenses button.  Check for anything that says something like "Upgrade-Sub". If it is expired, or there, call Ivanti Support to have the licensing team deauthorize the core server.
After its done, try to reactivate the core.

3. Disable the group policy "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" and reboot the core server before to retry the activation process.

    More details about this particular issue are available here: Error "Unable to build the core server activation file" when attempting to activate the LDMS Core Server

Errors in ...\landesk\managementsuite\ldmain\CoreDBUtil.exe.log as below:

System.Data.OleDb.OleDbException: Cannot drop the view 'ReplLENOVOBATTINFOV' because it is being used for replication.

  at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)

  at System.Data.OleDb.OleDbCommand.ExecuteNonQuery()

  at LANDesk.ManagementSuite.Database.Database.ExecuteNonQueryP(String sql, Int32 timeoutSeconds, Object[] parameters)

  at LANDesk.ManagementSuite.Database.Database.ExecuteNonQuery(String sql, Int32 timeoutSeconds, ArrayList oleDbParameters)

There should be a lot of this kind of errors, all about cannot drop a view named "repl*" because it is being used for replication

Root cause

There are rollup cores configured.

Solution

Disable replication following the article below:

https://community.landesk.com/support/docs/DOC-35699

Remove all repl views using scripts below:

declare @cmd varchar(4000)
declare cmds cursor for
select 'drop view [' + Table_Name + ']'
from INFORMATION_SCHEMA.VIEWS
where Table_Name like 'Repl%'

open cmds
while 1=1
begin
fetch cmds into @cmd
if @@fetch_status != 0 break
exec(@cmd)
end
close cmds;
deallocate cmds

After the upgrading is done, please manually set up the rollup configuration again.

Issue

EPM 2017.3 Core Server setup / installation is failing on the step "Configuring system settings"

Failed

Configuring system settings

On the target EPM 2017.3 Core Server a log file C:\ProgramData\LANDesk\Log\LANDesk.LANDesk.Common.RunMethod_%DATE%%TIME%.log reports

2018-02-26 15:38:12 INFO: Path to assembly: E:\LANDesk\ManagementSuite\.\Install Only Files\IdentityServerConfig.dll

2018-02-26 15:38:12 INFO: Class name: Setup

2018-02-26 15:38:12 INFO: Method name: ConfigureStandalone

2018-02-26 15:38:12 INFO: Arguments

2018-02-26 15:38:12 INFO: Searching assembly for types: IdentityServerConfig.Class1

2018-02-26 15:38:12 INFO: Does class: class1==setup

2018-02-26 15:38:12 INFO: Searching assembly for types: IdentityServerConfig.IdentityServerClient

2018-02-26 15:38:12 INFO: Does class: identityserverclient==setup

2018-02-26 15:38:12 INFO: Searching assembly for types: IdentityServerConfig.Setup

2018-02-26 15:38:12 INFO: Does class: setup==setup

2018-02-26 15:38:12 INFO: Found class?: True

2018-02-26 15:38:12 INFO: Try to run method: ConfigureStandalone

2018-02-26 15:38:12 INFO: Run method: ConfigureStandalone

2018-02-26 15:38:12 INFO: Run method with: 0 parameters

2018-02-26 15:38:12 ERROR: Error running method: ConfigureStandalone Message: Exception has been thrown by the target of an invocation.

2018-02-26 15:38:12 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

On the Core Server modified a file C:\ProgramData\LANDESK\ServiceDesk\My.IdentityServer\tps.config -- changed the the tags to <configuration> and </configuration> from <Configuration> and </Configuration> and clicked on the button "Try again".

Setup completed the step "Configuring system settings" successfully and moved on to the next step.

How To

For some reasons, you want to test a new version of LDMS version in the future production infrastructure (New Core Server) but you don't want yet to upgrade the production database.

The scenario would be;

• You have LDMS 9.5 Core Server, named LDMS95Core, with the Windows Server 2008R2 OS
• You have a Database Server, named LDMSDatabase, where the Production Database is which is named LDMSDBPROD
• You have a brand new server, named LDMS96Core, with the Windows Server 2012R2 OS
• You have a SQL Server where the Test Database is named LDMS96DBTEST
• LDMS96Core will be the future Production Core Server with LDMS Core Server version 9.6.
• LDMS96Core will be also the Test Core Server with LDMS Core Server version 9.6 on which you will

Steps

1. On a SQL Server, create a new database called LDMS96DBTEST
2. Install 9.6 Core Server on the LDMS96Core server by referring to the DB LDMS96DBTEST > At this stage, you can test the new LDMS version on a Test Database.

At a point, you may decide to make LDMS96Core server as the 9.6 Production Core Server. Here are the steps:

1. Do an "In-place" upgrade of the LDMS95Core server > It will then upgrade the LDMSDBPROD DB to version 9.6
2. On the LDMS96Core server, go to Start > Programs > LANDESK > Double Click on "LANDESK Configure Services" and a Window called "Configure LANDESK Software Services" will open
3. On tab "General", change the following items to point the DB to the "Production Dabase" called LDMSDBPROD (see below - put also your own credentials of course)
4. And restart all the LANDESK services (See article How to Stop/Start all LANDESK Services at Once? (now with PowerShell))

Other Interesting Links:

• Upgrading to 9.6: Making your LDMS 9.6 upgrade installation easier and How to do an EPM (Formerly LDMS) Side by Side Migration Process (All Versions)
• Installing 9.6: Best Known Methods for Installing LANDESK Management Suite 9.6 (with videos)

Issue

Getting error "Authentication failed because a certificate was not found on the remote computer" when remote controlling

Cause

The new server has a different set of certificates than the old server had, so the clients cannot communicate with the new core server.  The new core server certificate has the same name as the old server, so it is necessary to reinstall the server with a different certificate name and then copy the certificate files from the old core to the new

Resolution

Copying certificate/private key files among core servers

An alternative to deploying certificates (<hash>.0) to devices is to copy certificate/private key sets among cores. Cores can contain multiple certificate/private key files. As long as a device can authenticate with one of the keys on a core, it can communicate with that core

When using certificate-based remote control, target devices must be in the core database.

If you're using certificate-based remote control security with devices, you can only remote control devices that have an inventory record in the core database that you're connected to. Before contacting a node to launch remote control, the core looks in the database to ensure the requesting party has the right to view the device. If the device isn't in the database, the core denied the request.

To copy a certificate/private key set from one core server to another

1. At the source core server, go to the \Program Files\LANDesk\Shared Files\Keys folder.

2. Back up the source server's <keyname>.key, <keyname>.crt, and <hash>.0 files.

3. At the destination core server, copy the files from the source core server to the same folder (\Program Files\LANDesk\Shared Files\Keys).
The keys take effect immediately.   Care should be taken to make sure that the private key <keyname>.key is not compromised. The core server uses this file to authenticate devices, and any computer with the <keyname>.key file can perform remote executions and file transfer to a Management Suite device.

4. In addition the .0 file from the old core should be copied to the LDLOGON share on the new server.

Purpose

This article covers how to check for existing mounted WIM files. When applying Service Packs, Component Patches, or Upgrading versions, mounted *.wim files can cause OSD.Upgrade.exe to fail.

Related: https://community.landesk.com/support/docs/DOC-24702

Check for Mounted WIM files

• Open a CMD window as Administrator
• Run the following command to find all mounted WIM files

dism /get-MountedWiminfo

Were any Mounted WIM files found?

No mounted images found

• If  the results indicate 'No mounted images found.' proceed to Cleanup WIM

Yes, mounted images were found

• If any mounted images are found, the image file and the mounted directory will be listed.
• These mounted .WIMS must be unmounted before an upgrade can take place. Continue to Unmounting WIM files.

Unmount WIM Files

If mounted images were found, they will need to be unmounted before an upgrade can be run.

There are 2 options at this point, Commit the changes to the mounted WIM, or Discard the changes to the mounted WIM.

• Commit - Saves changes to a mounted WIM image
• Discard - Do not save changes to the WIM image

Decide which option is right for you, and progress to the corresponding section.

Commit the Changes

• Open a CMD window as Administrator
• Use the Mount Directory we previously found in the following command:

Dism /Commit-Image /MountDir:"mount directory"

• Proceed to Cleanup WIM

If you receive an error, please check this document: Error when unmounting WIMS

Discard the Changes

• Open a CMD window as Administrator
• Use the Mount Directory we previously found in the following command:

Dism /Unmount-wim /MountDir:"mount directory" /discard

• Proceed to Cleanup WIM

Cleanup WIM

At this point, there should be no remaining mounted wim files. Though it is not required

to Cleanup the WIM connections after every time a WIM image is mounted/unmounted, we want to do it as our last step here as a precautionary measure.

• Open a CMD window as Administrator
• Run the following command to clean up WIM connections

Dism /cleanup-Wim

With all WIM's unmounted, and the connections having been 'cleaned up', you should be prepared to continue with the other required pre-req checks for upgrading/patching etc.

Issue

When upgrading the LDMS core to 9.6 the prerequisite check fails if there is a full agent installed.

Resolution

Run uninstallwinclient.exe from c:\program files (x86)\landesk\management suite\ldmain\

If the keys folder is missing (c:\program files (x86)\landesk\shared files\keys\) the core upgrade will fail.

Applies to LANDesk Management Suite 9.6 (The information here may also generally apply to other versions of LANDesk Management Suite. Verify before planning any architecture)

LANDESK Management Suite and LANDESK Security Suite 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 LANDESK 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. LANDESK 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 LANDESK "environment". The servers, equipment and software that provide various services or functionality key to a smooth running LANDESK 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.

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 or Oracle)
• Mobile Device Management Server (MDM)
• 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.

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 2008 R2 should match the language LANDESK 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 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

Microsoft SQL Server 2005 Express is only supported if doing an in-place upgrade of an existing "all-in-one" Core Server/DB. Microsoft SQL Server 2008 Express can be installed during the LANDESK Core Server setup if needed.

Important Note: Microsoft SQL Express editions are severly 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.

Oracle 11g

Oracle 11g is supported for in-place upgrades only with Windows Server 2008 R2 as the Core Server.

• Oracle 11g Release 2 (11.2)
  • The Core Server and remote consoles should have the Oracle 12c client installed

For more information about Oracle please see: Upgrading Oracle Client to 64-bit (prior to core upgrade)

Selecting a Database Server

When considering what database server software to use, many considerations come into play such as existing licenses, systems and organizational experience and knowledge. LANDESK Management Suite supports both Microsoft SQL and Oracle. However in independent (non-LANDESK) testing of database systems, Microsoft SQL has been found to have better performance for the type of database access and use employed by LANDESK. Therefore, LANDESK Software recommends Microsoft SQL Server for the best experience.

Critical Note: LANDESK Mobility Manager (LDMO) does not currently support Oracle. If you intend to manage mobile devices, such as phones and tablets now or in the future, you must use Microsoft SQL Server

         

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 9.6, the Remote Console can only be installed and run on 64-bit systems.

Supported Operating Systems:

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

Supported Client Platforms

For 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.

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 to 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

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 to 16 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

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

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

• 3+ quad-core premium 64-bit processors (12+ CPU cores total)
• 16 GB to 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

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

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)
• 16 GB to 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.