SCCM Required and Available Install

jskfan
jskfan used Ask the Experts™
on
SCCM Required and Available Install

I am trying to Deploy Task Sequence from SCCM, when I select Required and click next, I get the popup error shown on the screenshot below.
Any reason why this is happening?

Thank you

r
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
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.
Mike TLeading Engineer

Commented:
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

Author

Commented:
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
Acronis in Gartner 2019 MQ for datacenter backup

It is an honor to be featured in Gartner 2019 Magic Quadrant for Datacenter Backup and Recovery Solutions. Gartner’s MQ sets a high standard and earning a place on their grid is a great affirmation that Acronis is delivering on our mission to protect all data, apps, and systems.

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?
Mike TLeading Engineer

Commented:
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.

OSD high-risk warning
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

Author

Commented:
the settings are as shown below:
s
Just tick Warn: .... It will show a warning and you can continue.
Leading Engineer
Commented:
Hi - feeling more awake I re-read your question. The error message says all you need to know!

"You cannot deploy 'My Wlndows 10 OS Image Deploy' with a purpose of Required to the OnePC collection because it contains
1 clients that host one or more site system roles. D0 one of the following to resolve this:

(1) Select a different collection
(2) Change the deployment type to Available

(3) Remove clients that host site system roles from the selected
collection
(4) Modify the site properties deployment verification settings

MS sometimes get their error messages right. The OnePC must have an SCCM site role. If you really, really want to continue change the Site option (4) by clicking on the Warn radio button. Before you go there, be sure you want to.

If I were you I would do the deployment and then go back and set it back to Block. Allowing collections to push to core SCCM machines is not wise and why they put the option then. You might think it's only a lab. Fine, but are you happy to spend hours fixing your lab?

Mike

Author

Commented:
Thank you Guys!

I will get back to SCCM Lab later

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial