VBScript and OpsMgr

I just ran into another bizzaro problem.  Here’s the low-down:

• Clean OpsMgr 07 SP1 environment
• Installed agents on two DCs, no problems encountered
• Installed Windows base MP, no problems encountered
• Installed AD MP, problems encountered.  The DCs never showed up in the DC State view and the following warning was recorded in OpsMgr and in the OpsMgr Event Log on both DCs.
  

  Event Type:    Warning
  Event Source:    Health Service Modules
  Event Category:    None
  Event ID:    21405
  Date:        6/10/2008
  Time:        3:18:55 PM
  User:        N/A
  Computer:    XXXX-DC-02
  Description:
  The process started at 3:18:55 PM failed to create System.Discovery.Data, no errors detected in the output.  The process exited with 1
  Command executed:    “C:\WINDOWS\System32\cscript.exe” “C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\2170\ADLocalDiscoveryDC.vbs” 0 {42180558-CF7E-7292-C345-CF1B3F5362DD} {24A4E1CD-9AB6-51C7-BB4C-B6A8E3BE69B9} xxxx-dc-02.YYY.ZZZ.COM XXXX-DC-02
  Working Directory:    C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\2170\

  One or more workflows were affected by this. 

  Workflow name: Microsoft.Windows.Server.2003.AD.DomainControllerRole.DCDiscovery
  Instance name: xxxx-dc-02.YYY.ZZZ.COM
  Instance ID: {24A4E1CD-9AB6-51C7-BB4C-B6A8E3BE69B9}
  Management group: XXXX-MG-01

My first step was of course searching the web: surprisingly almost nothing to be found.  Some references to oomads, the Operations Manager Helper Objects for AD.  So I checked out one of the DCs and they’re not there.  These are usually installed automatically when the MP rules are pushed to a system, but I gave it a shot.  After a manual install and re-installation of the MP, same issue.

Next, I logged into the DC to try to run the script manually: Can’t find script engine “VBScript” for script…  Now that’s something I’ve never seen before.  Back to my favorite search engine and lots of hits.  The solution appears simple: regsvr32 %systemroot%\system32\vbscript.dll.  This time, after re-installing the AD MP, everything works as expected.

So what’s unique about these DCs?  The only thing is that they are 64-bit Windows 2003.  I’ve installed lots of agents on 64-bit Windows 2003 before without issues, but this is the first time on 64-bit 2003 DCs.  Without further testing, I can’t verify if this is indeed the case, but it’s something to note. 

This was definitely not an OpsMgr problem, but I could see OpsMgr getting blamed for it — a classic example of shooting the messenger.  I’m sure that all OpsMgr administrators are used to this though.

Oh yeah, this was another “I am better than you [you stupid system]” moment.