PowerShell articles, tutorials, and guides from community experts.
Yesterday I pushed my first real project to a public repository on GitHub. It’s small right now though I hope to flesh it out over time, and it is very niche, but I hope it helps others who come across it. Regardless I’m proud of it. If you like, you can check it out here, I’d love your feedback, but that’s not the reason I’m writing this. I’m here to tell you why I did it.
The schedule for the 2018 Summit still needs a little bit of polishing to finish it but it’s taking shape. I’ve started releasing information on sched.com that we’re using for all our scheduling needs for the Summit. The one and only truth regarding the sessions and their times can be found at https://powershelldevopsglobalsummit2018.sched.com/ I’ll be adding sessions over the next few days so keep checking. I’m really excited about the schedule for the 2018 Summit.
So we’ve talked about Azure Automation DSC and the extensive reporting we can get from it. With the pricing as it is, it would be hard to argue as to why you would want to use anything else. But I’m a completionist, and there may be some edge cases that might come up where you wouldn’t be able to use the pull method for configurations. So let’s talk about how you can use Azure DSC to push a configuration to a virtual machine.
Last week we talked about modifying and uploading our configurations to Azure Automation DSC. We were able to import credentials from Azure’s Automation Account Credential store, and then compile the .mof files in the automation account for deployment. This week, we’ll be looking at how we apply those configurations to existing systems via PowerShell. Then we’ll take a look at some of the reporting available via Azure Automation DSC and send those reports over to Operations Management Suite for dashboarding.
The call for topics is closing 1 October at 23:59 GMT. We’ve had a fantastic set of submissions. Creating an agenda for the 2018 Summit is going to be very difficult because we’ve had so many fantastic sessions submitted and I don’t have enough slots to take them all. The call for topics is hosted by papercall.io – highly recommended – and the cut off is automatic. I WILL NOT ACCEPT ANY SESSIONS SUBMITTED AFTER THE CUT OFF DATE.
Today we’re going to be talking about adding configurations to your Azure Automation Account. In this article, we’ll be discussing special considerations that we need to take into account when uploading our configurations. Then we’ll talk about compiling the configurations into Managed Object Format (.mof) files, which we’ll be able to use to assign to our systems. Things to Consider When building configurations for Azure DSC (or anything where we are pulling pre-created .
I’ve been wanting to do this series for a while, and with some of the recent changes in Azure Automation DSC, I feel like we can now do a truly complete series. So let’s get started! Compliance is hard as it is. And as companies start moving more workloads into the cloud, they struggle with compliance even more so. Many organizations are moving to Infrastructure-as-a-Service for a multitude of reasons (both good and bad).
Microsoft recently published a “Future of DSC” post that I thought deserved some independent commentary.
We have started the acceptance process for the sessions to be presented at the 2018 Summit. Those currently accepted sessions are listed in the brochure The deadline for submissions still remains as 2 October 2017 We’ll probably be formally accepting a number of other sessions during September BUT the bulk of the agenda won’t be finalised until after the deadline closes. You still have plenty of time to get your submissions into the system.
PowerShell 2.0 is being deprecated - see the PowerShell Team blog for full details
Try adjusting your search terms or browse all content.