24 votes5 comments · General Operations Manager Feedback » Other Management Packs · Flag idea as inappropriate… · Admin →
Same goes for Windows Server 2019 soon I guess?
But 2016 has been out for a few years now.
Any update to this, at all?
It's a very simple fix.
219 votes20 comments · General Operations Manager Feedback » Administration · Flag idea as inappropriate… · Admin →
Thanks for your suggestion and up-votes. This request is under review and we will keep this thread updated on developments about the integration.
Meanwhile, I have a question for everyone that requested this feature. Hypothetically speaking, “If” this feature will be available in SCOM console ONLY if you have the OMS addon, would you be willing to/able to use this feature? Do any of you have a limitation of not being able to use OMS along with your SCOM environment?
This is even more important to get On-premise now, as we start seeing the actual pricing and licensing confusion regarding OMS features.
I have at least three customers where using OMS is prohibited (by national law, because of the nature of those organizations, they cannot put data outside of the country border and cannot be dependent on a third party).
Now, I know this feature has been somewhat implemented in OMS already. I found this feedback just now.
Port selection isn't really an issue, and separating monitoring traffic from "other" https (http is a no-go) usage is a good thing in my book. It's often more accepted to open 5723 from DMZ into the management domain than it is to open HTTPS. Even if you scope it to the specific management servers.
That said, the certification management is a bit weird in SCOM and should be looked into i think. It's not that hard to manage once you realize that it's just a regular client/server certificate (lot's of organizations routinely deploy these to their servers as part of their regular PKI strategy).
I also agree that installing an OMGW should be as simple as manually installing an agent. Provided the encryption is in place (the certs), it should simply plop into "Pending Management" for approval. No pre-approval from cmdline tolls you have to manually copy from an arbitrary place on the installation media, with undocumented requirements on database access and obscure (but lovely) settings like /SiteName. (Don't you dare remove /SiteName, Microsoft!)
While you can put object (like IIS) in maintenance mode and not only the entire server, I agree. Being able to pause a monitor between two points in time would be helpful. I'm out of votes (10 is a tad low on a product like SCOM) but yes. Absolutely agree.
Best scenario would be to be able to simply install the OMGW, then approve it in the console under Pending Management.
The, for clarity's sake, you must clearly mark what periods are edited. Otherwise the reports holds no value at all, especially in a SLA scenario. From the customer's perspective, we might just as well have painted it all green.
I think, perhaps, the question is about being able to clone a project (with file structure) and in an easy way refactor it.
The importer pretty much only adds a few references and dumps the mp into a single large fragment. I often prefer to simply create a new project, add the references manuall and then copy-past from the original XML into more logical fragments.
4 votes2 comments · General Operations Manager Feedback » Administration · Flag idea as inappropriate… · Admin →
Manual Reset is, and has always been, the bane of proper SLA reporting. Since the introduction of it in SCOM 2007 my job as a SCOM Consultant has been to create "adjustment MPs" to all these monitors. They are confusing to the customers at best, causing financial loss (SLAs tied to fees) at worst.
Just, remove them. Convert them to a timer reset monitor or a rule instead.
311 votesunder review · 10 comments · General Operations Manager Feedback » Authoring · Flag idea as inappropriate… · Admin →