KNOWN ISSUE: Package Server issue with Patch Management 6.2 packages
|Article:TECH25873|||||Created: 2007-01-08|||||Updated: 2009-10-27|||||Article URL http://www.symantec.com/docs/TECH25873|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
By default, the location field is empty and the Use alternate download location on Package Server is checked for the Advanced Microsoft Configuration for Package Distribution. On Package Servers, the Patch packages will create a GUID folder in the Altiris Agent folder and download the updates package to it. These folders do not get shared properly and clients are unable to receive the packages.
Location of "Use alternate download location on Package Server" on the Notification Server:
Configuration/Solution Settings/Software Management/Patch Management/Server Settings/Microsoft Settings/Microsoft/Advanced
Patch Management Solution 6.2.3540
The check box to "Use alternate download location on Package Server" was selected by default without an entry in the corresponding "Location" field. STEPS TO REPRODUCE:
1. Open up NS Console and go to Configuration - Solution Settings - Software management - Patch Management - Server Settings - Microsoft Settings - Microsoft - Advanced tab - make sure that the 'Use alternate download location on Package Server' check box is NOT enabled.
2. Close NS Console
3. Open up console again - it should navigate back to the Microsoft Page
4. Click Apply - no changes necessary
5. Go right to the Advanced tab - you can see that 'Use alternate download location on Package Server' is enabled
Run the attached script found in PackageServerPackageIssue.zip from a Command Prompt window. Copy both files into the <InstalledDir>\Notification Server\bin directory and then run:
This script will check all existing packages and correct the "Use alternate download location on Package Server " setting if it was checked and no location was specified. Since the script runs in a Command Prompt window, the quantity of packages corrected are displayed briefly. Then, the next time that the Package Server does an Update Configuration the packages will be moved from the default alternate location of <InstallDir>\Program Files\Altiris\Altiris Agent\<GUID> to the correct location under Package Delivery. No other user intervention is required. (The guid folders will automatically be moved from the root of the Altiris Agent folder Package Delivery folder.)
NOTE: Altiris has identified the source of the bug that causes this issue and it will be resolved in Patch Management Solution 7.0. The following query may help to determine if the Known Issue exists:
DISTINCT i.[Name], SUBSTRING (i.[State], CHARINDEX ('<pkgSvrLocation>',i.[State]) + 16,90) AS 'Package Server Path' FROM Item i
JOIN SwdPackagecodebase sbc ON sbc.PackageId = i.Guid
WHERE [State] LIKE '%<pkgSvrLocation>%'
AND ClassGuid = '6E89DC4B-693A-4BD3-AEFA-385CCD1874E8'
|Description||Logged in sydd2 (Altiris - Sydney) database|
Article URL http://www.symantec.com/docs/TECH25873