
Some time ago, information about updating Configuration Manager's collection (including the time required to perform the update) could be seen in a supplementary tool. Nowadays, there is no need to go to the supplementary tools, as such information is available directly in the administrator's console.
When you look into the summary of information about collections, there are some interesting data there that characterize the update processes. Here is an example of an embedded collection "All Desktop and Server Clients":

In addition to the information provided for individual collections, there is also an overall snapshot available in the monitoring section:

Here you can find a summary of the time required to update each collection, below is a case of a full update:

This additional functionality of the console allows you to easily find collections that are excessively "costly" - they take too long to update, perhaps indicating an improper selection of collection membership criteria.
Wanting to get a "behind-the-scenes" look at where this data is coming from, just look at the invaluable smsprov.log to catch the relevant SQL queries (WQL queries are also provided):

Of course, you can "paste" the query into SQL Management Studio and view the results:

Since the results for both device and user collections are given in the console, two queries will be found in the log, and the composite of their results is presented in the console. The form of the two queries is similar, what stands out is the condition of collection type CollectionType = 2 in the case of device collection, and ColletionType = 1 in the case of users.

- Support and development of Microsoft and Nintex based applications
- Application design and development including digital processes
- Invoice management
- Requisition management
- Contract management
- Modern Intranet
ISCG sp. z o.o.
Al. Jerozolimskie 178, 02-486 Warsaw
NIP: 5262798378
KRS: 0000220621
Phone