Quickpost: SCCM 1602 Query - All Online Machines
With the Advent of client activity indicators in SCCM 1606:
We can now see which machines are online at a given time. I love these green checkboxes.
I thought it would be cool to try to make a collection of only currently online machines. So, into the query editor we go! We’ll add a new query rule, and then use the wizard to add a new value. This is all that you need to grab only the currently online systems.
This collection works VERY well for Incremental Updates. However, Scheduled Updates don’t make much sense
And the end result:Continue Reading...
When I first looked into AWS and Azure, the notion of scaling out an application was COMPLETELY blowing my mind. I didn’t get it, at all. Like, for real, how would that even work? A server without a persistent disk?
This short post is not going to tell you precisely how to do devops, or even give you pointers on how to build scaling apps in Azure and AWS. No, instead, I’ll share an interesting conversation I had on redditt recently, and how I tried to explain the notion of stateless applications to someone with questions.
The initial question
AWS is a great example of how you could setup a stateless application.
It’s easy to configure an application with a load balancer. We can use the load balancer to gauge how many people are trying to hit our site at a given time. If traffic exceeds the capacity of one host, we can tell our web service to add another host to share the load.
These new workers are just here to help us with traffic and keep our app responsive and fast. They will probably be instructed to pull down the newest source code on first boot, and be configured not to save any files locally. Instead, they’ll probably get a shared drive, pooled among all of the other workers.
Since they’re not saving files locally, we really don’t care about the host machine. As long as users have completed their session, it can die at any point. This is what it means to be stateless.
The workers make their mark on the world by committing permanent changes to a DB or shared drive.
So, new worker bees come online as needed. They don’t need to be permanently online though, and don’t need to preserve their history, so in that sense they are stateless. After the load drops, the unneeded little workers save their changes, and then go to sleep until needed again in the future.
Actually they’re deleted but I always feel sad thinking about my workers dying or being killed, so I have to think about it in different terms
Just my take on how I think of designing and deploying a stateless application. What do you think? Did I get it wrong?Continue Reading...
Recently for a customer, we ran into an issue in which the SCCM 1511 upgrade was hanging at the following screen. 'Backing Files for Upgrade' Continue Reading...
It's a common enough scenario: build one template machine and then mirror that to make a testlab, so you'd think this would be a built-in feature of Hyper-V, but its not. Luckily, it's not too hard to do once you know how, and I'll guide you through the tough parts Continue Reading...
Streaming is cool and all, but there are times when it's nice to have videos saved locally, like the huge backlog of content from MMS and TechEd. However, a lot of streaming services want you to only view their videos within the confines of their web page, normally with a sign-in session. In this post, I'll show you a few ways to download videos you'll run across online, and how you can use PowerShell to download some of the REALLY tricky ones. Continue Reading...
In this post we'll be covering how to implement progress bars in your own application, and how to multi-thread your PowerShell applications so they don't hang when background operations take place. The goal here is to ensure that our applications DON'T lock up when the users click anything. Continue Reading...