Altiris® Task Server 6.0
Help
Notice
Altiris® Task Server 6.0 Help
© 2000-2006 Altiris, Inc. All rights reserved. Document Date: December 27, 2006
Information in this document: (i) is provided for informational purposes only with respect to products of Altiris or its subsidiaries (“Products”), (ii) represents Altiris' views as of the date of publication of this document, (iii) is subject to change without notice (for the latest
documentation, visit our Web site at www.altiris.com/Support), and (iv) should not be construed as any commitment by Altiris. Except as provided in Altiris' license agreement governing its Products, ALTIRIS ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTIES RELATING TO THE USE OF ANY PRODUCTS, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY THIRD-PARTY INTELLECTUAL PROPERTY RIGHTS. Altiris assumes no responsibility for any errors or omissions contained in this document, and Altiris specifically disclaims any and all liabilities and/or obligations for any claims, suits or damages arising in connection with the use of, reliance upon, or dissemination of this document, and/or the information contained herein.
Altiris may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights that relate to the Products referenced herein. The furnishing of this document and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any foregoing intellectual property rights.
No part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means without the express written consent of Altiris, Inc.
Customers are solely responsible for assessing the suitability of the Products for use in particular applications or environments. Products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications.
*All other names or marks may be claimed as trademarks of their respective companies.
OpenSSL License
Copyright © 1998-2005 The OpenSSL Project. All rights reserved.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). This product includes cryptographic software written by Eric Young (<mailto:[email protected])> [email protected]).
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment:
“This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)”
4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].
5. Products derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear in their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
Contents
Chapter 1: Introduction to Task Server 6.0 . . . 4
Tasks vs. Policies . . . 5
Chapter 2: Using Task Server . . . 6
Getting Started . . . 6
Task Server User Interface Elements . . . 7
Description of Altiris Task Server Components . . . 8
Using the Task Management Portal . . . 9
Creating Tasks . . . 9
Creating Jobs. . . 10
Deploying Task Servers . . . 12
Manually Deploying Task Servers . . . 13
Approving Task Servers. . . 13
Deploying the Task Agents. . . 14
Manually Deploying Task Agents . . . 15
Configuring the Client Task Agent . . . 16
Managing Task Servers . . . 16
Running Tasks and Jobs . . . 17
Receiving Task Input Properties . . . 18
Viewing Properties for Task Types and Job Types . . . 20
Task Advanced Properties . . . 20
Tasks Provided by Altiris Task Server . . . 21
Chapter 3: Task Management Pack . . . 22
Chapter 1
Introduction to Task Server 6.0
Altiris® Task Server is an infrastructure component that provides task sequencing and automation for Altiris solutions. The functionality is similar to what Altiris® Deployment Solution™ software provides with its Job engine, but it is built on the Altiris®
Notification Server™ infrastructure allowing the rest of the Altiris solution catalog to take advantage of its powerful features, such as:
! Executing multiple Tasks in a defined sequence called a Job
! Letting users provide logic to handle task errors or other return codes ! Including powerful command-line and VBscript capabilities
! Providing out-of-the-box Power Management task ! Supporting executing client-side and server-side tasks
! Providing quick acting features such as “Run Now” options and near-real time status
feedback on running Jobs
! Letting tasks be reused in multiple Jobs or cloned and modified as desired
Task Servers are similar to Package Servers in that they are designed to reside on a separate server and are very lightweight.
Terminology
See also: Description of Altiris Task Server Components (page 8).
Task - A task is an action that you want performed on a computer. There are two types of tasks: Client and Server. Client tasks are executed by Task agents on remote computers (through a Task Server) or on the Task Server itself. Server tasks are executed on the Notification Server. Altiris Task Server and Altiris solutions provide tasks for you to use.
Job - A job is a task that runs two or more tasks in a particular sequence. A job can have conditions to run different tasks under different situations. A job provides the flexibility you need when running tasks, including using conditions to determine which tasks to run. Jobs can be nested inside each other for complex sequences.
Other Sources of Information
Altiris Task Server online help provides information on basic Altiris Task Server tasks. For more in-depth information, refer to the information sources in this table.
Information source
Description Location
Task Server Release Notes
Installation, what’s new, and known issue information.
www.altiris.com/Support/ Documentation.aspx Altiris Knowledge
Forum
Quick Link
! Tasks vs. Policies (page 5)
Tasks vs. Policies
Use a task when
! You need to run actions in a specific order.
! You need to perform an action that finishes quickly (no ongoing actions).
! An action can be useful for an end user to sequence or tie to a Notification Server
message.
Use a policy when
! You have static configuration data to send to the Altiris Agent. ! You have ongoing actions with no definite end.
In general use policies for ongoing management; use tasks to enforce policies or perform one-time actions.
Chapter 2
Using Task Server
This section provides information on working with Altiris Task Server and its features.
! Getting Started (page 6)
! Description of Altiris Task Server Components (page 8) ! Using the Task Management Portal (page 9)
! Creating Tasks (page 9) ! Creating Jobs (page 10)
! Deploying Task Servers (page 12) ! Approving Task Servers (page 13) ! Deploying the Task Agents (page 14) ! Configuring the Client Task Agent (page 16) ! Managing Task Servers (page 16)
! Running Tasks and Jobs (page 17) ! Receiving Task Input Properties (page 18)
! Viewing Properties for Task Types and Job Types (page 20) ! Task Advanced Properties (page 20)
! Tasks Provided by Altiris Task Server (page 21)
Getting Started
After you install Altiris Task Server, you should follow these steps to start using it.
Important
You cannot use Altiris Task Server until the Task agents are deployed.
Note
To see where Altiris Task Server places the user interface elements on installation, see
Task Server User Interface Elements (page 7).
1. Deploy the Task agents. See Deploying the Task Agents (page 14). 2. Deploy Task Servers (optional). See Deploying Task Servers (page 12). 3. Create tasks. See Creating Tasks (page 9).
4. Create jobs. See Creating Jobs (page 10).
5. Run tasks and jobs and view real-time status. See Running Tasks and Jobs
Task Server User Interface Elements
Altiris Task Server is made to run on Altiris Console 6.5 or later. This section describes where the Altiris Task Server user interface elements are found in Altiris Console 6.5 after installation. However, Altiris Console 6.5 is customizable.
Configuration elements
! Client Task Agent Rollout folder – Contains the files needed for rolling out the
Client Task Agent.
! Client Task Agent Uninstall folder – Contains the files needed for uninstalling the
Client Task Agent.
! Power Management Task Agent folder – Contains the files needed for rolling out
the Power Management Task Agent.
! Power Management Task Agent Uninstall folder – Contains the files needed for
uninstalling the Power Management Task Agent.
! Script Task Agent Rollout folder – Contains the files needed for rolling out the
Script Task Agent.
! Script Task Agent Uninstall folder – Contains the files needed for uninstalling the
Script Task Agent.
! Service Control Task Agent Rollout folder – Contains the files needed for rolling
out the Service Control Task Agent.
! Service Control Task Agent Uninstall folder – Contains the files needed for
uninstalling the Service Control Task Agent.
! Task Server Rollout folder – Contains the files needed for rolling out a Task
Server.
! Task Server Uninstall folder – Contains the files needed for uninstalling a Task
Server.
! Task Types folder - Contains the task types that Altiris Task Server provides. This
gives you an easy way to view the properties and change security for task types and job types.
! Agent Configuration policy – The policy used for configuring the Client Task
Agent.
! Approved Task Servers collection - The collection that contains Task Servers
that have been approved.
! Task Data Purge policy - The policy used for purging task data. ! Task Servers policy – The policy used for managing Task Servers.
Task elements
! Client Tasks folder – A default folder for placing the Client Tasks that you create.
However, you can put any jobs or tasks in this folder that you want.
! Jobs folder – A default folder for placing the jobs that you create. However, you
can put any jobs or tasks in this folder that you want.
! Samples folder - A folder containing job and task samples. You can use these
! Server Tasks folder – A default folder for placing the Server Tasks that you create.
However, you can put any jobs or tasks in this folder that you want.
To view the Configuration elements
1. Open the Altiris Console and select View > Configuration.
2. In the left pane, select Server Settings > Notification Server Infrastructure > Task Server.
To access the Task Servers policy page
! Option 1: Open the Altiris Console and select View > Configuration.
! Option 2: Open the Altiris Console and select Configure > Task Servers > Task
Server Management.
To view the Task elements
! Option 1: Access the Task elements from the View link.
1. Open the Altiris Console and select View > Tasks. 2. In the left pane, select Task Management.
! Option 2: Open the Task Management Portal
1. Open the Altiris Console and select Manage > Jobs. 2. In the left pane, select Tasks and Jobs.
Description of Altiris Task Server Components
Task Server
This component can run on the Notification Server or on a remote computer. It is notified by the Tickle Server when there are tasks to run on its connected clients. It then tickles those connected clients and sends them the XML containing the job or task information using HTTP(S). It also collects status information and forwards it to the Notification Database using HTTP(S). A computer must have Windows 2000 or later and .NET 1.1 or later before Task Server can be installed.
Tickle Server
This component always runs on the Notification Server and sends an IP tickle packet to Task Servers when any of their clients have a job or task to run.
Data Loader
This component receives status information from Task Servers and caches it in memory until it can be sent to the Notification Database. This improves scalability by allowing status information for several hundred clients to be received at once without
overwhelming the SQL Server.
This component also runs on each remote Task Server and queues up data that is waiting until it can be sent to the Notification Server.
Altiris HTTP Server
When Altiris Task Server is installed on a remote computer that does not have IIS installed, this HTTP server is installed to facilitate HTTP(S) communication between the Task Server and clients and the Notification Server.
Client Task Agent
This agent runs on client computers and accepts tickles from a Task Server, receives job and task information, passes the information to a handler, and sends status information back to the Task Server. This agent requires the Altiris Agent to be installed on the computer.
Script Task Agent, Power Management Agent, and Service Control Task
Agent
The Client Task agent uses these agents to perform its script, power management, and service control duties. These agents require that Altiris Agent and the Client Task Agent be installed on the computer.
Using the Task Management Portal
The Task Management Portal gives you easy access to most task and job actions (see
Task Server User Interface Elements on page 7). You can use this portal as the main starting point when creating, running, or scheduling tasks and jobs.
This portal provides the following panes:
! Actions - Lets you create, run, or schedule tasks and jobs.
! Recently Accessed Jobs and Tasks - Lets you view recently accessed jobs and
tasks and perform actions on those jobs and tasks.
! Task Servers - Lets you view your Task Servers and how many clients are attached
to each Task Server.
! Resource Manager - Lets you select a resource and view it in Resource Manager. ! Job and Task Status - Lets you view the status on your jobs and tasks that have
run recently. Click Refresh as a task or job runs to see a real-time status.
Creating Tasks
Altiris Task Server provides task types for you to use to create and deploy tasks to Altiris Agent computers or to use when creating jobs. Some Altiris solutions also provide task types and sample jobs and many Altiris solutions will provide task types and sample jobs in the future. These task types and jobs appear on the Create a New Task dialog. You can use this dialog to create jobs and tasks to fit your needs.
You can create a new task by selecting any of the task types that appear on the Create a New Task dialog, changing the name, and editing it.
To create and run a Script Task
1. In the Task view, right-click a folder under Task Management and select New > Task/Job (see Task Server User Interface Elements on page 7). The Create a new task dialog opens.
Note
The task you create will be placed in the folder you select.
2. In the left pane, select the task type (example: Script). You can now change the name of the task, enter a description (optional), choose a Script Type, and enter command script code. Performing a
dir
followed by apause
command is a simple script for verifying that everything has been installed correctly.3. To save the task and exit the dialog, click OK.
4. In the right pane toolbar, click Run Now. Enter a Run name and select a resource the task will be performed on (this can be a collection or individual computers or a combination). Finally, click the Run Now button.
If everything is working properly, the task should run within a few seconds.
The Task Status area of the right pane contains information on all instances of the task that have been run. This area does not auto-update, but there is a Refresh button for updating manually. These columns are sortable. The detail information for each resource that ran the task is viewable by clicking Details. This opens a dialog box that shows each resource in the collection assigned to the task or job, and its current status. You can click Details on an individual resource to get more specific information such as the return code for the task, the specific error message in case of a failure, and task output if the task was configured to save script output with task status (this can be configured by clicking the Advanced button when editing a task). From the individual resource page, you can also click on the resource name to open the Altiris® Resource Manager.
Creating Jobs
Altiris Task Server lets you create jobs that run multiple tasks or jobs. These jobs can then be deployed to Altiris Agent computers by a Task Server. The Task agents then run the job and report back to the Notification Server.
Jobs can contain multiple tasks, multiple jobs, and multiple conditions, giving you great flexibility in setting up the job sequence you need.
To create a job
1. In the Task view, right-click a folder under Task Management and select New > Task/Job (see Task Server User Interface Elements on page 7). The Create a new task dialog opens.
Note
The job you create will be placed in the folder you select.
There are three folders available in the left pane of the Create a new task dialog. Even though they are named the same as the default folders under Task
Management, they are different folders. These folders contain task types and job samples that are available from installed Altiris solutions. The Client Tasks folder contains task types for creating tasks that are run on client computers. The Jobs folder contains job samples. The Server Tasks folder contains task types for creating tasks that are run on your Notification Server.
2. In the left pane, select a job (example: Client Job). You can now change the name of the job, enter a description (optional), and add tasks, jobs, or conditions to the
3. To add a new job to a job: a. Select New > Task.
b. In the left pane of the dialog, select a job, and enter the job name and description if desired.
c. Click OK to add the job and close the dialog box. You will see the added job appear in the right pane between Job Start and Stop.
4. To create a new task to add to a job: a. Select New > Task.
b. In the left pane of the dialog, select a task (example: Script), and enter a task name and command script text for the new task.
c. Click OK to create the task and close the dialog box. You will see the newly created task appear in the right pane between Job Start and Stop.
5. To add an existing task to a job: a. Click Add Existing.
b. In the left pane of the dialog, select the task you want to add. It then appears in the right pane of the dialog.
c. Click OK to add the task and close the dialog. The added task appears in the right pane.
Note
There is a drag and drop feature that lets you change the order of the tasks added to a job.
6. To add a condition to a job:
a. Select New > Condition. This opens the Create New Condition dialog. b. Select a condition from the Condition type list.
The Condition Details area of the Preceding Return Code condition lets you structure the condition to act on the success or failure of the preceding task, or to act on a return code you specify.
c. Click OK to create the condition and close the dialog box.
Note
The condition is inserted into the job below the highlighted line (use the mouse to click on a line to highlight). Add one or more tasks to run as a result of the condition by selecting the If … or Else line as needed.
7. To save the changes and exit Edit mode, click Apply.
8. Click Run Now in the right pane toolbar. Enter a Run name, and select a resource the task will be performed on (this can be a collection or individual computers or a combination). Finally, click Run Now.
9. If more than one task was added to the job, they will be performed one after another. If a condition was added, the tasks that are performed are based on the results of the condition. The server must receive status that a prior task completed before starting the next task in the job, so there might be a delay of a few seconds before the next task begins.
The Task Status area of the right pane contains information on all instances of the job that have been run. This area does not auto-update, but there is a Refresh button for updating manually. These columns are sortable. The detail information for each resource that ran the job is viewable by clicking Details. This opens a dialog that shows each resource assigned to the job, and its current status. Click Details to get more specific information such as the currently running task if the job is still running, the return code for finished tasks, the specific error message in case of a failure, and individual task output if the task was configured to save script output with task status (this can be configured by clicking the Advanced button when editing a task). From the individual resource page, you can also click on the resource name to open Altiris Resource Manager.
Deploying Task Servers
Task Servers let you distribute your jobs and tasks to different computers on your network where Altiris Agents can run the jobs and tasks. Distributing jobs and tasks reduces the load on the Notification Server and reduces network traffic because the Altiris Agent accesses the closest Task Server to it for job and task downloads.
Each Notification Server becomes a Task Server when Altiris Task Server is installed. You can then deploy more Task Servers as needed.
If the Notification Server manages 500 or less client computers, the Task Server on the Notification Server can manage your jobs and tasks without significantly affecting performance. If the Notification Server manages more than 500 client computers, we recommend deploying more Task Servers.
Note
Even though you can use the Task Server that is automatically installed when Altiris Task Server is installed, you still need to deploy the Client Task Agent to your client
computers in order for the Task Server to function.
Task Servers can be on the same computers as Package Servers.
How many Task Servers do I need?
We recommend the following:
! Your first Task Server running on the computer with Notification Server and
Notification Database should serve 500 or fewer client computers.
! For every 2500 client computers you have past 500, you should set up an additional
Task Server set up.
The amount of client computers that a Task Server can serve depends on the hardware of the Task Server computer. These recommendations are based on the Minimum hardware recommendations (page 13).
Task Server Requirements
! Microsoft .NET Framework versions 1.1 ! Microsoft Windows* 2000 SP4 or later ! Altiris Agent
Minimum hardware recommendations
! Intel Pentium* 4 processor or equivalent ! 1 GB RAM
! 1 GB disk space
To deploy Task Servers
Note
The explains how to automatically deploy Task Servers. To manually deploy Task Servers, see Manually Deploying Task Servers (page 13).
1. Add one or more computers that you want to become Task Servers to the Task Servers collection.
Note
You can use other collections if you want. However, the computers that get added to the Task Servers collection are automatically approved.
2. In the Configuration view, select Task Server Rollout > Task Server Install (see
Task Server User Interface Elements on page 7).
3. Select the collection from step 1, enable the policy, and then click Apply.
The next time the computers in the collection update their configuration, they will download and install the Task Server package.
Note
All Task Servers that get deployed using the Task Servers collection in the Task Server Install policy automatically become approved Task Servers (see Approving Task Servers
on page 13).
Manually Deploying Task Servers
The .MSI used to deploy Task Servers can be accessed and used manually. However, we recommend using the Task Server Install policy to deploy Task Servers automatically.
To manually deploy Task Servers
1. From the console, navigate to Install Path\Altiris\Notification
Server\NSCap\Bin\Win32\X86\Client Task Management\Server Package.
2. Run TaskServerSetup.msi on the computer that you want to become a Task Server.
Note
If you manually deploy a Task Server, it needs to be added to the Approved Task Servers collection before it can be used (see Approving Task Servers on page 13).
Approving Task Servers
Task Servers must be approved before they can be used. This prevents outside sources from creating an unauthorized Task Server and gaining access to the Notification Database.
Task Servers must be added to one of the following collections to be approved Task Servers:
! Task Servers - This collection was created to be used when deploying Task
Servers. This collection is a Configuration element and is found in the Task Server Rollout folder (see Task Server User Interface Elements on page 7).
! Approved Task Servers - This collection can be used to approve Task Servers that
you have added manually or that are not in the Task Servers collection. This collection is a Configuration element and is found in the Task Server folder (see Task Server User Interface Elements on page 7).
To use the Task Servers collection to deploy and approve Task Servers
1. Assign to the Task Servers collection the computers that you want to deploy theTask Server agents to.
2. Select Task Server Rollout > Task Server Install.
3. In the right pane, in the Applies to collections field, select the Task Servers collection.
4. Select Enable. 5. Click Apply.
All Task Servers that are added to the Task Servers collection automatically become approved.
To use the Approved Task Servers collection to approve Task Servers
1. Assign Task Servers to the Approved Task Servers collection that are not in the TaskServers collection.
All Task Servers that are added to the Approved Task Servers collection automatically become approved.
Note
The Task Server that is created on the Notification Server is an approved Task Server even though it is not in either the Task Servers or the Approved Task Servers collection.
Deploying the Task Agents
The following Task agents need to be deployed to Altiris Agent computers before you can use Task Servers:
! Client Task Agent
! Power Management Task Agent ! Script Task Agent
! Service Control Task Agent
The Client Task Agent is the main agent for working with Task Servers and uses the other agents to perform various functions.
To deploy the Task Agents
Note
The explains how to automatically deploy Task Agents. To manually deploy Task Agents, see Manually Deploying Task Agents (page 15).
1. In the Configuration view, select Client Task Agent Rollout > Client Task Agent Install (see Task Server User Interface Elements on page 7).
2. Verify that the Without Client Task Agent Installed collection contains all the computers that need the agent. By default, this collection contains all computers (assuming this is the first installation of Altiris Task Server on this Notification Server).
3. Make sure the Without Client Task Agent Installed collection is selected, enable the policy, and click Apply.
4. In the left pane, select Power Management Task Agent Rollout > Power Management Task Agent Install.
5. Verify that the Without Power Management Task Agent Installed collection contains all the computers that need the agent. By default, this collection contains all computers (assuming this is the first installation of Altiris Task Server on this Notification Server).
6. Make sure the Without Power Management Task Agent Installed collection is selected, enable the policy, and click Apply.
7. In the left pane, select Script Task Agent Rollout > Script Task Agent Install. 8. Verify that the Without Script Task Agent Installed collection contains all the
computers that need the agent. By default, this collection contains all computers (assuming this is the first installation of Altiris Task Server on this Notification Server).
9. Make sure the Without Script Task Agent Installed collection is selected, enable the policy, and click Apply.
10. In the left pane, select Service Control Task Agent Rollout > Service Control Task Agent Install.
11. Verify that the Without Service Control Task Agent Installed collection contains all the computers that need the agent. By default, this collection contains all computers (assuming this is the first installation of Altiris Task Server on this Notification Server).
12. Make sure the Without Service Control Task Agent Installed collection is selected, enable the policy, and click Apply.
The next time the computers in the collections update their configuration, they will download and install these agents.
Manually Deploying Task Agents
The .MSIs used to deploy Task Agents can be accessed and used manually. However, we recommend using the Task Agent Install policies to deploy Task Agents automatically.
To manually deploy the Task Agents
From the console, navigate to Install Path\Altiris\Notification Server\NSCap\Bin\Win32\X86\Client Task Management. 2. Run the following .MSIs on the client computer:
" CTAgentSetup.msi
" PowerMgmtAgentSetup.msi " ScriptTaskAgentSetup.msi
" ServiceControlTaskAgentSetup.msi
Configuring the Client Task Agent
Altiris Task Server provides an Agent Configuration policy that is enabled by default. This policy lets you specify how often the Client Task Agent requests tasks from the Task Server. This configuration policy is only used by the Altiris Agent if the tickle mechanism does not work on the Altiris Agent computer. We recommend the defaults unless you notice an impact on your network.
How Task Server uses the tickle mechanism
When a job or task is selected to run, the Tickle Server informs the Task Server. The Task Server has a tickle mechanism that the Task agents listen for. When the Task Server gets a tickle from the Tickle Server, it, in turn, sends a tickle to the Task agents that the job or task is supposed to be run on. The Task agents then download and run the job or task.
To configure the Client Task Agent
1. In the Configuration view, select Agent Configuration. 2. Make desired changes and click Apply.
Managing Task Servers
If you have multiple Task Servers, you can easily manage which collections get managed by which Task Servers. You do this on the Task Servers policy page. The Task Servers policy page can be used if your network is not organized into subnets already or if you want greater flexibility in managing your collections through Task Servers.
If you do not use the Task Servers policy page, the Notification Server chooses which Task Server to use to send a job or task based on which Task Server is closest to the client computer.
If you use the Task Servers policy page, Notification Server chooses which Task Server to use based on the collection that the client computer is in.
To use the Task Servers policy page, first select one or more collections that contain the client computers you want your Task Servers to manage. Next, select one or more Task Servers to manage each collection and move them up or down in the list to change the priority.
When a job or task is selected to run, Notification Server first looks at the list you create on the Task Servers policy page. The first available Task Server you have selected to manage a collection is chosen to deliver the job or task to the client computers in the
If there are no Task Servers listed on the Task Servers policy page, or if none of the Task Servers listed on this page are available for the collections that are listed, the
Notification Server chooses which Task Server to use based on its proximity to the client computer.
After a client computer uses a Task Server, it continues to use that same Task Server until its Altiris Agent is restarted. The Altiris Agent is restarted when a computer is restarted. Another way to restart the Altiris Agent is to install a software package that has a script that performs a Net stop and a Net start.
Note
The only time Task Servers are unavailable is if the computer they are on is turned off or if they are not configured properly.
Example
You have a collection called “All Windows XP Computers” and a collection called “All Windows 2000 Computers.” You also have four Task Servers: Task Server 1, Task Server 2, Task Server 3, and Task Server 4. You want two Task Servers to manage each collection. You would add the two collections to the list on the Task Servers policy page. Then you select Task Server 1 and Task Server 2 to manage the “All Windows XP Computers” collection and Task Server 3 and Task Server 4 to manage the “All Windows 2000 Computers” collection. You can then change the order of which Task Server gets chosen by moving Task Server 2 in front of Task Server 1. Then, suppose you create a job and select it to run on all Windows XP computers. Notification Server will try to send the job to Task Server 2, which will send the job to all Windows XP computers. If Task Server 2 is not available, Notification Server sends the job to Task Server 1.
To manage Task Servers
1. In Altiris Console 6.5, select Configure > Task Servers > Task Server Management.
2. Click New ( ) to add a collection to manage. The computers in that collection appear in the far right pane.
Note
Your Task Servers have “Agent” listed as the Registration Type in the far right pane.
3. To add a Task Server to manage, select a collection, then click Add( ).
4. Change the priority of a collection or Task Server by clicking on it and clicking the
Up or Down icon. 5. Click Apply.
Running Tasks and Jobs
After you create the tasks and jobs you need to run, you can run them on the computers you want.
To run a task or job one time
2. In the right pane, click Run Now.
3. Enter the Run name (optional). This is the name of the run instance that is displayed in the Task Status section.
4. Select the desired completion requirements.
5. Select the resources to run this task or job on. You can choose any combination of collections and resources.
6. Click Run Now.
To run a task or job on a schedule
1. In the Task view, under the Task Management folder, select the task or job you want to run (see Task Server User Interface Elements on page 7).
2. In the right pane, click Create Schedule.
3. Set up the schedule you want to run for the task or job.
4. Select the resources to run this task or job on. You can choose any combination of collections and resources.
5. Click OK.
When tasks or jobs are selected to run (either one time or on a schedule), they appear in the Task Status section. Click Refresh as a task or job runs to see a real time summary. For a detailed summary, click Details. On this run instance summary page, you can click Details to see which tasks in the job were run on that resource. From the individual resource page, you can also click on the resource name to open Altiris Resource Manager.
To rerun a previously run task or job
1. In the Task view, under the Task Management folder, select the task or job you want to run (see Task Server User Interface Elements on page 7).
2. In the right pane, under the Task Status section, right-click on a run instance and select Start now.
The task or job reruns with the same parameters (including selected computers) that were used the first time it was run. However, if running a job, the current version of the job is run with the tasks in the order they are set up to run currently. The task run name has “Re-” prefixed to the original name.
Receiving Task Input Properties
Tasks can receive input properties from a set value, from other tasks, or at run time. If you have a task that outputs properties, any subsequent task in that job can use those output properties for its input properties. The tasks do not need to be concurrent. Tasks that output properties have a Save script output with task status checkbox when you click Advanced.
To create a task that outputs properties
Note
1. Create a task that lets you save output properties (example: Script). 2. Click Advanced.
3. Select Save script output with task status. 4. Click OK.
5. Enter the script name, description, and script details. 6. Click OK.
To create a task that gets input properties from another task
1. Create a task that lets you get input properties (example: Script).2. If you want to use this task to pass through the properties to another task, do the following:
a. Click Advanced.
b. Select Save script output with task status. c. Click OK.
3. In the script command section, enter one or more variables (example: %input%). These catch the output.
4. Click OK.
To set up tasks within a job for input
1. Create a job and place in it the tasks you created for output and input. Each output task must precede the task that will receive its output.
2. Configure each input task in the job.
Any time there is a client task that has input and is in a client job or any time there is a client task inside of a server job, a Task Input appears on the right side when you click on the task. To configure the input task or client task inside of a server job: a. Select Prompt me for task input each time this job is run if you want to
enter the input manually when the job runs.
b. Select Enter task input now to enter the task input at this time.
use a set value - Select this to use a value that doesn’t change. Enter the value in the field that appears when the screen refreshes. If this is a client task inside a server job, you must select the computer or computers that will run the client task. All client tasks have this as a default input parameter when they are inside server jobs.
use a previous task’s output - Select this to use a previous task’s output. Use this if there is an output task in this job you want to use. When the screen refreshes, the variable name appears as well as a list of available output tasks. Select the task whose output you want to use for this task.
prompt at run time - Select this to be prompted for the input at run time. 3. Click Apply.
Viewing Properties for Task Types and Job Types
Altiris Task Server provides an easy way for you to view the properties and change security for task types and job types. The Properties page is described in the Notification Server documentation.To view properties for task types and job types
1. In the left pane, select the Task Type you want to view (see Task Server User Interface Elements on page 7).
2. In the right pane, click View properties.
3. To view and change security settings for the task type or job type, click the
Security tab.
Task Advanced Properties
Some tasks have an Advanced button when you edit them. The Advanced button is on the lower right corner of the Edit page. When you click Advanced, a dialog box appears. For a Script task, there are two tabs: Script and Task Options. Other tasks have similar tabs.
Script tab
! Run As - This option lets you select to run the task using either Altiris agent
credentials or a specific user’s credentials. The default is to use Altiris agent credentials.
! Other - In the Other section, you can choose how you want the script to appear. If
the task has output parameters that you want to be saved, select Save script output with task status (see Receiving Task Input Properties on page 18).
Task Options tab
! Ensure no other tasks are running while this task is running - If this is
selected, no other tasks will run until this task has completed. If this is not selected, other tasks can run while this task is running.
! End task after 30 minutes - This task will end after 30 minutes if it has not run.
The amount of time can be changed, but 30 minutes is the default.
Note
This option applies to all tasks. If there is no Advanced tab when editing a task, the task will always end after 30 minutes if it has not run.
Tasks Provided by Altiris Task Server
Client Tasks
Server Tasks
Task Name Description
Power Control Control power options for client computers.
Script Lets you run scripts on client computers (DOS Command Script, VBScript, and JavaScript).
Service Control Starts, stops, restarts, pauses, resumes, and gets status on Windows services. Example: You can stop and start the Altiris Agent on one or more client computers.
SVS Command Modifies virtual software layers using Altiris® Software Virtualization Solution™ software commands.
Task Name Description
Policy Control Enables or disables any policy.
Send E-mail Sends an e-mail. Example: You can send a form e-mail after a certain task runs.
Click Advanced to select input parameters. The parameters you select are available for input when the task runs.
Note
The e-mail text can only be entered when the task is created. Server Script Runs a script on Notification Server (DOS Command Script,
VBScript, and JavaScript).
Chapter 3
Task Management Pack
The Task Management Pack is a collection of extra tasks that run on Task Server. Some of these tasks run when one or more of these Altiris solutions are installed:
! Altiris® Inventory Solution®
! Altiris® Patch Management Solution™ ! Altiris® Recovery Solution™
If one of the tasks fails, be sure to check if the Altiris solution is installed. Example: To run a Patch Management task, Patch Management Solution must be installed.
Task Description
Altiris Agent Control Altiris Agent Control forces the Altiris Agent to update its current configuration and policy data and send basic inventory data.
VB Script is used to
1. Force the Altiris Agent to update its current configuration and policy data.
2. Force the Altiris Agent to send basic inventory data. Defrag Locates and consolidates fragmented boot files, data
files, and folders on local volumes.
Command-line options
1. Analyze only(defrag -a)
2. Force defragmentation even if free space is low (defrag -f)
3. Verbose output, add switch “-v” (defrag -v -f or defrag -v -a)
Inventory Provides comprehensive inventory for Windows
computers, including serial number, hardware inventory, software audit inventory, and user/contact information.
Command-line options
1. Clean the directory before a scan
(aexinvsoln.exe /cleanbeforerun /s “filename”) 2. Perform a scan with out cleaning the directory
(aexinvsoln.exe /s “filename”)
User has the option to hide the client side graphical user interface (GUI) by adding the switch “/hidden”.
Examples
1. Clean the directory before a scan
(aexinvsoln.exe /hidden /cleanbeforerun /s “filename”)
2. Perform a scan with out cleaning the directory (aexinvsoln.exe /hidden /s “filename”)
Ipconfig Displays all current TCP/IP network configuration values.
Command-line options
1. Display full configuration information (ipconfig -all)
2. Purge the DNS Resolver cache (ipconfig -flushdns)
3. Renew the IP address (ipconfig -renew)
4. Display the contents of the DNS Resolver Cache (ipconfig -displaydns)
Patch Management Provides improved functionality in terms of the analysis, collection, and distribution of operating system and application updates.
Command-line options
1. Kick off an update cycle (AexPatchUtil.exe /xa) 2. Run all Inventory(AexPatchUtil.exe /i) 3. Force a config request
(AexPatchUtil.exe /c)
Recovery Solution Protects operating systems, applications, and data stored on desktops and notebooks from unintentional changes, accidental deletions, and catastrophic loss from hardware failure, virus corruption, or theft.
Command-line options
1. Take a snapshot(aexcmd.exe /RunFullSnapshot /Silent /Wait) 2. Do a rollback if something went wrong
(aexcmd.exe /Rollback /Silent /Wait /LastRemote) 3. Perform a restore
(aexcmd.exe /Restore /Silent /Wait /folder) SVS Modifies virtual software layers.
Command-line options
1. Activate an SVS Layer(svscmd “Layer Name” ACTIVATE) 2. De-activate an SVS layer
(svscmd “Layer Name” DEACTIVATE -F) 3. Reset an SVS layer
(svscmd “Layer Name” RESET -F)
4. Send the SVS inventory to Notification Server (svscmd SENDINVENTORY)
5. Delete an SVS layer
(svscmd “Layer Name” DELETE -F) 6. Import an SVS layer
(svscmd “Layer Name” IMPORT -P “File Name” -F)
Index
A
agent
client task 9
power management 9 script task 9
service control task 9 Altiris HTTP server 9 Altiris Task Server tasks 21 approved task servers collection 7 approving
task servers 13
C
client task agent 9 configuring 16 client tasks 21 collection
approved task servers 7 configuration elements 7 configuring
client task agent 16 creating
jobs 10 tasks 9
D
data loader 8
deploy task agents manually 15 deploy task servers manually 13 deploying
task agents 14 task servers 12
G
getting started 6
H
help 4I
input task 18J
jobs creating 10 running 17M
managingtask servers 16
manually
deploy task agents 15 deploy task servers 13
O
output task 18
P
power management agent 9 properties
viewing for tasks and jobs 20
R
requirements task server 12 running
jobs and tasks 17
S
script task agent 9 server tasks 21
service control task agent 9
T
task agents configuring 16 deploying 14 task elements 7 task input 18
Task Management Portal 8, 9 task output 18
task server 8 components 8
Task Server requirements 12 task servers
approving 13 deploying 12
how many do I need 12 managing 16
task servers policy page 8, 16 tasks 21
creating 9 running 17 terminology 4 tickle 16 tickle server 8
