Posted on

Enabling Agent Proxy for all System Center Operations Manager Agents

SCOM is likley to require the proxy to be enabled on a large number of agents, certainly it is the case with a lot of the management packs and it can often be easier to enable it on all agents and then turn it off on the agents which don’t require it.

In any case, enabling the SCOM agent proxy on all agents is a simple power-shell one liner:

Get-SCOMAgent | where {$_.ProxyingEnabled.Value -eq $False} | Enable-SCOMAgentProxy

You can always modify the filter as required to match your own needs.  For example, to only enable the proxy on Agents installed within the last 3 months:

Get-SCOMAgent | where {$_.InstallTime -gt ((Get-Date).AddMonths(-3))} | Enable-SCOMAgentProxy

Posted on

System Center Operations Manager 2012 SP1 Failes on Data warehouse step and setup log shows “Create File” error

When installing SCOM setup fails during the Data warehouse step and the setup log file contains an error similar to the following:  EXEC(@sql);: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file ‘E:\SystemCenterData.mdf’.

scom dw install bug 2
There is a bug in the Operations Manager SP1 installer which causes the file to be created in the wrong location.  During setup the location was configured to use “E:\SystemCenterData” for the Data path and “F:\SystemCenterLogs” for the logs however setup attempts to create the file as “E:\SystemCenterData.mdf”

One way to work around this issue is to amend the configured path for the data warehouse data and log files during setup.  Simply append the name of the database to the end of each path. (The main operations manager database and logs do not need this change.) for example using the locations E:\SystemCenterData\OperationsManagerDW for data and F:\SystemCenterData\OperationsManagerDW for logs will result in the files being created as E:\SystemCenterData\OperationsManagerDW.mdf and F:\SystemCenterData\OperationsManagerDW.ldf and setup can continue as expected.

SCOM DW install bug 3