Dell™ Management Console Install Guide

By Rob Cox, Nadine Latief Dell │ Product Group - Enterprise

Revision History

Version Date Description Author(s)

1.0 5 May 2009 First Version Rob Cox, Nadine

Latief

1.1 27 May 2009 Ready for publish Rob Cox, Nadine

Latief

1.1a 28 May 2009 Minor changes, addition to

list of KB and SQL 2005 SP3

not supported

Rob Cox, Nadine

Latief

1.1b 3 June 2009 Infodev edits, more agent

info

Rob Cox, Nadine

Latief

1.2 21 Oct 2009 SQL appendix added, added

upgrade

Rob Cox, Nadine

Latief

1.3 17 Jan 2011 User guide updated for DMC

2.0 prerequisites and

Installation changes.

Nilesh Bagad

THIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR

IMPLIED WARRANTIES OF ANY KIND.

© 2009 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the express written permission of Dell, Inc. is strictly forbidden. Dell, the DELL logo, PowerEdge, PowerVault, and Dell EqualLogic are trademarks of Dell, Inc.; Microsoft is a registered trademark of Microsoft Corporation in the United States and/or other countries. EMC, CLARiiON, and UltraFlex are trademarks or registered trademarks of EMC Corporation. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell disclaims proprietary interest in the marks and names of others.

Contents

1. INTRODUCTION ............................................................................................. 4

2. GETTING READY ............................................................................................ 4

2.1. PHYSICAL SERVER ........................................................................... 4 2.2. OTHER IMPORTANT CHECKS ................................................................ 5 2.3. USING THE APPROPRIATE USER ID ...................................................... 7

3. INSTALLING THE DMC ............................................................................... 8

3.1. RUNNING THE DMC INSTALLATION ....................................................... 8

3.2. NETWORK PORT FIX ........................................................................... 8 3.3. INSTALL READINESS CHECKS! ............................................................. 13

4. DEPLOYING THE ALTIRIS AGENT ..................................................... 15

4.1. PREREQUISITES ................................................................................ 15

4.2. ALTIRIS NOTIFICATION SERVER AND ALTIRIS AGENT USER SECURITY

REQUIREMENTS .......................................................................................... 15

4.3. LOGS DURING ALTIRIS AGENT INSTALL ............................................... 16 4.4. UPGRADING TO THE LATEST VERSION OF DMC .................................... 16

5. POST-AGENT INSTALL ISSUES .................................................................... 18

5.1. AGENT DEBUGGING FAQ: ................................................................. 18 5.2. INSTALL LOGS .................................................................................. 19

5.3. OTHER LOGS AND DEBUG MECHANISMS ............................................. 19 5.4. UNINSTALLING AFTER A FAILED INSTALL .............................................. 19 5.5. MORE INFO ...................................................................................... 19 5.6. USING DELL PRIVATE PRODUCT LISTING ............................................ 20 5.7. MANUALLY PERFORMING THE CRL FIX (CRITICAL) ............................... 20

6. ALTIRIS KNOWLEDGE BASE ARTICLES.................................................. 21

7. SQL APPENDIX ................................................................................................. 23

7.1. STEPS TO INSTALL SQL EXPRESS 2005 FOR USE WITH DELL

MANAGEMENT CONSOLE .............................................................................. 26

1. Introduction The purpose of this document is to help you with the installation process for the

Dell™ Management Console (DMC).

To register and download Dell Management Console, see

http://www.dell.com/openmanage/register

2. Getting Ready

Before beginning the installation, ensure that you have the following set up in your

environment and on the server that will host the DMC installation.

2.1. Physical Server Below prerequisites are recommended minimum hardware Configuration for Dell

Management Console:

4 or more Processor cores

4 GB RAM

10 GB free disk space

DVD Drive

Microsoft .NET 3.5 (SP1 is supported)

Microsoft Silverlight 3.0

Windows Internet Information Services (IIS) 7.0

Microsoft SQL 2005 Express or SQL 2008 Express or

SQL Server 2005 SP1/SP2/SP3 (32-bit remote or 64-bit) or

SQL Server 2008 R2 (32-bit remote or 64-bit) or

SQL Server 2008 ENT (32-bit remote or 64-bit)

Windows Internet Explorer version 7.0 or 8.0 (32-bit only)

Windows 2008 R2

.NET 4.0 is supported only if .NET 3.5 (SP1) is present on the system.

Below prerequisites are recommended Hardware for Configurations over 500

Devices:

8 or more Processor cores

8 GB RAM

10 GB free disk space

DVD Drive

Microsoft .NET 3.5 (SP1 is supported)

Microsoft Silverlight 3.0

Windows Internet Information Services 7.0

SQL Server 2005 SP1/SP2/SP3 or SQL Server 2008, R2 (32-bit remote or 64-

bit)

Internet Explorer version 7.0 or 8.0 (32-bit only)

Windows 2008 R2

Dell recommends remote 64-bit database for larger environments.

Additional Software Required to Run Some Features of Dell Management

Console:

For Dell/EMC storage arrays, ensure the array is FLARE(R) version 26 or later.

Navisphere(R) Secure CLI (version 26 or above) installed on the management

station.

This CLI software is included on the Dell Management Console media.

Below are the recommended SQL server updates:

SQL Server 2005 SP1 or SP2 or SP3 is required for using SQL Server 2005

as the default database.

Optimize your SQL Server maximum memory settings as indicated in

Microsoft(R) knowledge base articles KB321363 and KB319942. This

Configuration may significantly improve product performance.

Ensure that during installation of the SQL Server 2005, you select a case-

insensitive collation setting. If you select a case-sensitive collation setting, then

the agent health Web part for an individual discovered device will not contain

any information. The default collation setting in SQL Server 2005 is case-

insensitive.

2.2. Other Important Checks On the installer readiness checker in the Symantec Installation Manager (SIM),

always apply the Certificate Revocation List (CRL) fix by clicking the fix link. (If

this pre-req shows up as green, you can still manually apply the fix; see below

“Manually performing the CRL fix”).

You must be logged in as a Local Administrator with full local administrator

rights (member of the local administrator group on the machine that DMC is

installed on) for SIM to run. Domain Administrator privileges will not work.

To create the DMC database:

o Need dbo privileges to the database notification server.

o dbcreator Server Role is also required

To use the Agent Deployment feature of DMC, you must be a member of the

group with local administrative rights on systems you are deploying to.

The DMC system must have.Net 3.5 installed.

IIS must be installed on the DMC system (default settings on Directory

Permissions on the Default website properties)

The DMC supports only Internet Explorer 7 and Internet Explorer 8 (32 bit only)

The DMC system IP address must be registered in the DNS or DDNS.

If DMC is running in an environment that is not connected to the Internet and

the Update Root Certificate option is selected, you may see the "Crypt32" errors

in the event log after installing DMC. For more information, see the following KB:

http://support.microsoft.com/kb/317541

To resolve this issue, either connect to the Internet or turn off the Update Root

Certificates

To turn off Update Root Certificate:

o Click Start, and then click Run.

o Type gpedit.msc, and then click OK.

o If the User Account Control dialog box appears, confirm that the action it

displays is what you want, and then click Continue.

o Double-click Administrative Templates, double-click System, double-click

Internet Communication Management, and then click Internet

Communication settings.

o Double-click Turn off Automatic Root Certificates Update, click Enabled,

and then click OK.

o Close the Local Group Policy Editor.

Dell recommends installing IIS on a system where IIS is not running any other

application.

If you have the Symantec Endpoint Protection (SEP) installed on the same

system as the DMC, disable SEP, and then re-enable it after the DMC installation

is complete. You may need to do this for other antivirus software as well.

You should install with Local Administrator, or you can use a Domain

Administrator account when it has been granted all local administrator rights

and is part of the local administrators group

Video resolution should be at least 1024 by 768 and, ideally, a higher setting

It is recommended to not install over a mounted share as it may cause time-

outs

2.3. Using the Appropriate User ID During DMC installation, on the database screen, ensure that you provide login

credentials of the user ID with full local administrator rights on the DMC system.

The user ID must be a member of the local administrator group and should have

rights to restart IIS services. If you are using a remote SQL database, the user ID

must also have dbo/dbcreate rights.

3. Installing the DMC Installation of DMC consists of:

o Installation of SIM, the install manager for all Symantec products. The

installation may take up to 5 minutes for SIM to launch after it is installed.

This is because on an offline environment, SIM tries to connect to the online

Download Verification Server and has to time out

o Installation of DMC – This process may take an hour or more

SIM (Symantec Installation Manager) is installed first, which, in turn, installs DMC.

SIM will also stay resident on the DMC server to provide access to future updates,

hotfixes, and upsells.

3.1. Running the DMC Installation Click the install link from the DMC welcome screen. Follow the instruction on SIM

install wizard.

Figure 1: DMC Welcome Screen

3.2. Network Port Fix When you begin installing, a pop up is displayed informing you that the number of

network ports should be increased. This is a registry change that is required to

support the large number of connections that happen when DMC performs discovery

and monitoring tasks. The default number of ports is approximately 15,000 and this

fix increases the number of ports to 64,000 connections. This fix is most important

for large environments, say 2,000 devices and up, but there are circumstances

when even 500 devices may need this registry fix. Reboot the DMC system to apply

the new settings. For more information, see the Configuration and Optimization

whitepaper on the Dell Support website at support.dell.com.

Figure 2: SIM Setup

Figure 3: SIM License Agreement

If you want to install DMC at a location other than the default path on C:\, indicate

that in the SIM install.

Figure 4: SIM Destination Folder

Figure 5: SIM Setup Complete

Figure 6: SIM Install New Products

Figure 7: SIM Install Optional Components

Figure 8: DMC EULA

3.3. Install readiness checks The screenshot is an example of the install readiness of the DMC system.

Figure 3: Install Readiness Checks

ASP .Net: Click the hyperlink to configure ASP Microsoft SQL Server 2005 or 2008

Microsoft Internet Explorer 7 or 8

Microsoft IIS 7

Microsoft Windows Server 2008 R2

Bypass proxy for local addresses

Install Silverlight 3.0 Dual Core Intel Xenon or AMD opteron 2200 series or above

Processor

crl.microsoft.com access check critical: Click Fix: Disable Publisher

Evidence Generation.

o You must fix this warning, or installing DMC in a non-internet

environment (e.g., lab network) may result in a failed installation and

UI latency problems.

To avoid network timeout issues which could impact the installation of DMC, the

certificate revocation (CRL) check must be disabled during the install process.

If your system is online the installer will re-enable signature verification at the

end of the install. The installer tests if your system is online by trying to reach

microsoft.com. If a proxy blocks the installer from reaching microsoft.com, it

will assume that the system is online and re-enable the CRL check. If the

system is not online (e.g., in a "lab" environment) the installer will try to keep

the check disabled to improve DMC run-time performance.

NOTE: To manually remove this change, edit the XML from the

machine.config file. For more information, see the KB.

http://support.microsoft.com/kb/936707

About Microsoft Authenticode signature

Notification Server uses many Microsoft .NET Framework managed

applications. A Microsoft .NET Framework managed application that has a

Microsoft Authenticode signature takes longer than normal to start. Because

this delay occurs with web applications, it causes delays in console page

loads.

CAUSE:

This problem occurs because the signature is always verified when the .NET

Framework-managed assembly has an Authenticode signature. The problem

may also occur because of other settings such as the network configuration.

RESOLUTION:

A configuration setting can be used to disable signature verification in a .NET

Framework-managed application. You use this configuration setting in the

system machine.config configuration file. The machine.config file is located

in the .NET Framework %runtime install path%\Config directory. Add the

following code to this file: This code disables signature verification and

the .NET Framework managed applications start faster. Note: When you

disable signature verification, the .NET Framework managed applications no

longer receive publisher evidence. This behavior affects the .NET Framework

managed application only when you use publisher evidence or when you use

the PublisherIdentityPermission

REFERENCES:

http://support.microsoft.com/kb/936707

http://support.microsoft.com/kb/941990.

For more information, search support.microsoft.com for "CRL".

4. Deploying the Altiris Agent Although deploying the Altiris Agent is a post-installation step, you should be aware

that the Altiris agent is required only Dell Patch Management and Server

Administrator Deploy features. It is not required for discovery, inventory, and health

monitoring of Dell systems.

4.1. Prerequisites The user credentials required for Altiris Agent push must have access to the

admin$ share. You can check for these privileges by entering

\\yourhostname\admin$

Ensure that the DMC system allows downloading of executable files. The Altiris

Agent installer is an .exe that is downloaded to the DMC system and runs

during the installation of DMC.

If you have discovered a system that has a Dell Remote Access Controller

(DRAC), the Altiris Agent may be pushed to the server, and not the DRAC itself.

Check the IP address in the agent install log file ([default install

path\altirisagent\logs) to ensure the IP address of the target system is that of

the server and not the DRAC.

4.2. Altiris Notification Server and Altiris Agent User Security Requirements

For Altiris Agent application identity, the user credentials should have local

administrator rights to the Notification Server. If you are using this account is for

the Altiris Agent Push tasks, it must also have the following rights:

Installing and running as a service (Logon as a Service),

Creating and removing folders.

Writing to the admin$ share.

Acting as part of the operating system.

Impersonating a client after authentication.

Accessing the registry.

Altiris Agent push mechanism uses hostnames (instead of IP address) during

installation. Ensure that you configure the DNS or add an entry in the host file under

<drive>\WINDOWS\system32\drivers\etc\ on the DMC system.

4.3. Logs during Altiris Agent Install Enable up to trace level logging on the LogViewer.

Review agent.log under agent install folder for more information.

Altiris Agent Installer Service

These are a useful place to look at logs if the agent fails to install. These logs are

available in the windows directory, usually c:\windows

AltirisAgentInstSvc.log

AltirisAgentInstSvc_del.log

4.4. Upgrading to the latest version of DMC Upgrading from DMC 1.x to DMC 2.x is not supported only data migrations is

supported. Follow following steps to migrate data to DMC 2.0

When upgrading from DMC 1.x to DMC 2.0 you are moving from a 32 bit to a

64 bit platform. The change in platform does not support a direct upgrade path

instead you must run a database migration. Before installation of DMC 2.0 and

running the migration please read DMC User Guide available

at:http://support.dell.com/support/edocs/software/smdmc/

After Database Migration, Altiris Agent Report will still be present even though

the feature is obsolete in DMC 2.0.

After DMC 1.x to DMC 2.0 migration, if you are not able to use the already

imported Server Administrator packages in the Agent Deploy Wizard then you

have to delete them from the Software Repository, re-import the packages and

use them for Server Administrator Deployment Task Wizard.

In the Altiris Log Viewer if you see "Authentication: Response to server

challenge denied, check credentials are correct. Error code: -2146893048",

there is no functional impact, and you may ignore this error message.

In the Altiris Log Viewer, if you see "Unable to get product details for the

specified product (Product Guid:Symantec Management Agent for UNIX, Linux,

and Mac 7.1 (c98d8bbb-70b9-4c39-ba55-110b2d07cbd6), MSI Product Guid:

8aa030b3-917a-49d8-a19b-f63c47ee23a0)", there is no functional impact, and

you may ignore this message.

In the Altiris Log Viewer, if you see "Failed to load row from MSI Upgrade table",

there is no functional impact, and you may ignore this message.

In the Altiris Log Viewer, if you see "Failed to load row from MSI Upgrade table",

there is no functional impact, and you may ignore this message.

When you run the migration wizard import process, you might see "Failed to

meet baseline requirements" message. There is no functional impact, you may

ignore this message.

Associated Dell devices task created prior to Migration will no longer function

after the Migration. A new associate Dell devices task has to be created.

After database migration, the migrated ESXi device primary health is displayed

as Undetermined and the Connection state is displayed as Disconnected.

Manually delete the device from the console and re-discover the device to

render accurate health.

5. Post-Agent Install Issues Enable the Altiris Agent diagnostics tool:

1. Register AexAgentDiagnostics dll with regsvr32.

2. Right-click the agent system tray icon and select Diagnostics.

5.1. Agent Debugging FAQ: Can you connect to remote system or database?

Answer: Logs tab on the agent diagnostics window will provide this info

Can you access the admin$ share?

Answer: The current error message in the log is as follows:

“Failed to copy the eXpress Client service to

\\<IP>\ADMIN$\AeXSWDInstSvc.exe.

Error: Access to the path \\<IP>\ADMIN$\AeXSWDInstSvc.exe is denied.”

See KB#45717 for more information.

Can the .exe files be downloaded?

Answer: The current error message would be something like this:

Process: aexsvc.exe (280)

Thread ID: XXXX

Module: AltirisNativeHelper.dll

Source: Altiris.NS.Utilities.RemoteServiceMgr

Description: Failed to copy the eXpress Client service to

\\XX.XX.XX.XX\ADMIN$\AeXSWDInstSvc.exe. Error:The process cannot

access the file "\\XX.XX.XX.XX\ADMIN$\AeXSWDInstSvc.exe" because it is

being used by another process. This type of failure can occur if a client push

is currently in progress or has completed but some files are still locked. This

problem can typically be solved by rebooting the computer

See KB#21574 for more information

Can you access the registry?

Answer: It should be on the a.log on the server side.

Is communication lost between NS and the agent?

Answer: Logs tab on the agent diagnostics window will provide information on

every connection attempt to the NS server and their status.

Is there possibility of a DNS error?

Answer: See if DNS is working properly by pinging the client computer opening a

command window and entering:

ping -a <IP address>

If DNS is working properly, the "-a" should cause the Computer Name to be

returned as follows:

Pinging <Computer Name> [IP address] with 32 bytes of data.

If the computer cannot be pinged and you cannot access the Admin$ share, it is

likely a DNS issue and will need to be handled by the network admin for the

network affected.

See KB#21574 for more information.

5.2. Install Logs

To view the install logs:

Go to Start-> Run and type %temp%.

The latest logs are available in the SIM Logs directory.

To search for errors, search for text for severity="2" or severity="1" errors.

These logs are needed to debug installation issues.

5.3. Other Logs and Debug Mechanisms SIM, Notification Server, and Windows Event logs:

You can find the notification server in default install dir C:\program

files\dell\sysmgt\. Windows logs are available through Event Viewer in

Administrative tools.

A copy of the product listing that was being used by SIM at the time of the

error. You can find the listing (dell.pl.xml) in the root DVD drive.

A screen shot of the error that displays not only the error dialog, but the state

of SIM at the time of the error (that is, the status bar at the bottom of SIM that

displays what is installed and the overall percentage of install).

IIS: Can you load DMC Console pages in the IE7 browser? If not pages, what

about static files, such as images? Are the Altiris, Dell virtual directories visible

in IIS?

A directory listing of the [install location]\Altiris directory and subdirectories.

An export of the HKEY_LOCAL_MACHINE\SOFTWARE\Altiris registry key.

5.4. Uninstalling after a Failed Install

If you get in a situation where an install failed and you cannot uninstall, here are the

steps to remove a failed install.

http://en.community.dell.com/groups/dell_management_console/media/p/19451341.asp

x

5.5. More Info For updated information, see:

o DMC FAQ.

o Symantec Knowledge Base

5.6. Using Dell Private Product Listing You can use the online global product listing to get the latest Symantec solutions,

patches, hot fixes, and DMC. However, you need a connection to the Internet. After

verifying that you have access to the Internet:

1. Launch the Symantec Installation Manager through Program Files->

Altiris-> Symantec Installation Manager.

2. Click Settings in the start-up page of Symantec installation Manager.

3. Click Change product listing.

4. Enter the location

5. http://www.solutionsam.com/solutions/pl/dell.pl.xml

6. Click OK.

On the main SIM page, click Install New Products. You now have access to the

latest solutions and updates.

5.7. Manually performing the CRL fix (Critical) When you start a Microsoft .NET Framework 2.0 managed application that has a

Microsoft Authenticode signature, the .NET Framework 2.0 managed application

takes longer than usual to start and may fail the DMC installation.

This problem occurs because a .NET Framework 2.0 managed assembly that has an

Authenticode signature that takes longer than usual to load. The signature is always

verified when the .NET Framework 2.0 managed assembly has an Authenticode

signature loaded.

You must have the .NET Framework 2.0 installed before you follow these directions.

You do not have to restart the computer after you make these changes.

These instructions add the generatePublisherEvidence configuration setting to

the .NET Framework 2.0.

To do this, add the following code to the machine.config file for the .NET Framework

2.0 managed application. This code can be inserted at the top of the file on the

next line below the: <?xml version="1.0" encoding="utf-8"?> line of code. This

code should be inserted using Notepad or WordPad and saved in text format.

Please make a backup copy of the file before proceeding.

(To revert it back to the default state, you can change “false” to “true”.)

<configuration>

<runtime>

<generatePublisherEvidence enabled="false"/>

</runtime>

</configuration>

6. Altiris Knowledge Base Articles http://www.symantec.com/business/support/index?page=home

Article ID: 43648 "FAQ for the release of the Symantec Management Platform 7.0"

Article ID: 43515 "How to enable MSI failures logging for Repairs, Uninstalls, or

Installations with Symantec Installation Manager (SIM 7)?

Article ID: 44245 "After installing NS 7.0, unable to access NS Console: An error

has occurred that prevents the Symantec Management Console displaying

correctly."

Article ID: 45462 "What is and how the Migration/Upgrade Wizard works?"

Article ID: 45132 "What and Where is NSConfigurator utility on NS 7?"

Article ID: 46797 "Getting "Exception encountered while verifying web service:

System.Net.WebException: The operation has timed out" warnings during Symantec

Installation Manager 7 installation process."

Article ID: 46638 "During SIM7 installation, the following error appears, causing

SIM7 to fail: "A critical error occurred: Product failed to install. See log for details.

Configuration failed while attempting: Configure..." "

Article ID: 46439 "Getting 'DownloadFile - No response was received during the

time-out period for a request' in the logs when trying to load the Product Listing on

SIM7."

Article ID: 46319 "CMS7 fails when installing the components saying: "Error During

Installation. Install could not continue because the web service was not available at

http://Servername.Domain.Com:80" “

Article ID: 46972 "How I can change the database information for the Symantec

Management Platform 7?"

Article ID: 46940 "How to use PreferredNSHost with Symantec Management

Platform 7 (NS7)?"

Article ID: 44263 "How to uninstall Symantec Installation Manager (SIM 7)

manually?

Article ID: 43253 "Why the available Suites/Solutions appear grayed out after using

the extracted files for SIM?"

Article ID: 43661 "The install of Symantec Management Platform (7.0.3798) failed

with a return code of 1638."

Article ID: 46193 KNOWN ISSUE: Error on Update Resource Membership Page

Article ID: 43175 "What Information should I collect for troubleshooting Symantec

Installation Manager 7.0 (SIM7)?"

Article ID: 46034 "Creating an installation package with Symantec Installation

Manager 7 (SIM 7)"

Article ID: 46128 "Can I use NS6 licenses on NS7 that are still valid?"

Article ID: 45916 "During initial installation for CMS7 using SIM 7, the following

message occurred: "Configuration failed A critical error occurred: The request failed

with HTTP status 401: Unauthorized. Configuration failed while attempting:

Configuring services."

Article ID: 45807 "When installing a Solution or Suite with Symantec Installation

Manager 7 (SIM7), the message "The following files have failed to validate for the

file

altiris_filename.msi. This error will not allow me to continue." appeared."

Article ID: 45762 "You are unauthorized to download one or more products in your

selection when using Symantec Installation Manager (SIM) 7.0"

Article ID: 45714 "Known Issue: If you attempt to uninstall Symantec Installation

Manager (SIM) using Add/Remove Programs, the Altiris Agent will crash"

Article ID: 46318 "When running the Symantec Installation Manager(SIM)

Credentials are required to connect to www.solutionsam.com"

Article ID: 45803 "Altiris 7 Planning and Implementation Guide - v1.1"

Article ID: 45569 "Upgrading to Symantec Management Platform 7.0 on a different

computer"

Article ID: 45597 "Symantec Management Platform Capacity Planning"

Article ID: 45092 "On-Box SQL Server Maximum Memory Settings"

Article ID: 44969 "Migration of 6.x Data to Symantec Management Platform 7.0"

Article ID: 45732 "Installing the Symantec Management Platform products"

Article ID: 45865 "KNOWN ISSUE: Symantec Installation Manager cannot be

installed to a mapped network directory"

Article ID: 45152 "KNOWN ISSUE: Unable to migrate 6.x data to Symantec

Management Platform 7.0"

Article ID: 46030 "Minimum System Requirements for Symantec Management

Platform 7.0"

Article ID: 46349 "Symantec Management Platform Support Matrix"

Article ID: 45844 "How to run a repair in Notification Server 7"

7. Installation Issues - Appendix Installing Dell Management Console version 2.0

The Dell Management Console Install Guide is available on the Dell Tech Center

website at www.delltechcenter.com. See the Dell Management Console page in

the OpenManage Systems Management section. Also see the Dell Management

Console User‟s Guide on the Dell Support website at support.dell.com/manuals

for more information on installing the Dell Management Console.

Symantec Installation Manager (SIM) is the installer for Dell Management

Console. It may take several minutes to launch SIM if your server is not

connected to the Internet.

If you do not have access to the Internet, you can only install products

locally available on the Dell Management Console DVD.

When SIM is launched for first time prior to DMC install, it may throw an

error dialogue box saying "Symantec Installation Manager has encountered a

fatal exception and cannot continue. Please see the log file for more

information".

This is a known issue, this error occurs as SIM tries to point to global product

listing instead of dell product listing. Work around for this is to continue the

installation without clicking "ok" on the exception dialog box.

For DMC 2.0 installation we have the following three optional components:

1. „Install Documentation‟

2. „Install Language Support‟ and,

3. „Install Migration Wizard Components for migrating Dell Management

Console data‟

If only some of the above three components are selected at the time of DMC

installation, for the remaining non-installed components SIM may show install

option as grayed out. To enable the install option for the non-installed

components, go to 'Settings' tab and click 'Update Now' button.

To view the Tutorials on the DVD, make sure you have Windows Media

Player installed. In Windows Server 2008 this comes with Desktop

Experience: http://technet.microsoft.com/en-us/library/cc772567.aspx

During install, take note of the following:

o Do not disable or disconnect any network port while the installation

is in progress.

o Dell Management Console may require more available ports for

agentless monitoring support. This change requires a system restart.

http://technet.microsoft.com/en-us/library/cc758002%28WS.10%29.aspx

o If you are using a remote SQL database on a system that has its firewall

enabled, ensure that the firewall ports are open for the SQL Server

instance to which the Symantec Platform will connect; otherwise you

will encounter errors during installation. Alternatively, disable the

firewall completely.

o Refer to this article on How to configure SQL Server 2005 to allow

remote connections: http://support.microsoft.com/kb/914277

o Refer to this article for an overview and network port requirements

for the Windows Server system: http://support.microsoft.com/kb/832017

o To prevent Microsoft Windows Installer conflicts, do not run another

install while Dell Management Console installation is in progress.

o Register at http://www.dell.com/openmanage/register to receive a free Dell

Management Console license. When installing the free Dell

Management Console license, the license Web part is removed from

the Dell Management Console portal page and you can customize

the portal page.

After installing Dell Management Console 2.0, do the following:

o Enable the Altiris(R) Agent upgrade policy so that the Agent-based

functionality is not interrupted.

o For Windows Altiris Agent: Go to Settings > All Settings >

Agents/Plug-ins > Altiris Agent > Windows > Altiris Agent for Windows -

Upgrade. Change this policy to On and save changes.

o For Linux Altiris Agent:

Go to Settings > All Settings > Agents/Plug-ins > Altiris Agent UNIX/Linux/Mac

> Altiris Agent for UNIX/Linux/Mac – Upgrade Change this policy to On and

save changes.

o After a successful upgrade of the Altiris Agent on the Dell Management

Console system, if the Monitor Agent service has stopped, ensure that you

restart the service manually.

o Be aware the proper operation of the Altiris agent on the managed systems

may require opening ports on any firewall that may be in operation.See the

Dell Management Console Ports document in the Dell Management Console

section of the www.delltechcenter.com website.Refer to this whitepaper for

information on network ports used DMC:

http://en.community.dell.com/groups/dell_management_console/media/p/1

9527831.aspx

8. Resource Links

The Dell TechCenter

http://www.delltechcenter.com/page/Dell+Management+Console

Altiris Knowledge Base Articles

http://www.symantec.com/business/support/index?page=home

Juice User Community: A community for Symantec customers and End

Users

http://www.symantec.com/community/

Video Tutorials

o DMC 2.0 media contains a bunch of video tutorials under tutorial

folder.

o Refer to "tutorial\Database Migration" folder on the media for videos

related to migrating database from DMC 1.x to DMC 2.x

environment.

9. SQL Appendix

By default, SQL Server 2005 Express Edition and SQL Server 2005 Developer

Edition do not allow remote connections.

http://support.microsoft.com/kb/914277

Potential causes of the "SQL Server does not exist or access denied" error

message

http://support.microsoft.com/kb/328306

9.1. Steps to Install SQL EXPRESS 2005 for use with Dell Management Console

1. From the Dell Management Console initial startup screen, select Minimum

System Requirements

2. Select SQL Express from the menu

3. Accept the Microsoft License Agreement

4. Click "Install" to proceed with the installation.

5. Click "Next" to continue.

6. Click "Next" to continue.

7. Ensure all components are listed with green check marks, and click next to

continue.

8. Fill out the Name and Company info. Be sure to "uncheck" the "Hide Advanced

Configuration Options" check box. Click next continues.

9. Below are the minimum requirements needed for Dell Management Console on

SQL Express 2005. Ensure your options are at least equal to what is listed below.

Click next to continue.

10. ***Most Important Step of the Document*** Be sure to select Default

Instance. DMC may not run properly under a Named Instance. Click "Next" to

continue the installation.

11. Ensure that the "SQL Server" and "SQL Browser" services are selected. It is

recommended to use the built-in System account to start these services.

12. Either Windows Authentication Mode or Mixed Mode are acceptable and

supported selection for Dell Management Console. If choosing Windows

Authentication Mode, please select "Next" to continue. If selecting Mixed Mode,

please enter a password for the "sa" login credential and select "Next" to continue.

13. On the Collation Screen, accept the defaults and select "Next" to continue with

the installation.

14. Please ensure both boxes are checked and click "Next" to continue.

15. Please ensure that both boxes are not checked and click "Next" to continue.

16. Click "Install" to proceed with installation.

17. Ensure all components have installed correctly (green check marks). If they

have not, please uninstall and retry the installation.

18. Click "Finish" to finalize the installation. Now you are ready to proceed with the

installation of Dell Management Console using SQL Express 2005.