Ok.. another one that's been in my drafts for the past 3 months, Seems to work fine, however if you run it in a TS over and over and over again because you're testing constantly, it seems to skip some, like Twitter blocks duplicate Tweets. Anyway, here ya go. If you have any improvements, please get ahold of me.
Hey Folks, so I am at MMS right now, and I saw a lot of demos were people were tweeting from at Task Sequence using Orchestrator. I was like, um.. that seems like a lot of work to just tweet, I don't want to support another server, hopefully it's actually doing more than just tweeting. I set this up a while back for fun, and forgot to blog it, so here it goes. The hardest part... was already done by Adam! I stole his work, and built on top of it. You've probably noticed that is a theme on my blog, I like to borrow the hard work of other and twist it for my own purposes, of course giving credit where credit is due. I hope you are doing the same to my blog, and please give me a shout out if you take something I've done and add to it, and then blog it for everyone else to use!
So I started here, Adam's Blog. This provided the connections to Twitter. I created a new account specifically for my blog (@garytownblog) and set it up in his script, which he explains in great detail. So Part 1 ... Go there and do that..
This was one of Keith S. Garner’s (@keithga1) gifts to me before he parted ways on his new adventure. I asked him for a script to automatically pull the Hard Blocker from the compatdata XML file created during the Windows 10 compatibility scan. After I gave him my request, he hit me up on skype about 2 hours later and said he didn’t write a script, he wrote me a 1 liner. Keith knows how much I like 1 liners. Why? Task Sequences! If I don’t have to have content to accomplish a step, all the better! I've been known to build scripts on the fly using echo >> script.bat then running the script.bat file just so I don't have to have content.
So what’s this magic 1 line of code? I'm getting to that.
Why? Ever want to run a few tasks after upgrade, or more importantly, ensure a few things happen if the upgrade goes south and rollsback? Why not hitch a ride on what ConfigMgr is doing natively and add a few things you need.
Supported? Highly unlikely. Please test, and please don’t say “Gary did it” as rationalization when someone asks why you decided to do this.
Do you do it? Heck yes I do, in my lab. Need to get a little more test results before implementing in Production
How do you use it? I’m not telling! Oh wait, that’s why I’m blogging. I modify the SetupRollback.cmd to ensure the machine is pulled out of provisioning mode when it the upgrade rolls back, and to set a registry key for our reporting, and trigger hardware inventory.
ConfigMgr has two files in the c:\windows\ccm folder that it uses:
So, you think you’re setting the lock screen, just to have OSD finish and be like “Why is the lock screen missing and showing a dark blueish color?” or “Argh, it’s the stinking Windows default lock screen, not the one I wanted”. Perhaps you have a lab, and don’t activate your PC’s, so you get the rotating Bing Picture of the day, which is actually pretty cool and all, unless you’re trying to test Lock Screens. Thanks to Doug (managedoug.com) for bringing this to my attention and having me dig into it a bit more.
I’ve got Several Steps to control this during OSD which include Copying Files over the default lock screen images, and setting registry keys, basically depends on exactly what outcome you’re looking for.
Scenario 1, you want to set the Lock Screen and NEVER allow the user to change it.
Scenario 2, you’re cool with the user changing it, but want to set it to your own custom default.
To accomplish both, there are several things in common you need to do, so I’ll start with the steps you need to do for either situation, then break apart the single additional step that enables scenario 1. Read more
So this will be the first of several posts, well, it’s sorta the second, this heavily relies on the Script I posted for writing values to registry & WMI a few posts ago, however I’ve made several modifications to it since then, and have done A LOT of testing. Hence my last post about testing Low Disk Space machines.
WaaS Process, as Designed by Mike Terrill & Keith Garner quick overview:
- PreAssessment: Set of Rules run against hardware inventory data to rule out machines that be known to fail the upgrade. Rules include:
- Hardware Checks
- Free Disk Space
- Software Checks (Software we know that needs to be at specific versions to survive IPU, or not block it)
- 3rd Party Encryption Version level
- 3rd Party AV Version level
- Several other Apps
- General Checks
- Last HWInv Date
- Last MP Checkin
- OS / Build / OS Arch
- CCM Cache Size
- PreCache / Compat Scan (Task Sequence): After it passes all of the rules, the computer then added to a collection targeted with this TS. The TS is setup as a Required Deployment, and set to Pre-Download Content, and Download all Content before starting the TS. Then will dynamically download the driver packages, run the Check Readiness, and then Compat Scan.
- Schedule for Upgrade: After it has been cached, and passes the compat scan, the machines can be schedule (added to collection targed with the upgrade).
That’s a really quick overview of how we’ve setup WaaS, we went over this in great detail @ MMS, and I’d expect Mike Terrill to eventually blog that detail, I just don’t want to steal all of this thunder, but felt you needed a little overview to explain where this TS fits in.