CA Client Automation - 14.0

PDF
English

Asset Jobs in DSM Explorer

Contents
cla140
Contents
An asset job directs Agents to perform specific actions on a computer or when a user logs in. You can, for example, use asset jobs to run a script or command, and display a message.
Jobs can be created at the asset, group, and domain level. Jobs created at the asset level are linked to the respective assets, and those at the group level are linked to all the member assets in the group. At the domain level, you can view all the jobs in the domain, create new jobs, and link it any group or asset. You can create and link any number of jobs to a particular asset or group.
Append the following path to the Domain name in the address bar of the DSM Explorer window. In the following paths,
  • Computer
     refers to the name of the computer in the domain.
  • User
     refers to the name of the user in the domain.
  • Asset/User Level
    Assets - Domain/Computers and Users/All Computers/
    Computer
    /Jobs/Asset Jobs
    Users - Domain/Computers and Users/All User Accounts/
    user
    /Jobs/Asset Jobs
  • Group Level
    All Computers Group - Domain/Computers and Users/All Computers/{Group Details}/Jobs/Asset Jobs
    All Users Group - Domain/Computers and Users/All User Accounts/{Group Details}/Jobs/Asset Jobs
    User Defined Groups - Domain/Computers and Users/
    Group Name
    /{Group Details}/Jobs/Asset Jobs
  • Domain Level
    Domain/Jobs
An existing job can be linked to any group or computer. Hence, the folder under which a job is created is irrelevant.
Navigate to the asset jobs folder to see the available jobs and their scheduling options.
For more information about job types and creating and editing jobs, see the Asset Management section of the
DSM Explorer Help.
Access the Asset Jobs Folder in the DSM Explorer
You can create, configure, link, and schedule the assets jobs in the Asset Jobs folder.
To access the Asset Jobs folder in the DSM Explorer
  1. Navigate to the following paths in the DSM Explorer depending on the level at which you want to view or configure the asset jobs:
    • Group Level
    • Computer Group
      Domain, Computers and Users, All Computers, Group Details.
    • User Account Group
      Domain, Computers and Users, All User Accounts, Group Details.
    • User Created Group
      Domain, Computers and Users,
      Group
      , Group Details.
    • Computer Level
      Domain, Computers and Users, All Computers,
      Computer
    • User LevelDomain, Computers and Users, All User Accounts,
      UserAccount.
      Domain Level
      Domain
  2. From the above paths, navigate to the Jobs, Asset Jobs folder.
    Jobs created at the group level are automatically linked to the member assets of the group. You can, however, disable the execution of such jobs at the asset level. Jobs linked to user are executed when the user logs in.
You can link the asset jobs created at all these levels to any managed asset or group.
Job Types
You must select a job type when you create a new job. Each type of job requires different parameters for executing the job. The following asset jobs are available:
  • Message Job (Windows only)
  • Command Job
  • Synchronization Job (Windows only)
  • External Utility Job
  • Secure Configuration Files Job (Windows only)
  • Script Job
Message Job
Message jobs can display a message on the asset or when a user logs in. You can see the job status to know when the message was displayed.
When a message job is assigned to a user and the same user logs on to more than one session, the message job can be displayed in any one of the user sessions.
This job is applicable only for Windows agents.
Command Job
Command Jobs enable you to execute a command file (for example, a batch file or a UNIX shell script) on the selected asset or group. All normal native command-language commands can be used in this file.
Synchronization Job
Use the Directory Synchronization Job to synchronize two directories on an asset. Synchronization involves comparing the contents of the target directory and the source directory, and making the content of the former identical to the latter.
This job can be linked only to the computer assets and is applicable only for Windows agents.
In Step 3 of the New Job wizard, specify the directories:
  • Source
    Indicates the directory to be compared against (the image).
  • Target
    Indicates the directory to be examined for differences (reflection of the image).
The use of UNC path is supported. Syntax: \\servername\sharename
In Step 4 of the New Job wizard, specify the following:
  • Whether subdirectories should also be examined for differences.
  • Whether files on the Target that are nonexistent on the Source should be deleted.
  • Whether attributes should be ignored when comparing, to prevent making Target file attributes equal to Source file attributes.
  • Whether attributes should be ignored when copying, in which case the job will try to overwrite Target files that are write protected.
  • Whether to cancel the job, when the size difference between the two directories exceeds the specified size in KB. This parameter is provided to prevent accidental copying of a large number of KB over the network.
Example: Printer File Synchronization
This is an example of how to update the printer files of users that are on the local hard disk of the users. To make it easier, you need to update only, say, N:\PRINTERS with the latest printer files. You can then use directory synchronization to equate the directories C:\WINDOWS\PRINTERS and N:\PRINTERS. The printer files located on the hard disk are now made equal to the printer files on the network drive N. The directory is thereafter examined for differences each time the computer starts on the network.
Source: N:\PRINTERS
Target: C:\WINDOWS\PRINTERS
Enabled: Include Subdirectories; Delete unknown files; Ignore file attributes on compare; Ignore file attributes on copy.
Example: Portable Computer File Update
If there are portable computers on your network, you can synchronize a sub-directory on the portable computer’s hard disk with a personal network drive on the server. This permits automatic transfer to the network of portable computer files that were created while the portable computer was not connected to the network.
The Directory Synchronization Job ensures absolute conformity between two directories. It ensures that the attributes are also equal. Files on the target that are not found on the source will be deleted, if so specified. Directories not found on the target will be created.
In some cases, you do not want all files and subdirectories in a directory to be synchronized. (For example, in an Agent Software directory, you do not want the PROTOCOL.INI and the HOST files to be equal throughout your network.) In this case, you should specify the files and directories, which should not be synchronized.
Example: File Exclusion
This is an example of how to exclude files from synchronization. Assume that the local C:\PW directory is synchronized with a default network directory F:\PWDEFAUL. As a system manager, you know that the PROTOCOL.ini file and all the *.TPL files of that directory must be excluded from synchronization, because those files contain unique values for each individual computer. (The directory BAK is also excluded).
Source: F:\PWDEFAUL
Target: C:\PW
Enabled: Include Subdirectories; Delete Files on Target if Unknown on Source.
Specified: Files not to be synchronized: *.TPL, PROTOCOL.INI, (DIR) BAK
External Utility Job
External utility jobs execute an external utility. This type of job can be used to execute a script written for a management tool other than asset management.
Script Job
Script jobs can execute scripts on assets. You can either write the script directly or open a saved script from a file.
Secure Configuration Files Job
A Secure Configuration Files Job ensures that the specified system or configuration file is always equal to the content (secure file) specified in this job.
When the Agent runs, it checks whether the configuration file is modified. If yes, it copies the secure file to the asset and overwrites the modified file.
This job is applicable only for Windows agents. On UNIX or Linux, you can create a DSM script to copy files onto a share.
Change Job Execution Order
Jobs are executed in the same order in which it was created. However, you can change this order if the execution of one job depends on the execution of another.
You can do this only at the group and asset level.
To change the job execution order
  1. Navigate to the Asset Jobs folder.
  2. Right-click the job for which you want to change the order and select Reorder.
    A sub menu appears.
  3. Select any of the following menu items:
    • Move Up
      Moves the job one level up. If you want to move ahead more than one job, click this menu item till you reach the position.
    • Move Down
      Moves the job one level down. If you want to move down more than one job, click this menu item till you reach the position.
    • Move First
      Moves the job to the first position.
    • Most Last
      Moves the job to the last position.
    • Set Position
      Moves the job to the specified position. You can use this option for example, when you want to move ahead or below of more than 5 jobs.
    • Clear Job Order
      Clears the existing order of the jobs and reorders them alphabetically.
    The jobs are reordered based on the selected menu item.