Service Manager uses groups to manage CI and Queues for WI to scope the user view criteria.Groups/Queues can either contain objects of the same class or it can collection of objects for different classes. They can be dynamic collection of objects based on inclusion rules or a static list or a combination of both. In addition, Queues are used for SLO too. More details about Groups/Queues can be found here
The GroupCalculation module is used to calculate the membership for a given group/queue. Given a membership rule the module looks at the managed type of the instances in the CMDB, finds all the instances that satisfy the criteria and then creates a relationship between the group and instance and writes it back to CMDB. Once the initial membership calculation is done, the module then periodically detects (default is 30sec) if there is change in the managed type instance space (add/delete/update). If it detects change, then it runs the membership rule again and updates the relationship between the groups and instance. However, the calculation of membership is delayed for 30min if Service Manager is under high load. This means, you would see that instances are added to Groups and Queues only after 30min . In fact, the calculation of membership is delayed for 30min
For TP5, when SM is under high load the worst case time is brought down to 15min. Which means in R2 when it used to take more than 30min to see an instance in group or a queue, in TP5 this time is brought down to around 15min.
Also the time to view the list of groups in service manager console is brought down. In R2 if there are 100 groups defined in service manager, to view this list of 100 groups it used to take around 1.5 min. This time is now reduced to below 10sec.
You can read about all System Center 2016 TP5 features from here and can download Service Manager bits from http://aka.ms/getSM2016
Feel free to use the comment section below for any queries or to share your feedback. We are looking forward to hear from you.
