LANDesk Management Suite 9.5 - LANDesk User Community ...

LANDesk ® Management Suite 9.5
Configuring Microsoft ® SQL Server 2012 for LANDesk ®
Management Suite 9.5
Written by Nathan Smith
This is a Beta Document for internal use.
Last updated 10/04/2012

Contents
I NTRODUCTION .................................................................................................................4
S COPE ...................................................................................................................................4
A SSUMPTIONS .....................................................................................................................4
I NSTALLING MSSQL 2012 .............................................................................................5
SQL S ERVER I NSTALLATION C ENTER .........................................................................8
Planning Menu ....................................................................................... 8
Platform Support .................................................................................... 9
Installation Setup .................................................................................. 11
S ETUP S UPPORT R ULES ..................................................................................................11
I NSTALLATION O PTIONS AND C ONFIGURATION ....................................................16
Instance Configuration ......................................................................... 19
Disk Space Requirements ..................................................................... 19
Server Configuration ............................................................................. 20
Database Engine Configuration ............................................................ 21
Analysis Services Configuration (Optional Component) ....................... 22
Report Services Configuration (Optional Component) ......................... 23
Error and Usage Reporting ................................................................... 23
Installation Rules .................................................................................. 24
Ready to Install ..................................................................................... 24
Installation Progress .............................................................................. 25
Successful Installation ........................................................................... 25
E NABLE TCP/IP CONNECTIONS TO THE D ATABASE S ERVER ..............................27
Restarting SQL Server ........................................................................... 28
C REATE THE D ATABASE FOR LDMS ..........................................................................29
Create the Database .............................................................................. 29
New Database – General Page .............................................................. 31
New Database – Options Page .............................................................. 34
C REATE A SQL L OGIN WITH DBO R IGHTS TO THE D ATABASE .........................35
Login Properties .................................................................................... 36
Server Roles .......................................................................................... 37

User Mapping ....................................................................................... 38
C ONCLUSION ...................................................................................................................39
References and resources ....................................................................... 39
LANDESK® S UPPORT AND DBMS I SSUES .................................................................39
I NSTALLING THE A PPLICATION S ERVER R OLE ........................................................40
G ENERAL T ROUBLESHOOTING ....................................................................................46
How to view the setup log file ............................................................... 46
Example of an Installation failure .......................................................... 47
T ROUBLESHOOTING THE I NSTALLATION .................................................................48
Server Configuration Troubleshooting .................................................. 48
Database Engine Configuration Troubleshooting ................................. 49
A BOUT LANDESK® S OFTWARE ....................................................................................50
This document contains confidential and proprietary information of LANDesk Software, Inc. and its affiliates (collectively “LANDesk”) and is provided in connection with the identified LANDesk ® product(s). No part of this document may be
disclosed or copied without the prior written consent of LANDesk. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. Except as provided in LANDesk’s terms and conditions
for the license of such products, LANDesk assumes no liability whatsoever. LANDesk products are not intended for use in medical, life saving, or life sustaining applications. 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.
Copyright © 2007, LANDesk Software Ltd. All rights reserved.

INTRODUCTION
This document is intended to assist LANDesk® Management Suite users with the install and configuration of
Microsoft® SQL Server 2012 (MSSQL) for a LANDesk® Management Suite 9.5 installation. Once the
database has been installed and configured, refer to the product documentation in the docs folder from the
installation media or source.
SCOPE
This document covers the steps necessary to install MSSQL 2012 and steps to create a MSSQL 2012 database for
Management Suite. These items are used to install the Management Suite 9.0 Core Server. Database performance tuning
is not within the scope of this document and should be performed by a database administrator (DBA). This document
only covers the information necessary to create the MSSQL 2012 database and user in preparation for installing the
Management Suite 9.0 Core Server.
Note: Some of the screen layouts will look different based on the Operating System and Edition of SQL 2012 being
installed.
ASSUMPTIONS
This document assumes that the LANDesk® administrator is confident to perform basic operations on
databases and have a general understanding of Microsoft® SQL Server.

INSTALLING MSSQL 2012
Prerequisites
Server 2012: Installing SQL 2012 to Microsoft® Server 2012 by default should not need anything installed
before being installed.
Server 2008 R2: Installing SQL 2012 to Microsoft® Server 2008 R2 requires that the Application Server
role be added prior to running setup. Once done the server should meet the primary prerequisites.
• Because Installing the Application Server role with the asp.NET 3.5.1 component is required;
instructions can be found in the Installing the Application Server Role section.

Click OK if prompted
Follow any additional prompts to update the necessary prerequisites (where applicable).

• Click Exit
• Click Exit

If prompted, apply the Windows Installer hotfix.
• Click Continue
Restart if prompted and continue the setup after reboot.
SQL SERVER INSTALLATION CENTER
Planning Menu
The planning menu contains help files that go over everything from System Requirements to
Upgrade Documentation.

Platform Support
The platform OS requirements depend on the Installation.
Click the Hardware and Software requirements section to view requirements specific to the Server
Edition being installed. When done, return back to the planning menu.
Server Core Support:
SQL Server 2012 is now supported on a Server Core installation of Windows Server 2008 R2
and Windows Server 2012. Installing SQL Server 2012 is supported on the Server Core
mode of the following editions of Windows Server:
• Windows Server 2012 64-bit x64 Datacenter
• Windows Server 2012 64-bit x64 Standard
• Windows Server 2008 R2 SP1 64-bit x64 Datacenter
• Windows Server 2008 R2 SP1 64-bit x64 Enterprise

• Windows Server 2008 R2 SP1 64-bit x64 Standard
• Windows Server 2008 R2 SP1 64-bit x64 Web
Example of the table for x64 software requirements

Installation Setup
• Click on Installation on the left pane to access the installation menu.
• Installation options are shown on the right.
• Click “New SQL Server stand-alone installation or add features to an existing installation”.
SETUP SUPPORT RULES
Setup support rules runs a prerequisite check, these are Operating System checks. Rules and status of pass,
failed, warning or skipped will be returned. If a failure is returned it is helpful to consult the planning menu
for requirements.
• Once these rules are met then click OK.

Details about the support rules can be displayed by clicking Show Details or by clicking View detailed report.

• Enter the Product Key and Click Next

• Review the license agreement; to accept the terms check “I accept the license terms.”
• Click Next

• Click Install

• Click Next once all support rules pass for the Setup support files.
INSTALLATION OPTIONS AND CONFIGURATION
Commonly used Components
Database Engine - Required
Replication - Optional
Full-Text Search – Optional
Analysis Services – Optional
Reporting Services – Optional
Business Intelligence Development Studio - Optional
Client Tools – Optional
Integration Services – Optional
SQL Server Books Online - Recommended
Management Tools - Basic - Required
Management Tools - Complete - Required
SQL Client SDK – Optional
Microsoft Sync Framework - Optional

• Check the required features as well as any optional features that are desired.
• Click Next

Instance Configuration
• Make changes to the instance ID and root directory if instructed by the DBA, otherwise accept
defaults and choose next.
Disk Space Requirements

• Click Next
Server Configuration
Specify the accounts SQL Server processes will use to run.
Server Configuration provides the option to select Network Service or System from the Account Name drop
down. Microsoft® recommends using a new account for each these services. Otherwise use "NT
Authority\System".
• Click Next

Database Engine Configuration
By default, Windows authentication is selected, which must be changed.
• Authentication Mode MUST be set to Mixed Mode.
• SA (SQL Server system administrator) should use a strong password even though the installer may not check it.
Note: If sa is the account to be used by the LANDesk Database install then the password must be 8 characters
minimum with numbers and letters.
• Specify non-built in SQL server administrators. For example: a domain administrator who is responsible for
and should have full rights to the SQL server.
• Click Add Current user button if the currently logged in user should have rights to this tool.
• Click Next

Analysis Services Configuration (Optional Component)
• Leave options at default
• Supply a user account to be used by Analysis services.
• Click Add Current user button if the currently logged in user should have rights to this tool.
• Click Next

Report Services Configuration (Optional Component)
Install the default unless otherwise directed by the DBA.
• Click Next
Error and Usage Reporting

• Click Next
Installation Rules
• Click Next
Ready to Install

• Click Install
Installation Progress
• Click Next
Successful Installation

• Click Close if successful
• In the event of a failure, see the General Troubleshooting section at the end of this guide.

ENABLE TCP/IP CONNECTIONS TO THE DATABASE SERVER
• From the start menu open up the SQL Server Configuration Manager.
• Expand the SQL Server Network Configuration menu and select Protocols for the Instance (MSSQLSERVER
is the default instance).
• If the TCP/IP status is disabled, right Click on TCP/IP and choose Enable then click OK.
Note: If it is required by company policy to change the TCP/IP port in the properties, then during the LANDesk install
the new port must be specified during database configuration. Otherwise there is no need to modify the properties.
The SQL Server Service requires a restart for the change to take effect.
• Click OK

Restarting SQL Server
• Open up the services menu (start | run | services.msc).
• Right Click on SQL Server and Choose restart.

CREATE THE DATABASE FOR LDMS
• Open SQL Server Management Studio. Start | All Programs | Microsoft SQL Server 2012 | SQL
Server Management Studio
• Enter the Login and Password and Click Connect.
Create the Database

• Create a new Database by right clicking on the Database folder and choose “New Database…”

New Database – General Page

• Enter the desired Database name.
• Leave the owner as . (This is required for the LDMS database to function properly do
not change this from )
• Set the Row Data Initial file size to the number of nodes to be managed by this core multiplied by 2.
• Set the log file initial file size to be 25% of data file with a minimum of 30MB.
• Modify the Path to save the Data and Log files to a different location. (Optional)
• Click on the Options Page

New Database – Options Page
• On the Options Page, change the Recovery model to Simple.
• Click OK

CREATE A SQL LOGIN WITH DBO RIGHTS TO THE DATABASE
Consult company security policy and/or the DBA to determine if a SQL Login should be created, if one
already exists with the necessary rights, or if sa should be used. The section below outlines how to create a new
Login and what rights, roles and settings are required by LANDesk.
• Create a new user for the LANDesk® Database
• Expand the Security folder and Right Click Logins, choose New Login.

Login Properties
• Change Authentication to SQL Server then enter the login name and password.
• Uncheck Enforce password policy.
• The Login Password to be used by the LANDesk Database install must be 8 characters minimum with numbers
and letters.
• Do not use the following character(s) or character sets in the password: “$$” “,” “-“ “_”.
• Click on the Server Roles page

Server Roles
Important: For normal use, the only role required is public. However for 8.7/8.8 to 9.0 upgrades the Login
for the destination database requires sysadmin role during the upgrade. This is so it can create linked server
objects on the SQL Server to the source database.
Note for Rollup Core users: The sysadmin role is required for the Login on a Rollup Core Database.
• Check sysadmin if doing an upgrade, otherwise leave public checked. In the event of an upgrade,
the sysadmin role can be removed from the login once the upgrade succeeds.
• Click on the User Mapping page.

User Mapping
• Check the Box next to the Database to map the user.
• Check the db_owner box in the role membership section.
• Click OK
This will map the default schema as dbo automatically after clicking OK. It also replaces the need for using sp_addalias
which is no longer available in SQL 2012.

CONCLUSION
The steps outlined in this document provide the user with the basic information required to configure
Microsoft® SQL Server 2012 to operate within a LANDesk® Management Suite 9.5 environment. The server
is now configured to accept communication from the core. An empty database has been created to be used
with the LANDesk® 9.5 install.
For Core installation documentation refer to the docs folder on the LANDesk® 9.5 installation media.
References and resources
Installation: http://msdn.microsoft.com/en-us/library/ms143219.aspx
Books Online: http://msdn.microsoft.com/en-us/library/ms130214.aspx
LANDESK® SUPPORT AND DBMS ISSUES
LANDesk® provides DBMS support for the following actions:
• Installing a supported DBMS for use with Management Suite
• Installing a supported DBMS with Management Suite-specific parameters
• Creating a database and devices for Management Suite
• Creating users for Management Suite
• Creating maintenance tasks for Management Suite databases
• Troubleshooting Management Suite databases
LANDesk® customer support is committed to helping resolve issues for LANDesk® Management Suite 9.5.
Some issues may require additional assistance from the database vendor or through an approved third party.
The database support that LANDesk® customer support does not provide includes, but is not limited to the
following:
• Configuring the DBMS with additional parameters for performance or other reasons
• Creating scripts
• Configuring and existing DBMS installation to work with Management Suite 9.5
• Restricting rights or perform other user maintenance
• Backing up the databases
• Repairing corrupt databases
When called, LANDesk® Software customer support personnel will attempt to do the following:
• Isolate the problem
• Verify the LANDesk-specified DBMS parameters are correct
• Verify that Management Suite 9.5 is working correctly
• Verify that Management Suite 9.5 works with Microsoft® SQL Express 2008

If at this point the DBMS still doesn’t work, the DBMS may need to be reinstalled or the issue may need to
be resolved through other means.
INSTALLING THE APPLICATION SERVER ROLE
For Windows Server 2008 R2 the Application Server Role must be added with the asp.NET 3.5.1 component
before the SQL 2012 setup can run.
• Open the Server Manager console: Start | Administrative Tools | Server Manager
• If the Application Server role is already present then proceed with SQL Server Installation Center.
• If the summary does not show the Application Server role, click the Add Roles button.
The Add Roles Wizard will launch.

Verify the settings as described in the “Before You Begin” section.
Click Next

• Check the Application Server Role.
• Choose Add Required Features from the window that pops up.
Click Next

Click Next
Check the box for .NET Framework 3.5.1 if it is not already selected.
Click Next

Click Install
Successful Installation

• Click Close.
• Reboot if prompted to.
• Run setup to begin installing SQL Server 2012
• Proceed to the section SQL Server Installation Center.

GENERAL TROUBLESHOOTING
How to view the setup log file
Logging for SQL Server Setup has changed in this release. The main log you should look at is
l:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\LOG\Summary.txt
Each execution of Setup will generate a new time-stamped log folder. For example, if you launch the SQL
Server Installation Center page, it gets its own time-stamped log folder, and each Setup action invoked from
that page gets its own as well, so you will probably see several time-stamped log folders in this directory. The
time-stamped log folder name format is YYYMMDD_hhmmss.
Detailed Setup logs are at the following location:
:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\LOG\.
When looking for errors in the detail log, search for the following phrases:
Watson bucket
Error:
Exception has been
A typical Setup request goes through three execution phases:
Global rules check
Component update
User-requested action
Each of these phases will generate detail and summary logs, with additional log files being generated as
appropriate. Setup is called at least three times per user-requested Setup action.

• Click Close when finished.
Example of an Installation failure
• In the event of a failed install follow the top link to the provided summary log.
• In the above example, the log file stated “logon failure” and suggested to uninstall and reinstall.

TROUBLESHOOTING THE INSTALLATION
Server Configuration Troubleshooting
Install using known good accounts under the Service Accounts section

Database Engine Configuration Troubleshooting
• On the Database Engine configuration: Ensure the Built in SQL Server SA account has a strong password.
• Add valid users into the SQL Server administrator box.

ABOUT LANDESK® SOFTWARE
The foundation for LANDesk’s leading IT management solutions was laid more than 20 years ago. And LANDesk® has
been growing and innovating the systems, security, service and process management spaces ever since. Our singular focus
and our commitment to understanding customers’ real business needs—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-packet distribution with LANDesk® Targeted Multicast technology and LANDesk® Peer
Download technology in 2001, and delivering secure systems management over the Internet and hardware-independent
network access control capabilities with LANDesk® Management Gateway and LANDesk® Trusted Access Technology
in 2005.
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.