Software Library FAQ for Software
Management Solution 7.0
The Software Catalog provides new functionality and dynamic abilities in managing Software. As there
have been many questions and confusing on how the Software Library interacts with the Software
Catalog, this Frequently Asked Questions has been created to provide information and help you
administer and successfully use the Software Library as part of the Software Catalog. This FAQ was
written against version 7.0 SP4 of the Software Management Framework.
What is the Software Library?
The Software Library is a new package source type that was added to the 7.0 release of Software
Management. The Software Library allows for an Administrator to maintain all deliverable software
packages within a single securable location, so that the packages are not spread out over various
unsecured network shares or local hard drive locations. Essentially this creates a repository for the files
associated to a Software Resource.
Is the Software Library required?
In short, no, it is not required. There are some benefits for using the Library, covered in the subsequent
section. It’s important to understand what is gained and what is not, as some use cases may lend to a
non-Software Library package source. Almost all functionality that Software Management uses,
including all Solutions who plug into the Framework (for example Patch Management, Asset
Management, Inventory Solution, etc), is available regardless of the package source type.
Why use the Software Library?
There are various benefits to using the Software Library as the package source, and the primary benefits
are outlined below:
 The Administrator is able to secure the Software Library so that only the Altiris Service is able to
access it, and that only authorized administrators can perform actions that interact with the
packages within the Software Library. This way unauthorized users can not modify the package
contents. While this can be completed manually with other Package Sources, using the Software
Library greatly simplifies the process.
 The Software Library allows for Administrators to setup a single location that all of the delivery
packages can be stored. This way the Administrator does not have to keep track of where the
package exists (what network share or what folder on the local hard drive). This is especially


important when access rights change or accounts are decommissioned, potentially severing the
Notification Server’s ability to reach the Package Source.
By having all of the packages within one managed location it allows for the Software Library to
be migrated to a new location in the event that the share needs to change. For example if the
file server being used for the Library needs to be replaced, using the Library greatly simplifies
the move process. During a migration the actual file contents would be moved from the current
location to the new location, and the actual package source locations would also be updated
within the Notification Server. This is all done by changing the location, found in the Symantec
Management Console under Settings > All Settings > Software > Software Catalog and Software
Library Settings > and select Software Library Configuration. When you change the location,
you’ll receive this prompt:
Also, the ability to create software packages based upon files that are from various locations is
introduced. When importing a package into the Software Library the user is able to select
individual files or folders that can then be used in creating a new deliverable software package.
For instance, the Administrator may want to include an MSI from one location and a MST from
another location to create a single deliverable software package, and this can be accomplished
by using the using the “Software Library” package source type when importing a package via the
“Import Software” dialog or via the “Add or Edit Package” dialog.
When should I not use the Software Library?
With all the above benefits for using the Software Library, why would another package source method
ever be used? The short answer is performance. The Software Library source-type includes a hash
generation for all files within the Package. This process can take a long time, and, in some situations,
cause a timeout, failing the import of the Package into the Software Library. See the following KB articles
for more details:
 https://kb.altiris.com/article.asp?article=49112&p=1 – When this issue was originally reported,
the timeouts occurred more frequently than not. This issue has been mostly addressed by SP4 of
Software Management Framework.
 https://kb.altiris.com/article.asp?article=52996&p=1 – With some very large packages, the
import can take hours, or timeout altogether. There does appear to be a technical limit for
importing very large packages or packages with a high number of files.
The reason the import process can take so long is the MD4 hash created for each file within the Package.
The duration of this process grows with many or larger files.
What are Common Misconceptions of the Software Library?
There are various misconceptions as to what the Software Library is and how the Software Library
works, and the following items below will hopefully clarify some of these.
 Is the Software Library and the “Software Catalog” the same? No, the “Software Catalog” is a
view of the software resources that are defined within your organization. The Software Library is
a package source location for where the content of software packages can be stored. All
metadata, including most intersects by other Solutions, resides or passes through the Software
Catalog.
 Does the software package resource that is associated with the software resource need to be
within the Software Library if the software resource is within the Software Catalog? No, the
Software Catalog shows all software resources independent upon the associated software
packages source type.
 Can I use the “Import Software” dialog to create a software resource that is not created within
the Software Library, and still have the necessary metadata read from the installation file?
Yes. While this functionality has been available via the Software Library, some improvements
were added in Service Pack releases. This allows for any type of package source to be used to
create a software resource so that the appropriate metadata is also created (software command
lines, company resource, etc).
 Does having the package within the Software Library impact how the package is delivered to a
client? No. Having a package within the Software Library does not provide any added
functionality to how the package is delivered to clients. The delivery uses the Snapshot method
used previous in the 6.x code. This has not changed.
 Does the Software Library prevent package contents from being changed outside of the UI?
No, not exactly. The concept of the Software Library allows for the Software Library location to
be locked down so that only the Altiris Service can access the package contents directly, but the
Software Library does not prevent anyone with access to this directory to modify the contents of
the packages. It has no mechanism to monitor the source location. Instead, this information is

stored for the next time the Package, in the UI, is updated to include more files, modified files,
etc. This is where the hashes are used generated during the Software Library Import.
Is the file hashing that is used by Software Library used in delivering the package contents?
No. The hashing of the files that are located within the Software Library is used to maintain what
files are needed to be uploaded to the server when a package is modified via the Package UI.
How can a user create a package within the Software Library?
There are currently three different ways that a user can create a package within the Software Library,
and each of these methods is outlined below.
 Import Software Dialog – The “Import Software” dialog allows for a software resource to be
created based upon the software installation file that is selected within the initial screen of the
dialog. If the package source is set to “Software Library” then the “package contents” that are
defined within the dialog will be moved to the “Software Library” location. If the package source
is not set to “Software Library” then the package contents will remain at the location that was
specified, and the installation file that is specified will be parsed to gather any software meta
data that can be gathered (software command lines, company resource, etc). This is the only
method that will parse the provided files to automatically create the Rules, Associations,
Company resources, etc). The import is launched under any of the Software views shown under
Manage > Software > Software Catalog > etc. This screenshot illustrates where this can be
accomplished:

Add or Edit Package Dialog – The “Add or Edit Package Dialog” allows for a software package
resource to be created, and allows for the user to specify any software installations files that
they would like to define. These files can then be used within the “Add or Edit Command Line”

dialog to create command lines based upon the installation file type. This is the traditional
location for creating or editing Packages or Command-lines.
Import Package action – The “Import Package” action can be taken on any software package
that is currently not located within the Software Library. When this action is taken it moves the
contents of the software package to the Software Library. For instance, if a package source is
currently set to “UNC” then the contents of the package at the UNC location will be moved to
the Software Library, and then the package will be a managed package.
Conclusion
The information presented in this FAQ is, as far as the author knows, is accurate at the time of
publication. Changes to the underlining technology in subsequent releases from Software Management
Framework 7.0 SP4 may render some of these details obsolete. Current investigations include improving
the Import method to be more reliable and efficient.