Month: June 2017

Monitoring Domain Controllers in SCOM 2016 – Event ID 1102

SCOM & Other Geeky Stuff

So  you deploy a SCOM2016 agent to a Windows 2016 Domain Controller, only problem is, after the agent push, discovery doesn’t work. Well, the agent isn’t corrupted… Ports are open… SCOM agent is being deployed using the System Local account…  etc. etc. So, now what?

Taking a look at the Windows 2016 domain controller and its event log, the domain controller OpsMgr log is getting bombarded with Event IDs 1102….

After some investigation, seems to be this has been an issue in SCOM 2012 (and 2012R2) as well. Well, here’s the fix…

Taking a look at the HSLockdown, the Local System account is being denied access..  Browse to the following folder “%windir%Program FilesMicrosoft Monitoring AgentAgent “and run the following command (elevated access…), “HSLockdown.exe /L

Now that we can see the Local System account is being denied access, let’s give it access… Running the…

View original post 30 more words

Advertisements

SCOM Servers not “Remotely Manageable”?

SCOM & Other Geeky Stuff

Odds are you probably will have some machines where you can’t deploy the SCOM agent via SCOM console, or PowerShell, or some automated way, and you must install and configure the agent manually. Days/weeks/years go by and now you need to decommission that troublesome, manually installed agents Primary Managed Server. You go to the console and right click, and notice you cannot change the machines primary management server.  Well that is because any manually installed agents SCOM/SQL disables this feature. Well, there is a workaround!

Launch SQL and run the following query against the OperationsManager database to get a list of all manually installed servers:

select bme.DisplayName from MT_HealthService mths
INNER JOIN BaseManagedEntity bme on bme.BaseManagedEntityId = mths.BaseManagedEntityId
where IsManuallyInstalled = 1

Now that you have determined which servers were manually installed, to re-enable the remotely manageable feature, run the following SQL query (against the OpsMgr DB).

UPDATE MT_HealthService
SET IsManuallyInstalled=0

View original post 33 more words

Enabling SCOM 2012R2 Agent Proxy

SCOM & Other Geeky Stuff

The other day, I’m asked, “what the heck are these SCOM agent proxy alerts!?” I’m sure you fellow SCOM admins have seen these alerts before:

1

You could go to the computer that SCOM is complaining about and manually enable the agent proxy via Administration > Managed Computers, and modifying its properties, see below:

2

Or…… you could make your life easier, and do this…

The fix is easy, and the explanation are both below:

To resolve the “Agent proxy not enabled” alert for all machines in your current environment, run the following PowerShell code in the SCOM PowerShell Console:

get-SCOMagent | where {$_.ProxyingEnabled -match "False"} | Enable-SCOMAgentProxy

3

To prevent this alert in the future, run the following below:

add-pssnapin "Microsoft.EnterpriseManagement.OperationsManager.Client";
new-managementGroupConnection -ConnectionString:yourSCOMserverFQDNhere;
set-location "OperationsManagerMonitoring::";
Set-DefaultSetting -Name HealthServiceProxyingEnabled -Value True

4

View original post 24 more words

Step-by-Step – SCOM 2016 Update Rollup 2 (UR2) Install Procedure

SCOM & Other Geeky Stuff

My personal notes for installing SCOM2016Update Rollup 2, Step-by-Step. UR2 (Update Rollup) has a lot improvements, please see below the many updates being provided in this UR. Two fixes I am seeing that makes me happy, is having the alerts view fixed… Previously alerts within the Alerts view would still appear even after the alert was closed. Also, the Get-SCOMGroup cmdlet consistently failed when there was a great number of groups within an environment.

It is highly recommended to upgrade your lab/Dev environments first before upgrading your Production environment(s). The step by step procedures below are the steps I took and in no way shape or form do I accept responsibility for any data loss, and/or issues within your environment. It is advised to always take a backup of your SQL databases and/or snapshots of your SCOM environment(s). Please take these notes as suggestions. Always refer to…

View original post 900 more words

Step-by-Step – SCOM 2012 R2 Update Rollup 11 (UR11) Install Procedure

SCOM & Other Geeky Stuff

My personal notes,  SCOM 2012 R2 Update Rollup 11 (UR11) has a lot of networking monitoring fixes, Linux/UNIX support and security fixes, along with more OMS integration. What is OMS, please go HERE. It is highly recommended to upgrade your lab/Dev environments first before upgrading your Production environment(s). The step by step procedures below are the steps I took and in no way shape or form do I accept responsibility for any data loss, and/or issues within your environment. It is advised to always take a backup of your SQL databases and/or snapshots of your SCOM environment(s). Please take these notes as suggestions. Always refer to Microsoft’s KB (posted above) for full documentation steps.

Here are the key updates for UR11 (source Microsoft):

Issues that are fixed in this update rollup can be found here, https://support.microsoft.com/en-us/kb/3183990

Once you are ready to begin your upgrade, it is recommend you…

View original post 325 more words

Step-by-Step – SCOM 2016 Update Rollup 1 (UR1) Install Procedure

SCOM & Other Geeky Stuff

Well, that was fast… System Center/Microsoft Operations Manager (MOM) team just released Update Rollup 1 for SCOM 2016, only weeks after the System Center 2016 suite and Windows Server 2016 were released.

The MOM team did not indicate what exactly the fixes were in this Update Rollup, so your guess is good as mine. However, I believe one of the issues that may have been resolved was the SCOM 2012R2/SCOM 2016 Console crash due to the October Cumulative Update, October 2016 Windows Server Cumulative Update(s).

Below step by step procedures below are the steps I took and in no way shape or form do I accept responsibility for any data loss, and/or issues within your environment. It is advised to always take a backup of your SQL databases and/or snapshots of your SCOM environment(s). Please take these notes as suggestions. Always refer to Microsoft’s KB (posted below) for full documentation steps.

View original post 472 more words

Step-by-Step – Installing System Center Operations Manager (SCOM) 2016 on Windows Server 2016 with SQL 2016

SCOM & Other Geeky Stuff

This post I will be installing System Center Operations Manager 2016 (SCOM) RTM, Build Number 7.2.11719.0.

Here is some of the background information. As this post will concentrate on the installation of SCOM 2016, I am going to omit the setup and configuration of the Domain Controller, Windows Server 2016 for both SCOM Management Server and SQL Server (Please note, I am using SQL Server 2016, both servers on Windows 2016).

If you need help setting up SQL 2016 for SCOM 2016, please visit HERE.

Environment:  Virtual; ESX 6.0 Hypervisor

SCOM Management Server:

  • Windows Server 2016
  • 4 vCPU (2.00GHz)
  • 12 GB memory
  • 100GB Diskspace
  • 1GB vNIC

SQL Server:

  • Windows Server 2016
  • SQL Server 2016
  • 4 vCPU (2.00GHz)
  • 24 GB memory
  • 300GB Diskspace
  • 1GB vNIC

Service Accounts and Local Administrator:

DomainAccount Description Local Admin on…
domainSCOM_AA SCOM Action Account SCOM & SQL
domainSCOM_DA SCOM Data Access/SDK Account SCOM &…

View original post 335 more words

Installing System Center Operations Manager (SCOM) 2016 Step by Step (Technical Preview 5)

SCOM & Other Geeky Stuff

IF YOU ARE LOOKING FOR INSTALLING SCOM 2016 [RTM] ON WINDOWS SERVER 2016 WITH SQL SERVER 2016, GO HERE.


This post I will be installing System Center Operations Manager 2016 (SCOM) –  Technical Preview 5 (TP5). Technical Preview for both System Center 2016 and Windows Server 2016 was recently released, April 27th.

Here is some of the background information. As this post will concentrate on the installation of SCOM 2016 TP5, I am going to omit the setup and configuration of the Domain Controller, Windows Server 2012R2 for both SCOM Management Server and SQL Server (Please note, I am using SQL Server 2014 SP1, both servers on Windows 2012R2).

Environment:  Virtual; ESX 5.5 Hypervisor

SCOM Management Server:

  • Windows Server 2012 R2 — SCOM2016TP5
  • 4 vCPU (2.00GHz)
  • 12 GB memory
  • 100GB Diskspace
  • 1GB vNIC

SQL Server:

  • Windows Server 2012 R2 — SCOMSQLTP5
  • SQL Server 2014 SP1
  • 4 vCPU (2.00GHz)

View original post 311 more words

Step-by-Step – Upgrading to SCOM 2016 from SCOM 2012 R2

SCOM & Other Geeky Stuff

So you’ve decided to take the jump and upgrade to System Center Operations Manager 2016? Assuming you are running a SCOM 2012R2 (UR11) environment, this post will be exactly what you need to have a successful SCOM 2012 R2 to SCOM 2016 upgrade. **Although the recommended path is to upgrade from UR9**

In my environment, here is the quick breakdown:

  • SCOM 2012 R2 environment has two Management Servers.
    • Handful of clients (Windows 2012R2) being monitored.
  • Both Management Servers live on a Windows 2012 R2 operating system.
    • Both Management Servers are running with UR 11 (Update Rollup) **Microsoft recommends upgrading the environment at latest version number minus one (latest – 1), so in this case, UR9 (UR10 was never issued for SCOM 2012R2)**.
  • The SQL environment is a SQL Server 2014 SP2 also running on Windows 2012 R2.
    • The Operations and Data Warehouse live on dedicated SQL instances, however reside on the…

View original post 572 more words