Best Known Methods for Installing or Upgrading the Core Server to LDMS 8

May 21, 2008

LANDesk® Management Suite 8.8

Best Known Methods for Installing or Upgrading the Core Server to LANDesk Management Suite 8.8

2

Introduction .......................................................................................................................... 4

Scope .................................................................................................................................... 4

Installing/Upgrading to Management Suite 8.8 - Check Box List .......................................... 5

Assumptions .......................................................................................................................... 7

Step 1 - Planning the Installation/Upgrade ............................................................................ 7

Documenting All Decisions when Planning ................................................................................ 7

Gathering Network Information ................................................................................................. 7

Choosing the LANDesk® Components to Implement .................................................................. 8

Choosing the Core Server Operating System ............................................................................... 8

Choosing the Core Server and Database Hardware .................................................................... 10

Selecting the Database Software: MS SQL 2000, 2005 or Oracle 9i, 10g ................................... 13

Choosing the Installation/Upgrade Procedure ........................................................................... 14

Determining the Domain Policies and other Security Requirements to Apply ............................ 16

Step 2 - Backing-up the Existing Core Server ....................................................................... 16

Backing-up the Core Server ....................................................................................................... 16

Backing-up the Database ........................................................................................................... 17

Backing-up Critical Core Server Files ........................................................................................ 17

Backing-up Other Needed Files and Information ...................................................................... 18

Step 3 Preparing for the Management Suite 8.8 Core Server Installation .......................... 19

Obtaining Licensing.................................................................................................................. 19

Preparing Microsoft Windows 2003 Server for a New Management Suite 8.8 Installation ......... 20

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

Choosing a Certificate Name .................................................................................................... 25

Preparing a Management Suite Database on the Database Server ............................................... 25

Step 4 - Implementation the Installation/Upgrade Procedure .............................................. 25

Downloading the Installation Media ......................................................................................... 26

Avoiding Unforeseen Errors ...................................................................................................... 26

Extracting LANDeskSoftware.exe ............................................................................................. 27

Performing a New Installation .................................................................................................. 28

Performing an In-Place Upgrade ............................................................................................... 36

Performing a Clean Core Server Installation with an Upgraded Database .................................. 41

Performing a Side-by-side Migration ......................................................................................... 42

Step 5 Restoring Backed-up Files and Information ........................................................... 42

Restoring Critical Core Server Files ........................................................................................... 42

Contents

3

Restoring Other Needed Files and Information ......................................................................... 43

Step 6 Verifying the Core Server Installation .................................................................... 43

Verifying Services ...................................................................................................................... 43

Verifying the Console and Web Console and Web Services ....................................................... 43

Verifying the LANDesk Database ............................................................................................. 44

Verifying the Core Server Name in the Database ....................................................................... 44

Step 7 Post-Installation Configuration .............................................................................. 44

Configuring Windows Server Settings ....................................................................................... 44

Following the New Management Suite 8.8 Wizards .................................................................. 45

Tuning Application Pools in IIS ................................................................................................ 46

Installing Flash Player ............................................................................................................... 46

Adding LANDesk® Management Suite Users ............................................................................. 47

Applying Domain Policies and Other Security Requirements .................................................... 47

Configuring SQL Tuning and Performance .............................................................................. 47

Implementing a Plan for Consistent Core Server and Database Backups .................................... 47

Appendix A Troubleshooting an Installation Failure ......................................................... 48

Install Sections .......................................................................................................................... 48

Install Logs ............................................................................................................................... 48

Troubleshooting MSI errors ...................................................................................................... 48

Troubleshooting Post Setup Config Errors ................................................................................ 49

Sample Post Setup PostSetupConfig_<date_time>.xml.bak ....................................................... 49

About LANDesk Software ................................................................................................... 52

Introduction

The purpose of this document is to cover the Best Known methods for installing or upgrading a LANDesk®

Management Suite Core Server to Management Suite 8.8. This document will cover a clean install, an

upgrade over the top of a previous version, 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 Side-by-side Migration

Scope

This guide is designed to provide an experienced LANDesk® User 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 Management Suite and LANDesk® Security Suite 8.8, 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 document 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 8.8 Core Server Installation

Step 4 Implementation the Installation/Upgrade Procedure

Step 5 Restoring Backed-up Files and Information

Step 6 Verifying the Core Server Installation

Step 7 Post-Installation Configuration

The following two pages contain a check-box list you can print out to help make sure that all the tasks

involved in installation of or upgrade to Management Suite 8.8 are completed and to log who performed and

accomplished each task.

5

Installing/Upgrading to Management Suite 8.8 - Check Box List

Planning the Installation/Upgrade Procedure

I reviewed the installation/upgrade options and I have planned the

installation procedure

Initials: __________

I have documented decisions here: ___________________ Initials: __________

I have gathered any necessary network information Initials: __________

I have chosen the LANDesk® features and components to implement Initials: __________

I have chosen the both Core Server hardware and the operating system Initials: __________

I have chosen the database hardware, Operating System, and database

software


I have chosen the installation/upgrade procedure Initials: __________

I have determined the Domain Policies and other security requirements to

apply to the Core Server


Backing-up the Existing Core Server

I have backed up the Core Server Initials: __________

I have backed up the LANDesk® database Initials: __________

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

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

Preparing the Core Server for Installation/Upgrade

I have obtained licensing for Management Suite 8.8 or evaluate with the

45-day trial


The Core Server Operating System has been installed and patched and all

the necessary prerequisites applied


I determined the name for the Core Server ___________________ Initials: __________

I have obtained the LANDesk® installation software Initials: __________

Scheduler service and Com+ Applications ___________________


I have chosen a certificate name and verified that it is not the same name

as a previous certificate name ___________________


I have a database instance created and ready for the Management Suite 8.8

installation


Installing/Upgrading

I installed Management Suite 8.8 and any other feature sets needed Initials: __________

6

Restoring Files and Settings

All critical files and other files and settings have been restored Initials: __________

Verifying the Core Server Installation

I verified the installation was successful and performed any required tests Initials: __________

Performing Post-Installation Configuration

I configured the Scheduler Service account with a domain account Initials: __________

I configured the Com+ Application Identities with a domain account Initials: __________

I configured Local Intranet and Trusted Sites in IE and Explorer Initials: __________

I added the users to the LANDesk® Management Suite local group Initials: __________

The Windows Firewall is properly configured or disabled Initials: __________

(Optional - If using the Web Console from the Core Server) Flash Player

is properly installed on the Core Server


A database maintenance plan has been implemented Initials: __________

A plan for consistent Core Server and database backups is implemented Initials: __________

7

Assumptions

This document assumes that the reader is knowledgeable in Microsoft Windows Server 2003, Microsoft

Internet Information Server (IIS) management. Microsoft SQL Server 2000, 2005 or Oracle 9i, 10g

database is installed and configured using the LANDesk® Database installation guides found in the

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 2000, 2005 or Oracle 9i, 10g

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.

http://community.landesk.com/

8

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

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

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 ProServices any such particulars should be immediately

brought to the attention of ProServices.

Choosing the LANDesk® Components to Implement

LANDesk® solutions have many features that can be implemented and each feature may lead to different

requirements. There are many features some of which, though not all, are listed below.

LANDesk® Management Suite and Server Manager

Inventory and Software License Monitoring

Software Distribution / Application Virtualization

Remote Device Management through the Management Gateway

Operating System Deployment / Provisioning

Remote Control

LANDesk® Security Suite

Patch Management

Antivirus / Spyware

Connection Control Manager

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 Microsoft Windows 2003 Server and Microsoft Windows 2000 Server.

It is expected that any new installation will use Microsoft Windows 2003 Server. 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 2003 Server Platforms and Software Requirements

Microsoft Windows 2003 Server Platforms and Software Requirements

Microsoft Windows Server 2003 Standard (32 bit) with latest Service Pack

9

Microsoft Windows Server 2003 Enterprise Edition (32 bit) with latest Service Pack

Microsoft .NET Framework 2.0 (3.0 may be installed but 2.0 should be registered)

Microsoft Web Services Enhancements (WSE) 2.0 SP3

Microsoft NT File System (NTFS)

Core Server must be installed as a standalone server

The servers should be dedicated to hosting LANDesk® Management Suite

(Optional) Microsoft Simple Network Management Protocol (SNMP)

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:

64-bit Operating Systems

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

Windows 2000 Server Platforms and Software Requirements

Microsoft Windows 2000 Server with SP4

Microsoft Windows 2000 Advanced Server with SP4

IIS 5

Microsoft Data Access Components (MDAC 2.8)

Microsoft Web Services Enhancements (WSE) 2.0 SP3

Internet 6 with SP1 or later Explorer

Microsoft NT File System (NTFS)

(Optional) Microsoft Simple Network Management Protocol (SNMP)

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:

64-bit Operating Systems

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

The server cannot be a Primary Domain Controller (PDC), Backup Domain Controller (BDC), or

an Active Directory Domain Controller

Servers running other third-party applications as their primary server function

10

Choosing the Core Server and Database Hardware

Decisions must be made on the speed, memory, and storage of the servers involved. The administrator must

also decide when to move to multiple Core Servers. This section will cover these decisions. The four main

hardware choices are the CPU, memory, storage, and network card selection. The lists that follow are

recommendations on hardware for various numbers of managed nodes.

The biggest factor in making these decisions will be the number of managed nodes in the network. The

number of nodes should have already been estimated during while gathering network information. However,

other factors such as which components will be the most used, the number of people needing to access the

LANDesk® console or the web console, network management model, and compliance with business practices

and standards should be considered.

LANDesk Hardware Recommendations

Hardware recommendations are different for each environment and the following are general guidelines to

help determine what the desired hardware would be for a given environment.

All Management Suite Services Hosted on One Server (up to 1,500 Devices)

For Management Suite management domains with 1,500 devices or fewer, you can install the Core Server,

console, Web console server, and the core database on one server. For these networks, you may want to

consider using the default Microsoft MSDE database, which is generally easier to maintain. Your server

should at least meet these system requirements before you install Management Suite in a 1,500 or less device

configuration.

Intel Xeon processor or better (preferably a dual-core processor)

2-3 GB of RAM

Network adapter (100 or 1000 Megabit)

72 GB of free disk space on 10K RPM or faster drives

Using multiple drives, especially to have a separate drive for the database is recommended

Important! Microsoft SQL Express 2005 has a 2 Gigabyte limitation. If this limitation is reached, the Core Server will stop functioning properly and the database will no longer be able to write more data. It is possible that each agent could use as much as 2 megabyte or more so be careful when using SQL Express to monitor the disk usage and upgrade to a full version of SQL prior to reaching the 2 gigabyte limit.

All Management Suite Services Hosted on One Server (1,500-3,000 Devices)

If your Management Suite management domain consists of 1,500-3,000 devices, you can still use one server.

Your servers should at least meet the following system requirements before you install Management Suite.

Two physical processors, each dual-core or better

4 GB or more of RAM

Network adapter (100 or 1000 Megabit)

72 GB of free disk space per array on 15K RPM or faster drives

11

Important: The server hosting this configuration requires three drive arrays on separate spindles (physical disks).

The OS array should be RAID 1

The Database data, Database log, and LANDesk® Application array should be RAID 0, 1, or 5

The database array should be RAID 0, 1, 5, or 10

Multi-server configuration (3,000-8,000 devices)

If your Management Suite management domain consists of 3,000-8,000 devices, LANDesk recommends that

you divide your Management Suite components between two servers for improved database performance.

Your servers should at least meet the following system requirements before you install Management Suite.

Management Suite Core Server and Web console software on one server



4 GB of RAM

Important: The Management Suite Core Server in this configuration requires two drive arrays on separate spindles.

The Operating System array should be RAID 1

The application array should be on a second separate RAID array

Core Database on a Second Server

64bit Operating System is recommended for the Database server for the memory management.

Important: If using a 32-bit Windows Server Operating System with SQL 2000 Enterprise or SQL 2005, AWE (Addressing Windowing Extensions) must be enabled.


4 GB or more of RAM minimum

Important: RAM requirement varies. Multiply the number of devices this Core Server will be managing by 1 to 2 MB to get a better estimate. For example, 8,000 devices require 8 to 16 GB of RAM.

SQL 2000 Enterprise, SQL 2005, or Oracle 10g


One gigabit network adapter

Important: The database server in this configuration requires three drive arrays on separate spindles.


The SQL log array should be RAID 0,1, or 5

The database array should be RAID 0, RAID 10, or RAID 5

12

Multi-server configuration (8,000 or more devices)

If your Management Suite management domain consists of 8,000 or more devices, LANDesk recommends

that you divide your Management Suite components between multiple servers for improved performance in

all areas. Your servers should at least meet the following system requirements before you install Management

Suite.

Management Suite Core Server and Web console software on one server



4 GB of RAM

Important: The Management Suite Core Server in this configuration requires two drive arrays on separate spindles.

The Operating System array should be RAID 1

The application array should be on a second separate RAID array

Core Database on a Second Server

64bit Operating System is recommended for the Database server for the memory management.

Important: If using a 32-bit Windows Server Operating System with SQL 2000 Enterprise or SQL 2005, AWE (Addressing Windowing Extensions) must be enabled.

Quad Xeon 2 GHz or faster processors

8 GB or more of RAM minimum

Important: RAM requirement varies. Multiply the number of devices this Core Server will be managing by 1 to 2 MB to get a better estimate. For example, 8,000 devices require 8 to 16 GB of RAM.

SQL 2000 Enterprise, SQL 2005, or Oracle 10g


One gigabit network adapter

Important: The database server in this configuration requires three drive arrays on separate spindles.


The SQL log array should be RAID 0,1, or 5

The database array should be RAID 0, RAID 10, or RAID 5

Off-Core Web Console Server (Optional)

In some organizations a large number of support individuals may be accessing the web console. If the Core

Server is already under a heavy load, the use of the web console may be slowed significantly. This can be

alleviated by installing an additional Web Console server.


2-3 GB of RAM

13

Gigabit Network adapter

Off-Core Inventory Server (Optional)

In some organizations a large number of inventory scans may be coming in and the Core Server may be under

a heavy load with other LANDesk® features. In this instance it may be desired to off-load inventory scanning

to an additional Inventory server. This feature is used less often now that the Core Server supports multiple

inventory threads but still may be needed if t


2-3 GB of RAM

Gigabit Network adapter

Selecting the Database Software: MS SQL 2000, 2005 or Oracle 9i, 10g

When choosing the database software there are four choices:

Microsoft SQL 2000

Microsoft SQL 2005

Oracle 9i

Oracle 10g

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 either MS SQL or Oracle. Cost

and the ability to hire a database administrator should also be evaluated.

Database Documentation

LANDesk® Management Suite Microsoft SQL Server 2005 Configuration

http://community.landesk.com/support/docs/DOC-2482

LANDesk® Management Suite Microsoft SQL Server 2000 Configuration


LANDesk® Management Suite Oracle 9i Support and Configuration


LANDesk® Management Suite Oracle 10g Support and Configuration


SQL Tuning and Maintenance


Reindexing LANDesk® Databases








14

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 the company in question.

The following table lists some of the various choices that can be made when upgrading a Core Server. These

are not all the possible combination but a general overview of command types.

Core Server Database

New Installation Clean install on same or new server hardware

New clean database instance

Clean Core Server Installation with an Upgraded Database

Clean install on same or new server hardware

Upgraded Database instance

Upgrade In-Place Upgrade existing server. Backup server prior to upgrade.

Same database upgraded during install. Backup database prior to upgrade.

Side-by-side Migration New server hardware that will be installed while current server is running.

Multiple options: new database instance, upgraded database.

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/wheretobuy/default.aspx

For more information visit the following web site:

http://www.landesk.com/SupportDownload/Support.aspx?id=3215

Because each environment has different needs, it is recommended that you contact your reseller or ESP about

our Certified LANDesk® Deployment. Ask your LANDesk® Solution Provider which option is best for

your environment or contact LANDesk Worldwide Professional Services by emailing

[email protected].

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

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 7.x or prior, to Management Suite 8.8 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.


http://www.landesk.com/SupportDownload/Support.aspx?id=3215

mailto:[email protected]

15

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 2000 and it is

desired to move to Windows 2003 before moving to Management Suite 8.8. 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.

Upgrade In-Place (Same Server)

An upgrade in-place is when a server already has an existing version of Management Suite and Management

Suite 8.8 is installed on the same server. The installation processes should handle uninstalling the previous

version, installing the new version, and upgrading the existing database.

An upgrade in-place 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 8.6 or Management Suite

8.7 to Management Suite 8.8.

Due to the fact that Management Suite 8.5 and prior are not compatible with .NET 2.0 and Management

Suite 8.8 requires .NET 2.0, an upgrade in-place from Management Suite 8.5 and prior versions is not

supported. Instead, choose one of the other three installation methods.

An upgrade in-place 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 upgrade in-place 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 Operating System to a

newer version, major hardware upgrade, moving forward several versions i.e. Management Suite 8.5 to

Management Suite 8.8, 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 applied to the new server.

16

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 be a side-by-side migration. If you need to migrate from Microsoft Windows 2000 to Microsoft

Window 2003 then a side-by-side migration is recommended as upgrading from Microsoft Windows 2000 to

Microsoft Windows 2003 is not supported.

Determining the Domain Policies and other Security Requirements to Apply

Often there are already Domain Policies and Security Requirements documented. There are many policies

that may exist, for example, there may be a policy that every computer run antivirus. These policies should be

documented.

LANDesk has created a document to help indicate where Domain Policies can affect Management Suite

functionality. This document can be found here.

Installing LANDesk® Management Suite 8.6 in a High Security Environment


Important: Some Domain Policies and security requirements may affect Management Suite functionality or prevent Management Suite installation. It is recommended that no policies be applied until the Core Server is installed and working. If after applying the policies a feature then stops working, it is easy to know that the reason the feature stopped working is policy related.

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 and Phylock

The Core S 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:


17

Manually Capturing an Image with ImageW.exe


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 8.8 installation files is an updated CoreDataMigration.exe and it may be

better to use the Management Suite 8.8 version instead of the version that is currently on the Core Server.

The new Management Suite 8.8 version of CoreDataMigration.exe can be found in the Management Suite

8.8 installation media under the \LANDesk\SetupFiles. If Management Suite 8.8 was downloaded, extract

LANDeskSoftware.exe to access this file, otherwise this path is on the CD-Rom.

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.

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.


18

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

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.

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

ManagementSuite\LANDesk\Vboot\LDVPE1.IMG

ManagementSuite\LANDesk\Files\DOSUNDI.1

ManagementSuite\LANDesk\Files\BOOTMENU.1

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

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

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

\ldlogon\AgentWatcher\*.ini files

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:

s

net localgro Reports > s

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

19

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. An example 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

Preferred Server settings

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


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


20

Preparing Microsoft Windows 2003 Server for a New Management Suite 8.8 Installation

Before installing the Management Suite 8.8 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 2003 Server from CD-Rom

Applying Microsoft Updates to the server

Adding the Application Server Role

Registering Microsoft .NET Framework 2.0 with IIS

Installing Web Services Enhancements (WSE) 2.0 SP3

(Optional) Installing SNMP

Installing Microsoft Windows Server from CD-Rom

The best-known method for a new installation is to install Microsoft Windows Server from CD-Rom (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

LANDesk makes every effort to support the latest patches and updates. As of the date this document was

written, March 2008, all Microsoft Windows 2000 and Microsoft Windows 2003 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.

When building a new Core Server, it is recommended that the new Core Server use the same name if possible.

However, if both Core Servers must exist simultaneously on the network, it is not possible for them to have

the same name. If this is the case, be prepared to change the DNS record for the old Core Server name to

oon as the old Core Server is decommissioned.

http://community.landesk.com/

21

Adding the Application Server Role

Use the Add or remove a role link in the Manage Your Server window to add the Application Server role.

During this process, IIS and ASP.NET are installed. By default, this wizard pops up upon login after a clean

installation of Microsoft Windows 2003 Server. However, the Manage Your Server link can be found by

simply clicking Start | Manage Your Server or it can also be found under Administrative Tools.

Using the Add or remove a role link in the Manage Your Server window to add the Application Server

role will cause Microsoft Windows 2003 Server to install the needed components in the proper order. .NET

and IIS must be installed in the proper order to allow for proper component registration. This wizard will

ensure that the components are installed and registered correctly. Adding these features through the

Add/Remove Windows Components located in Add/Remove Programs is not tested and doing so may

leave your Core Server in an unsupported state.

The following steps demonstrate how to add the Application Server role to Microsoft Windows 2003.

1. If not already opened, open the Manage Your Server window by going to Start | Manage Your

Server.

2. Click Add or remove a role.

The Configure Your Server Wizard begins.

22

3. Click Next and you will be prompted to select a Server Role.

Note: You may be prompted to Unblock the Configure Your Server Wizard. If prompted, click unblock to unblock it.

4. Click to highlight Application Server (IIS, ASP.NET) and click Next.

5. Check the Enable ASP.NET option and click Next.

23

The Application Server Options window appears.

6. Click to check the Enable ASP.NET option as shown above and click Next. The Summary of

Selection window appears.

7. Click Next to start the installation.

The installation runs and finishes with the following window.

24

8. Click Finish.

The Server has now been given the Application Server role.

Registering .NET Framework 2.0 with IIS

Usually .NET Framework 2.0 is installed during the previous section Applying Updates to Windows Server

before the Application Server role was applied. If this is not the case install it now.

When .NET Framework 2.0 is installed before applying the Application Server role, then when the

Application Server role is applied IIS is registered only with .NET Framework 1.1. In order to install

Management Suite 8.8, .NET Framework 2.0 must be registered with IIS.

To register Microsoft .NET Framework 2.0 with IIS, do the following:

1. Open a command prompt by going to Start | Run and running CMD.EXE.

2. Change to the C:\Windows\Microsoft.NET\Framework\ v2.0.50727 directory:

cd C:\Windows\Microsoft.NET\Framework\ v2.0.50727


aspnet_regiis.exe i

Microsoft .NET Framework 2.0 is now registered with IIS.

Installing Web Services Enhancements (WSE) 2.0 SP3

Management Suite 8.8 now requires Web Services Enhancements (WSE) 2.0 SP3 and cannot be installed

without it. This can be downloaded by going to www.microsoft.com and searching for Web Services

Enhancements (WSE) 2.0 SP3.

Accept the defaults when installing.

(Optional) Installing SNMP

SNMP is not required unless installing some additional features such as Server Manager.

To install SNMP, do the following:

1. Open Add/Remove Programs by going to Start | Run and running APPWIZ.CPL.

2. Click Add/Remove Windows Components.

The Windows Component Wizards opens.

3. Scroll down and click to highlight Management and Monitoring Tools and then click Details.

The Management and Monitoring Tools window opens.

http://www.microsoft.com/

25

4. Click to check the box next to Simple Network Monitoring Protocol and then click Ok.

The Management and Monitoring Tools window closes.

5. Click Next and the installation of SNMP begins.

Note: Access to the Windows 2003 media may be requested. Make sure the installation media, and service pack media if different, us available.

SNMP is now installed on the Windows Server.

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_3march08. If the date is

part of the certificate name, you will never have to worry about the certificate name being unique.

Preparing a Management Suite Database on the Database Server

If using the Microsoft SQL Express 2005 that is installed with Management Suite 8.8, 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 8.8. For information on supported database software see the

previous section titled Selecting the Database Software: MS SQL 2000, 2005 or Oracle 9i, 10g.

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

8.8 can occur. To setup the database follow the guides documented in the section titled Database

Documentation.

Step 4 - Implementation the Installation/Upgrade Procedure

26

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

Downloading the Installation Media

The Management Suite 8.8 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.

Self Service Portal

(http://SelfService.LANDesk.com) A login is required. Only existing customers and partners

can use the Self Service Portal.

Download the latest Service Pack for LANDesk

Software products Service Packs and updates can be downloaded from here:


The file that is downloaded is a self-extracting executable, LANDeskSoftware.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

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 8.8 and not all of them

are known or can be predicted.

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

http://www.landesk.com/Tools/Trial/Index.aspx

http://selfservice.landesk.com/

http://selfservice.landesk.com/




27

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 LANDeskSoftware.exe

If the software was downloaded, it comes in a self-contained executable called LANDeskSoftware.exe. If the

installation is available already, skip this section.

1. Double-click on LANDeskSoftware.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.

28

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

Once extracted the LANDesk®Autorun windows automatically opens.

Performing a New Installation

To perform the installation of Management Suite 8.8, 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 Autorun from the installation files to open the LANDeskAutorun window.

29

2. Click the appropriate installation option.

To install any of the following products, choose LANDesk Management Suite.

LANDesk® Management Suite

LANDesk® Patch Manager


LANDesk® Handheld Manager

LANDesk® Inventory Manager

To include LANDesk Management Suite and Server Manager, choose LANDesk Management

Suite and Server Manager.

The next screen checks to make sure that the server has passed the prerequisites. If the prerequisite

checker detects that it passes, the screen shows a green circle with a check mark and provides the

Install now button.

30

3. Click the Install now button and you will be prompted for the language.

31

4. Choose the language and click OK.

5. Click Next.

6. Read and click to accept the License agreement.

7. Select the Install to location and click Next.

A prompt to install LANDesk System Manager is displayed.

8. To install it, check the box.

9. Click Next and you will be prompted for the database information.

10. Select the desired option and click Next. (This walk through assumes that Add LANDesk tables to

a database is selected.)

If Create a new database now is selected, Microsoft SQL Express 2005 will be installed on the Core

Server. This version has a 2 gigabyte limit and should not be used unless care has been taken to make

32

sure the 2 gigabyte limit is not going to be reached.

If Add LANDesk tables to a database is selected, a prompt will appear asking for the database

connection information.

11. If using Oracle, click to check the box next to Use an Oracle database, otherwise, leave this box

unchecked.

12. Enter the server name of the database server in the Server field.

13. Enter the name of the database in the Database field.

14. Enter the username and password in the User name and Password field.

15. Once the data is entered, click Next and you will be prompted for the Organization and Certificate

name.

33

16. Enter your Organization.

17. Enter the Certificate name that was decided on earlier.

Important! The certificate name must NOT be the same certificate name as used in previous Core Server.

18. Click Next and you will be prompted for the LANDeskReports user.

19. Enter a password for this user and click Next.

You will now be prompted as to whether you want to migrate settings from an existing Core Server.

34

Note: If performing a side-by-side upgrade, click to check the box next to Migrate core settings from a previous installation, otherwise leave this value unchecked.

20. Click Install and the Management Suite 8.8 software installs.

35

21. When the installation finishes, if you checked to migrate existing data you will be prompted now to

do so. Otherwise skip to step 25.

22. Enter the name of the previous Core Server in the Core Server field and enter a User name and

Password that is an administrator on the previous Core Server.

23. Click OK.

The critical information from the previous Core Server is migrated to the new current Core Server.

24. Click OK.

The installation finishes configuring and says successful.

25. Reboot the Core Server.

26. Login and a prompt to active the Core Server automatically opens.

36

27. Enter the username and password and click Activate.

Note: The 45-day trial is only allowed on a new Core Server and may be denied if the Core Server has already been activated with a 45-day trial once or has already been otherwise activated.

28. Click Ok and Close.

The new Core Server installation is complete.

Performing an In-Place Upgrade

Now that everything is backed-up and the Core Server is ready for the upgrade, follow these steps to perform

the upgrade to Management Suite 8.8:

1. Run Autorun from the installation files to open the LANDeskAutorun window.

37

2. Click the appropriate installation option.

To upgrade the following products, choose LANDesk Management Suite.

LANDesk® Management Suite

LANDesk® Patch Manager


LANDesk® Handheld Manager

LANDesk® Inventory Manager

To include LANDesk Management Suite and Server Manager, choose LANDesk Management

Suite and Server Manager.

The next screen checks to make sure that the server has passed the prerequisites. If the prerequisite

checker detects that it passes, the screen shows a green circle with a check mark and provides the

Install now button.

38

3. Click the Install now button.

Setup will begin and detect and existing installation.

4. Click Next.

39

5. Click to accept the license agreement and click Next.

6. Click Install to begin the installation.

Note: Notice on an in-place upgrade, there is not option to put in the language, the database information or a key name as the information already in place is used.

7. The installation continues and finishes.

Note: It is important to read the information in this popup message.

8. Click Close and the LANDesk Install window will display what installed and give you the option to

Close or Reboot.

40

9. Click Reboot and the system reboots.

10. Login and a prompt to active the Core Server automatically opens.

41

11. Enter the Contact Name and Password and click Activate.

Note: The 45-day trial is grayed out and is not allowed on an upgraded Core Server.

12. Click Ok and Close.

The new Core Server installation is complete.

Performing a Clean Core Server Installation with an Upgraded Database

This process follows the same process as when performing a New Installation. For a walk-thru go to the

section titled Performing a New Installation and when asked for the database information put in the

existing database and the existing database is upgraded.

With this option it is recommended that you give the Core Server the same name as the previous Core Server.

A restoration of critical files from the previous Core Server will need to be done. See the section titled

Restoring Files from Backup.

42

Performing a Side-by-side Migration

The most common type of side-by-side migration is where both Core Servers must exist simultaneously

during the migration.

This process for the Core Server follows the same process as when performing a new installation. For a walk-

thru go to the section titled Performing a New Installation.

If the server can be built in a lab environment or otherwise isolated, it can be given the same name as the old

Core Server. Then it can replace the old Core Server when placed on the production network. If both Core

Servers must exist on the production network simultaneously, the names cannot be the same. The Core

Server cannot be renamed. Instead, once the old Core Server is decommissioned, change DNS to point the

old Core Server name to the new Core Server IP address.

The database can be a new clean database, or it can be a copy of the existing database, such as back-up that

was restored as a different database instance. Though care must be taken if the new Core Server has a

different name but copy of the old database is used. See the section titled Verifying the Core Server Name

in the Database.

A restoration of critical files from the previous Core Server will need to be done. See the section titled

Restoring Files from Backup.

Step 5 – Restoring Backed-up Files and Information

In Step 2, critical files, and other files and information were backed-up. Now is the time to restore those files

and reapply any settings needed.

Restoring Critical Core Server Files

Ensure the server has access to the LANDeskBackup folder created on a separate server. This was created

during the section titled Backing-up Critical Core Server Files.

To restore files from the backup folder do the following:

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

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


CoreDataMigration.exe RESTORE \\differentserver\share\LANDeskBackup

Note: The word RESTORE must be all capital letters

43

Restoring Other Needed Files and Information

Review the other files and information that were backed-up during the section titled Backing-up Other

Needed Files and Information and evaluate whether to restore the files and settings or simply apply the

changes made to the new files and settings.

Step 6 – Verifying the Core Server Installation

It is part of every good change control process to verify that the server is installed as desired. The following

items are important to check when verifying a successful Core Server installation.

Verifying Services

Verify that the following services are installed and started

Intel Alert Handler

Intel Alert Originator

Intel PDS

Intel QIP Server Service

LANDesk® Activation Service

LANDesk® Inventory Server

LANDesk® Policy Server

LANDesk® Process Manager Scheduler Service

LANDesk® Scheduler Service

LANDesk® Transport Initiator Module

LANDesk® Usage Service

LANDesk®Agent Portal Service

LANDesk®Agentless Discovery Service

LANDesk®Alert Service

LANDesk®ASF Proxy Service

LANDesk®Console Redirection Service

LANDesk®Dashboard Report Summary Service

LANDesk®Management Agent

LANDesk®Management Gateway Service Only started if using the Management Gateway

LANDesk®System Manager SNMP Message Relay Service

Verifying the Console and Web Console and Web Services

Verify that the Console is working

44

Start the console and login

Verify LANDesk Web Console

Open the web console from the Core Server

Note: Flash Player is needed for the Web Console in Management Suite 8.8

Open the web console from a different computer

Verifying the Web Services are functioning by open in IIS, browsing to the following locations and doing a

right-click browse:

WSVulnerabilityCore | VulCore.asmx

LANDesk | ManagementSuite | Core | Core.WebServices > Pxe.asmx

Verifying the LANDesk Database

Verify that the Database was populated with LANDesk tables

Verify the tables are created

Verify the tables are properly owned by DBO.

Verifying the Core Server Name in the Database

The database can be a new clean database, in which case the Core Server name will be correct in the database

already. The database could also be a copy of the existing database, such as back-up that was restored as a

different database instance. Care must be taken if the new Core Server has a different name than the Core

Server name that was used to originally create the database that is being upgraded.

The database stores the Core Server name in the Metasystems table. This table must be manually changed.

To updated the Core Server name in the LANDesk database, work with the database adminsitrator to run the

following SQL query on against the database:

UPDATE METASYSTEMS SET CORESERVER='CoreServerName'

The database should now have the correct Core Server name.

Step 7 – Post-Installation Configuration

After the Core Server is installed, there are some simple configurations that need to be done.

Configuring Windows Server Settings

Management Suite 8.8 runs on Windows Server and there are many settings in Windows that must be made.

These are listed below.

45

Configuring Local Intranet and Trusted Sites Internet Explorer and Explorer

Microsoft has increased its security when accessing either web sites or UNC shares. If a site is not added to

the Local Intranet or Trusted Sites lists, the server will not run executable software, even if the site is the local

server itself.

For both Internet Explorer and Explorer, sites should be added as Local Intranet or Trusted.

Local Intranet

Add the following items:

http://CoreServerName

https://CoreServerName

\\CoreServerName (appears as file://CoreServerName)

Any other local intranet web site or UNC share, such as the package server

Trusted Sites

Add the following locations:

http://*.landesk.com

https://*.landesk.com

Configuring the Proxy Server in Internet Explorer

If Internet Explore is enabled, the proxy server should be configured to by-pass the proxy for local sites.

Note: For patch and antivirus downloads, it may be desired to configure the proxy server to allow a direct non-proxy connection to http://*.landesk.com and http://*. kaspersky-labs.com.

Configuring the Windows Firewall

The Core Server may have the firewall enabled. The firewall is enabled by default when using Microsoft

Windows 2003 R2 SP2.

Exceptions can be made to the firewall, or it can be disabled, depending on your security requirements.

An exception should be configured for the executables used for each LANDesk® service.

The following article discusses ports used by LANDesk® Management Suite:

Ports used by LANDesk Management Suite - Full List


Following the New Management Suite 8.8 Wizards

The new Management Suite 8.8 installation now has wizards that appear when the Console is opened. These

wizards walk through some important post-installation configuration. The first step is to open the LANDesk®

Console on the Core Server.

These wizards walk the new user through the following items:


46

Configuring the Scheduler Service account

Configuring Intel vPro

Configuring the Com+ Application Identities

Configuring and Scheduling Unmanaged Device Discovery

Configuring and deploying a LANDesk® Agent

Security Suite

Tuning Application Pools in IIS

Management Suite 8.8 now creates multiple application pools by default making the installation run more

efficiently out of the box. These application pools can be further tuned if needed.

The WSVulnerabilityCore application pool may be enhanced to use multiple worker processes in the web

garden.

Installing Flash Player

Before using the Web Console from the Core Server install Flash Player version 9.0.115.0. When the Web

Console opens the first time, the page should redirect to a web page from where Flash Player can be installed.

If using Windows Server 2003 SP2 it is not possible to install Flash Player for Internet Explorer from the

Flash Player web site due to the fact that enhanced security is enabled. It can be installed most easily by

disabling enhanced security.

To install Flash Player without disabling enhanced security, the following can be done:

1. Go to this site: http://www.adobe.com/cfusion/entitlement/index.cfm?e=shockwave

2. Create a new username, or login if you already have one.

3. Enter the Operating Systems you will be deploying to and fill in the drop down menus and click to

accept and then submit.

4. An email will be sent to you shortly that will allow you to login and download the redistributable

version of Flash Player for IE:

install_flash_player_active_x.msi

install_flash_player_active_x.exe

5. Download and install either of those on the Core Server.

If using a browser such as Firefox, enhanced security does not apply so Flash Player can be installed from the

web site. However, an installer for Firefox can also be obtained using the steps above.

1. Click the link provided once the Web Console opens or download and install Flash player from here:

http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player.exe

http://www.adobe.com/cfusion/entitlement/index.cfm?e=shockwave

http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player.exe

47

Adding LANDesk® Management Suite Users

In order for a user to log into the Console, they must be a member of the LANDesk Management Suite local

group on the Core Server. If migrating an existing Core Server, this may have already been done as part of

restoring backup settings.

Add the users as follows:

1. Before configuring the template user add any LANDesk® administrators while the template user is set

to the default value of administrator.

2. Configure the template user.

3. Add other users as follows and they will receive the new template user permissions by default.

Applying Domain Policies and Other Security Requirements

Now is the time to carefully join the Core Server to the domain and apply Domain Policies and other security

requirements.

Joining the Domain

1. Verify that the Core Server is in its own OU with no policies applied and then join it to the domain.

2. Add any Domain Users or Groups to the LANDesk® Management Suite group on the Core Server.

3. Apply Domain Group Policies (GPOs) carefully.

Note: Many policies can interrupt LANDesk services, especially the web services. If after applying a policy a feature in LANDesk fails, remove the policy and determine which policy setting is causing the failure and resolve it before reapplying the policy.

Installing/Enabling Antivirus

If antivirus is not installed, install it now. If antivirus was previously installed, it was recommended that real

time antivirus scanning be disabled during the installation of Management Suite 8.8 and can be enabled now.

Note: Take care to make sure that LANDesk® services are not interrupted by the Antivirus service.

Configuring SQL Tuning and Performance

Work with the database administrator to configure and tune SQL. Review the documents in the previous

section titled Database Documentation and make sure the database administrator has a copy.

Implementing a Plan for Consistent Core Server and Database Backups

Backup the critical files from the new Core Server. Implement any other desired backup, such as a backup to

external media or a drive image.

Work with the database administrator to configure a routine backup of the LANDesk® database.

48

Appendix A – Troubleshooting an Installation Failure

LANDesk has improved the ability to troubleshoot the Core Server installation/upgrade. The installation has

been broken down into multiple sections and these sections have been pulled from the Custom Action section

of the MSI and are performed after the MSI completes. Many of these commands cannot be rolled back, for

example, CoreDBUtil.exe. By performing these sections after the MSI finishes, the MSI will not try to roll

back after these action have been run.

Install Sections

When setup.exe is launched, the installation proceeds through these sections in this order:

LANDeskSoftware

PreDBConfig

DBConfig

PostDBConfig

PostAddOn

PostMSI

When a section completes successfully, it is written by name to this registry key string:

HKLM\software\LANDesk\LANDeskSoftware

String: LastInstalled

Now the installation failure can be resolved, and the installation can continue without having to repeat what

it has already done. This means if you fix the failure and restart the install, it picks up after the section that is

in the LastInstalled registry string, so it does not repeat a section that has already been performed

successfully.

The following file stores what commands are going to be run in each section:

PostSetupConfig_<date_time>.xml.bak

Install Logs

Many logs are in %TEMP%. The MSI log, LANDeskSetup.exe.log and PostSetupConfig.exe.log are also

in %TEMP%.

Other important files are located here:

LANDesk\ManagementSuite\Install Only Files

Troubleshooting MSI errors

If the installation fails during the MSI portion, the MSI log should be analyzed. This log should be opened

with WiLogUtil.exe, which can be found by installing the windows installer portion of the Microsoft

Platform SDK.

49

Troubleshooting Post Setup Config Errors

The following file stores which commands are going to be executed in each section.

PostSetupConfig.xml

If the install fails, the following troubleshooting steps can be performed:

1. Look at the LastInstalled registry string to see which section is the last section to complete

successfully.

2. Look in the PostSetupConfig.xml to see what the following section is and what commands will run

in the next section.

3. Look in the PostSetupConfig.exe.log to determine which command is failing.

4. Troubleshoot the failed command by running it manually. This should allow for the error to be

identified and resolved more easily.

5. Run each command in that section manually.

6. Once each command in that section completes successfully, manually change the LastInstalled

registry string to the name of the section that was just manually completed.

7. Restart setup and it will finish the final sections.

8. If an error occurs again, repeat the above steps.

Sample Post Setup PostSetupConfig.xml <?xml version="1.0" encoding="utf-8"?> <sections> <section name="PreDBConfig"> <command CustomActionName="Installing LANDesk Process Manager"> <executorPath>C:\Documents and Settings\Administrator\Desktop\ldms

8.8\landesk\LPM\Setup.exe</executorPath> <CommandLine>/s /L1033 /v"/q ADDLOCAL=ALL LAUNCHPROGRAM=0 INSTALLDIR=\"C:\Program

Files\LANDesk\Process Manager\""</CommandLine> </command> </section> <section name="DBConfig"> <command CustomActionName="Database - Build Components"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe</executorPath> <CommandLine>/buildcomponents /DDON

/log=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\PostSetupConfigAll.log</CommandLine> <LogFile>C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\LANDesk.CoreDbUtil.CoreBuildComp.log</LogFile> </command> <command CustomActionName="Database - Publish Software"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe</executorPath> <CommandLine>/PublishSoftwareConfiguration

/log=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\PostSetupConfigAll.log</CommandLine> <LogFile>C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\LANDesk.CoreDbUtil.CorePublishSw.log</LogFile> </command> <command CustomActionName="Database - Update Canned Reports"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe</executorPath> <CommandLine>/UpdateCannedReports /silent

/log=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\PostSetupConfigAll.log</CommandLine> <LogFile>C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\LANDesk.CoreDbUtil.CoreUpdateRep.log</LogFile> </command>

50

<command CustomActionName="Database - Patch Manager"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe</executorPath> <CommandLine>/xml=datamartpm.xml /buildcomponents /DDON

/log=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\PostSetupConfigAll.log</CommandLine> <LogFile>C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\LANDesk.CoreDbUtil.PatchManager.log</LogFile> </command> <command CustomActionName="Database - Provisioning"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe</executorPath> <CommandLine>/xml=provisioning.xml /buildcomponents

/log=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\PostSetupConfigAll.log</CommandLine> <LogFile>C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\LANDesk.CoreDbUtil.Provisioning.log</LogFile> </command> </section> <section name="PostDBConfig"> <command CustomActionName="Import Alert Names To Database"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\alertname2table.exe</executorPath> <CommandLine>-c -d "C:\Program Files\LANDesk\ManagementSuite\alertstrings"</CommandLine> </command> <command CustomActionName="Import Alert Rules To Database"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\alertruleset2table.exe</executorPath> <CommandLine>"C:\Program Files\LANDesk\ManagementSuite\alertrulesets"</CommandLine> </command> <command CustomActionName="Importing Software Distribution Methods To Database"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\swdCoreCustomAction.exe</executorPath> </command> <command CustomActionName="Installing LANDesk MBSDK"> <executorPath>C:\Documents and Settings\Administrator\Desktop\ldms

8.8\landesk\MBSDK\Setup.exe</executorPath> <CommandLine>/s /v"/q"</CommandLine> </command> <command CustomActionName="Import Web Console Hostname To Database"> <executorPath>rundll32</executorPath> <CommandLine>"C:\Program Files\LANDesk\ManagementSuite\Install Only Files\ldmsinst.dll",

LDSetDBKeyValue</CommandLine> </command> </section> <section name="PostAddOn" /> <section name="PostMSI"> <command CustomActionName="Migrating Core Data"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\CoreDataMigration.exe</executorPath> <LogFile> </LogFile> </command> <command CustomActionName="Installing CBA 8"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\ldlogon\rainstall.exe</executorPath> <CommandLine> /delayextensioninstall /dontmove /vroot=ldms.vroot /extension=lclxsvc.dll /install

/cert=383b2b55.0</CommandLine> </command> <command CustomActionName="Create Monitor Root"> <executorPath>C:\Program

Files\LANDesk\ManagementSuite\LDLOGON\CreateMonitorRoot.exe</executorPath> <CommandLine>"" "C:\Program Files\LANDesk\\"</CommandLine> <LogFile> </LogFile> </command> <command CustomActionName="Install Ams For Core"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\ldlogon\instams.exe</executorPath> <CommandLine>Core</CommandLine> </command> <command CustomActionName="Running Stamper"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\stamper.exe</executorPath> </command>

51

<command CustomActionName="Creating Client Configuration"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\CreateClientConfiguration.exe</executorPath> </command> <command CustomActionName="Provisioning Configuration"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\prov_createstartnet.exe</executorPath> </command> <command CustomActionName="Provisioning Database 1"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\prov_Loaddb.exe</executorPath> <CommandLine>-f "C:\Program

Files\LANDesk\ManagementSuite\ENUActionsAndSections.xml"</CommandLine> </command> <command CustomActionName="Provisioning Database 2"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\prov_Loaddb.exe</executorPath> <CommandLine>-f "C:\Program Files\LANDesk\ManagementSuite\ENUInitialGroups.xml" -u 1</CommandLine> </command> <command CustomActionName="Provisioning Database 3"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\prov_Loaddb.exe</executorPath> <CommandLine>-f "C:\Program Files\LANDesk\ManagementSuite\PublicVariables.xml"</CommandLine> </command> <command CustomActionName="Provisioning Install Plugin"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\prov_InstallPlugin.exe</executorPath> <CommandLine>-a</CommandLine> </command> <command CustomActionName="OS Virtualization Provider Setup"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\Virt_Esx_Manage.exe</executorPath> <CommandLine>/genkey=ESX</CommandLine> <LogFile> </LogFile> </command> <command CustomActionName="Running Stamper"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\stamper.exe</executorPath> </command> <command CustomActionName="Cert Install"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\SecureWebSiteInstall.exe</executorPath> <CommandLine>"d88_04April08" landesk/managementsuite/core/ssl

landesk/managementsuite/core/ssl/remotecontrol landesk/managementsuite/core/ssl/information</CommandLine>

</command> <command CustomActionName="Server Configuration"> <executorPath>C:\Program Files\LANDesk\ManagementSuite\CreateDefaultMNodeConfig.exe</executorPath> </command> <command CustomActionName="Prepare to register on reboot"> <executorPath>regedit</executorPath> <CommandLine>/s "C:\Program Files\LANDesk\ManagementSuite\Install Only

Files\RunRegisterCore.reg"</CommandLine> </command> </section> <section name="Unspecified" /> </sections>

52

About LANDesk Software

management solutions was laid more than 20 years ago. LANDesk

has been growing and innovating the systems, security, service and process management spaces ever since.

and to delivering

easy-to-use solutions for those needs are just a few of the reasons we continue to grow and expand.

LANDesk pioneered the desktop management category back in 1993. That same year, IDC named LANDesk

the category leader. And LANDesk has continued to lead the systems configuration space: pioneering virtual

IT technology in 1999, revolutionizing large-

gement

over the Internet and hardware-independent network access control capabilities with LANDesk® Management

In 2006, LANDesk added process management technologies to its product line and began integrating the

systems, security and process management markets. LANDesk also extended into the consolidated service

desk market with LANDesk® Service Desk, and was acquired by Avocent to operate as an independent

division.

Today, LANDesk continues to lead the convergence of the systems, security, process and service management

markets. And our executives, engineers and other professionals work tirelessly to deliver leading solutions to

markets around the globe.

This information is provided in connection with LANDesk products. No license, express or implied, by

estoppel or otherwise, or warranty is granted by this document. LANDesk does not warrant that this material

is error free, and LANDesk reserves the right to update, correct or modify this material, including any

specifications and product descriptions, at any time, without notice. For the most current product

information, visit http://www.landesk.com.

Copyright © 2008 LANDesk Software Ltd. or its affiliated companies. LANDesk is a trademark or registered

trademark of LANDesk Software, Ltd. and its affiliated companies- in the United States and/or other

countries.

*Other names and brands may be claimed as the property of others. .

http://www.landesk.com/

Date post:	10-Apr-2015
Category:	Documents
Upload:	api-3840339
View:	498 times
Download:	1 times