About relocating the Software Library

You might need to relocate the Software Library. For example, relocation might be required if the existing location runs out of disk space or if it is decommissioned.

Do not move the Software Library directory or the packages that it contains. If you move the packages, you break all the references to those packages in existing policies. The only safe way to relocate the Software Library is through the Symantec Management Console, because the relocation process maintains the package links.

The process for the Software Library relocation is the same as for its initial setup. The difference is, when you specify the new location, you are prompted to either migrate or convert any packages that are in the old location.

Migrating

Copies the existing packages from the old Software Library folder to the new one. The migration also changes the packages' source paths in any existing policies that refer to those packages.

Converting

Leaves the packages in the old Software Library folder and marks them as UNC-sourced. The conversion also changes the packages' source paths in any existing policies that refer to those packages. The new source path is the UNC path of the old Software Library.

See Setting up the Software Library.

The relocation of the Software Library is different from the replication of the Software Library. Replication copies the data that is in the Software Library so that it can be used on a different Notification Server computer.

See About replicating the Software Catalog.

Imported Document ID: HOWTO62906
Legacy ID: v16433937_v66611926

Thanks for your feedback. Let us know if you have additional comments below. (requires login)

    © 1995-2019 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.