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.
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
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.
This is part 1 of a multi-part post on updates that I’ve made to How I Build an Orion Server. Primarily, it will be three parts. If you need this for a Hyper-V environment, I’ve got that script as well.
- Building my Orion Servers in VMware
- Configuring the disks on the VM after OS install
- Configuring the VM with the new disks
This is it. The endgame. Here I’ll give you the final steps in configuring my server. We started with creating the virtual machine then moved to configuring the disks. We’re at the end – where’s it’s time to do the final configurations.
In summary, we’re going to do several steps here. They pretty much follows my other guide step-by-step, so I’ll be brief in covering them here.
- Variable Declaration
- Installing Windows Features
- Enabling Disk Performance Metrics
- Installing some Utilities
- Copying the IIS Folders to a new Location
- Enable Deduplication (optional)
- Removing unnecessary IIS Websites and Application Pools
- Tweaking the IIS Settings
- Tweaking the ASP.NET Settings
- Creating a location for the TFTP and SFTP Roots (for NCM)
- Configuring Folder Redirection
- Pre-installing ODBC Drivers (for SAM Templates)