21-09-2009 Update: Since the 18th of September Windows 2008 R2 is now officially supported. Not only as a monitored Operating System but also as a platform for any OpsMgr Server role. Want to know more? Check this posting of mine.
A few things on monitoring Windows 2008 R2 with OpsMgr (R2). Out of the field I do get questions about OpsMgr (R2) monitoring W2K08 R2 RTM.
- When will there be a MP for monitoring this version of Windows 2008 R2 RTM?
Normally a MP comes out 60+ to 90 days after the product hit RTM. On the OpsMgr forum there is a good thread about this topic to be found. Check here.
- I already have some W2K08 R2 RTM servers. I cannot push an Agent to it. Why?
By default W2K08 R2 RTM has it’s firewall enabled which blocks much (incoming) traffic. For an OpsMgr Agent push installation to be successful, many ports need to be opened and some services need to be running as well. Kevin Holman has blogged about it, found here.
- What and what not will be monitored when I install an Agent on a W2K08 R2 RTM Server?
Hmm, in order to give a more detailed answer to that (even though the outcome didn’t surprise me), I pushed an OpsMgr Agent to a W2K08 R2 RTM server in order to see what it shows in the OpsMgr Console. Here are my experiences: (The W2K08 R2 RTM server is the MS01 server):
The Agent has landed neatly and is working. However, the OS is not recognized. The most recent server OS MP is in place and properly configured.
When the Health Explorer is opened this is to be seen:
As you can see, only the Health service related components are discovered and thus being monitored. No Windows Server 2008 R2 RTM components are discovered/recognized and therefore not monitored.
- A while ago you blogged about the extended MPs. How about the extended MP for the server OS?
Here RFTM (Read The Friendly Manual) is at order. The document states on page 5:
So this MP will not make any difference since it adds extra value to the AD MP, not to the Server OS MP.
No comments:
Post a Comment