SCCM Windows 10 OSD Best Practices with ConfigMgr

Let us learn how to SCCM Windows 10 OSD Best Practices with ConfigMgr.Windows 10 OSD and migration are today’s hot topics. I think all the organizations are started Windows 10 projects.

If not, they might already be completed their migration projects. It would help if you were very careful about Windows 10 OSD deployments. I read about another probable “Human Error,” which slowed the whole bank.


  1. How to Prevent SCCM Windows 10 OSD TS Accidental Deployments
  2. Various Ways to Perform Windows 10 OS Deployment?
  3. Webinar – Windows 10 OSD Best Practices with SCCM

How to Prevent SCCM Windows 10 OSD TS Accidental Deployments

There are loads of systematic ways to prevent accidental deployments of Windows 10. Following are some quick tips to avoid unintentional implementations of the Windows 10 task sequence. Some discussions are going on in SCCM ConfigMgr Facebook Group on this topic.

  1. Better RBAC (Collections***)
  2. PXE Password (Unknown Computer Support****)
  3. Task Sequence Condition before Booting into WinPE (Required Deployment****)
  4. Validate Collection Query (Test, Test, and Test ****)
  5. 3rd Eye Process (To make Change management team & Management Happy******)

I have another post that will help you find out “Who Deleted or Modified or Changed SCCM Settings.”

Various Ways to Perform Windows 10 OS Deployment?

We can perform OS deployment of Windows 10 using MDT, SCCM, and Windows AutoPilot when you use SCCM and MDT to perform OSD of Windows 10 using Task Sequence.

However, Windows Autopilot is not a pure Windows 10 OSD solution, as I mentioned in the previous post, “Beginners Guide Setup Windows AutoPilot Deployment.”

Webinar – Windows 10 OSD Best Practices with SCCM

Windows 10 migrations are the best chance to start the journey towards modern management for your organization. My recommendation would be to start planning for a future-proof workplace environment as part of the Windows 10 migration. 

If you have questions about best practices of Windows 10 migration, the following Webinar is one of the chances to get the answers.


High-Level Agenda

  1. Windows 10 OSD planning, deployment, and maintenance
  2. Large-scale, zero-touch deployments and ongoing servicing
  3. Security configuration management to harden attack surfaces
  4. Real-time incident response to urgent security issues

Schedule and Registration Details 

Windows 10 OSD Best Practices with ConfigMgr Webinar By Microsoft MVP Ami Casto 

Tuesday June 26, 2018 9am PDT / 12pm EDT / 6pm CEST

Registration RSVP ->

5 thoughts on “SCCM Windows 10 OSD Best Practices with ConfigMgr”

  1. Here’s a Tip: Don’t use Windows 10!

    Instead, make good use of Windows 7 and all it has to offer. Win7 is still by far one of the most stable OS products MS has ever created and as far as being a sufficient productivity platform, it’s very hard to beat.

    MS just wants everyone to jump on to their gravy-train so that they and their filthy-rich ad-marketing partners can continue to amass large swaths of money off who you are, where you go and what you do online and even when you’re not online but when you simply might be using your home computer for some word-processing——-an activity that is no longer personally yours (nor private) on the Windows 10 platform.

    Make no mistake about it——–Contrary to what many MS trolls and their partnered corporate thugs will have you believe——-Windows 10 and all that comes with it, drives a wedge right between you and your right to privacy period!

    With Cortana and the Edge browser as part of Win10, you might as well just create your own highly-detailed dossier and post it online to as many sites as you possibly can find, because really, that’s essentially what you’re doing when you use the Win10 OS——-Microsoft’s Ultimate SAAS model platform.

    It’s also not unlike cloud services, that no matter how much they boast about how secure their cloud is), it’s really only as good as the server network such service is hosted on and it will never be as secure as you having complete physical control of your files and private information that you store on your own personal computer and lock down with your own security.

    Remember, the corporate construct of this world (as a whole) cares nothing for the average user, except for the purpose of lining their fat pockets with enough money to feed the entire world 10 times over——-if only they’d actually give a damn and finally decide to give up this ridiculous charade of mass-exploitation for profit.

    Don’t give in to these corporate fascists creeps just because they wield such influence. You still have control of your life and what you do with it——-Don’t let them take away your dignity and privacy. Stand up to their tyrannical grasp and it they, themselves, will not have a leg to stand on.

    • @TruthOperator – that’s the most ridiculously pointless comment I have ever seen on a blog post and i hope when the author notices it, he deletes it. You can turn off sending private data to Microsoft in Windows 10 (unless you are using a free version of Windows 10 Insider). And if you are really paranoid you can block access to the domains via the firewall etc… I manage a fleet of over 10,000 corporate computers – Windows 10 is more stable and performs better than Windows.

      • I don’t think your comment is about as pointless as his, but probably more.

        Windows 7 was much easier for admins to manage. There is no argument here. If you make the argument, you’re new.

        Windows 10 is a far superior OS. However, from 1511>1803 there have been so many stupid dumbass changes by Microsoft it makes architecture a real pain. A great example is how we got a functioning StartMenu.xml in 1607, but in 1803 the xml syntax changed (with NO notice), breaking OSD. It took quite a bit of research to correct that. That’s one of like 500 examples.

        OP makes a great point about privacy too. You’re wrong about turning off sending private data to Microsoft. If Telemetry is turned on, data is going out. Disable Telemetry, and other things break. Microsoft worked with the NSA to illegally steal our data, so OP’s point is further backed up. Microsoft isn’t a friend or ally to anyone. They’re progressive fascists hungry for the dollar.

    • Bullshit, new Intel CPU will not be supporting Win 10, are you going to use your Sandy Bridge CPU for another 20 years? LMFAO

  2. It’s only ridiculous to those who’ve fallen, hook, line and sinker for the bold, sugar-coated claims MS, Google, Facebook and many others like them have heralded the world over, as the next best thing since sliced bread.

    You can buy their bologna if you want to, but as for me, I’m sticking with my Custom Built PC, that I still have complete physical control over——-period!

    Windows 10 Telemetry cannot be completely shut down. MS hard-wired those spyware parameters to the kernel. It is nearly impossible to do, contrary to the bologna you’re now slinging, unless of course you violate their terms of service agreements & EULA by gutting them out of the registry using sophisticated hacking techniques——-but even then, this assumes that you already know you way around the entire inner workings of the Windows kernel. In either case, you still run the risk of seriously damaging the kernel and it really is not advisable to mess with the registry, especially if you don’t know what you’re doing.

    The corporate world will never admit to the public their shiesty dealings and they also count on their loyally duped supporters to help them quell the masses into submission.

    You can try all you want to sweep the truth underneath the rug, but for a certainty, the devil is in the details…


Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.