Report for Packages with Invalid Source Path

[twister12]

Dear All,

is there a report for packages with invalid source path? for example if the source folder for the package is deleted.

Best regards

[Igor Perevozchikov]

Hi twister12!

There is a default "Package Status by Package Server" report, so if there is any invalid package, then there will be drop-down menu "Package Status" with "Invalid" status 

Best regards,
IP.

------------------------------
[JobTitle]
[CompanyName]
[State]
------------------------------

[twister12]

Hi Igor,

package is still shown as valid.
package source location is "local on NS".
if the folder on NS was deleted you get a warning in NS Log that path is unavailable but package is still valid.
any idea?

Best regards

[Igor Perevozchikov]

Hi twister12!

Unfortunately there is no any event records in database from "NS.Package Distribution Point Update Schedule.{29a2b641-222a-43b0-830c-a25c59e93fe4}" task execution, when it detects that some of packages have an invalid source path, etc. therefore impossible to get any custom report for this purpose.

Only manual checking (with filter) logs from Altiris Log Viewer is the way to identify problematic packages

and manually fix their source location via right click on appropriate package from SMP Console > edit software resource

Best regards,
IP.

------------------------------
[JobTitle]
[CompanyName]
[State]
------------------------------

[twister12]

Hi Igor,

thanks for your answer.
a second option is to react on the ns log event (warning) via system messages(automation policy).
any idea how to implement this?
i have only create system messages if task is successfull.

Best regards

[Igor Perevozchikov]

Hi twister12!

As far as I see, there is no exact type of "NS Messages" available to check logs from "NS.Package Distribution Point Update Schedule.{29a2b641-222a-43b0-830c-a25c59e93fe4}" task. 

I think that using Automation policy for monitoring of these warning messages about invalid path of package is not good way, because there can appear lot of such warning messages which will trigger Automation policy non stop.

I would consider to use "Monitor Solution" to let administrator know that now there are warning messages in NS log about invalid path for packages, so for this purpose I created custom Monitor policy with custom metric and rule

Metric polls "C:\ProgramData\Symantec\SMP\Logs\a.log" after every 5 or 10 minutes (you can set any required polling time) and in case if there will be such warning message, I will get an alert in event console (and it will not trigger non-stop and raise new alerts, until administrator will manually resolve this alert in Event Console) otherwise it will catch first warning message and record it but will doesn't catch other warning messages related to invalid path of package (anyway this will be a signal to check SMP Logs and identify what packages now are inaccessible)

Or event add "Send Email" task, specify there required mail addresses, so if rule will be triggered, then it will send same alert information to specified mail addresses

Example:

Sharing (attached) this custom monitor policy (maybe will be useful)

How to import custom monitor policy:
1. Download attached "Monitor Policy (Agent-based) - check SMP Log for invalid path of packages.xml"
2. Open "Import monitor pack" page in Console > click "Add" > specify .xml. Now click on added custom monitor policy and click "Schedule"

Best regards,
IP.

------------------------------
[JobTitle]
[CompanyName]
[State]
------------------------------

Attachment(s)

Monitor Policy (Agent-based) - check SMP Log for invalid ...xml   10 KB 1 version