No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
There are 2 DS running on MC 14.4.4 that manages 4200 Android devices. According to Advanced configuration we have set DS server priorities different for a subset of devices. It guides half of devices to connect in DS1 and half in DS2. One of the DS is always with many itens queued (around 1000) and other is almost none. We have tried to invert the server priorities and the behavior of queue size follow it. Both subset of devices has rules and profiles locked by kiosks. Is there any way to see what kind of task is in the DS queue? In positive way, we would be able to review the rule/profile or split the subset in a different way.
Our support constantly come across customer issues that revolve around constant high queue length in DS and this queue length does not come down for several hours. I want to know some of the commonly seen reasons that can cause this high queue length for DS which can be useful during initial investigations.
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points
Highly experienced members with valuable inputs. Should have more than 700 points
Beginners taking the initiative. Should have more than 500 points
