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.
This is where I show that I’m really not a DBA. I’m an Accidental DBA at best, and a nuisance at worst. SQL Server already has the capability to be installed via command line parameters or a configuration file. If I setup the machine the same way every single time, this would be fine, but since I need to change the placement of certain file types, I need to have the ability to change on the fly.
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’m trying to automate as much as possible in my lab and part of that is building SQL Servers. I’ve taken to trying to scripting this out. For me, that involves using PowerShell to build out this machine.
A few months ago, I really stated digging into the Orion SDK and I wanted to know more about ways to automate adding nodes to Orion. Sure, I can wait for the Network Discovery to kick off, but I’m impatient. I’ve gotten many of the parts together over time, but this is my first post where I put everything together. For this version, I use the PowerShell Snap-In. I will add an additional post later using the PowerOrion Module.
A few months ago, I wrote about the third step in setting up an Orion server from scratch. After using this script for a few months, I realized there was an eventuality that I missed.
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).
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.
Installed Orion Modules
WHEN Name = 'APM' THEN 'Server & Application Monitor'
WHEN Name = 'IPAM' THEN 'IP Address Manager'
WHEN Name = 'NCM' THEN 'Network Configuration Manager'
WHEN Name = 'NPM' THEN 'Network Performance Monitor'
WHEN Name = 'NTA' THEN 'NetFlow Traffic Analyzer'
WHEN Name = 'Orion' THEN 'Orion Core'
WHEN Name = 'SEUM' THEN 'Web Performance Analyzer'
WHEN Name = 'SRM' THEN 'Storage Resource Monitor'
WHEN Name = 'Toolset' THEN 'Enterprise Toolset'
WHEN Name = 'UDT' THEN 'User Device Tracker'
WHEN Name = 'VoIP' THEN 'VoIP & Network Quality Manager'
WHEN Name = 'EOC' THEN 'Enterprise Operations Console'
END AS [Product Name]
WHEN IsEval = 'True' THEN CONCAT('Evaluation (', [DaysRemaining], ' days left)')
END AS [License Type]
ORDER BY CASE
WHEN Name = 'APM' THEN 9
WHEN Name = 'IPAM' THEN 5
WHEN Name = 'NCM' THEN 4
WHEN Name = 'NPM' THEN 2
WHEN Name = 'NTA' THEN 3
WHEN Name = 'Orion' THEN 0
WHEN Name = 'SEUM' THEN 11
WHEN Name = 'SRM' THEN 10
WHEN Name = 'Toolset' THEN 8
WHEN Name = 'UDT' THEN 6
WHEN Name = 'VoIP' THEN 7
WHEN Name = 'EOC' THEN 1