Learn how to install System Center Operations Manager. Once the prerequisites have been completed, installation is fairly easy for SCOM.
- [Instructor] We spent a lot of time in previous videos preparing for our System Center Operations Manager installation, and now, we're ready to actually do the installation. There's a list of different things that we talked about in previous videos that we're going to do now, and we need to do those in order, as you see them from the top. We need to go into our Active Directory server, and create the first four accounts that you see there, followed by the SQL Service account, and the OMAdmins account as well. Let's go to our domain controller and take a look.
We are in our domain controller, or Active Directory, and we're going to go to a new organizational unit I created, simply by right-clicking on widget.internal and choosing new organizational unit. And from here, I've already pre-created the accounts, and it's as simple as just right-clicking and choosing new, user account, just like we've all done before in Active Directory. The different accounts, as listed previously in the document shown, shows the five different individual accounts, as well as the one security group.
Now, if I double-click on one of the users, I just want to show that we want to go to the Account tab, and see that we want the password never expires option checked. These are service accounts used by System Center Operations Manager, and not by users. So, if our password expires, then System Center Operations Manager will cease to function until we fix that. So, let's go ahead and click Cancel, and we want to go into our OMAdmins group, and we want to make sure that we add the first four users.
This does not include the SQL Service group, as mentioned earlier, just the four users. We also want to add our administrator account as well, simply by clicking on Add, and typing in administrator. If you have any other administrators you would like to use for System Center Operations Manager, instead of the administrator account for the Active Directory domain, then you can add that user here. Let's go ahead and click OK. Our users have been created, and our group has been set up with the users added.
We are back in our System Center Operations Manager server, and we are preparing for installation. We've already created the accounts and the groups, and now, we're down to adding the OMAdmins group, from our active directory we did earlier, to the local administrator's group on the server. Let's go down to Server Manager, and go up to Tools, and go into Computer Management. From here, we're going to expand Local Users and Groups. Click on Groups, and you'll see the administrators group.
Let's go ahead and double-click on the administrator's group, and we want to make sure that the OMAdmins group has been added. If you don't see it there, just go ahead and click Add. Type OMAdmins. Check Name, and click OK. Once that's there, click Apply, and OK, and now that portion is done. Now, we need to add the OMAdmins group in, because all those service accounts and the domain administrator account need to have full control over the server once we run System Center Operations Manager.
Let's go ahead and close Computer Management, and minimize Server Manager, and we'll move on to the next step, and that is going to be to install the SQLSysClrTypes.msi file followed by the Report Viewer. This is so our Report Viewer will run properly, so the administrator will have the ability to view any alerts and reports from System Center Operations Manager. Now, we need to use the version SQL Server 2014 Feature Pack. That's because that's the one that works with this particular version of System Center Operations Manager.
There's also a SQL Server 2016 Feature Pack, in case you're using the SQL Server 2016. Go ahead, install both of those if you are using SQL Server 2016. If you're just using 2014, you only need to install the 2014, and that's because the Report Viewer requires the 2014 Feature Pack, but SQL Server 2016 requires the '16 version. So, if you're using SQL Server 2016, install them both. All you need to do is to copy this phrase, and paste that into a Google search, and I do recommend Google over Bing, because it does find it more easily.
Go ahead and download the Feature Pack, and in that Feature Pack, there's only one file you want, and that is the SQLSysClrTypes.msi file for x64. Then, you can go ahead and install the Microsoft Report Viewer 2015 Runtime, which is also another free installation. Once you go ahead and do a search for that and install it, then we can go ahead and move on, but we need to install that first. So, we've already downloaded the files. Let's go ahead and install the SysClrTypes first, and again, that says for 2014, although I have also done the '16 version, and now it's done.
Let's go ahead and double-click the Report Viewer. Accept the terms, and install, and now we're done with the Report Viewer. Let's go back to our document, and see what's next. We need to install the following features, and you can see a long list of features, and we can do that through our Sever Manager, so lets open up Server Manager, and find these different features and get them installed. We're in Server Manager on our SUM server. Let's go ahead and click on Add roles and features, and click Next.
Next. Next. And here's a list of server roles, and then after that is the features. First, we'll need to check the Web Server IIS. Click Add Features, and let's click Next, and Next, Next, and now, we see all the role services for the server role of Web Server IIS. We're going to want to make sure Static Content is checked, which it is by default. Then, we've got Default Document, which is checked. We want Directory Browsing, this is also checked.
We want HTTP Errors, which is checked. HTTP logging, which is also checked. Web Request Monitor, and that is right here. We next need to have the filtering, which is down here. Static Content Compression, Management Console, which at the bottom, and that is checked. We want the Metabase, and we'll have to expand under Management Tools to get to the Metabase, and then, we'll also want to expand the Application Development as well, to get ASP Net, and we'll choose all those, and we want Web Windows off, and that is known as Windows Authentication.
We'll go ahead and click Next, and Install. Now, we want to make sure we restart after doing these different feature installations. Otherwise, we will get some errors when we try to install and run our System Center Operations Manager program. Our feature installation is complete. Let's go ahead and restart. Our server is back up. Let's go ahead and go back into Server Manager, as you see we have here, and go to the add roles features, and we want to make sure we have one more feature installed after the reboot, and that is going to be under the .NET 4.6 Features, if you're on Windows Server 2016.
If you're on 2012, you're going to see the 4.5. From here, we're going to click on the HTTP Activation. Click Add Feature. Next, and Install. Now, our feature installation is installed for activation, and we can go ahead and install our SQL Server. As mentioned earlier, we're going to install SQL Server 2016. You could also do 2014, as long as it has Service Pack 2, and now a wizard comes up. Click on Installation on the left-hand side, and at the top, we're going to click new SQL Server stand-alone installation.
While we're waiting, I should mention that you do want to have all Windows Updates up-to-date, and that way, you can make sure that you have everything working the way it should be. Let's go ahead and click Next. Accept the license terms and click Next. Now, this installation could take anywhere from a few minutes to much longer, depending on the speed of your server, so just make sure you are prepared for that, and you can also check for updates for SQL, that is recommended, and there is an update, as we see here.
Go ahead and click Next and it will automatically install it. In some cases, you'll also need to reboot after one of these updates is done. It just depends on which update it is, or updates, and after the installation is done, it will tell you whether or not you need to reboot. The update has completed, and it shows that we have passed all of our prerequisites, with the exception of a warning on the firewall, which probably wants to make sure that the proper rule is set up. So, let's go ahead and click Next, and we're going to check specific things in our list.
The first will be Database Engine Services, and we want Full-Text and Semantic Extractions, and we want Reporting Services. I'm going to leave the location of the root directory and the shared feature as the defaults, and we'll click Next. The Instance ID is going to be important if you have multiple databases on this server. I'm going to go ahead and leave the default, but you might want to change it to something that has to do with System Center Operations Manager, so it doesn't get confused with other databases.
Now, we're just choosing this one database for this particular server. Let's go ahead and choose Next. And now, we're supposed to make some changes, such as the Startup Type. We want to make sure that it's set from Manual to Automatic. Now, what we want to do is to change our SQL Server Agent, Database Engine, and Reporting Services to be out new SQL Service accounts. So, go ahead and choose to browse. Choose SQLSVC. Click Check Name, click OK, and make sure it shows those accounts on all three.
Then, we want to put in the passwords that we entered when we created the accounts as well, and we shall click Next. Let's go ahead and choose to add the current user for the authentication for SQL Server administrators, and we want to use the Windows authentication mode, not the mixed mode. Go ahead and choose Next. Let's leave the install and configure option the same way it is, and click Next, and now choose the Install.
Of course, you can change the configuration file path if you choose, and this could take a while to install, so be prepared to wait for a little bit. It could take anywhere from a few minutes up to an hour, depending on the speed of your server. While we're waiting, let's go ahead and make a change to the firewall. So, we open up TCP port 1433, which is the default port for SQL Service. That way, our other devices can communicate with our SQL Server. We just go down to our Control Panel, and choose the Windows Firewall option.
Scroll to the bottom. Next, we will click on Advanced Settings, then we'll click on inbound rules. We could look for the specific rule that we want or just create a new rule, which is a little bit faster, and we want to allow a port through, so click Next. TCP, specific port, 1433. Next. Allow the connection on all different network types, and we'll call it InboundSQL, and we'll click Finish.
There's our InboundSQL rule. Double-click on the rule, and if you have more than one subnet, you're going to want to make an additional change. Click on the Advanced tab, and make sure you change the block edge traversal to allow edge traversal. Once that's done, you can go ahead and click OK, and we can continue on. We're back in our SQL installation, and it looks like we're almost halfway done. We've now progressed a little farther, and I just want to mention the type of installation we're doing, because in previous videos, we talked about a single installation verses a distributed installation, and in this particular case, we're installing all the different rules onto one server.
So, it's definitely not a distributed installation, and the advantage to that, of course, is that everything is all in one place, but the disadvantage is there's no way to have any type of high availability or redundancy when doing that, and it doesn't distribute the load across multiple things, which would be very helpful if we wanted to spread that load out in case there was a lot of reporting going on, and our server wasn't able to handle it. We're just about done here. When that's finished, we can go ahead and start the System Center Operations Manager 2016 installation, and it appears that our installation was successful.
So, let's go ahead and close that, and move on to the next task, which is the Operations Manager. We've mounted our ISO file, double-clicked on the single file that's inside it, and now we're ready to do the installation. It's going to attempt to extract the files into the E drive, which is a read-only file. So, let's go ahead and change that to the C drive, and extract. Our extraction is now complete. Go ahead and click Finish, and we'll go ahead and double-click on our C drive, and to the extracted folder, and click Setup.
Here's our Setup screen, and we can choose to download the latest updates to the setup program, and click Install. We're going to choose the management, operations, and web console. We're not going to choose the optional reporting server at this time. We'll go ahead and click Next, and we'll choose the default location, and Next, and now it's verifying that we have everything set up properly, which we do, and we'll click Next. Let's choose a management group name. Now, the name of our server is SCOM, so we'll call this SCOM1, and keep it simple.
We will go ahead and choose to scroll through everything and accept. Next. Since we installed SQL on the local server, we'll just go ahead and put in the local server name, and instance name. After putting in the local server, everything else just automatically populated, because it found that instance of SQL Server. Go ahead and click Next. Now, it wants the data warehouse database, and once again, it auto-populated everything. The data warehouse database is the database that keeps the data after the initial database is done collecting everything it needs.
Yeah, let's go ahead and click Next. In a previous video, we did discuss the difference between the two different types of databases, which you can review if you need to. We're going to choose the default website. You can choose SSL if you would like to secure that website, which I recommend. In our case, for testing purposes, we're not going to check that. Let's go ahead and click Next. We'll go ahead and choose the default authentication of mixed authentication. This is for the website, not for SQL server. Let's go ahead and add in our domain username and password.
Let's copy our domain username, and paste it into the other two locations. Now, we can also use one of the service accounts that we created earlier, but in this case, we're just going to go ahead and use the administrator, and click Next. We're getting a messages saying that it doesn't recommend using the domain administrator account for security reasons. So, that's why I recommend using the OM accounts that we created earlier. But in this case, we're going to go ahead and choose Next.
We're onto the Diagnostic and Usage Data area. We'll go ahead and choose Next. Now, we'll take a look at the installation summary, and if we want to change anything, we can go back and choose Install, and this could take a little while, just like the SQL Server installation. So, just make sure you have some extra time and be patient while it goes through the different installation progress pieces of our SCOM. While we're waiting, let's talk about the domain account that I went ahead and used the administrator account instead.
What you can do is you can choose the O-M-A-A, O-M-D-A-S. The different accounts that we created to put in to that previous screen, because they're not domain administrator accounts, and adding a domain administrator account actually adds a bit of a security risk, and that's because if anyone was able to get a hold of that information, then they would have full access to the server and be able to make changes to it, whereas if we use the OMA acccounts that we created earlier, which do not have administrator access, then they would not be able to gain full administrator access into our System Center Operations Manager server.
So, in that previous screen, you had that option to choose the OM read and the OM write accounts, as well as the O-M-D-A-S and the O-M-A-A. That's certainly the recommended path to doing the installation in a production environment. Now that our files have been installed, we can double-click on the expansion folder, and double-click on Setup, and here is the Operations Manager installation. We'll go ahead and check the box to download the latest updates to the setup program, and click Install.
Here we are presented with the different features we would like to install. Let's go ahead and install all of them, and again, this is a single server installation. Let's go ahead and choose Next. So, all of the different features are going to be on this one server, and we're going to choose the default location, and click Next, and now it's verifying that everything has been properly installed ahead of time, which it has. So, we can proceed with the setup. Let's go ahead and get a management group name, and we'll just call it S-C-O-M-M-G-M-T, but you can call it anything that makes sense to you.
Let's go ahead and click Next, and we'll check that we have read and understood, of course, after reading all of the license terms, and click Next, and we're going to choose the server name, which is the local server name that has SQL Server installed on it. In your case, if you have a distributed installation, you might see a different server name to put in there, and just by typing in the name of the server, it should auto-populate everything we need, which it did, fantastic. Let's go ahead and click Next. And once again, we'll put in our server name, and it should auto-populate for the operations portion, and it did, and we'll go ahead and choose Next, and for reporting services, it went ahead and found our local server.
So, go ahead and click Next. If it didn't find it, you can go ahead and type it in at that time. Now, we're presented with the option to put in the website information. We're going to choose the default website, because it's the only thing we have on the server, and you can also choose Enable SSL if you have a certificate ready. Since this just a test server, we do not have certificate ready, so we'll just go ahead and click Next, and we're going to stay with the mixed authentication. Now, this is for the Web IIS. This is not the SQL Server, so we're going to go ahead and leave the mixed authentication in there for forms authentication and choose Next.
Now, we have several different accounts that we need to put in. We're going to use the accounts that we created earlier. The first one is going to be our domain name, which is widget backslash, and it's going to be the O-M-A-A account. That is our server action account, and now we're going to go down to the Data Reader account, and we're going to put in widget once again, backslash, and we're going to put in OMRead, and now we have our Data Writer account, and we're going to put in widget, backslash, OMWrite, and we're going to change our System Center Configuration service account in the middle to widget, backslash, O-M-D-A-S.
I'm going to fill in the passwords for each one, and then we'll click Next. Now, if the accounts have domain administrator access, you may get a popup warning, but you can still proceed, and we'll go ahead and click Next to our Diagnostic and Usage Data, and Install, and this is going to take quite a while, depending on the speed of your server. Anywhere from 10 minutes up to one hour or more, and it appears that setup is complete, and everything was good.
We do have one warning that we just have a demo version of the management server, we just need to properly license it, which we can do. Let's go ahead and click Close, and it's launching for the first time. We're connecting to the database, and here we are! We are now in System Center Operations Manager. We have lots of different areas, which we'll be covering upcoming videos. Monitoring, Authoring, Reporting, Administration, and Workspace.
Stay tuned to upcoming videos on how to configure System Center Operations Manager, and how to use all the different parts and pieces, and we will demonstrate those for you in upcoming videos shortly.
- Exploring System Center Operations Manager (SCOM)
- Planning for service monitoring
- Planning for deployment
- Deploying SCOM
- Administering packs
- Monitoring administration