Scott

My feedback

  1. 44 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  General Operations Manager Feedback » General  ·  Flag idea as inappropriate…  ·  Admin →
    Scott commented  · 

    Here's the rub - I can't suggest to the company we move to SCOM 2019 and have a quarter of my servers hoping for the best when it comes to monitoring right now. I can rig ways to make it work (and have in a dev SCOM 2019 environment for a worst case scenario test), but if anything goes awry there's nothing I can do.

    I can't speak to what the others believe, but regardless of how much time is left in the support cycle, right now 2008 R2 IS a supported OS, even if that is just for extended support. That being the case, it would make sense for SCOM 2019 to support that operating system, at least in the present iteration. The 2019 agent runs on 2008 R2 - it does not seem like it would be that hard to support that OS in SCOM 2019, since I've been able to do it in a throw together test environment. I understand not officially supporting it past next January and in future releases of SCOM, but we really are dead in the water with this until 2008 R2 is gone out of our environment.

    When I'm already having to defend this product internally, being in this situation helps very little. The reality is that, because of how Microsoft has moved forward on this, I have the option of running SCOM unsupported (since I've got 1807 at the moment), or upgrading SCOM and having however many of my servers are left at 2008 R2 being unsupported come January. That number is questionable, but the theory is the same. If the 2019 RTM supported it, at least I'd have some leeway as we finish transitioning.

    By the way, Kevin - you've got a great blog. It's been a huge help to me with this product since I've taken it over at my company.

    Scott supported this idea  · 
  2. 0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General Operations Manager Feedback » General  ·  Flag idea as inappropriate…  ·  Admin →
    Scott shared this idea  · 
  3. 29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Scott supported this idea  · 
  4. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General Operations Manager Feedback » General  ·  Flag idea as inappropriate…  ·  Admin →
  5. 20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. 28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Scott supported this idea  · 
  8. 87 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Scott supported this idea  · 
  9. 30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General Operations Manager Feedback » General  ·  Flag idea as inappropriate…  ·  Admin →
    Scott commented  · 

    I had just discussed this with a Microsoft rep we had in for an Exchange deal. This would be extremely useful - we have backups running on machines and to have an ability to set a timeframe where systems would have higher than expected activity would be excellent.

    Scott supported this idea  · 

Feedback and Knowledge Base