Ok, Maybe I've not understood the screen from your other post https://www.experts-exchange.com/questions/29164488/SCCM-Device-Collection-shows-Devices-that-do-not-belong-to-the-Collection.html. It looks like you've created a collection containing all collections and systems available on your SCCM.

Hi,

Please say what collection this is going to. Is it in a lab or in Production?

This warning is by design to prevent doing things like "deploying XP to every computer in the business including mail servers, SQL servers and SCCM itself". *That* is what "All Systems" contains. It has happened, to a bank. The guy quit and left Australia where he lived.

So, if you' ARE using SCCM in Production I would stop where what you are doing and create a Lab instead. For your own sake.

Mike

this is just a LAB

The collection has just one PC windows 7,  if I select "Available" the wizard proceeds , if I select "Required" it pops up that error message

It should only display a warning for a "high risk deployment" if you deploy an OS task sequence to a collection containing simple clients. Is it exactly the same error as above?

Hi,

OK. MS added this feature to try to prevent the "Sev 1" incidents I described. It applies to any OSD and defaults to "collections targeting over 100 objects". It is set on the properties of the site (in Admin/Site config). It only applies if Required as you've found.


Ref: https://docs.microsoft.com/en-us/configmgr/core/servers/manage/settings-to-manage-high-risk-deployments

I sounds like the number is set to 1.

The behaviour is by design.

Mike

the settings are as shown below:

Just tick Warn: .... It will show a warning and you can continue.

Thank you Guys!

I will get back to SCCM Lab later