POWER SOLUTIONS

More documents

Recommendations

Info

SYSTEMS MANAGEMENTConsole, Altiris eXpress Deployment DataStore, and Altiris eXpressDeployment Server.For each managed server on which administrators intend toinstall Dell OpenManage Server Administrator, they must first installthe Altiris agent software. For Windows systems, the simplest way toinstall the agent is to click the Remote Agent Install icon in the taskbar of the Deployment Server Console. For systems running Red Hat ®Enterprise Linux 2.1 (or later), administrators must install the Linuxagent manually—push installation is not available out-of-the-box forLinux servers, although many administrators deploy Linux imageswith the Altiris agent already installed. When a simple installationof the Deployment Server is performed, the Altiris Linux agent isavailable in the c:\Program Files\Altiris\eXpress\Deployment Serverdirectory. The name of the agent is altiris-adlagent-x.y-b.i386.rpm—for example, altiris-adlagent-2.2-14.i386.rpm. Administrators musttransfer this Red Hat Package Manager (RPM) file locally to theLinux system and run a simple RPM installation. After the installation,they can configure the agent by running the configure utilityunder the /opt/altiris/deployment/adlagent/bin directory. Once theAltiris agent is installed, an icon representing the server is createdin the Altiris console. From that point forward, Linux serversare managed through many of the same features used to manageWindows servers.With a simple installation as described in this article, administratorscan launch the Deployment Server Console, view the Windowsand Linux managed servers, and begin setting up jobs to remotelydeploy Server Administrator onto these remote managed systems.Altiris Deployment Solution provides a sample job for installing ServerAdministrator on Dell servers. This article describes some advancedconcepts beyond the scope of the sample job. Figure 1 shows the DeploymentServer Console with two active computers: a Dell PowerEdge 2800 server running Windows Server 2003 and a PowerEdge 2600server running Linux. The Jobs pane of this console shows severalAltiris Deployment Solution jobs—described in the followingsections—that can be executed on these servers.Deploying Server Administrator on WindowsThis section describes the various Altiris Deployment Solution jobsthat can be used to deploy Dell OpenManage Server Administratoronto Windows-based servers.Prerequisite checkingThe Prerequisite Checker is a utility independent of the ServerAdministrator installer. It should be used in tandem with the installerto help ensure that the server meets the specified requirements priorto deploying and executing the installer via msiexec.exe.The Prerequisite Checker utility is located at /srvadmin/windows/PrerequisiteChecker/runprereqchecks.exe on the Dell Installationand Server Management CD. Administrators can script the executionof this utility with an /s parameter that invokes the utilitysilently. This invocation returns one of several return or errorcodes. For more details, see the Run Script task in Figure 2. Inaddition to the return code, administrators can query the WindowsRegistry for feature-level detail regarding which features will beaffected by a prerequisite warning or error.The installer package expects the Prerequisite Checker to havebeen executed prior to the installation. Upon launch, it will querythe registry for the prerequisite check results and then deselectdefault features that indicate a warning and disable features thatindicate an error. If the prerequisites are not run, the installer willapply the features selected for installation and Server Administratormay, as a result, run in a degraded state.Administrators should use the Altiris Job Wizard and create ajob to execute the Prerequisite Checker. Next, they should add aRun Script task to the job and embed the script shown in Figure 2.Administrators should run this job on all servers to which they planto deploy Server Administrator and correct any failed prerequisites.Express installationSeveral methods are available to install Server Administrator.The Express Install job applies the default features available in theMicrosoft Windows Installer (MSI) package. Administrators can executean express installation by issuing the following command:msiexec /qa /i /srvadmin/windows/SysMgmt/SysMgmt.msi /l*v c:/sysmgmt.logFigure 1. Altiris Deployment Server ConsoleThe /qa parameter invokes the installation silently while the/l*v parameter logs the progress of the installation to the specifiedfile. Several return codes could result from executing the installationcommand. These codes should be evaluated to determine whetherthe installation was successful. Figure 3 shows common error codesfor an express installation on a Windows system.Note that Altiris jobs can be configured to watch for specificreturn codes and to reroute job functions based on specific values.34DELL POWER SOLUTIONS Reprinted from Dell Power Solutions, August 2005. Copyright © 2005 Dell Inc. All rights reserved. August 2005
SYSTEMS MANAGEMENT@ECHO OFFREM Run Prerequisite CheckerREM\\altiris_1\srvadmin\windows\PreReqChecker\RunPreReqChecks.exe /sSET ERRORLEV=%ERRORLEVEL%REM Prereq ErrorIF %ERRORLEV%==3 GOTO ErrorLabelREM Prereq WarningIF %ERRORLEV%==2 GOTO WarningLabelREM Prereq InformationIF %ERRORLEV%==1 GOTO SuccessLabelREM Prereq SuccessIF %ERRORLEV%==0 GOTO SuccessLabelREM Other errorsGOTO OtherLabel:SuccessLabelEXIT 0:FailureLabelEXIT %ERRORLEV%:WarningLabelREM Prerequisite Check reported a WarningEXIT 0:OtherLabelREMREM process return code if desiredREM - Prerequisite checker did not run.REMREM -1 Windows Host Scripting ErrorREM -2 Operating system not supportedREM -3 User lacks Administrator privilegesREM -4 UnusedREM -5 Failed to change working directory to %TEMP%REM -6 Destination directory does not existREM -7 Internal errorREM -8 An instance is already runningREM -9 Windows Host Scripting Error: wrongREM version, corrupted or not installedREM -10 Error with scripting environmentEXIT %ERRORLEV%Figure 2. Prerequisite Checker sample script for Windows systemsFor example, the default setting for a return code of zero willallow the job to advance to the next sequenced task included inthe job. For a return code of 1603, administrators may want touse the Altiris LogEvent utility to write a specific message backto the Altiris console and store it in the database. In the case of a1602 code, administrators may want the console to display “Theuser canceled the installation.” 1Administrators can use the Altiris Job Wizard to create aSoftware Deployment Job. When the wizard prompts, administratorsshould browse to the /srvadmin/windows/SysMgmt/SysMgmt.msiinstallation package on the Dell Installation and Server ManagementCD. In the Package Distribution Options pane associated with thepackage, administrators should select “Copy all files and subdirectories”and add the logging parameter to the optional parametersfield as discussed earlier. Administrators should run this job on allservers on which they want Server Administrator installed.Note: Best practices recommend that the installation packageis deployed only to servers that have successfully executed thePrerequisite Checker job with no warnings or errors. Administratorscan enforce this recommendation by defining specific returncode actions. For more information, see the Altiris DeploymentValueDescription0 The action completed successfully.1601 The Windows Installer service could not be accessed.1602 The user canceled the installation.1603 A fatal error occurred during the installation.1618 Another installation is already in progress.1619 The installation package could not be opened. The administratorshould verify the package exists and that it is accessible.1638 Another version of this product is already installed.1639 An invalid command-line argument was provided.1641 The installer has started a reboot after a successful installation.Figure 3. Common return codes after an express installation on a Windows systemSolution 6.1 Product Guide at www.altiris.com/docs/support/deploymentserver/6.1/deployment.pdf.For sample scripts to repair installation and uninstall DellOpenManage Server Administrator, visit Dell Power Solutionsonline at www.dell.com/powersolutions.1For more information about using the Altiris LogEvent and WLogEvent utilities within custom code, see page 170 in the Altiris Deployment Solution 6.1 Product Guide at www.altiris.com/docs/support/deploymentserver/6.1/deployment.pdf.www.dell.com/powersolutions Reprinted from Dell Power Solutions, August 2005. Copyright © 2005 Dell Inc. All rights reserved. DELL POWER SOLUTIONS 35
Page 2 and 3: Gigabit EthernetMulti-Gigabit Ether
Page 4 and 5: TABLE OF CONTENTSPOWERSOLUTIONSTHE
Page 6 and 7: TABLE OF CONTENTSDATABASE TECHNOLOG
Page 8 and 9: EDITOR’S COMMENTSRelational Bliss
Page 10 and 11: SYSTEMS MANAGEMENTTake Control with
Page 12 and 13: SYSTEMS MANAGEMENTInstrumented plat
Page 14 and 15: SYSTEMS MANAGEMENTinterface (CLI) a
Page 16 and 17: SYSTEMS MANAGEMENTIntroducing Dell
Page 18 and 19: SYSTEMS MANAGEMENTA query definitio
Page 20 and 21: SYSTEMS MANAGEMENTremote agents. Fo
Page 22 and 23: SYSTEMS MANAGEMENTError code Error
Page 24 and 25: SYSTEMS MANAGEMENTFigure 3. Wbemtes
Page 26 and 27: SYSTEMS MANAGEMENTSoftware Change M
Page 28 and 29: SYSTEMS MANAGEMENTDell UpdatePackag
Page 30 and 31: SYSTEMS MANAGEMENTFigure 5. Summary
Page 32 and 33: SYSTEMS MANAGEMENTIT Assistant UI I
Page 34 and 35: SYSTEMS MANAGEMENTFigure 3. Configu
Page 38 and 39: SYSTEMS MANAGEMENTDeploying Server
Page 40 and 41: SYSTEMS MANAGEMENTAdvancing the Upd
Page 42 and 43: SYSTEMS MANAGEMENTallows administra
Page 44 and 45: SYSTEMS MANAGEMENTTime-Savings Vali
Page 46 and 47: SYSTEMS MANAGEMENTBENEFITS OF ALTIR
Page 48 and 49: SYSTEMS MANAGEMENTLANDesk Server Ma
Page 50 and 51: SYSTEMS MANAGEMENT• SEL event cre
Page 52 and 53: SYSTEMS MANAGEMENTAdministrators ca
Page 54 and 55: SYSTEMS MANAGEMENTUsing the DRAC 4
Page 56 and 57: SYSTEMS MANAGEMENTVirtual floppy me
Page 58 and 59: SYSTEMS MANAGEMENTUpdating theDell
Page 60 and 61: SYSTEMS MANAGEMENTthe overall Power
Page 62 and 63: SYSTEMS MANAGEMENTFor the firmware
Page 64 and 65: DATA CENTER TECHNOLOGYGuidelines fo
Page 66 and 67: DATA CENTER TECHNOLOGYusing the tem
Page 68 and 69: DATA CENTER TECHNOLOGYInformation L
Page 70 and 71: DATA CENTER TECHNOLOGYdata center:
Page 72 and 73: DATA CENTER TECHNOLOGYresources and
Page 74 and 75: BUSINESS CONTINUITYe-mail systems u
Page 76 and 77: BUSINESS CONTINUITYGalaxy and Backu
Page 78 and 79: STORAGE TECHNOLOGYWhen migrating fr
Page 80 and 81: STORAGE TECHNOLOGYwhich can lead to
Page 82 and 83: STORAGE TECHNOLOGYChannel ports; al
Page 84 and 85: STORAGE TECHNOLOGYMaximum zone sets
Page 86 and 87:
STORAGE TECHNOLOGYbenefits includin
Page 88 and 89:
STORAGE TECHNOLOGYmemory manager wa
Page 90 and 91:
STORAGE TECHNOLOGYLink-Level Error
Page 92 and 93:
STORAGE TECHNOLOGYThe extended link
Page 94 and 95:
STORAGE TECHNOLOGYMigrating from De
Page 96 and 97:
STORAGE TECHNOLOGYFigure 3. Managin
Page 98 and 99:
DATABASE TECHNOLOGYFast, Flexible C
Page 100 and 101:
DATABASE TECHNOLOGYScaling Out SQL
Page 102 and 103:
DATABASE TECHNOLOGYMSN Communicatio
Page 104 and 105:
DATABASE TECHNOLOGYThe MSN CSP appl
Page 106 and 107:
DATABASE TECHNOLOGY1,20070Transacti
Page 108 and 109:
DATABASE TECHNOLOGYAdvantages of OC
Page 110 and 111:
DATABASE TECHNOLOGYASM instance ins
Page 112 and 113:
VIRTUALIZATION TECHNOLOGYDomain 0 V
Page 114 and 115:
SYSTEM ARCHITECTUREImproving Fault
Page 116 and 117:
SYSTEM ARCHITECTUREBIOS Hot Hotopti
Page 118 and 119:
SYSTEM ARCHITECTUREinitialized. The
Page 120:
If you’re paying unreasonable lic
show all

POWER SOLUTIONS

Create successful ePaper yourself

Delete template?

Save as template?