LDMS 8.8 Installation

This is an overview of the issues that one could run into with a basic install of LDMS 8.8 on Windows 2003 R2 SP2.

The following were used for this walk-thru:

• A total of three Windows 2003 R2 SP2 Servers

• One for the Core Server

• One for the Microsoft SQL 2005 Server with Service Packs applied, running on hardware that includes a RAID array.

• One for the Domain Controller which was already configured.

Preparing the Operating System (2003 R2 SP2)

1. Install Windows 2003 clean.
    
   Warning: Do not join the server to the Domain until it is clear that none of the Group Policies will affect the Core Server functionality.
    

2. Log as as a local administrator.
    

3. Run Windows Update and apply all updates. All updates were applied for this walk-thru as of 3/14/2008.
    
   Note: If you are reading this document in the future and there is some new major update, you might want to hold off.  For example, if Microsoft develops and releases .NET 4.0, you should hold off until LANDesk officially announces support for it.
    

4. Determine the Server Name now.  If the desired name is different than the current name, change the computer name now.  Once you make this an application server, renaming the Server places the Core Server in an unsupported state. 
    

5. Go to Start | Manage Your Server | Add or remove a role option, and add the Application Server role.
    

6. Register .NET 2.0 with IIS by running the following command.  The prerequisite checker will not pass until this has been done.
    
   C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
      

7. Download and install the Web Services Enhancements (WSE) 2.0 SP3 for Microsoft .NET Redistribution Runtime MSI. 
    
   Note: Choose Runtime or Administrator when installing.
    

8. If installing Server or System Manager, install SNMP using these steps:

1. Go to Add/Remove Programs

2. Click Add/Remove Windows Components

3. Select Management and Monitoring Tool and click Details.

4. Check the Simple Network Management Protocol check box and click OK.

5. Click Next.

6. Click Finish.
    

Note: If you are going to practice the installation multiple times, now is good time to image your server (or snapshot it if using VMWare).  That way if you have to start over, you can jump back to this point much more quickly then having to install, apply the patches, and configure Windows 2003 R2 SP2 again.

Preparing the Database

For this walk-thru, Microsoft SQL 2005 Server with Service Packs applied, running on hardware that includes a RAID array was used.

The Following article was followed to the letter:
 
Installing Microsoft SQL Server 2005 for use with Management Suite 8.8
 

Installing the Core Server

1. Download the LANDeskSoftware.exe file according to this guide:
    
   How Can I Download LANDesk Software?
    

2. Run LANDeskSoftware.exe and when prompted for a path, choose a location where the files can stay.  By default it chooses a temporary directory, but you probably want to extract to a data storage drive.
    

3. Continue to follow the prompts to install the Core Server software.
    
   Important! When prompted for a certificate name, make sure to use a unique name.  Do NOT use the same name as you have used in the past.  You have to use the certificate the Core Server was installed with for now.  If you overwrite them because your old ones were named the same, you will be reinstalling.
    

4. If you have an existing Core, click the option to Migrate data from an existing Core Server.  Not right away but later in the installation process, you will be prompted to enter the old Core Server's name and a user name and password to access it. Be aware that the old Core Server has to be accessible via the network in order to do this.
    

5. Once the installation finishes, choose to Reboot.
    
   Note: If the installation fails, refer to this document:
    
   How to troubleshoot LDMS 8.8 Core Installation or Upgrade Failures

Post-installation Configuration

1. Login and activate the Core Server.
    
   Note: The Activation window automatically opens at login.
    

2. The Core Server is not in the Domain yet, but if you want to login to the console as a user other than the local administrator account you used to install the software, add that account to the LANDesk ManagementSuite group now.
    

3. Login to the Console on the Core Server and follow the new Pop-up wizard's instructions.
    
   Note: This explains how to configure the Scheduler Service credentials and BMC Credentials, as well as how to modify the LANDesk and LANDesk1 Com+ Applications.  It then has a wizard for Unmanaged Device Discovery.  Security Suite has a wizard to that explains how to first download patch content.  Not every item under Tools had a wizard, however.
    

4. When editing OS Deployment Scripts that used Sysprep, this issue occurred by default with Windows 2003 R2 SP2:
    
   There was an error in opening the associated file. This script may have been removed from the file system.
    

5. When viewing IIS (Internet Information Services), LANDesk automatically created six application pools.  So tuning IIS should be pre-configured to some extent with a default installation. There are still a lot of web services under the LDAppMain web service that potentially could be moved to even another web service. 
    

6. With 2003 R2 SP2, the LANDesk firewall is on by default.  LANDesk's agent services register with the Firewall but the LANDesk Core Server services do not.  Services such as the Inventory Service will be blocked.  Either disable the firewall on the Core Server or apply any needed Firewall exceptions and/or allow any necessary ports. 
    
   For more information see Ports used by LANDesk Management Suite - Full List
    

7. Test any other features you are going to use.
    

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

Using the Web Console from the Core Server

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

If using Internet Explorer it is not simple to install Flash Player on 2003 R2 SP2 due to the fact that enhanced security is enabled. In order to do this without disabling enhanced security, the following was completed:

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 or install_flash_player_active_x.exe. 
    

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

If using a browser such as Firefox, it is much simpler to install Flash Player.

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