Software Update Groups - All Deployments changed from Available to Required after Last Evaluation ADR

I need help to get an explanation for the result of what the ADR did to the Software Update Group Deployments.

After the evaluation of the ADR all the deployments of that Software Update Group the Type of deployment changed from "Available" to "Required". The result of this was that all members were forced to update. I thought i prevented this to happen by setting the target collection of the ADR to an empty device collection. After the creation of the Software Update Group i placed an additional deployment on it and changed the Deployment Type to "Available". On this second deployment i pointed the software update group to a device collection filled with Windows Servers.

Before this all happened, because all functioned good first, there have been time issues on the internal domain. Because of these problems SCCM had time settings in the past but also far into the future. After this problem when the evaluation of the ADR had changed because of new updates available the Software Update Group got corrupted.

This happened once, after i recreated all ADR's en redeployed the Software Update Groups everything looks fine again.

Can anyone help me to explain how this all happened en how to prevent this from happening again?

Could it be possible that there are more issues and where do i have to look for these?

May 22nd, 2015 3:35am

I've never seen or heard of this happening and it (to my knowledge) is not by design as that would cause issues. Can you recreate the issue?
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2015 8:45am

No i tried recreating the issue but now it seems to work again as expected. So far it looks like it was a one time failure only i need some kind of assurance that something like this is not going to happen again. Perhaps there is something i can do as precaution? Reinstall a role or something?
May 22nd, 2015 9:18am

There are no assurances in life.

ADRs have nothing to do with roles.

You should always QC your ADR activity although I highly doubt this was something done by ConfigMgr but there is no way to prove that one way or the other.

Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2015 9:20am

Yes i know, that's what i know now that i have to CQ my ADR's. And i also have my doubts but i checked the audit log and all i can see there is just before this problem happened a change was logged but one i did myself. I deployed the Software Update Group to a additional device collection. Much further information i can not get out off this audit log. Are there any other suggestions?
May 22nd, 2015 9:47am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics