Client Management Suite

Hi,
I've a problem with invalid software packages at our Site Servers.
I've uploaded some software products to the software library. The packages are replicated to our Site Server. But the path lenght is more the 256 signs.
In the library this no Problem, but at the Site Server the path is much longer e.g.
"D:\aplls\altiris\altiris agent\Package delivery\...."
My Question, can I redirect the "Package Delivery" path?
It's no solution to define in every Software package an dedicated path for the Site Servers.
In this environment it's also the problem, that the struktur of the site server aren't identical.  Specifically, the location of the Altiris Installation is different.
Any Ideas to solve this??
I do not want to give up the way to use UNC-Path Downloads.
 

Thanks for your Ideas,

Hi Nessaja,

You may change the package destination location on package servers for affected packages.

Right Dmitri,

I made a similar change on NS 6 when I had a similar issue.

Good Morning,
that's right, I know the way to change the package location. But this change is for all Package-Servers.
And if I change the location for the package e.g. D:\tmp, the unc Download doesn't work at the site-servers.
I'm looking for a way to change the default package delivery folder at the site servers.

Thanks

This is not 100% related to your request and i never tried it. It was even written for 6.0.

But maybe you wanna try. It will probably not be supported anyway ;)

http://www.symantec.com/business/support/index?page=content&id=TECH38307

The Altiris\PS virtual directory is created based upon the HKLM\SOFTWARE\Altiris\Altiris Agent\Package Server\PackageServerBaseDir path.

Hi Mistral,

this looks good. The reg entries are the same.
I will test this in my testing environment.
But the problem is, it isn't supportet.. and if the unc works I'm not sure.

regards

For the share see:

http://www.symantec.com/business/support/index?page=content&id=HOWTO3545

1. Create a shared folder on your Package Server. If more than one Package Server is used, create the same share name on all Package Servers.
2. Modify the sharing and security properties of the shared folder so that the Package Server can write to the folder and the clients can read from the folder. In most cases you can set the permissions so that the application identity has full control
3. On the package's Advanced tab, check the box Package Destination Location on Package Servers and specify the location of the shared folder. For multiple package servers this use "%COMPUTERNAME%" in place of the package server name. Example:  \\%COMPUTERNAME%\MyShare
4. Apply the changes.

Well ... skip 3. and 4. if the "global" setting works.

Perfectly...
Thanks. that's it what I'm looking for.
Sometimes, you know the solution, but you don't know the way :)

Don't forget, beside the UNC share you can install IIS on the package server to get a second valid download location (URL).

An URL supports byte level recovery, while an UNC path only supports file level recovery.

Yes,

I'm using package and Task-Service at the same system. So all the time, all packages are available via unc and url download.