Adding my own 2¢ to the PowerShell & Technology Communities
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.
Over the years, I’ve worked for various organizations and most have had a fairly routine process for applying patches. The best of these uses a defined Change Management window during which the patches were deployed and the computers rebooted (if necessary). This post is not a recommendation on when to do this or how to do … Read more
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.
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).
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.
Installed Orion Modules
SELECT CASE
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'
ELSE Name
END AS [Product Name]
, Version
, CASE
WHEN IsEval = 'True' THEN CONCAT('Evaluation (', [DaysRemaining], ' days left)')
ELSE 'Licensed'
END AS [License Type]
FROM Orion.InstalledModule
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
ELSE 99
END
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.