Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Altiris 7.5 Change Location of Image Packages

Created: 20 Dec 2013 | 5 comments

We're running Altiris CMS on a Windows 2008 R2 server Hyper-V VM.  We do not have enough space on our SAN to store the images.  With our current Altiris 6.9 solution we use an array on that machine.  We plan to use that array for storing images in the new solution when ready.

Is it possible to redirect our image packages to that server with a UNC path like we were able to specify the path in 6.9?  I've read some vague things about moving the agent but nothing how to do this or another method that won't affect performance.

Thanks

Bill

Operating Systems:

Comments 5 CommentsJump to latest comment

James007's picture

Specifies the location to which you want to download the software update packages.The default location is C:\Program Files\Altiris\Patch Management\Packages\Updates.

If you change the location and you want to relocate existing software update packages, use the Check Software Update Package Integrity task.

See “Checking the integrity of software update packages ”

Checking the integrity of software update packages

You can verify that software update packages in software update tasks have the correct global server settings applied. If you changed settings in a vendor policy,

run the  CheckSoftwareUpdatePackageIntegrity task to check that all software update packages have the correct new settings and values.

Configuring Patch Management server tasks 41

Downloading the QChain software

See

“Configuring vendor settings” on page 31.

The task also relocates the software update packages in case you changed the

default software update package location on the

Core Services page.

See

“Configuring patch management Core Services settings” on page 29.

To check the integrity of software update packages

1

In the Symantec Management Console, on the Manage menu, click Jobs and

Tasks

2

In the left pane, expand Jobs and Tasks > System Jobs and Tasks > Software

> Patch Management, and then click Check Software Update Package Integrity

3

If you want to delete the downloaded updates that are not part of any software update policy or belong to a superseded bulletin, check

Delete updates from file system that are no longer in use

4 If you want to relocate downloaded updates if the Software Update Package

Location has changed, check Relocate existingpackagesif default Software Update Package location on Core Service page has changed

See

“Configuring patch management Core Services settings” on page 29.

5

Under Task Status, click New Schedule and specify a schedule on which to

run the task.

AttachmentSize
PatchWindows_user_guide.pdf 402.91 KB
bill_mcc's picture

I don't think that is what I'm looking for.  I'm looking to relocate the images.  This seems to be software updates.

 

If my thought is incorrect please explain. The images packages in 7.5 are stored in. E:\Program Files\Altiris\Altiris Agent\Package Delivery

James007's picture

Check this
Configuring Package Location on your Package Server

 

 

Article:HOWTO4752  |  Created: 2006-08-23  |  Updated: 2010-06-11  |  Article URL http://www.symantec.com/docs/HOWTO4752

 

http://www.symantec.com/connect/forums/can-i-redirect-package-delivery-path

bill_mcc's picture

That is one of the things I read that mention moving the agent. It doesn't really describe that process or what the effect is.  Would I be mounting the UNC as a drive and installing the agent there?  Is it safe to do?  I know this isn't supported by Symantec but I have no other choice.  Do not have the money to buy the storage.

James007's picture

How to configure an alternate package destination location on Package Servers for a Software Delivery package

 

 

Article:HOWTO3545  |  Created: 2006-05-11  |  Updated: 2007-07-17  |  Article URL http://www.symantec.com/docs/HOWTO3545

Symantec™ Software Management Solution 7.5 powered by Altiris™ User Guide

 

 

Article:DOC5446  |  Created: 2012-03-21  |  Updated: 2013-10-04  |  Article URL http://www.symantec.com/docs/DOC5446