SCOM Adapter Configuration for vCOPs

I wanted to test the SCOM adapter in vCOPs to see what data I could get and see how it could be used.  Unfortunately, the VMware video demonstrating it's installation did not work for me without some tweaks.

vCOPs 5.7.1 (vApp)
SCOM Adapter Build 1036195

Installing the Adapter:

  1. Log into your vCOPs admin page (Usually https://vcopsServer/admin)
  2. Select the Update tab and upload the 'pak' file

  3. Accept the EULA, wait.
    • Pretty much the same as updating vCOPs @ this point.
  4. Once completed, you need to log into the custom UI (https://vcopServer/custom) as an admin.
    • If you setup LDAP and made your account an admin, you're good.  Otherwise, you can login as the same admin account as the admin page.
  5. Once in the custom UI screen, hover over admin and select 'support'

  6. Select the 'Info' tab, click the gear to start the 'describe' process.

  7. Once the process is completed you should see the SCOM adapter available in the adapters info table.

  8. Congrats, the adapter is now installed.  Next we need to configure it to pull data.
    • If it's not there, you may need to restart vCOPs services.
SCOM Adapter PreReqs:
  1. SQL Account w/ dataread role access to the SCOM database.
    1. Windows account "MAY" work, but there may be a syntax problem.  I still need to test this more.

Configure Adapter Instance:
  1. At this point, watching the video would probably be easier than me typing it out w/ screenshots.
  2. If it works, GREAT!  If not, follow these next steps.
  3. SSH into the UI VM.
  4. Use VI to edit the file.
    1. vi $ALIVE_BASE/user/plugins/inbound/msscom_adapter3/conf/
    2. Click here if you need info on how to use VI.
  5. The line you need to change is jdbcDriver=jtds to jdbcDriver=sqljdbc
  6. Save your changes and now SSH into the Analytics VM and start @ step 4.
  7. Once done, try configuring the adapter again.  Hopefully this solves your problem.  It certainly solved mine.


Anonymous said…
Have you had any luck testing Windows Authentication with your SCOM adapter. When using the vAPP for vCOP there seems to still be an issue with Windows Authentication. VMware's recommendation was to put the SCOM adapter on a Windows box or just Authenticate with SQL
Zsoldier said…
Haven't revisited this. It may be a combination of driver and username formatting.
Anonymous said…
Hi, i tried to install vcops with SCOM, but i have the next error, " Failed to collect data from SCOM: invalid object name "managedEntityGenericView" "i hope that you can help me.

Popular posts from this blog

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Azure VMware Solution: NSX-T Active/Active T0 Edges...but