I’m not sure why I have a hard time remembering which way the numeric representation goes – but here it is.
- Informational = 0
- Warning = 1
- Critical =2
- Low = 0
- Medium = 1
- High = 2
By default, when SCOM 2012 R2 is installed, it uses an eval license (hence the yellow warning when you install the management server). When you go to the “Administration” workspace there is a center page link to technet to “Upgrade SCOM to full version”.
Here’s the simple way to add that product key from powershell.
set-SCOMLicense -ProductId “insert product key here”
stop-service cshost; stop-service omsdk; stop-service healthservice
start-service cshost; start-service omsdk; start-service healthservice
Alternatively, you can reboot the management server.
After that, to verify the key is install you can take the following steps.
Launch the Operations Manager Console > Go to “Help” and click “About” > Next to the Version information it should now say Retail. *Note that it’s okay if the Product ID is blank.
I hope this makes your day at least a little bit easier.
So this is the issue — you’re going to subscribe to a report in SCOM and the only options are “Windows File Share” and “Null Delivery Provider”.
Well that’s a problem…we want these reports emailed. This error typically occurs when a SQL Migration is done, the reporting role is migrated, or on new installs. So go open up SQL Server Reporting Services Configuration Manager, and go to the “email settings” tab on the side. Notice there’s no data in there.
Configure this to include whatever you want your sender address to be, and your SMTP server, then click apply and you should get this.
Now, let go back and open up the SCOM Report Subscription again, and there we go!
I hope I’ve made your day, at least a little bit easier.
I did a few new SCOM 2012 installs recently and noticed that after pushing the agent to the DCs, they showed up grayed out in Ops Manager. Here’s a quick tip on how to fix that.
Logon to the DC(s), and with an administrative comand prompt run the HSLockdown tool, and add the local system account to the allowed group.
C:\Program Files\System Center Operations Manager\Agent:
*NOTE* In newer version, this is now stored in “C:\Program Files\Microsoft Monitoring Agent\Agent”
Run the command “HSLockdown /L” to show what accounts are being allowed or denied. In this case, my local system isn’t even populated.
Now run the HSLockdown tool again with the add switch to allow local system.
“HSLockdown /A “NT AUTHORITY\SYSTEM”
Restart the agent with “net stop heathservice && net start healthservice” and give it 5 minutes or so then it should be all green in your dashboard.
Hope this made your day at least a little easier!