Partager via

OpsMgr 2016 – QuickStart Deployment Guide

  • Article

<!--[if lt IE 9]>

<![endif]-->

Comments

  • Anonymous
    October 22, 2016
    Thanks for sharing this !
  • Anonymous
    October 29, 2016
    Trying to install second management server I am getting the following error:(SQL is on AlwaysOn 2014) SCOM\Setup\AMD64\Server\OMServer.msi returned error 1603 :ProcessInstalls: Install Item Management Server failed to install. We did not launch the post process delegate.
  • Anonymous
    November 03, 2016
    Does the 2016 operations console support connecting to a 2012 R2 UR11 management group?
  • Anonymous
    November 03, 2016
    I don't know if Microsoft officially "supports" that - but it certainly works.
  • Anonymous
    November 10, 2016
    Hi Kevin, What account must have the privileges for to install agents, the Action Account?Regards
    • Anonymous
      November 10, 2016
      I do not recommend making the action account have rights on all your agents.Generally speaking - you type in YOUR credential that has rights to the agent managed machines that you want to deploy agents to. The only reason to grant this to the management server action account, would be if you DON'T have rights - and you restrict individuals, but grant rights to shared service accounts (which from a security and audit perspective is archaic)
  • Anonymous
    December 04, 2016
    Can we install Ops DB & DWH & Reporting on same SQL 2014 server with Always ON all under same named instance or there are any challenges?
    • Anonymous
      December 04, 2016
      @Jay - OpsDB and DWDB, and reporting DB's are all fine in the same AlwaysOn availability group (assuming you fit the scale model per the sizer to be 500 agents or less)Any more than 500 agents, we recommend dedicated servers and instances for each database (OpsDB and DW).As to where to install the SRS instance, I recommend that to be on a dedicated server and not part of the always on SQL DB engine servers, because it is not redundant.... it is a stand alone web instance of SSRS.
      • Anonymous
        December 09, 2016
        Hi Kevin,Do you have any advice you can give as to what SQL Licenses are covered under Microsoft statement that "SQL Server runtime" Licenses are included? I've read all available documentation, and the only detailed statement I've read is that "SQL Server Standard" runtime is eligible. I've not read anything about the number of licenses covered (i.e. are multiple instances on different servers, but all SCOM related, supported?) nor do MS state whether license mobility rights are included if deploying to a host-floating VM? I've attempted to get this information indirectly from MS in the past, but information has not been forthcoming. Ideally, I'd like to form a 2 host SQL cluster for the DB and DW and a separate host for the Reporting instance as per our existing model. Now that SQL standard edition supports clustering this could save some serious cash if its all included under the SQL runtime entitlement.Regards,
        • Anonymous
          December 09, 2016
          I am not a licensing expert - so always check with your Microsoft rep/TAM. However, historically speaking - SQL Standard Edition licensing is included in your System Center licensing. This means as long as you ONLY use SQL standard, for System Center deployments, and that SQL instance will ONLY support system center databases (and DB's that support SC deployments such as the reportserver DB's, then this is included. This means you could have a two node failover cluster housing a single instance, or two instances of SQL standard edition, and as long as you only use it for System Center product back ends, that would be included in your system center licensing.Additionally, there is no limit to the number of SQL database instances or SQL reporting instances to support system center. If you deployed one cluster for SCOM, and one for SCCM, one for SCSM, one for SCDPM, and one for SCORCH, etc.... Again - the limitation is they must be Standard edition of SQL, and ONLY support System Center deployments.
  • Anonymous
    December 09, 2016
    Hi Kevin, thanks for the guide.Does SCOM 2016 run any AD scripts during installation? I'm planning for a temporary test environment and I don't want to make any permanent changes to the AD.
    • Anonymous
      December 09, 2016
      SCOM does not make any changes to AD, and the user account installing SCOM should not need any rights to the domain. Only the local administrator and SQL rights as defined by the deployment guide.
  • Anonymous
    January 06, 2017
    Hello Kevin,Thank you for this excellent post as usual you are terrific!!!The installation on new server is working fine but for an upgrade it seems there are hurdles ...I am trying to upgrade SQL 2012 to SQL 2016 (Both enterprise Edition) and I am getting two errors during the setup:SQL Enterprise to SQL Standard Failed Rule "No Custonm Security Extensions" The Report Server has some custom security extensions configured Rule "No Custom Authentication Extensions" failed The Report Server has some custom authentication extensions configuredThe only steps I found so far are:http://thoughtsonopsmgr.blogspot.in/2013/01/om12-sp1-upgrading-sql-server-2008-sp1.htmlThis seems heavy for an upgrade!!! and also risky...Any other idea?Thanks,Dom
  • Anonymous
    January 12, 2017
    Hi Kevin,thank you for your very good article!I have some questions about planning of SCOM server roles.We will deploy SCOM 2016 and have 5 server in the 1.Active Directory domain, and 2 servers in 2.Active Direcrory domain. All server OS (Windows Server 2012 R2) are deployed on the VMWARE virtual machines.We planned following server roles and want to know your opinion / feedback about these role distribution:In the 1.Active Directory domain--------------------------------------Server1: Management Server, Operations ConsoleServer 2: Management Server, Operations Console, Web ConsoleServer3: Management Server, Operations Console, Web Console, SQL Server Reporting Services & DBServer4: SQL Server Operations Manager Instance & DBServer5: SQL Server Datawarehouse Instance & DBIn the 2.Active Directory domain (untrusted)---------------------------------------Server6: Gateway Server, Operations Console, Web ConsoleServer7: Gateway Server, Operations Console, Web ConsoleWe want to deploy two Gateway Servers in the 2.Active Directory domain because of availability. Is it perhaps better, these both server (Server6 and Server7) also deploying as Management Server in this untrusted domain?Can I deploy all Web Console in the 1.Active Directory domain with only one FQDN (load balancing? availability?), and in the 2.Active directory domain with another one FQDN? Is there any references/documentation about Web Console deployment?I will be very glad to hear from you.Best RegardsBirdal
    • Anonymous
      January 13, 2017
      @Birdal - I am afraid these conversations are far too complex to be handled over this forum. Please send me an email via the contact page with any questions like this.But basic holes I'd point out:1. We dont support management servers in untrusted domains. So that's not an option. Management servers should be in the same domain and in the same datacenter, on the same network preferred.2. You should not install the Console or Web Console on your gateway servers.
      • Anonymous
        January 16, 2017
        Hi Kevin,thank you for your feedback.Can you give me please the link for the "contact page"? I could not see this link in this page.Best RegardsBirdal
  • Anonymous
    January 20, 2017
    Hi KevinI am upgrading from SCOM 2012 Sp1 to SCOM 2016.and since there is no upgrade path from 2012 Sp1 to 2016.I want to go for Alongside Migration.I have new servers for SCOM 2016, I will install a new copy of SCOM 2016 on the new servers.but now the trick is how to move the current data from 2012 Sp1 on the old servers to 2016 on the new servers.I know I can't backup the operations manager DB from 2012 Sp1 and restore it in 2016 because the DB structure is different.So is there is any Scenario I can use to move the Data From SCOM 2012 Sp1 to SCOM 2016 without a need for going to the upgrade operation ?
  • Anonymous
    January 25, 2017
    Hello Kevin, I'm planning a migration from SCOM 2012 SP1 to SCOM 2016 and I thought about side by side migration. Can I deploy SCOM 2016 agent to my SCOM 2012 SP1 monitored servers so that their SCOM 2012 SP1 agent is upgraded to SCOM 2016 and multihomed between the SCOM 2012 SP1 management group and the SCOM 2016 management group ?Regards, P.
    • Anonymous
      January 27, 2017
      We did not test nor support a SCOM 2016 agent reporting to a SCOM 2012 SP1 management group, that I am aware of. We did test and support a SCOM 2016 agent reporting to a SCOM 2012R2 management group. It will likely work just fine, however.... but you'd need to verify that.
  • Anonymous
    February 24, 2017
    If I just have a dedicated SQL server and another server for the rest of the SCOM functions does it mean that I have to install the web console on the SQL server too based on the below? I also see an error in SCOM stating that the reporting console is unavailable, but I can browse to the directories. "The Reporting Console is unavailable. This was detected by pinging the reporting URL from the reporting server. By default, this monitor pings the reporting URL every 15 minutes""Although SQL Server Reporting Services is installed on the stand-alone server, Operations Manager reports are not accessed on this server; instead, they are accessed in the Reporting work-space in the Operations console. If you want to access published reports through the web console, you must install the Operations Manager web console on the same computer as Operations Manager Reporting server."
  • Anonymous
    March 02, 2017
    After upgrading from SCOM2012R2 to SCOM2016, how soon must I upgrade the agents? Will SCOM2016 still monitor 2012r2 agents?
  • Anonymous
    March 03, 2017
    This is a great little guide. However and perhaps I missed this you do not seem to go over the SPN registrations needed for action accounts? I found another article that you posted on your bloghttps://blogs.technet.microsoft.com/kevinholman/2011/08/08/opsmgr-2012-what-should-the-spns-look-like/This article helped clear up some issues I had with my deployment. I now have some event ID 7016's on some of my agents installed on RODC's in child domains, strangely its not happening on all of them. It has been mentioned that for cross domain boundaries I need to setspn for these runas accounts as well?
  • Anonymous
    April 12, 2017
    I just finished a new deployment and when I try to run some reports, I am getting the following error: System.InvalidOperationException: Some parameters or credentials have not been specified at Microsoft.Reporting.WinForms.ServerReport.GetDocumentMap(String rootLabel) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.OnRenderingCompleteJob(Object sender, ConsoleJobEventArgs args)What is confusing me is that the first time I ran the report it worked fine, but after the second run it is now always giving this error.Any suggestions?
  • Anonymous
    April 18, 2017
    I am receiving this error during configuring the operational database part of setup:The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported Configurations document for further information.We are running SQL Server 2012 11.3.6020.0
    • Anonymous
      April 18, 2017
      What OS are the SQL servers on? When I hear this - it is usually Server 2012 RTM or earlier, which arent supported.
      • Anonymous
        April 19, 2017
        Hi Kevin, Our SQL Servers run off Windows Server 2012 R2.For the record I am performing a fresh install (which I've now read may not be supported if not doing an in-place upgrade).
  • Anonymous
    April 25, 2017
    The comment has been removed
  • Anonymous
    May 08, 2017
    Hey Kevin,Does SCOM 2016 Support SQL Basic availability groups which is part of SQL 2016 Standard? If yes does it support having it configured in Synchronous mode and have the two DB's at different locations? The desire is to auto failover to the alternate location. My first thought and concern is the additional latency of Synchronous mode as well as the single point of failure of between sites. I want to find out if it is even supported before I way the options.Thank you,Brett
    • Anonymous
      May 08, 2017
    • the single point of failure the two link between the two sites creates. * weigh my options. :)
  • Anonymous
    May 29, 2017
    Hi Kevin,Please check this topic.https://social.msdn.microsoft.com/Forums/sqlserver/en-US/704a6ebf-d215-4965-b68a-45fcf421ff8a/to-much-space-unused-aproximtly-50?forum=sqlgetstarted Can you replicate this also?It happend on 3 Enviroments!
  • Anonymous
    July 19, 2017
    Hi Kevin, We are running a SCOM 2016 UR3 / SQL 2016 Always On solution. When we fail over to node B there seems to be a permissions issue oarising. The current security model is mixed mode on SQL. We have run into the issue Travis Wright has documented with the Azman auth errors and SQL config changing back in 2011. Have you or anyone you know possible run into this issue and found a resolution?
  • Anonymous
    October 11, 2017
    The comment has been removed
  • Anonymous
    October 13, 2017
    Hi Kevin,got a question related to SCOM setup : is it possible - and supported - to prestage SCOM databases and if so, how to do it ? SCOM 2016 setup still does not recognize mount points and I'm on a configuration where I can't resize up the volumes hosting the mount points dedicated to SQL.Regards, P.
  • Anonymous
    November 14, 2017
    Hello Kevin,Is there any detailed document explaining about setting up SCOM 2016 Management Servers as on-standby recovery in secondary datacenter ?, if yes, could you please provide me the link or let me know what steps need to be taken care when my primary datacenter is not reachable. Many Thanks, Raj
  • Anonymous
    December 14, 2017
    Does SCOM 2012 R2 agent work with SCOM 2016 Management Servers/Gateways? Or do they grey out when you update your SCOM 2012 R2 environment (management servers) to SCOM 2016?