SCCM - Collection Query OS Change Issue

[FN-GM]

Hello,

 

Not an issue as such but here goes.

 

I am assisting a school to migrate to Windows 10. They have a collection called "all computers". I have adjusted it so it only picks up Windows 7 machines so the wrong software isn't deployed to Windows 10.

 

When I image a workstation to Windows 10. SCCM is not pickup up the OS change quick enough and so the now Windows 10 machine is still in the Windows 7 collection and installing Windows 7 only software. Does anyone have any tips on how I can make SCCM pickup the changes quicker please?

 

Thanks

[Steve21]

Depends which bit is being slow, the client end of if you haven't put incremental updates on your collection.

 

If you right click the collection and choose update does it pull them across? If so you're probably missing incremental updates option on the collection queries.

 

If not you can modify the client settings to do the scans/inventory on the client quicker

 

Steve

[ShellfishClive]

I think SCCM just reports in when it does, I don't think you can change that. You might be better off imaging all the machines that are going to Windows 10 then making a collection on those machines to deploy the software. You can then just add any other machines that you image to that collection and it will deploy that software to it.

[FN-GM]

Depends which bit is being slow, the client end of if you haven't put incremental updates on your collection.

 

If you right click the collection and choose update does it pull them across? If so you're probably missing incremental updates option on the collection queries.

 

If not you can modify the client settings to do the scans/inventory on the client quicker

 

Steve

 

I have the increment button selected. I would have though a fresh install of the SCCM client would force a scan/refresh?

 

I think SCCM just reports in when it does, I don't think you can change that. You might be better off imaging all the machines that are going to Windows 10 then making a collection on those machines to deploy the software. You can then just add any other machines that you image to that collection and it will deploy that software to it.

 

The whole point is I do not want to to deploy the software. They are being left in the old collection because SCCM hasn't caught up that the OS is now Windows 10.

[clareq]

Could you set the requirements on the software you want as Win 7 to only install on Win 7?

[FN-GM]

Could you set the requirements on the software you want as Win 7 to only install on Win 7?

 

That wouldn't help either. SCCM still think they are Windows 7 machines for a period after the Windows 10 upgrade.

[Steve21]

I have the increment button selected. I would have though a fresh install of the SCCM client would force a scan/refresh?.

 

The scan is normally still dependant on the policies that are applied to those machines. (As it's not a new "machine" in SCCM, just a reinstall of client etc unless I misunderstood)

 

As an example, we've modified our Win10 policy to reduce the scanning time down to 5 minutes for deployments etc to get software out faster.

 

The operating systems get picked up during Hardware Inventory Cycle which I can't even remember the standard time but think it's 7 days + up to 240 minutes offset?

 

Steve

[FN-GM]

I have recurred the scanning period. Hopefully it will help.

 

Thanks

[clareq]

That wouldn't help either. SCCM still think they are Windows 7 machines for a period after the Windows 10 upgrade.

 

Then use a custom requirement and look for a registry fragment that's unique to the OS.