Collection Membership mismatch
Came up with some weird issue, we are using dynamic application method to install applications during build.
As of now for one machine which we have found till now and can be more, we wanted the machine to be rebuild and applications which were installed previously should not get installed so we deleted the machine from sccm and imported it again( so that machine gets removed from previous collections).
Now when rebuilding the machine the application are still installing, when checking in console it shows machine is part of only two collection which it should be however when i run below sql query in DB it shows machine part of other collection as well.
I am using below SQL query:
join dbo.v_Collection Coll on FCM.CollectionID = Coll.CollectionID
FCM.Name = ‘Machine name’
Checking the logs of dynamic app it detects machine part of various collection so it installs it.
Answers ( 5 )
how is your collection membership query looking like? is it a direct membership or query based membership? give us more info on the collection membership type, based on that we can tell what could be the problem
That is the problem, in sccm console machine is showing part of only two collections one is ‘All systems’ which is by default and the other one is OSD collection on which task sequence is deployed.
However when quering the SQL database with the query mentioned it shows me machines is part of few more collections other than those two.
I deleted the machine twice from SCCM console , imported it back again with GUID and imaged the machine still the same results.
Were you able to solve the issue?
Not at the moment but I am resolving it, wil update the answer once I find something
Do you have CAS? I have seen a similar type of issue before.
I have standalone primary☺️
Ah … may be you might need to look into WMI to get some more clue?