LANDESK Management Suite 2016 Install Guide

LANDESK Global Services
Best Known Methods for Installing

LANDESK 2016
Prepared by Bryce Stringham
LDMS 9.6
WWW.LANDESK.COM | REVISION: <REVISION 2>

SUPPORT.LANDESK.COM LAST UPDATE: February 4th, 2016
Best Known Methods for Installing LDMS 2016
Contents
Introduction .................................................................................... 3
Scope ............................................................................................... 3
Installing/Upgrading to Management Suite 2016 - Check List ..... 4
Assumptions.................................................................................... 7
Step 1 - Planning the Installation/Upgrade................................... 7
Step 2 - Backing-up the Existing Core Server .............................. 16
Step 3 Preparing for the Management Suite 2016 Core Server
Installation .................................................................................... 22
Preparing Microsoft Windows 2012 R2 Server for a New
Management Suite 2016 Installation ........................................... 22
Step 4 - Implementation the Installation/Upgrade Procedure .. 25
Log Location and Troubleshooting ............................................. 38
To the maximum extent permitted under applicable law, LANDESK assumes no liability whatsoever, and disclaims any express or implied warranty, relating to
the sale and/or use of LANDESK products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any
patent, copyright or other intellectual property right, without limiting the rights under copyright.
LANDESK retains the right to make changes to this document or related product specifications and descriptions, at any time, without notice. LANDESK makes
no warranty for the use of this document and assumes no responsibility for any errors that can appear in the document nor does it make a commitment to
update the information contained herein. For the most current product information, please visit www.LANDESK.com.
Copyright 2014, LANDESK Software, Inc. and its affiliates. All rights reserved. LANDESK and its logos are registered trademarks or trademarks of LANDESK
Software, Inc. and its affiliates in the United States and/or other countries. Other brands and names may be claimed as the property of others.
WWW.LANDESK.COM | SUPPORT.LANDESK.COM 2
Introduction
The purpose of this guide is to cover the Best Known methods for installing or upgrading a LANDESK Management
Suite Core Server to Management Suite 2016. In this guide we will discuss considerations when performing a clean
install, an in-place upgrade, and an upgrade on a new server (side by side). Once the Management Suite Core Server
has been installed the final steps for configuration are the same. In order for this document to best help in your
installation or upgrade, find the section that matches what method will be used until the common configuration
section.
Method 1 New Installation
Method 2 In-place Upgrade
Method 3 Clean Core Server Install with an Upgraded Database
Method 4 Test or Lab Core Becomes Production
Method 5 Side-by-side Migration
Scope
This guide is designed to provide an experienced LANDESK Administrator with the information needed to make
choices during a Core Server install or upgrade. It should help in the choices concerning the database, Operating
System, and the Management Suite application.
When preparing to install LANDESK Management Suite 2016, decisions must be made about the speed, memory,
storage and network cards. Decisions must also be made on how many Core Servers and when to separate the
database server from the Core Server.
This guide will cover the following:
Step 1 Planning the Installation/Upgrade Procedure
Step 2 Backing-up the Existing Core Server
Step 3 Preparing for the Management Suite 2016 Core Server Installation
Step 4 Implementation the Installation/Upgrade Procedure
Installing/Upgrading to Management Suite 2016 - Check List

The following three pages contain a check list you can print out to help make sure that all the tasks involved in
installation of or upgrade to Management Suite 2016 are completed and to log who performed and accomplished
each task.
Planning the Installation/Upgrade Procedure

o I reviewed the installation/upgrade options and I have planned the installation procedure Initials: __________
o I have documented decisions here: ___________________ Initials: __________
o I have gathered any necessary network information Initials: __________
o I have chosen the LANDESK features and components to implement Initials: __________
o I have chosen the both Core Server hardware and the operating system Initials: __________
o I have chosen the database hardware, Operating System, and database software Initials: __________
o I have chosen the installation/upgrade procedure Initials: __________
o I have determined the Domain Policies and other security requirements to apply to the Core Server
Initials: __________
Backing-up the Existing Core Server

o I have backed up the Core Server Initials: __________
o I have backed up the LANDESK database Initials: __________
o I have backed up the Core Servers critical files Initials: __________
o I have backed up any other need files or information Initials: __________
Preparing the Core Server for Installation/Upgrade

o I have obtained licensing for Management Suite 2016 or plan to evaluate with the 45-day trial
o The Core Server Operating System has been installed and patched. Initials: __________
o All the necessary prerequisites applied Initials: __________
o I determined the name for the Core Server ___________________ Initials: __________
o I have obtained the LANDESK installation software and made sure the installer file is for the correct version.
o I have obtained the proper Domain credentials to be used for the LANDESK Scheduler Service and Com+
Applications ___________________ Initials: __________
o I have chosen a certificate name and verified that it is not the same name as a previous certificate name
___________________ Initials: __________
o I have a Unicode database instance created and ready for the Management Suite 2016 installation
Installing/Upgrading
o I installed Management Suite 2016 and any other feature sets needed Initials: __________
Restoring Files and Settings

o All critical files and other files and settings have been restored Initials: __________
Verifying the Core Server Installation

o I verified the installation was successful and performed any required tests Initials: __________
Performing Post-Installation Configuration

o I configured the LANDESK Scheduler Service account with a domain account Initials: __________
o I configured the Com+ Application Identities with a domain account Initials: __________
o I configured Local Intranet and Trusted Sites in IE and Explorer Initials: __________
o I added the users to the LANDESK Management Suite local group, and LANDESK Administrators group
o The Windows Firewall is properly configured or disabled Initials: __________
o Flash Player is properly installed on the Core Server (Even with the 32 bit Console, such features as Reporting
and Alerting will require flash to be installed) Initials: __________
o A database maintenance plan has been implemented Initials: __________
o A plan for consistent Core Server and database backups is implemented Initials: __________
Assumptions
This document assumes that:
1. The reader is knowledgeable in Microsoft Windows Server 2008 (In-Place upgrade only), Microsoft Windows Server
2012, and Microsoft Internet Information Server (IIS) management.
2. Microsoft SQL Server 2008, 2012 or 2014 database is installed and configured using the LANDESK Database
installation guides found in the community. http://community.LANDESK.com.
Step 1 - Planning the Installation/Upgrade

Before beginning, a plan should be made to determine the best installation procedure for your environment.
This should be based on the following items:
Documenting All Decisions when Planning
Gathering Network Information
Choosing the LANDESK Components to Implement
Choosing the Core Server Operating System
Choosing the Core Server and Database Hardware
Selecting the Database software: MS SQL 2008, 2012 or 2014
Choosing the Installation/Upgrade Procedure
Determining the Domain Policies and other Security Requirements to Apply to the Core Server
Documenting All Decisions when Planning

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

There are many network concerns that must be addressed including but not limited to the following:
Determine the IP address, Hostname, and FQDN of Core Server and other servers
Important: Once the Core Server is installed, the name cannot be changed.
Estimate of total number of devices on which the LANDESK agent will be installed
A diagram of the network and any and all sites involved
Gather the type of Operating Systems that will have the LANDESK agent installed (Windows, MAC, Linux, etc.)
Noting any network appliances that may exist between the Core Server and agent workstations such as
firewalls and caching appliances.
Noting any network appliances that may exist between the Core Server and the Internet.
Note: Some of these network appliances may need to have exceptions added or be bypassed all together for traffic
between the Core Server and the agent workstations.
Speed of network connections between the Core Server and the agent workstations
Proxy server configuration (The Core Server must be configured to bypass the proxy to talk to itself and other
local sites)
Core and Clients be in the same domain (recommended) or all in the same workgroup (not recommended). If
core and clients are not in the same domain, they need to have a trust relationship between the domains.
There may be other concerns that are not listed above that are particular to your environment and these should be
noted as well. If you are working with Professional Services any such particulars should be immediately brought to
their attention.
Choosing the LANDESK Components to Implement

LANDESK solutions have many features that can be implemented and each feature may lead to different
requirements.
When installing Management Suite 2016, all Management Suite features are installed but the license you purchase
will determine which features are activated and which are not. There are many features some of which, though not
all, are listed below.
LANDESK Management Suite
o Inventory and Software License Monitoring
o Software Distribution / Application Virtualization
o Remote Device Management through the Management Gateway
o Operating System Deployment / Provisioning
o Remote Control
LANDESK Security Suite
o Patch Management
o Antivirus / Spyware
o Host Intrusion Protection System (HIPS)
Different features may lead to different hardware requirements.
For example, a server that will be used for all features of both Management Suite and Security Suite will utilize more
memory and processor resources than one that is used for Inventory only.
Another example is if Software Distribution and Operating System Deployment are going to be implemented, a share
server may be needed to store the images and software packages. This may be an existing server, a new server, or
even a separate drive on the Core Server.
Choosing the Core Server Operating System
The Core Server can be installed on the following platforms:
Microsoft Windows 2012 R2 Server 64-bit
Microsoft Windows 2008 R2 Server 64-bit (In-Place Upgrade Only)
It is expected that any new installation will use Microsoft Windows 2012 R2 64-bit.
Note: If Microsoft has released a new service pack for any of these operating systems, check with LANDESK
Support before applying it.
It is also expected that the Operating System is installed clean just prior to the Core Server installation and is not
already running other third party applications.
Microsoft Windows 2012 R2 Server Platforms and Software Requirements

Microsoft Windows Server 2012 R2 Standard (64 bit)
Microsoft Windows Server 2012 R2 Enterprise Edition (64 bit)
Core Server must be installed as a standalone server
A Clean Installation of the Operating System is Recommended
The servers should be dedicated to hosting LANDESK Management Suite
Important: The following items are NOT supported for the Core Server installation:
A Primary Domain Controller (PDC), Backup Domain Controller (BDC), or an Active Directory
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
Virtualizing the Core Server

One of the main reasons for virtualization is to fully utilize your hardware. If multiple servers are hardly used, often
termed slacker servers, then they could potentially be handled by one physical server. The Core Server, however, is
NOT a slacker server and usually fully utilizes the hardware allocated.
There are some other benefits of virtualization, such as backup features, snapshot features, etc., that may lead you to
want to put the Core Server inside a virtual environment. While the Core Server can be installed in a virtual
environment, remember that the hardware requirements listed still apply and that the hardware allocated should not
be shared with other virtualized servers.
Selecting the Database Software: MS SQL 2008, 2012 or 2014

When choosing the database software there exists four choices:
Microsoft SQL 2008 R2
Microsoft SQL 2012
Microsoft SQL 2014
The hardware requirements have already been covered and any of the listed database software is fully supported.
One way to determine which database software to use is to look 1) what database software you are currently using
and 2) Is there already an SQL administrator that has strong skills in MS SQL. Cost and the ability to hire a database
administrator should also be evaluated. Oracle database servers are no longer support, even in an upgrade scenario.
Database Documentation
LANDESK Management Suite Microsoft SQL Server 2012 Configuration
http://community.LANDESK.com/support/docs/DOC-26993
SQL Tuning and Maintenance
https://community.landesk.com/support/docs/DOC-39315
Reindexing LANDESK Databases
http://community.landesk.com/support/docs/DOC-4362
Choosing the Installation/Upgrade Procedure

When it is time to upgrade there are multiple choices that have to be considered and the pros and cons of each
should be analyzed to see what best works for your environment.
The following table lists some of the various choices that can be made when upgrading a Core Server. These are not
all the possible combinations but a general overview of command types.
Install/Upgrade Method Core Server Database

Clean install on the same or on New clean database instance
New Installation
new server hardware
Upgrade existing server. Backup Same database upgraded during

In-Place Upgrade
server prior to upgrade. install. Backup database prior to
upgrade.
Clean install on the same or on Upgraded Database instance

Clean Core Server Installation
new server hardware
with an Upgraded Database
Upgrade existing server. Backup Same database upgraded during
Test or Lab Core Becomes
server prior to upgrade. install. Backup database prior to
Production
upgrade.
New server hardware that will be Multiple options: new database

Side-by-side Migration
configured while the current instance, upgraded database.
server hardware is hardware
running.
Certified LANDESK Deployment

Because each environment has different needs, it recommended that you contact your reseller or Expert Solution
Provider (ESP) about the Certified LANDESK Deployment. If you are unsure who your reseller is, go to this site to find
a LANDESK inside sales manager who can direct you to your reseller:
http://www.landesk.com/partners/find/
For more information visit the following web site:
http://www.landesk.com/support/
Ask your LANDESK Solution Provider which option is best for your environment or contact LANDESK Worldwide
Professional Services by emailing
ProServices@LANDESK.com.
New Installation
A new installation is where the Core Server is built starting with a new clean install of the Windows Server
environment from CD, a new empty database, and a new installation of Management Suite 2016.
A new installation is always the solution for new customers who are not upgrading from a previous version.
A new installation is rarely the preferred option for existing customers who already have Management Suite in their
environment. However, a new installation may be the best option for an existing customer if they wish to make a
migration from a legacy version, such as 8.x or prior, to Management Suite 2016 as the database upgrade from legacy
version are not tested.
If there is a concern about the stability of both their existing Core Server Operating System and their database, this
option may be desired to eliminate such concerns.
Clean Core Server Installation with an Upgraded Database

A clean Core Server installation with an upgraded database is when an existing Core Server and database exist, but the
Core Server needs to be rebuilt.
This may occur if the existing Management Suite Core Server is running Microsoft Windows 2008 R2 and it is desired to
move to Windows 2012 R2 before moving to Management Suite 2016. Since it is not supported to upgrade the Core
Server Operating System, the Core Server should be rebuilt. However, the database is still intact, valid, and can be
upgraded. So in this situation, the Core Server files should be backed up, (see backup section) and then the server can
be rebuilt from a clean Core Server installation with an upgraded database is a good option when the database is
working well but the stability of the Core Server is in question.
Renaming the Core Server is an example of something that would cause the Core Server to be in an unstable and
unsupported state and a reinstallation using the clean Core Server installation with an upgraded database is required.
In-Place Upgrade (Same Server)

An in-place upgrade is when a server already has a previous version of Management Suite and Management Suite
2016 is going to be installed on the same server. The installation processes will handle uninstalling the previous
version, installing the new version, and upgrading the existing database.
An in-place upgrade is a good choice when little has been done to customize the installation of LANDESK software
and when moving forward only one or two releases, i.e. Management Suite 9.5 or Management Suite 9.6 to
Management Suite 2016.
Due to the fact that Management Suite 8.8 and prior are not compatible with .NET 4.0 and Management Suite 2016
requires .NET 4.0, an in-place upgrade from Management Suite 8.8 and prior versions is not supported. Instead,
choose one of the other three installation methods.
An in-place upgrade is a good choice when the Core Server and the database are currently functioning properly and
there is no concern of Operating System or database stability.
An in-place upgrade is not a good option if the Core Server or database may already be considered unstable. An
upgrade will not resolve the instability but instead such instability will simply cause the upgrade to fail or leave the
upgraded Core Server in the same state of instability.
Side-by-Side Migrations (Separate Server)

A side-by-side migration is most common when it is needed to have both the old and new Core Server running and
functioning at the same time.
A side-by-side migration is a good choice when wanting to upgrade the Core Servers Operating System to a newer
version, major hardware upgrade, moving forward several versions i.e. Management Suite 8.8 to Management Suite
2016, or for a clean Operating System environment to start with before installing the new Management Suite version.
A side-by-side migration is also a good choice if the installation of the previous version is highly customized, because
such customization may not be upgradeable in-place. Instead, a new server should be built with the new version and
these customizations should be documented and then applied to the new server.
A side-by-side migration is also a good choice if there is a concern about the stability of both their existing Core Server
Operating System and database. Using a side-by-side migration can eliminate such concerns.
A side-by-side migration is the only choice when deciding to increase certain hardware or when upgrading the
Operating System. For example, if you need to purchase a more powerful server that would be a separate server and
use the side-by-side migration method. If you need to migrate from Microsoft Windows 2008 to Microsoft Window
2012 R2 then a side-by-side migration is recommended, as upgrading from Microsoft Windows 2008 to Microsoft
Windows 2012 R2 is not supported.
Step 2 - Backing-up the Existing Core Server

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

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

Many companies have a backup policy to backup servers to a specific external media type such as tape drive, DVD, or
even external drives.
If your company has a backup policy, this policy should be implemented before upgrading the Core Server.
Backing-up the Core Server with ImageW.exe

The Core Server drives or partitions can be backed up using LANDESKs imaging tool, ImageW.exe. The system drive,
and the drive the Core Server is installed if different, should be backed-up.
For information on backing-up the Core Server with ImageW.exe, see the following document: Manually Capturing an
Image with ImageW.exe
https://community.landesk.com/support/docs/DOC-32296
Backing-up the Database

Backup the database. This document does not include the steps for backing up the database on the database server.
Work with the database administrator to create a backup of your database.
Important: Backing-up the database is absolutely critical. There are many reasons a database may fail to
upgrade. If the Core Server successfully upgrades, but the database does not, then without a backup database, you may
have to start with a new database and lose your data. If you have a backup of the database it can be restored, the
upgrade problem can be resolved, and the database can then be upgraded to maintain your data.
Backing-up Critical Core Server Files

Even though we have a backup of the entire Core Server and database, it is still a good idea to have the critical files
backed-up and accessible. If the only backup is on a tape drive, the critical files are not necessarily accessible without
restoring the tape. It is better to have these files backed-up to a share for accessibility.
LANDESK has a created a tool to backup critical files to a share. This tool is called CoreDataMigration.exe.
Backing-up Critical Files with CoreDataMigration.exe

Newer versions of CoreDataMigration.exe may backup files that were not backed-up in previous versions.
One of the Management Suite 2016 installation files is an updated CoreDataMigration.exe and it may be
better to use the Management Suite 2016 version instead of the version that is currently on the Core Server.
The new Management Suite 2016 version of CoreDataMigration.exe can be found in the Management Suite
2016 installation media under the \LANDESKSoftware2016\LD\MS\PF\LD\MS\_non. If Management Suite 2016 was
downloaded, extract LANDESKSoftware.exe to access this file.
It is recommended that the critical files be backed-up to a secure share on separate server. The following steps
explain how to use CoreDataMigration.exe for side-by-side migrations.
You can also find more information here: http://community.landesk.com/support/docs/DOC-6970
Recommended Method:
1. On the new core server (LDMS 2016) run CoreDataMigration.exe with no parameters to launch it in GUI mode.
2. Check the boxes (LDMS Core and Web Console) and fill out the other required info and click OK. In this mode
the tool has been updated to create temporary network shares on the remote system to get to the Shared
Files folder and the ManagementSuite folder. It copies over the necessary files and then removes the temp
network shares. It handles registry values in WOW6432Node.
Optional Method:
1. Create a directory called LANDESKBackup on a share on a separate server that is not the Core Server.
2. Open a command prompt on the Core Server by going to Start | Run and launching CMD.EXE.
3. In the command prompt, change to the ManagementSuite directory. By default the managementsuite
directory is located at %ProgramFiles%\LANDESK\ManagementSuite but it may have been installed to a
different location. cd %ProgramFiles%\LANDESK\ManagementSuite
4. Run the following command:
coredatamigration.exe GATHER \\ServerName\Share\LANDESKBackup
Note: The word GATHER must be all capital letters but the rest is not usually case sensitive.
Backing-up Other Needed Files and Information

There are many other files and information that may be necessary to backup. Not everything is backed-up by
LANDESKs CoreDataMigration.exe. Many of these other files are files that only you know about and only you can be
responsible for making sure they are backed-up properly.
In the previous section a share was already created and this share can be used to backup any other needed files or
information.
Other Needed Files

Distribution Package installation files, if stored on a package share on the Core Server
The Patch directory, if it is stored on the Core Server
\ldlogon\ldappl3.template, if modifications have been made to it.
\ldlogon\AgentWatcher\*.ini files
Other Needed Information

There is other information that may be needed. This information usually includes items that are not stored in the
database but are only stored on the Core Server. This information is especially important to backup if performing a
side-by-side Migration or a clean Core Server installation with an Upgraded Database because in both cases the Core
Server will be new and not have that information.
Export the users and groups added to the LANDESK ManagementSuite group on the Core Server to a file and then
backup the file by copying it to a share. The file can be create by running these commands:
net localgroup LANDESK Management Suite > LANDESK Groups.txt
net localgroup LANDESK Reports >> LANDESK Groups.txt
Note: Domain users and groups may not show up when running these commands if the Domain Controller is not
accessible at the time the command is run (for example if the Core Server is moved to a lab environment for
upgrading).
If migrating to a new database, many items can be exported from the existing database, including the following:
Queries
Distribution Packages
Delivery Methods
Software License Monitoring
Custom Vulnerabilities
Patch status (which patches are set to autofix)
If migrating to a new database, many items cannot be exported. Screen shot such configurations so that they can be
applied to the new Core Server. Examples of these include but are not limited to:
RBA configuration for the LANDESK users and for the Template user
Preferred Server settings
Unmanaged Device Discovery configurations
Settings under Configure | Services
PXE Boot Menu
Security and Patch settings
Document any custom changes made for your environment. Many companies have made custom alterations or
changes for reasons specific to their environment. Most of these changes are only known to you.
Step 3 Preparing for the Management Suite 2016 Core Server Installation
Now that the Core Server is backed-up, it is time to prepare it for installation or upgrade. Some preparation steps may
already be done on the existing Core Server and do not need to be done again if doing an in-place upgrade.
Obtaining Licensing
The Management Suite Activation user name and password is obtained once you have purchased licensing from
LANDESK. To find where to purchase licenses, go to the following web site.
http://www.LANDESK.com/wheretobuy/default.aspx
Upgrading Licenses
An existing customer who is upgrading should verify with their sales representative that their existing username and
password will activate with licensing for 2016 and any other features they have purchased.
Tip: Activate the existing Core Server again, and then look at the Product Licensing to see if the Management
Suite 2016 licensing is appearing. The list of licenses shows up even though you are on a previous version of the
Core Server.
45-Day Trial
New installations can use the 45-day trial and a license can be purchased after installation before the trial period
ends.
Preparing Microsoft Windows 2012 R2 Server for a New Management Suite

2016 Installation
Before installing the Management Suite 106 Core Server software, Windows should be properly configured and
prepared. To prepare a Core Server for installation, the following must be done:
Installing Microsoft Windows 2012 Server R2 from DVD
Applying Microsoft Updates to the server
Installing Microsoft Windows Server from DVD

The best-known method for a new installation is to install Microsoft Windows Server from DVD (or a scripted install
from a network share) and not from an already existing image. As we cannot determine what is already on an image
we cannot recommend using an image as a best-known method, though the image may work fine.
It is up to you to decide if you want to use a corporate image for the Windows Server. Use it only if you are confident
that your image does not have any changes or installed software that will prevent the Core Server from installing and
functioning correctly. It is recommended that the image be tested in a lab environment before using it in production
for the Core Server.
Applying Updates to Windows Server

Windows Update Service needs to be enabled or at least set to "Manual". LANDESK makes every effort to support the
latest patches and updates. As of the date this document was written, February 2016, all Microsoft Windows 2012 R2
Service Packs and other Microsoft updates found by going to Windows Update can be applied.
If a new major update such as a new service pack or a new version of .NET Framework is released, check the
LANDESK community at http://community.LANDESK.com or contact LANDESK support to verify that it is currently
supported before applying it.
Naming the Core Server

The Core Server name should have already been decided. If the Core Server does not have the proper name then this
name must be assigned now.
Important! Once installed a Core Server cannot be renamed.
Obtaining a Domain Account for the Scheduler Service and Com+ Applications
In a Domain or Active Directory environment, the Scheduler service and the Com+ applications will need to run as a
domain account. A domain account should be created for this purpose.
Schedule Service account should be a domain administrator or an account that is a local administrator on all agent
workstations. It should also have access to all packages servers via UNC or HTTP.
Choosing a Certificate Name

Choose the name for the LANDESK certificate file. The name must be unique. If you plan to copy certificates from a
previous Core Server, the new certificate name cannot be the same as the previous certificate name.
The best-known method for certificate naming is to include the date in the certificate name. For example, instead of
just naming the certificate something simple like ldcert, name it ldcert_3march16. If the date is part of the certificate
name, you will never have to worry about whether the certificate name is unique or not.
Preparing a Management Suite Database on the Database Server

If using the Microsoft SQL Express 2014 that is installed with Management Suite 2016, no configuration needs to be
done here.
If performing an upgrade, verify that the database version is a supported version, the database service must be
upgraded before installing Management Suite 2016. For information on supported database software see the
previous section titled
Selecting the Database Software: MS SQL 2008, 2012 or 2014.
If doing an in-place upgrade Server that is already pointing to a database, that database is used. If the database
software is supported, no changes are required here. This included MSDE. If the current Core Server is running MSDE,
MS SQL Express 2014 will not be installed, but instead the existing MSDE database will be used.
If a new database is needed, a database instance must be created before the installation of Management Suite 2016
can occur. To setup the database follow the guides documented in the section titled Database Documentation.
Step 4 - Implementation the Installation/Upgrade Procedure

Now that the Core Server and the database are backed up and the server is ready for installation/upgrade, it is now
time to begin the installation of Management Suite 2016.
Downloading the Installation Media

The Management Suite 2016 installation source can be downloaded from the following locations:
http://www.LANDESK.com/Tools/Trial/Index.aspx New customers must use this LANDESK

trial page
LANDESK Product Downloads A login is required. Only existing

(http://community.LANDESK.com/support/community/prod customers and partners can see the
uct_downloads) downloads section.
Download the latest Service Pack for LANDESK Software Service Packs and updates can be
products downloaded from here:
http://community.LANDESK.com/support
/docs/DOC-1001
The file that is downloaded is a self-extracting executable, LANDESKSoftware2016.exe.
Avoiding Unforeseen Errors

This section gives tips on avoiding unforeseen errors that could be impossible to duplicate.
Reading the Release Notes

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

A server reboot can be extremely helpful just before an upgrade. Remember, your Core Server has been under a heavy
load handling hundreds to thousands of clients and requests on many different services. To make sure that the Core
Server, the Operating System, and all supporting software are running smooth and wont interfere with the upgrade,
a reboot is recommended.
Verifying All LANDESK Services and Processes Are Stopped

The installer will stop all services and processes. LANDESK services, as well as IIS and other services, may be under
very heavy use and may have been under heavy use for a long time. If you just rebooted, as mentioned previously, the
Management Suite installer should stop all services and processes without error.
The Management Suite installation needs all the services and also all other LANDESK processes to be stopped in
order for the upgrade to complete. If you see a process that fails to stop, please contact LANDESK Support.
Important! IIS must be running and should not be stopped.
Stopping non-LANDESK Services and Processes

There are many processes that could get in the way of installing Management Suite 2016 and not all of them are
known or can be predicted.
Stop any antivirus programs if already installed, especially real-time antivirus services.
Stop the Indexing Service.
Disconnect any Console and Web Console connections.
Read-only Files
If performing an in-place upgrade, make sure that no LANDESK files are marked as read-only that should not be.
Some people have marked files such as the NTSTACFG.IN# or their agent configuration files as read-only to prevent
them from being modified. This may lead to an error upgrading as these files cannot be renamed to .bak and replaced
because they are read only.
Stop all real-time scanners during the install in order to improve install time and to ensure services and other critical
files get updated correctly.
Extracting LANDESKSoftware2016.exe
If the software was downloaded, it comes in a self-contained executable called LANDESKSoftware2016.exe. If the
installation is available already, skip this section.
1. Double-click on LANDESKSoftware2016.exe.
Warning: Do not try to extract the software with a third party zip utility as some files may not be extracted.
2. Click Next and you prompted for a location to extract the files to.
Important! Notice the default location is the temp directory. The installation media will be needed later. Choose and
enter a permanent location where these files can be extracted and kept. The best-known method is to store this
installation media on the package server that supports UNC shares so the Remote Console can be deployed.
3. Once you have chosen the location, click Next and the files are extracted.
Once extracted the LANDESKSetup windows will automatically open.
Performing a New Installation

To perform the installation of Management Suite 2016, follow these steps:
Warning: Do not install through Remote Desktop Protocol (RDP) or Terminal Services. Some features cannot
install. Always install when logged in directly on the machine.
1. Run Setup.exe from the installation files to open the LANDESK Setup window.
2. Check for latest updates: This new feature to the installer will download the latest updates automatically if
the Go online and get updates (recommended) option is selected. Ensuring that your core server has the
latest updates from the beginning.
3. Click Continue after selecting the appropriate language.
4. Read the Terms and Conditions, then if you agree, then Select Accept
5. Click the appropriate installation option.
Core Server
Remote Console
Rollup Core Server
To include LANDESK Management Suite, choose LANDESK Core Server.
The next screen checks to make sure that the server has passed the prerequisites. If the prerequisite checker
detects that it is missing a required feature, the screen shows a button with Install Prerequisites.
6. Select Install Prerequisites
7. Once the prerequisites are done installing select Continue.
8. You will be prompted for the database information. (This guide assumes that Configure a new 10.0 database
is selected.)
9. Select the desired option and click Next. (This guide assumes that Microsoft SQL Server is chosen.)
10. Enter the following SQL Server information:
a. Server Name of the Database Server in the Server field.
b. Enter the Name of the database in the Database field.
c. Enter the Username and Password in the User name and Password field.
d. The Port field can be left blank, unless you have changed the default port from 1433.
11. Once the data is entered, click Test Connection to test database connectivity or Select Continue.
12. Next, you are prompted for the location where you would like LANDESK Management Suite installed. Choose
the default location or if desired, change it and select Continue.
13. Secure Client Management: In LDMS 2016 we are introducing a new feature called Secure Client Management.
If you are doing a brand new install, and will not be managing ANY clients with an older LANDESK Agent
installed now would be a good time to enable this feature. However, if you are migrating and will be
managing some older agents for a while then you can enable this feature later on from the LANDESK Console.
(You can find more information here: http://community.landesk.com/support/docs/DOC-39948)
14. Click Continue and the Management Suite 2016 software summary is shown.
15. Click Install and the LANDESK Management Suite 2016 software installs
16. When the installation finishes, you will be prompted to reboot. Select Reboot.
17. Activate your core once the core server has finished rebooting.
The new Core Server installation is complete.
Log Location and Troubleshooting

With 2016, we have moved the installation logging to C:\ProgramData\LANDESK\ManagementSuite\Install\10.0\Log.
These logs are also linked within the GUI of the install if a failure occurs. When looking through the MSI log, look for
Return Value 3. This information right before it and right after this contains the last step the installation attempted
to perform. When contacting LANDESK Support this information will help the Support representative resolve any
installation in a more quickly. It would also be recommended to zip up this directory and attach to the case.
About LANDESK Software

Simple IT environments are a thing of the past. IT departments juggle too many tools from too many vendors while
facing pressure to cut costs, reduce risk and boost productivity. Workers are adding smart phones and tablets to PC
or notebook use, dramatically increasing the number of endpoints and operating systems that must be managed.
Organizations need intelligent, integrated control over diverse systems and devices.
Customers worldwide use LANDESK systems lifecycle management, endpoint security and IT service
management (ITSM) solutions to simplify IT complexity and manage mobility mayhem; discover, track and
safeguard assets and endpoints; and enable IT staff to improve service levelsall while reducing costs and requiring
less infrastructure.
An IDC study found that on average, LANDESK customers realized a three-year return on investment of 698% for their
deployed LANDESK solutionsa nearly sevenfold return. The average payback period to recover the initial
investment averaged a short 5.1 months.

LANDESK Management Suite 2016 Install Guide

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

LANDESK Management Suite 2016 Install Guide

Încărcat de

Drepturi de autor:

Formate disponibile

LANDESK Global Services

Best Known Methods for Installing

WWW.LANDESK.COM | REVISION: <REVISION 2>

Method 1 New Installation

Method 2 In-place Upgrade

Method 3 Clean Core Server Install with an Upgraded Database

Method 4 Test or Lab Core Becomes Production

Method 5 Side-by-side Migration

This guide will cover the following:

Step 1 Planning the Installation/Upgrade Procedure

Step 2 Backing-up the Existing Core Server

Step 4 Implementation the Installation/Upgrade Procedure

Installing/Upgrading to Management Suite 2016 - Check List

Planning the Installation/Upgrade Procedure

o I have documented decisions here: ___________________ Initials: __________

o I have gathered any necessary network information Initials: __________

o I have chosen the installation/upgrade procedure Initials: __________

Backing-up the Existing Core Server

o I have backed up the LANDESK database Initials: __________

o I have backed up the Core Servers critical files Initials: __________

o I have backed up any other need files or information Initials: __________

Preparing the Core Server for Installation/Upgrade

o All the necessary prerequisites applied Initials: __________

Restoring Files and Settings

Verifying the Core Server Installation

Performing Post-Installation Configuration

o The Windows Firewall is properly configured or disabled Initials: __________

o A database maintenance plan has been implemented Initials: __________

Step 1 - Planning the Installation/Upgrade

This should be based on the following items:

Documenting All Decisions when Planning

Gathering Network Information

Choosing the LANDESK Components to Implement

Choosing the Core Server Operating System

Choosing the Core Server and Database Hardware

Selecting the Database software: MS SQL 2008, 2012 or 2014

Choosing the Installation/Upgrade Procedure

Documenting All Decisions when Planning

Gathering Network Information

A diagram of the network and any and all sites involved

Choosing the LANDESK Components to Implement

LANDESK Management Suite

o Inventory and Software License Monitoring

o Software Distribution / Application Virtualization

o Remote Device Management through the Management Gateway

o Operating System Deployment / Provisioning

LANDESK Security Suite

o Host Intrusion Protection System (HIPS)

Different features may lead to different hardware requirements.

Choosing the Core Server Operating System

The Core Server can be installed on the following platforms:

Microsoft Windows 2012 R2 Server 64-bit

Microsoft Windows 2008 R2 Server 64-bit (In-Place Upgrade Only)

Microsoft Windows 2012 R2 Server Platforms and Software Requirements

Microsoft Windows Server 2012 R2 Enterprise Edition (64 bit)

Core Server must be installed as a standalone server

A Clean Installation of the Operating System is Recommended

The servers should be dedicated to hosting LANDESK Management Suite

A server that has been upgraded from a previous version of windows

Virtualizing the Core Server

Selecting the Database Software: MS SQL 2008, 2012 or 2014

Microsoft SQL 2008 R2

Microsoft SQL 2012

Microsoft SQL 2014

o I have documented decisions here: _________ Initials: