Wednesday 15 June 2016

Configuring new DSC Pull server - error Nº1 - Error executing Start-DSCConfiguration

Hi all!

I'm starting another series of posts about my experiences with PowerShell DSC!!

As it can not be otherwise, I'm going to start with an error...so here we go!


the error:

You just configured a your new DSC Pull server, using xWebService resource, and created your first MOF file that you are going to use to start DSC Pull server configuration, and run:

Start-DscConfiguration -Path c:\\PullServer -Wait -Verbose

After some information messages...
The expression after '&' in a pipeline element produced an object that was not valid. It must result in a command name, a script block, or a CommandInfo object.
    + CategoryInfo          : InvalidOperation: (:) [], CimException
    + FullyQualifiedErrorId : BadExpression
    + PSComputerName        :

the solution:

This error appears because of known issue #143, reported in GitHub.

Although the version is in dev(at the moment I write this post), you can go here, download the full zip and copy files:


xPSDesiredStateConfiguration-dev.zip\xPSDesiredStateConfiguration-dev\DSCResources\MSFT_xDSCWebService\...
             MSFT_xDSCWebService.psm1
             PSWSIISEndpoint.psm1 

Then you only need to overwrite the old ones (remember to backup) at:
C:\Program Files\WindowsPowerShell\Modules\xPSDesiredStateConfiguration\3.10.0.0\DSCResources\MSFT_xDSCWebService
That's all!

Wednesday 18 May 2016

Error enabling Operations Manager Audit Collection Service with SCOM 2016 TP4

Hi all,

If you want to install Operations Manager Audit Collection Service and the Audit collection services Collector Setup Wizard finishes with the following error:
start adtserver service: failure 0x00002098
...should it mean that you have some problems with the SPNs(Service Principal Name). If you check the Event Viewer,  you will find the following error registered:
EventID: 7023
Source: Service Control Manager
Message: The Operations Manager Audit Collection Service service terminated with the following error: Insufficient access rights to perform the operation.
Then the solution it's easy, you need to register the required SPN in order the service can start correctly:

Management Server:

  • AdtServer/FQDN DOMAIN\account
  • AdtServer/NetBios DOMAIN\account
  • MSOMHSvc/FQDN DOMAIN\account
  • MSOMHSvc/NetBios DOMAIN\account
Database Server:
  • MSSQLSvc/FQDN:1433 DOMAIN\account
  • MSSQLSvc/FQDN DOMAIN\account
  • MSSQLSvc/NetBios DOMAIN\account
Ok...let's go to see a real case...

Suppose you has a management server named "ScomServer", database server "RandomDBServer" and a domain named "TheXdom.com". Then the "Operations Manager Audit Collection Service" is running under "Network Service" account and the "SQL Server" service running under "TheXdom\sqlEngineAcc". Then you need to run in a elevated command prompt:

  1. setspn -S AdtServer/ScomServer.TheXdom.com TheXdom\ScomServer$
  2. setspn -S AdtServer/ScomServer TheXdom\ScomServer$
  3. setspn -S MSOMHSvc/ScomServer.TheXdom.com TheXdom\ScomServer$
  4. setspn -S MSOMHSvc/ScomServer TheXdom\ScomServer$
  5. setspn -S MSSQLSvc/RandomDBServer.TheXdom.com TheXdom\sqlEngineAcc
  6. setspn -S MSSQLSvc/RandomDBServer TheXdom\sqlEngineAcc
Don't worry if your environment still have one of these SPN, the -S parameter checks it for you!


If these steps cannot solve your problem, perhaps you need to check this Microsoft KB

Hope it helps!