Adding my own 2¢ to the PowerShell & Technology Communities
In learning about PowerShell and Web API’s, I figured I would start with something fun and easy.
Let’s forget all about my previous step 3. For the sake of argument, step 3 is dead, long live step 3.1! Any script should be a living, breathing document which gets updated as needed. In this case, it was needed. Why would I burn such a good script to the ground? Well, to be blunt, I’ve found a better way to do this, with better ultimate performance.
If you need a refresher on the previous steps, I have Step 1 for Hyper-V, Step 1 for VMware, and Step 2.
In Part 1 of trying to tame my photos, I tried to wrangle my horribly organized photo library. My organization skills were lacking, like many, when it comes to photos. We take them, we import them or save them and then we… forget about them. That’s a problem when I’m trying to handle large amounts of them (22.8 GB in 13,316 files) and organize them in ways that seem sensible. To use this we leverage the metadata tags that describe the date and time the photo was taken.
No one could ever accuse me of being a shutterbug. I’m more of a casual photographer and much most of that was from mobile devices. But that’s not the be-all-end-all. I’ve also got scores of scans of old photographs, screenshots, and a bunch of other graphics that have accumulated over the years. Thankfully modern mobile devices tag photos with a plethora of information. Now it’s just a matter of getting to that information. These tags can help you organize your data so you don’t run into my problems.
In September I wrote a few things about how I use SAM Script Templates – specifically with PowerShell. One of the more powerful things in the SAM arsenal is the ability to return multiple components in a single script. I’ve used this in any number of ways, but the one that gives me the most satisfaction is a PowerShell script that I wrote for Linux.
Yesterday, I wrote about how I setup SQL Servers Virtual Machines using PowerShell and PowerCLI. Now that I’ve got the SQL Server imaged, it’s time to format the disks and prep the Page File. Let’s dig in.
I write a lot of PowerShell scripts. Like a lot, a lot. I write them for any manner of things, but recently I’ve been tasked to help out with a few Server & Application Monitor templates. These are some of the most interesting things that SAM has to offer.
Looking at each of the scripts, I decided it was worth revisiting based on some of my newly acquired PowerShell superpowers (cape not included).
SAM script templates (Windows Scripting, PowerShell, Perl, Python, whatever) require two things – a statistic and an exit code.
Do you run a bunch of Orion servers? Do you hate exporting your custom NCM Device Templates one at a time?
No? Only me?
Well, if you are ever like me, I’ve got something to help you out.
It basically checks for all the device templates in your database for those that aren’t out of the box and exports them in the proper format.
In a previous post I said how to run multiple Orion installations without running the Configuration Wizard. This is great if you have a new big installation planned. So the last step is to actually run the configuration wizard.
I stumbled across an article called Install Orion products in unattended or silent mode that made me so happy because I install new Orion servers about 4 times a month. There are only so many time I want to click “Next,” “Next”, “Finish” in any given day. So, since I do this so often, I wanted to script this out. The big two takeaways from this article are that you run the installer silently and can skip the Configuration Wizard from running after installation.