After leaving this overnight, only about 100 of the 10600 pending installs changed to a completed or failed state.  So, there are still a significant number of devices in a pending install state.

One other piece of information: when I look at the Profile tab in the accordion for the device, I see the profile name with Pending Install.  When I expand the profile, it shows Antivirus Protection as Delivered.

Did you have similar problem for other profile(s) that has payload(s) other than Antivirus Protection?  If so, what payload(s) is/are there?

Unfortunately, this is the only profile/payload that we are deploying.  The device is a single-purpose device that we preload with software and lock down to prevent other installations.  All software updates are controlled from within our applications.

I have access to the logcat output from these devices.  Is there anything that I should be looking for that may help understand what is happening?

One other confusing thing - I've been looking at a few devices that show the profile as Pending Install but I can run the antivirus scan on these devices.  I'm wondering if the install status isn't being updated correctly...

Hi Steve,

I would check the DS Queue length in the Servers Tab to see if the DS has a large number of tasks pending in the queue. If this profile was deployed simultaneously to all the 16000 devices, there is a high chance the DS had too many tasks lined up in the queue. 

 As far as the fact that you can run Virus scan on the devices even when the profile is pending install, here are two recommendations to try:

1. If on MobiControl version < 14, refresh the Device panel from the bottom of the web console, for MobiControl v14, refresh the search results from the search bar for pending updates and see if the profile status then updates to be installed 

2. On any such device can you request a device check-in and see if the profile status updates once the check-in is finished? 

Please let me know if you have any further questions. 

 Thanks

Thanks for the tips.  I can indeed see the queue sizes jump when I assign the profile.  Both deployment servers have 5000+ connected devices and the queue sizes jumped up to almost the same numbers (hard to be exact because of snapshot data).

When I refresh the devices page, I am still seeing that the profile is Pending Install.  If I manually request a device check-in or file sync, the profile status does not change.  However I am able to run a virus scan on many more devices than those with profiles marked as Installed (9000+ scans vs 5200 installs).

Is it possible that I am exceeding a queue size on the deployment servers?  If so, is there a setting that I can adjust to see if the queue size makes a difference?

Steve...

It's strange why remaining devices with profile not yet deployed cannot get higher priority in subsequent schedule updates to have the profile eventually deployed.

If your thousands of devices reside in multiple device groups,  have you tried staggering the schedule update time for different top-level groups to spread the computation loading as well as untangling any possible scheduling abnormalities.   By staggering, I mean making devices in different device group sub-trees to get update  at different times of an hour (e.g. 10 past, 20 past, ..., 50 past, etc).

That is a good suggestion.  I should be able to find a device property that I can use to easily partition the devices into virtual groups to see if that helps.

Staggering schedule-update can ONLY be applied to physical groups.  Virtual groups do not have configurable advanced settings, basically because a device can belong to multiple virtual groups and it is impossible to resolve  conflicts in advanced settings between them.