Powershell

I needed to find a way to automate the change of Mac Management profile of a logical NSX-T switch for a vRA project. This post describes how I did just that

In this post I’m going through some of the lessons and practices I’ve picked up over the years when it comes to working with Powershell

Recently I’ve worked a bit with the HPE OneView Global Dashboard. I was surprised to see that HPE hadn’t created a Powershell Module for it so I decided to create one my self

As a follow-up of my exploration of the HPE PDU REST API I wanted to create a Powershell module as a wrapper for the API. I’ve previously written a post on how to create a Powershell module as a wrapper for an API here. The PDU module will be built in the same way where there will be a private function that handles the actual API requests

We all love today’s modern web with lots of API’s available, both for retrieving information from various sources, gaining additional insights and for transform and enrich your data. Most API’s today are RESTFUL, meaning that they should follow the REST principles. REST is not a standard, it’s more a guideline for how to design your API. With the REST guidelines in place many API’s share the same or similar structure and with that it gets easier to work with API’s as you can make use of the same techniques.

I’m using the Scheduled Tasks functionality in Windows Server quite extensively. I have tasks for importing stuff to a database with Powershell scripts, running some cleanup scripts etc Almost all of my scripts run on different intervals during the day. Some maybe just once a day and some might run every x minutes. Recently I encountered a difference in the way Scheduled Tasks work on Windows Server 2012R2 (and below) and on Windows Server 2016.