Browsed by
Month: September 2016

Enable Proxy as a default setting in SCOM 2016

Enable Proxy as a default setting in SCOM 2016

As you may know, the default setting for new SCOM agents is that proxy is disabled. You can enable this agent by agent in the console, or even use script automation. But as more and more management packs require this capability to be enabled (e.g. Active Directory, SharePoint, Clustering, etc.), it makes really more sense to just enable this by default.

In order to achieve this, just connect to a SCOM Management Server and run these PowerShell commands.

If you want to check the actual configuration of your SCOM environment settings, you can also run these commands.

 

Install SCOM 2016 PowerShell Modules without SCOM Console

Install SCOM 2016 PowerShell Modules without SCOM Console

If you work with SCOM and custom management packs, you are most likely using SCOM PowerShell modules. By default, these modules are installed with the console using SCOM setup. But one of my customers needed to install these modules on a Gateway Server installed on a Windows Server 2016 Core running custom PowerShell rules.

In order to install SCOM 2016 PowerShell Modules on a Windows Server or even on a Windows Client without having to install SCOM console and its prerequisites, follow the following steps.

First, you need to copy the PowerShell Modules source folder from a computer with the SCOM console installed to your target computer.

Additionally, to avoid any future error with the import of the OperationsManager, you have to create two additional empty folders (Console and Server) as below.

Then, you have to copy these 3 DLLs from the same source computer to a temporary folder on your target computer:

  • Microsoft.EnterpriseManagement.Core.dll
  • Microsoft.EnterpriseManagement.OperationsManager.dll
  • Microsoft.EnterpriseManagement.Runtime.dll

Once you copied these DLLs, you need to register them to your local GAC (Global Assembly Cache). The easiest way to accomplish this is to open a PowerShell session as Administrator and run these commands (replacing your temporary folder path if needed).

Finally, you need to set the module path to the local environment variables (as always modify path accordingly to your environment). It will simplify the import of these modules in your future PowerShell sessions.

And it’s done… As you can see above you can now import Operations Manager PowerShell modules easily.

Note
You will obviously need to open a Management Group Connection to one of your Management Server with proper credentials, in order to use cmdlets.
Note
You can delete DLLs in temporary folder on your target computer once you finished the import to your GAC.