As we all know, Operations Manager 2012 requires activation through entering the well-known powershell command “set-scomlicense”. This is documented in http://support.microsoft.com/kb/2699998
Even though the license isn’t entered, OM12 will let you work 180 days and at the end SDK service will not authorize the connections from ANY console including powershell – hey wait! how am I supposed to run the powershell command then??? – wait till the end of the post
Before diving into the details please check your license status using “Get-SCOMManagementGroup” and if your MG is not expired please set the license ASAP not to cause an operations outage.
The exception details can be found in Operations Manager Event Log , Event id 26319 (a generic authorization event);
Exception message: You have exceeded the evaluation period of this product. Please upgrade to the retail version to continue using the product. For information on purchasing the retail version of this product, go to http://go.microsoft.com/fwlink/?LinkID=74446. Full Exception: System.UnauthorizedAccessException: You have exceeded the evaluation period of this product. Please upgrade to the retail version to continue using the product. For information on purchasing the retail version of this product, go to http://go.microsoft.com/fwlink/?LinkID=74446
With Operations Manager 2012 Update Rollup 2 license can be entered after the period expired but if only you can connect to SDK right?? (Actually No)
If you Install UR2 and try to open SCOM PowerShell console (Operations Manager Shell) you will receive the same exception because the console will try to connect to SDK service. However the Set-SCOMLicense cmdlet does not require SDK connection and does its job on the Management Server side with UR2.
The easier solution (Solution 1) is based on bypassing the SDKconnection requirement by just loading the OM module but not connecting to SDK, the second option (Solution 2) is a Disaster Recovery of an MS (actually all MSs)
The high-level steps of Activating the expired OM12;
In case the above steps don’t work (I hope it won’t be required) the second option is to run a disaster recovery for the management servers for details http://technet.microsoft.com/en-us/library/hh531578.aspx.
The high-level steps of MS Recovery are as follows – This has to be applied on all Management Servers;
I hope this explains and helps.