Client Management Suite

Good day! I have a problem on the client side - package install not start and the download history is empty! Somebody faced with similar? The log file does not contain download errors.

Hi,

You may see situations when package name and all properties are empty for packages that were executed on the computer and then computer has been removed from the target of the policy that responsible for the package delivery. This is quite common case for the plugin install policies - some plugin installed then updated basic inventory send to NS and after collections updated computer will no longer be in "Plugin install required" collection. After some time properties of the package will be emptied on a client side. If you will add corresponding computer to the install policy manually then after policy/collections update on NS side and configuration update on a client side you will see package properties again in SMA UI.

HTH,

Alex.

Hi, Alex! This situation occured with one specific package. I think, that it's a problem with my task server. I will check task service status on NS.

Good, it also might be good to check the status of the package on a package server UI.

THank you,

Alex.

The problem is relevant. So I can not find a solution. What could miss out on the preparation of the policy package delivery?

Hi,

Please provide more information related the schedule settings for Compliance and Remediation for your problematic policy?

Also please verify Download the package file ASAP agent setting (need to verify for multiple policies). If this setting is not set it can cause problems with policies if they have different schedules for Compliance and Remediation schedules (especially if is set to install in maintanance widow). In this case Download will not start immediately after policy arived to client and download tab will be empty.

Thank you, Dmitry! In version 7.1 package download setiings can be found here (screenshot) : Settings - Software - Managed Delivery Settings. I'll try this method!

Hi Alexander,

Did you configure the Multicasting in Targeted Agent Settings? (for more details about Multicasting please reffer the link).

Regards,
Dmitri

Dear Colleagues! The problem is still relevant. Now i have some interesting information about this package - it was registered in the system by running the script (vbs). So, this package have a non-default location. On client Software Delivery folder not contain information about package. May be i must verify all records about location of package in Symantec database (CMDB)?

Hi Alexander,

Please provide more information:

About package - If I understand you correcly it's imported by using ASDK via VBS script, after it was imported can it be opened via UI? 

You did not ansevered on question about multicasting? How it's configured? 

Also please verify does this package exists on package server which manage this client machine? (if you use Package Servers and they manage different subnets or clients manually assigned to some package servers).

Did you try to import same package via UI and create new MD policy, what will be happen in this case? is this package comming on client?

Regards,
Dmitri

Sorry for the pause. I tested possible solutions.

The toolkit (package) can be found in a snap "Jobs and Tasks".

The Package server (on NS) contain the package (checked in Agent tab).

There is no need to configure multicast - package delivery testing is performed on the stand (several workstations).

About the manual creation of policy delivery - try it today!

Thank you, Dmitri.

Hi Alexander,

Try to import same package again, not only create new polcy or task.

After that try to refresh the packages on Package Server (PS in future). 

After packages refreshed on PS enable policy or launch task from Notification server.

Regards,
Dmitri

Colleagues!
I found a small error in the policy settings.
How can I specify the correct "Task valid" period (details in the screenshot)?