Compartilhar via

Enabling Scheduled Maintenance in SCOM 2016 UR1

  • Artigo

<!--[if lt IE 9]>

<![endif]-->

Comments

  • Anonymous
    October 22, 2016
    Thanks to share this !
  • Anonymous
    November 21, 2016
    Thanks for the info. Very helpful! Fixed it for me.
  • Anonymous
    April 18, 2017
    Thank you! Worked perfectly.
  • Anonymous
    April 18, 2017
    I am running SCOM 2016 UR2 and ran into this issue. Made the changes specified, rebooted management and SQL servers. Still get the 2nd of the two errors mentioned in this post.Any other ideas to resolve?Michael R.
  • Anonymous
    April 18, 2017
    The comment has been removed
    • Anonymous
      April 24, 2017
      The comment has been removed
  • Anonymous
    July 13, 2017
    Kevin to the rescue again!
    • Anonymous
      October 12, 2017
      The comment has been removed
  • Anonymous
    November 23, 2017
    Hi!Thanks for hint - will that work as well once we move database to AlwaysOn? Do we need to configure that role on msdb on both sides if we plan to use it like that?
    • Anonymous
      November 24, 2017
      Yep. Anything you have to do manually on one side, must be done on the other. (for any database that is non-replicated - like Master or MSDB)