Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Quickstart Guide: Dell Client Manager 2.0

Updated: 07 Jul 2009
Jordan Gardner's picture
Jordan Gardner
Symantec Employee
Accredited
0 0 Votes
Login to vote

Gentlemen, (and ladies) fire up your servers. This "quick start" guide covers the fundamentals necessary to install and configure Altiris Dell Client Manager.

Technical Strategist Jordan Gardner lives and breathes this stuff. Lucky for us, he writes about it too.

Introduction

This document is provided to help you install and configure Altiris Dell Client Manager. More detailed documentation is bundled with the product download. Altiris recommends that, after using this Quickstart Guide, you refer to the included product documentation to learn more about all the Altiris features and configuration options. Please note that the latest Altiris documentation can also be downloaded and studied in advance of the product installation at http://www.altiris.com/support/documentation/.
For more information about all of the solutions which Altiris provides, visit: http://www.altiris.com/products/.

Installation

Follow these steps to install Dell Client Manager

Step 1: Prerequisites

The Altiris Dell Client Manager Solution is one of many solutions that plugs into the Altiris Notification Server. (For more information on Altiris Notification Server, read Appendix A). The Altiris Notification Server is a free component which has the following minimum requirements:

  • Intel Pentium III 800 MHz, 512 MB RAM, 5 GB FREE DISK SPACE
  • Windows 2000 Server (SP4) or Windows Server 2003. *Cannot be a Domain Controller
  • .NET Framework (v1.1 or later)
  • Internet Information Services (IIS), with ASP.NET enabled
  • MS SQL 2000 (SP3 or later) or SQL 2005 database. (MSDE 2000 or SQL 2005 Express may be used for evaluation purposes, however are not recommended.)

Step 2: Obtaining Dell Client Manager Software

The steps below will assist you in downloading the Altiris Installation and Configuration Manager (AICM). AICM will assist you through the setup and installation of Notification Server and Dell Client Manager.

  1. To download Dell Client Manager 2.0 point your browser to:
    http://www.altiris.com/eval/dell

  2. Enter your email and select Dell Client Manager Standard from the drop down list.
  3. Click Submit to begin downloading the setup.
  4. Click Yes to agree to the End User License Agreement.
  5. Click Dell Client Manager via Download Altiris Installation and Configuration Manager.
  6. Click Save.

Step 3: Install Dell Client Manager via AICM

The Altiris Installation and Configuration Manager (AICM) will step you through the installation and configuration of the Altiris Notification Server and Dell Client Manager.

  1. Double-click on the "Altiris Dell Client Manager Standard.exe" file, obtained in Step 2.
  2. Click Extract & Execute App. This will extract and launch the "Altiris Installation and Configuration Manager".

    Click to view.

  3. Select Download and Install on this computer and click Next.

    Click to view.

  4. Click Next on the "Welcome to the Altiris Installation and Configuration…" dialog.
  5. On step 1 of 8, Accept the terms of the license agreement and click Next.
  6. On step 2 of 8, Provide a desired install path and Click Next.

    Note: The default install path C:\Program Files\Altiris is recommended but not required.

  7. Step 3 of 8 will check that the Notification Server minimum requirements are met. If all requirements are met, click Next. For more information on Prerequisites, refer to Step 1: Prerequisites. Note that any requirements labeled with a warning indicator will not cause the installation process to fail. These are informational only.

    Click to view.

  8. Step 4 of 8 will allow you to apply your Dell Client Manager license. By default, a 90 day evaluation license will be installed (although the screen reports 30 days), however an Unlimited Node, Non-expiring Dell Client Manager Standard license can be obtained from here.

    You can obtain and install the free, unlimited license at this time or do it later after Dell Client Manager is installed.

    1. To apply the license, select Apply licenses and click Add.

      Click to view.

    2. From the Add Licenses dialog, you can do the following: 1) Browse to the license .txt file, 2) Browse to the folder which contains the license(s), or 3) Copy & Paste the license contents into the text box. Click OK, then Next to proceed to step 5 of 8.

      Click to view.

      NOTE: Visit this site for information on how to receive an unlimited node, non-expiring DCM license.

  9. Step 5 of 8 will require local Administrative credentials for the Notification Server. These credentials must have rights to: Act as part of the OS, Logon locally, Logon as a Batch Job, and Logon as a Service.

    Altiris Agent credentials may also be supplied. These credentials are used to authenticate to windows machines to install the base Altiris Agent used to communicate with the Notification Server.

    Supply the appropriate credentials and click Next.

    Click to view.

  10. Step 6 of 8 allows you to supply E-mail configuration information used to send notifications when alerts or notification policies are enabled. E-mail configuration can also be performed after the Notification server and Dell Client Manager Solution have been installed, therefore this in an optional step and you may select Later, then Next.

    Click to view.

  11. Step 7 of 8 allows you to provide database information and credentials. Supply the location of the MS SQL Server Database and the appropriate credentials and click Next.

    Click to view.

    Note: If you are using SQL 2005, you must enable TCP/IP in the SQL Config Manager and supply the computer name as the SQL Server name, rather than localhost. If you are using SQL 2005 Express, supply 'localhost\SQLExpress' as the SQL Server Name.

  12. Step 8 of 8 allows you to select or supply Windows client machines which should automatically receive the Altiris base agent. The credentials used in Step 5 of 8 will be used to authenticate to the client machine. The Altiris agent installation can also be performed after the Notification server and Dell Client Manager Solution have been installed, therefore this in an optional step. Select those machines that should receive the Altiris agent and click Next.

    Click to view.

  13. In the Summary dialog, review your settings and click Next to start the Notification Server and Dell Client Manger Installation.

    Click to view.

    img   The installation takes about 30 minutes to complete, however no further interaction is required. Once the Notification Server and Dell Client Manager installation completes, the Altiris Console will automatically open.

Configuration

Every Altiris agent communicates with the Altiris Notification Server on a scheduled basis to update its configuration. Administrators can configure the agent's schedule to check every minute, hour, day or on a weekly basis. By default the Altiris agent is set to check the Altiris Server for new policies every 1 hour. This schedule will effect how quickly policies are pushed out. The goal is to balance the need for frequent configuration updates with the need to minimize network bandwidth dedicated to such tasks. (Note: Each configuration request is less than 5kb in size.)

Step 1: Configure Altiris Agent Settings

Now that the Altiris Notification Server and Dell Client Manager Solution are installed, we need to configure the Altiris agent settings.

To configure the agent update interval and basic inventory schedules for TESTING purposes, follow the steps below:

  1. Launch the Dell Client Manager Quickstart. Start –> All Programs –> Altiris –> Quick Starts –> Dell Client Manager Standard
  2. In the Getting Started Section of the left pane, click on Configure Altiris Agent Settings.
  3. In the content pane, set Request new configuration information every: to 1 minute (testing only).
  4. Set the Send basic inventory every: parameter to 15 minutes.
  5. Click Apply.
img   NOTE: Short configuration request and basic inventory intervals are only recommended for testing purposes.

Enable Hardware Management

Once the Altiris agent settings are configured, it is time to discover and push the Altiris agent to those machines.

Step 1: Discover Machines to Manage

The Altiris Notification Server makes it easy to identify machines in your environment. Follow these steps to perform a machine discovery.

  1. Launch the Dell Client Manager Quickstart. Start –> All Programs –> Altiris –> Quick Starts –> Dell Client Manager Standard
  2. In the Getting Started Section of the left pane, Click on Discover Manageable Resources.
  3. In the Content Pane, click the folder img to open the Domains Picker dialog, or you may type a valid domain or workgroup name in the text box and click the add img button.
  4. Check the Domain Browse List if you are searching for manageable computers within a workgroup, or the Domain Membership if you are searching for manageable computers within a domain.
  5. Click the Discover Now button, to start to computer discovery.
    img   Computer discovery can also be performed on a scheduled basis by checking the Enable Schedule checkbox, and setting a custom schedule for resource discovery.
  6. Click View Discovery Reports to view a list of reports which show the discovered computers.

    NOTE: The discovery process assists in identifying and targeting machines for the Altiris agent installation. It does not install any agents.

Step 2: Install the Altiris Agent on client machines

After resource discovery and configuring the Altiris agent settings, follow these steps to install the Altiris agent.

  1. Launch the Dell Client Manager Quickstart. Start –> All Programs –> Altiris –> Quick Starts –> Dell Client Manager Standard.
  2. In the Getting Started Section of the left pane, click on Install the Altiris Agent.
  3. In the content pane, click the Select Computers… button
    (img) to install the Altiris agent to machines discovered in Step 1, or type the IP address or NetBIOS name into the textbox and click the Add button (img).
  4. Once resources have been added to the text box, img those which are to receive the Altiris agent by holding down the ctrl + right-mouse click.

    Click to view.

  5. Click the Install Altiris Agent button.
  6. In the Altiris Agent Installation Options dialog, check the Use the following admin account instead of application credentials checkbox.
  7. Supply Administrative credentials to install the Altiris agent on the selected machines. These credentials should have administrative rights to install software on the client machines.

    Click to view.

  8. Click Proceed With Install to start the Agent installation on the remote machines.
  9. (Optional) Click View Installation Status Report to view the status on the Agent installation.
    img   The Altiris agent installation takes about 7 minutes to complete. During this process the hardware, OS, and space requirements are checked. The Altiris agent can also be "pulled" from Notification Server to any client machine by pointing the client's browser to: 

    http://<NSSERVERNAME>/Altiris/NS/Agent/AltirisAgentDownload.aspx

Step 3: Enable Installation of the DCM Agent on Dell Clients

In this step we will enable 2 important policies. First, the Dell Client Discovery Policy which will discover (of those machines with the Altiris agent) supported Dell machines. Second, the Dell Client Manager Install Policy, which will rollout the Dell Client Manager agent to support Dell Clients to enable hardware and bios management.

  1. Launch the Dell Client Manager Quickstart. Start –> All Programs –> Altiris –> Quick Starts –> Dell Client Manager Standard.
  2. In the Enable Hardware Management section of the left pane, click on Discover Dell Client Systems.
  3. In the content pane, check the Enable checkbox and click Apply.
  4. In the Enable Hardware Management section of the left pane, click on Configure Agents for 32-bit Hardware Management. (Note: Select "Configure Agents for 64-bit Hardware Management" if you plan to manage 64bit Dell client machines)
  5. In the content pane, check the Enable checkbox and click Apply.

    img   Notice the collections to which this policies apply. You may change these collections to target a specific group of Dell Clients (for lab or testing purposes, for example).

    img   The Dell Client Manager Agent provides the necessary functionality to inventory hardware values and BIOS settings, monitor hardware status and health, and manage the BIOS of Dell client machines.

Hardware Management Tasks

Once the Altiris agent and Dell Client Manager agent are installed on supported Dell clients, hardware management tasks can be performed.

Exercise 1: Enable the Hardware and BIOS inventory policies

Two separate inventory policies allow you to collect Dell Hardware and Dell BIOS information. Administrators can define when these scans should occur, and can even "wake up" powered off machines to perform the scan. In this section, you will explore and enable the BIOS and Hardware Inventory Policies to collect inventory.

  1. Launch the Dell Client Manager Quickstart. Start –> All Programs –> Altiris –> Quick Starts –> Dell Client Manager Standard.
  2. In the Hardware Management Tasks section of the left pane, click on Scan for Inventory Data.
  3. In the content pane, check the Enable checkbox and click Apply.
  4. In the Hardware Management Tasks section of the left pane, click on Scan for Current BIOS Settings.
  5. In the content pane, check the Enable checkbox and click Apply.

Exercise 2: (OPTIONAL) View the Inventory Status on the Client

This optional step will allow you to see what takes place on the Dell client machine when the inventory policies are sent and executed from the Notification Server.

  1. On the target Dell client machine, double click on the Altiris Agent in the SysTray.
  2. Ensure the appropriate "Options" (shown below) are checked
  3. The Hardware and BIOS Inventory Tasks will be listed to the right and should be complete.

Exercise 3: Explore the BIOS and Hardware Inventory Reported

The Dell specific inventory can be view in each Dell Clients Resource manager as well as from the canned reports. In this exercise we will explore the Resource Manager and canned reports.

  1. Launch the Dell Client Manager Quickstart. Start –> All Programs –> Altiris –> Quick Starts –> Dell Client Manager Standard.
  2. In the Reports section of the left pane, click on Inventory.
  3. In the content pane, double-click the Dell Client Hardware in Inventory report
  4. Click Run this report in a new window, to run the report. A report (similar to the one below) will open.

    Click to view.

  5. Double-click the graph to drill-down and view the count of Dell Models.

    Click to view.

  6. Double-click the graph again, to drill-down and view the computer names count of Dell Models.

    Click to view.

  7. Right-click on a computer name listed and select "Resource Manager" from the context menu.

    Click to view.

    img   The Resource Manager is a one-to-one detailed view of a resource (computer, printer, etc.) in the Notification Server.

    img   Dell clients running the DCM agent will contain a Dell Client Manager Summary (shown above).
  8. Click on the Inventory Tab of the Resource Manager.
  9. Expand the Data Classes –> Dell Client Manager Inventory –> Dell Client BIOS Settings folder
  10. Expand the Data Classes –> Dell Client Manager Inventory –> Dell Client Hardware Inventory folder.

    Note the Chassis Intrusion Status, in the SMBIOS Settings data class.

    Click to view.

    img   You can now see the available Data Classes that the Dell Client Manager inventory scans populate. These are the actual table names within the Altiris Database and can be used to create custom reports.

Exercise 4: Use BIOS version reports to create a dynamic collection.

In this step we will use one of the Dell Client Mangers' out-of-the-box reports to create a dynamic collection. This dynamic collection will allow us to correctly target and perform a successful BIOS upgrade.

  1. Launch the Dell Client Manager Quickstart. Start –> All Programs –> Altiris –> Quick Starts –> Dell Client Manager Standard.
  2. In the Reports section of the left pane, click on BIOS.
  3. In the content pane, double-click the Systems with Specified BIOS Version report
  4. Click Run this report in a new window, to run the report.
  5. This report allows you to specify criteria to generate a very specific subset of Dell Machines. Specify the following (modify where necessary) and click Refresh

    Product Line: OptiPlex Desktops
    Model: GX620
    Operator: Older Than
    BIOS Version: A03

    img   This report now lists only those OptiPlex GX620 machines that are running BIOS versions older than A03. Creating a collection to use for a BIOS upgrade from this report can be done in a single mouse click.

    Click to view.

  6. Create a dynamic collection from the BIOS version report to be used later in a BIOS upgrade policy.
  7. From the report click the dynamic collection from report button
  8. A new dynamic collection is created.
  9. Rename the Collection to "GX620's running older than BIOS A03"
  10. Click Apply

Exercise 5: Remotely upgrade the BIOS on you Dell Clients

The Dell Client Manager Solution allows you to remotely upgrade the BIOS on you Dell Machines. To do this, you must first obtain the BIOS file from support.dell.com. In this exercise we will configure the BIOS Upgrade Policy.

  1. Launch the Dell Client Manager Quickstart. Start –> All Programs –> Altiris –> Quick Starts –> Dell Client Manager Standard.
  2. In the Hardware Management Tasks section of the left pane, click on Upgrade BIOS Version.
  3. In the content pane, check the Enable checkbox.
  4. In the content pane, click the Browse… button. Browse to the BIOS Upgrade file (on the desktop)
    img   All available BIOS Upgrade files can be obtained from the Dell support website.
  5. Click the Select collection(s) link. (Collection browser will open)

    Click to view.

  6. In the collection selector dialog, select the collection we created in the earlier exercise. Located in Collections -> Computer Collections -> My Collections -> GX620's running older than BIOS A03
  7. Leave the default scheduling options.
  8. Click Apply.
    img   Using the Collection which we created from the BIOS version report ensures that the correct BIOS upgrade is applied to the correct machines. Since our collection is dynamic, any GX620 machine running BIOS Version older than A03 will automatically receive a BIOS upgrade.

Exercise 6: Remotely configuring BIOS Settings across your network

A 'Dell BIOS Profile' is a template of BIOS settings that you can assign to a collection of computers. Machines included in the assigned collection will then assume those BIOS settings defined in profile. In this section we will remotely configure BIOS settings with BIOS profiles. In this step we will create a BIOS profile by importing inventoried settings.

  1. Launch the Dell Client Manager Quickstart. Start –> All Programs –> Altiris –> Quick Starts –> Dell Client Manager Standard
  2. In the Hardware Management Tasks section of the left pane, click on Configure BIOS Settings
  3. In the content pane, click the Select Profile link.
    img   The BIOS Setting Policy allows you to select a BIOS profile and define a collection to apply it to. One nice feature of using these Profiles is that they're model independent. You can capture the bios profile settings from a Latitude D610 laptop and apply that profile to all your OptiPlex GX620 Desktops. Option not available on the machine BIOS will be ignored.
  4. From the BIOS Profile Selector dialog, click the New button
    img   Dell BIOS Profiles can be created from scratch, by configuring any desired options one at a time, or you can import existing settings from those Dell Clients which have run the BIOS inventory scan.
  5. From the Dell Bios Profile dialog, Click on Import, Click Find, Select an inventoried Dell Client from the list. The inventoried BIOS settings are imported into the BIOS Profile

    img   You can modify any of the BIOS settings imported, such as the BIOS Password, or Boot Order, or Force PXE on next Boot.
  6. In the Dell Bios Profile dialog, check the "Chassis Intrusion" checkbox and set the drop down list value to "Enabled"
  7. In the Dell Bios Profile dialog, check the "Chassis Intrusion Status" checkbox and set the drop down list value to "Clear"
  8. Click Save As, and name the BIOS Profile as "Imported Clear Chassis Intrusion Profile"
  9. Click OK
  10. Click Close
  11. From the BIOS Profile Selector dialog, select the newly created "Imported Clear Chassis Intrusion Profile"

    Click to view.

  12. Click OK
    img   The BIOS Profile will be distributed and applied to the selected collection.

Exercise 7: Monitor Dell Client Machines with Dell Client Manager

The Dell Client Manager allows you to monitor various items on you Dell Machines, such as Chassis intrusion status, memory or disk changes, Operating System Status, etc. In this exercise we will configure and enable the Dell Client Managers monitoring policy and configure an Automated Action. To configure the Dell Client Monitoring Policy:

  1. Drill to Tasks –> Platform Administration –> Dell Client Manger –> Dell Client Monitoring Policies.
  2. Select the Dell Client Monitoring Policy
    img   Notice all the available values and metrics that you can monitor.
  3. In the Right Pane, Check the Chassis Intrusion Status checkbox and set the values to:

    Click to view.

  4. Next to the Chassis Intrusion status dropdown boxes, click the Automated Action link:
  5. Ensure the "Create Incident" checkbox is checked and click on the img to edit the incident.
  6. Edit ONLY the following properties of the incident (as shown below):

    Assigned: Administrator
    Status: Open
    Category: Authorize Approve… Desktop

    Click to view.

  7. Click OK to close the "Create Incident" dialog.
    img   For Monitor Agents, you have the ability to configure automatic actions if any of these areas being monitored raise an alert. You can define a default action for all triggered alerts, and you can override that default action for specific monitored items
  8. (OPTIONAL): You may click the img next to the "Email" automated action to view the details of the email that will be sent when a chassis is opened.
  9. Click Apply to close the "Automated Actions" dialog.
  10. Click Apply to set the changes to the Monitoring Policy.

Exercise 8: Integrate Alert Manager/Helpdesk with DCM

DCM's Monitoring Policy or any Notification Server Policy can create incidents in the Altiris Alert Manager console. (Alert Manager is the free helpdesk console which is a part of Notification Server which allows solutions to create incidents. The full Helpdesk Solution provides the ability to end users and IT administrators to create incidents). In this exercise we will integrate Dell Client Manager with Alert Manager by creating a custom "Smart Task" which will link you to the actual Dell machines warranty and support webpage. To configure the Alert Manager Smart Task:

  1. Click on the Incidents Tab in the NS Console.
  2. In the left pane, create a new Smart Task by drill to: Admin –> Tasks –> New Task (as shown below).

    Click to view.

  3. For Name enter: View Dell Support & Warranty Information.
  4. For Description (Optional) provide: This smart task, when clicked, sends you to the appropriate support and warranty information page for the Dell computer which created the incident.
  5. For Consumer ID provide: Dell Client Manager.
  6. In the "Task is available:" section, select Created by worker from the drop down list and click Add.

    Click to view.

  7. Check the "When the value of 'Created by worker:'" checkbox.
  8. Set the drop down list value to: is equal to.
  9. Select Altiris Dell Client Manager from the drop down list (see below).

    Click to view.

  10. Click OK.
  11. In the "When criteria are true:", set the drop down list to Invoke a URL.
  12. For "Base URL:" supply the string:
    http://support.dell.com/support/topics/global.aspx/support/my_systems_info/en/details
  13. For URL parameters, we will supply 2 parameters:
    1. Name: c (<– The letter "c")
    2. Value: us
    3. Click Add
    4. Name: ServiceTag
    5. For Value, select "Asset serial #" from the drop down list, then img
    6. Click Add (See image below)

      Click to view.

  14. Click OK to save the Task.
    img   Now when any incidents are created from the Dell Client Manager Solution, you will have a smart task available that will take you to the Dell support website where you can view original configuration and warranty information about the Dell computer that is associated with the incident.

Exercise 9: Test the Dell Client Manager Monitor Policy

In this exercise we will test the Dell Client Manager monitoring policy by popping open the chassis and checking helpdesk and our email for the triggered alert.

  1. Perform a chassis intrusion

    1. On the host machine, open the box.
    2. After the chassis has been opened, reattach the chassis.
  2. Check your Helpdesk console for the triggered Incident
    1. Click on the Incidents tab
    2. In the left pane, select Incidents –> Worker Report
    3. In the right pane, click on the All Incidents assigned to me: link
    4. The incident should be listed (see below)

      Click to view.

    5. Double click on the "Dell Client Manager: Chassis Intrusion Alert" incident to view the details. Notice the "Smart Task" which will take you to the Dell Support website.
    6. Read through the incident to see what was sent from the DCM Solution, notice the smart task (displayed below)

      Click to view.

      img   Notice: A smart task is available that will take you to the Dell support website where you can view original configuration and warranty information about the Dell computer that is associated with the incident.
  3. Check your email for the triggered email
    1. From the Start menu, or quick launch bar, open Outlook Express
    2. If no emails appear, click the Send/Receive button
    3. Open and read the automatically generated email.

Appendix A

Notification Server Architecture Overview

The Notification Server architecture is a key component of the Altiris value proposition and a distinguishing characteristic of Altiris solutions over competing products.

All Altiris products which end with "Solution" are built upon the same infrastructure. This infrastructure simplifies management tasks by integrating all the Altiris solutions into a central console that allows data and management functions to be shared across individual solutions. This infrastructure can be deployed to support just one Altiris solution or multiple product suites. Even with multiple suites, all solutions are installed into the same framework so they can work together from the same console. For example, Altiris Server Management Suite, Altiris Client Management Suite and Altiris Handheld Management Suite can all be installed into the same backend server framework to provide a single management console across an entire company for server, desktop and mobile device management. The Altiris role and scope security engine works across all installed solutions.

Click to view.

The key component of this infrastructure is Altiris Notification Server. Altiris Notification Server (NS) is provided to customers without charge and can be installed independently of any Altiris solutions. Without any Altiris solutions installed, the NS console can still be used to push the Altiris agent to managed devices. No meaningful work can be performed on those devices, however, until solutions are installed into NS.

During installation, the NS console creates the Altiris database in an SQL 2000 or 2005 server that can be installed either on the same machine with NS or on a remote server. As evidenced by the above graphic, NS manages communication with the database and with all the remotely installed Altiris agents. It also manages the Altiris web console, Altiris connectors into third party products, and system Notification policies.

Communication between the Altiris agent and Altiris Notification Server fundamentally consists of XML files that are compressed and transferred via HTTP (port 80) or HTTPS (port 443). Altiris Notification Server incorporates a pull agent model. By default each Altiris agent requests a policy update from Altiris Notification Server every 1 hour. In production environments, this interval is generally extended to be every 6 to 12 hours though it may be longer or shorter.

During this update, the agent requests Altiris Notification Server to determine what new policies are associated with it. If at least one policy addition or modification exists for an agent, that agent will download a new policy configuration XML file. This file informs the Altiris agent what work it is to perform. For example, the agent may download and parse the configuration file to determine that it is to run a software inventory scan every 12 hours, a hardware inventory scan once a week, it is to deny access to any unauthorized software programs (games or instant messengers, etc.) during the working hours of 8am to 5pm, and it is to download and execute the most recent Microsoft or Dell patches from the Altiris server immediately. The entire process of downloading the config policy generates a little less than 2K of traffic roundtrip per agent.

As inventory scans are performed or other agent events are triggered, that data is communicated to the Altiris Notification Server as an XML formatted file with an *.nse extension (NSE = Notification Server Event).

All the solutions built on the Altiris Notification Server framework use the same Altiris agent. The agent disk and memory footprint is dynamically extended as needed when new Altiris solutions are installed. Typical disk footprint for the Altiris agent is approximately 5MB to 12MB depending on what solutions are installed and how many policies the user has created.

By leveraging the same infrastructure (policy engine, role/scope security engine, client/server communication model, etc.), Altiris solutions gain incredible efficiencies that are realized in part by the infrastructure's ability to scale. For example, while many competing solutions require 6 to 30 different servers to inventory a 25,000 node infrastructure it is entirely possible for Altiris to simply use one NS server (depending on what solutions are installed and how many policies a customer defines).

Fundamentally, Altiris Notification Server uses policies to associate tasks and software packages with collections. A collection is a grouping of computers. Computers can belong to zero or more collections. There are two types of collections:

  • Static Collections - A computer's membership in a static collection can only change when an administrator explicitly assigns or removes the computer from a collection. When an administrator puts a managed client in a static collection, the client stays in that collection until the administrator removes it.
  • Dynamic Collections - A computer's membership in a dynamic collection changes based on the properties of the computer. As the properties change, the computer automatically moves into and out of dynamic collections. It can be helpful to think of dynamic collections as being based on a SQL WHERE clause. For example, an administrator might create a dynamic collection that consists of all Dell clients where the operating system is Windows 2000 and the client is joined to a specific domain. If anyone of those 3 properties changes on the client then Altiris Notification Server will remove it from the collection.

Dynamic collections are a very powerful mechanism for automating systems management. For example, policies can be created that will, on an ongoing basis, deliver a specific Dell BIOS update to any client system that might require it. Two months after the policy is created, a new client might be added to the LAN. Soon after the Altiris agent is installed on that client, it will be joined to all the predefined collections it qualifies for. When that happens, any policies assigned to those collections will become effective for the new client - the client will then automatically receive not just the BIOS update it needs but it will also execute any other tasks assigned to the policies that govern the computer.

article Filed Under:
,

Technical Support

Symantec.com

Store

Community Stats

Total Content Items
Members
258,921