Client Management Suite

Hey all,

Lately, whenever I create a new policy and upload new software to be deployed, the policy gets stuck on 'retrying download' status multiple times. Sometime it takes 1 hour for clients for download but other times over 3. This happens for every single software resource, so policies with multiple pieces of software take over a day to install.

Screenshot of client:

Screenshot of package server:

Please help, I'm basically unable to reliably deploy any software at the moment.

Thanks

Hi Thijnb,

Do you use package servers? If yes, you should update package sources on them after you have Imported new Software or have updated some package for some software. If package source is not updated manually it will be automatically updated few houres later. Before it's happens package source is unknown for clients.

If you are using managed delivery policies you can start Emergency policy update for policy with new/edited Software (right click on the policy and select Emergency policy update).

Regards,
Dmitri

Hey Dmitri,

Thanks for your reply.

Yes, we have 1 package server (see second screenshot in original post) but the software status of the package I'm trying to deploy (Cisco Spark 2.0.2992.0 English), has "Package is ready" as status already. Doesn't that mean the package server received the package and it is ready for deployment?

Additionally, I made a new policy with .NET Framework 4.6.2 and used the emergency policy update as Dmitri suggested. The update complete, the package shows as "Package is ready" on the package server yet when I try to download it on my client I get the following. Any ideas?

Hi ThijnB,

This last screenshot shows that Notification Server have no source location for this package. If it's showed as ready on the Package Server then Notification Server should get to know about it (it's may takes some time). Same issue can occurs if client have taken the policy earlier than it's package got ready on Package Server and Notification server received this status. It's should be resolved on next download retry on client after Notification Server get the package status.

Next workflow witll help to avoid the poroblem you described:

1. Import Package -> Package Server got it -> Managed Delivery Policy Created (better to create it after Package Server receive the package to avoid situation when package have no "source location" on the Notification Server) -> recive the policy on client

To speed up, you may create Managed Delivery Policy right after Package was imported or edited, but before receive the policy on client you should start Emergency Policy Update (from right click menu).

Regards,
Dmitri

Thanks Dmitri, I was under the assumption that when I uploaded a package is would automatically be known by the Notification Server already.

I'll try your steps next time I have a package. Thank you.

It will be known by notification server but not so fast. Emergency Policy Update speed up the process.