Information about the software package, such as name, version, type, registration date.
You can check a box to perform checksum control of package consistency
The name of the software item should be given with alphanumeric characters.
You can give the item a name of your liking. It is advisable to choose a name that is not too long and such that you can easily recognize it, when you work with the program later on.
The version of the software item should be given with alphanumeric characters.
Give the Item a unique version number of your choice. Since you yourself decide how to number the versions, it is important to use a numbering scheme that makes it easy to distinguish the different versions of the item.
If you create a New Version of an existing software package, this version will be created as "Generic (Open)". To seal an open package, see Seal.
the software item has not yet been sealed
the software item has been sealed
an open MSI item,
a sealed MSI item
a sealed Windows CE package,
a sealed Palm application
a Software Management item.
the software item has been moved to an archive location,
an archived Software Management item
an archived MSI item,
an archived WinCE item
an archived Palm application.
Size of the package
Date and time when registration started
The Filed by field either states "System", if the software item is automatically registered in the SD library, or the individual, for instance "Local Administrator", registering the item.
This field is optional and you can enter for example name and address of the vendor.
This field is not displayed in any tree views after registration. You can see it, if you select Properties in the context menu for the item after registration.
This field is optional and you may enter any comment about the item that you want to make, for example about characteristics of the item.
This field is not displayed in any tree views after registration. You can see it, if you select Properties in the context menu for the item after registration.
This field is optional. You may select it in order to enable integrity checking.
If this box is checked, and the package has been tampered with, you cannot distribute the software to any agents. The manager will block its delivery, when it verifies the checksum and finds an error.
Note that the checksum refers to the number of files, their names and size. It does not involve the actual contents of the files.
If a job has been set up for many targets, job execution could (in principle) end differently. For example, the job for the first computer executes OK (checksum verification was successful when this job was to be delivered), but when the job is to be delivered to the next computer, the manager detects a checksum error. The job for the second computer will then end in Error. And so will it for all following target computers, unless the checksum error is corrected.
If DTS is used to deliver the job to many targets (and the checksum control is successful), the package will be sent to all of these targets which then execute the job independently.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|