I have just deployed SCOM 2012R2. One of the selling points was that we would be able to edit company knowledge regarding issues. Unfortunately I just discovered that their is a requirement for MS Word to make it work. Not only that, but that it must be an older version of Word.

I really don't understand the logic behind this dependency.

Does anyone know how to make the 2012r2 OpsMgr console work with Word 2013 32bit? So far my searches have only yielded advise for SCOM 2012 and Word 2010. I have followed that advise, but it hasn't worked for Word 2013. Must still be missing something.

I'm going to guess the steps in this article will have to be followed to the T:

http://technet.microsoft.com/en-us/library/hh212900.aspx

then there was this, but it's not very informative and seems like it is dated:

http://blogs.technet.com/b/momteam/archive/2012/10/10/how-to-get-knowledge-editing-to-work-in-operations-manager-2012-with-office-2010.aspx

Sorry, I am looking specifically for a solution that allows SCOM 2012R2 to work with Word 2013. I have already attempted the instructions presented in the links you provided, but they appear to be specific to older version of SCOM and Word.

So, if anyone has gotten Word 2013 and SCOM 2012R2 to play nicely together, please let me know.

I don't think it does, that's the point.  So you will have to use an older version, until they fix it.

I was hoping someone had a work around. The articles you pointed to helped people start using the newer versions of word with SCOM 2012 before it was officially supported.

Hoping someone had figured out how to get 2013 working with it.

Sad thing is, we shouldn't have to figure anything out. This stuff should just work out of the box. How can someone make enterprise class software with such a ridiculous dependency. You should be able to enter information straight from the gui with no dependency on external tools.

I take it this is your first year working with SCOM.  Trust me, there are a lot of things that "should" work and be included out of the box, but unfortunately with the dev time cycles the teams are under, it would be impossible to complete v.next if they fixed/included everything that everyone wanted.  They have to work on the top ten asks, based on feedback from TAP, connect, etc.  I suspect many of those top 10 don't even make it into the final product.  Luckily there are a lot of motivated professionals who make third party solutions, extensions, etc for free (and sometimes profit) to fill the gap.  Many of those people are developers for the product, or former developers/pfe's/mvps etc.  They feel the pain, as much as you do, and when they can, they build unsupported solutions.  So while it is frustrating, and trust me, I have been working with this product since NetIQ owned it so I know what being frustrated feels like, you will find that the pro's outweigh the  con's.

Also I would encourage you to get familiar with XML and working in XML.  The company knowledge can be entered using word, but if you are comfortable with XML, you can hack the knowledge right in the management pack using XML, no need to launch word, and it's much faster.

Good luck Tim, and don't let this one issue turn you off from SCOM.

If you suggest editing the MP XML, do you have any examples on how to do that?

I don't, but if you export a sealed MP that has knowledge, then poke around and find how it's laid out.  I know you will find <malm> tags for the knowledge (at least that's what I remember).