Related Articles
SCOM – Failed SCOM Agent Installation Error Code 80004005
Posted on Author stefanroth
Today I bumped into an issue, while deploying a SCOM 2012 SP1 agent to a Windows 2003 server. The task failed with the following error… In English it says that “The MOM Server could not execute WMI Query “Select * from Win32_Environment where NAME=’PROCESSOR_ARCHITECTURE’” on computer server.domain.com.” Error Code: 80004005. The server I wanted to […]
SCOM 2012 R2 – PowerShell To Determine Agent Required Disk Space
Posted on Author stefanroth
Do you use any of the System Center products which use an agent? SCOM is one of these products which needs to have an agent installed on the monitored systems. But do you know how much space an agent really uses? Why is this important? Well, let’s assume you have to monitor an older operating […]
SCOM 2016 – Upgrade Notes from the Field
Posted on Author stefanroth
Upgrading from SCOM 2012 R2 to SCOM 2016 is theoretically no such big deal. BUT sometimes you could face issues at the customer’s infrastructure, which force you to take some extra hurdle. This post should give you a high level overview of different migration scenarios and additionally some pitfalls you could meet upgrading to SCOM […]