System Center Operations Manager:System Center Operations Manager

System Center Operations Manager:System Center Operations Manager
Application	System Center Operations Manager
Purpose	Systems Administration
Server	Servers:SAD-SCOM01
Location	Site:HME
Rack	Rack: HME-R01
Accounts	Users and Groups:svc_scom Users and Groups:svc_scomsql Users and Groups:svc_scomwrite Users and Groups:svc_scomread

Deployment

1. Begin with a clean install of Windows Server 2022 Desktop Edition. You can find specific VM requirements for this server at Servers:SAD-SCOM01.
   1. A total of five virtual disks are needed for a proper installation:
      1. 128GB OS Disk - For Windows Server 2022.
      2. 256GB Program Data Disk - For Database: Microsoft SQL Server 2022 and System Center Operations Manager:System Center Operations Manager program files.
      3. 256GB Database Disk - To store database files.
      4. 256GB Logs Disk - To store SQL log files.
      5. 64GB TempDB Disk - To store SQL TempDB files.
2. Install Microsoft SQL Server 2022.
   1. Mount the Microsoft SQL 2022 ISO and run setup.exe.
   2. Click "Installation" on the sidebar then click "New SQL Server standalone installation or add features to an existing installation".
   3. On the Edition screen, enter your product license key.
   4. On the License Terms screen, Accept the license terms.
   5. No action needed for section Global Rules.
   6. Choose whether or not to use Windows Update on the Microsoft Update tab. I choose not to.
   7. Click Next on the Install Rules tab.
      1. Note: I received a warning about Windows Firewall, there's no need to worry about this.
   8. Perform the following actions on the Feature Selection screen:
      1. Check "Database Engine Services" and "Full-Text and Semantic Extractions for Search"
      2. Change the "Instance root directory", "Shared feature directory", and "Shared feature directory (x86)" drive letter to your Program Files disk. In my case, this is drive D. Leave the rest of the path untouched.
   9. On the Instance Configuration screen, the defaults are fine. Click Next.
   10. Perform the following steps on the Server Configuration page:
       1. Open Active Directory Users and Groups and create a service account for SQL to run under. I am using Users and Groups:svc_scomsql.
       2. Change the Account name for both services and input the password. Make sure this account is documented. SQL Server Browser cannot be modified.
       3. Set the Startup Type to Automatic.
       4. On the Collation Page, the default of SQL_Latin1_General_CP1_CL_AS is fine.
       5. Click Next.
   11. On the Database Engine Configuration section, perform the following tasks:
       1. On the Server Configuration Tab: The default of "Windows Authentication Mode is fine. Add Domain Admins and your SQL Service account Users and Groups:svc_scomsql to the SQL Server Administrators box.
       2. On the Data Directories tab: set "Data Root Directory" to your database drive. In my case that would be E:\Database. The other data directories should change to reflect this new path. Do not change those paths! Change the "User database log directory" to your Logs drive. In my case it would be F:\Logs\SQL. The Backup Directory is fine. Mine defaulted to E:\Database\MSSQL16.MSSQLSERVER\MSSQL\Backup.
       3. On the TempDB Tab: Remove the default data directory and specify your TempDB drive. In my case, it is G:\TempDB. Change the Log Directory to your logs drive. I choose to use path F:\Logs\TempDB.
       4. On the Memory tab: Click "Recommended" then accept the recommended configuration.
       5. All other tabs can be left at default values. Click Next.
   12. On the Ready to Install Screen, Click Install.
3. Configure SQL Post-install by launching "SQL Server Configuration Manager" from the Start Menu.
   1. Expand "SQL Server Network Configuration" then click "Protocols for MSSQLSERVER" Enable "Shared Memory", "Named Pipes" and "TCP/IP".
4. Install Microsoft SQL Server 2022 Reporting Services. The installation is next, next finish easy, so the following steps will review configuration.
   1. Under Service account, specify the SCOM SQL service account, for example, Users and Groups:svc_scomsql.
   2. Under Database, click the Change Database button to begin the wizard.
      1. On the Action Page, select Create a new report server database.
      2. On the Database server tab, test the connection. Please note: This is usually your admin account these credentials will not be saved, just used for elevated permissions. Click Next.
      3. Click Next on the Database tab, the defaults are fine. Click Next.
      4. Click Next on the Credentials tab, the defaults are fine. Click Next.
      5. On the summary page, review your setup and click Next.
      6. Navigate to the Web Service URL and click apply. This will create the virtual directory.
      7. The SSRS service should now be working properly, with the service running. You can verify this under the HOSTNAME\SSRS tab.
5. Install System Center Operations Manager
   1. Run the following command from an admin Powershell session to install dependencies:

      Install-WindowsFeature -Name Web-Server, Web-WebServer, Web-Common-Http, Web-Default-Doc, Web-Dir-Browsing, Web-Http-Errors, Web-Static-Content, Web-Health, Web-Http-Logging, Web-Request-Monitor, Web-Http-Tracing, Web-Performance, Web-Stat-Compression, Web-Security, Web-Filtering, Web-Basic-Auth, Web-Windows-Auth, Web-App-Dev, Web-Net-Ext, Web-Net-Ext45, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Includes, Web-WebSockets, Web-Mgmt-Tools, Web-Mgmt-Console, Web-Scripting-Tools, Web-Mgmt-Service, Web-Lgcy-Mgmt-Console, Web-WMI, Web-Asp-Net, Web-Asp-Net45, NET-Framework-Features, NET-Framework-Core, NET-Framework-45-Features, NET-HTTP-Activation, NET-Non-HTTP-Activ

   2. Reboot the server.
   3. Launch the installer from the ISO. On the first page, click Install, then install all available roles.
   4. On the Select Installation Location Page, change C:\ to the Program Data disk D:\, keeping the rest of the path unmodified. Click next.
   5. Specify the Management Group. I am using "sysadminafterdark". Click Next.
   6. Agree to the license terms.
   7. On the Configure Operational Database page, type in the hostname of your server and tab over to another text box. The wizard should recognize it is a valid SQL database and allow you to continue. All of the defaults are fine, as they were specified during SQL setup. Click Next.
   8. On the Configure Data Warehouse Database page, type in the hostname of your server and tab over to another text box. The wizard should recognize it is a valid SQL database and allow you to continue. All of the defaults are fine, as they were specified during SQL setup. Click Next.
   9. On the SQL Server Instance for Reporting Services page, select the SSRS server you setup earlier in this guide. Click Next.
   10. On the Specify a web site for use with the Web Console, select the Default Website. I will not be using SSL at this time and will configure this later. Click Next.
   11. On the Authentication Mode page, select Use Network Authentication. This will allow you to authenticate with AD accounts only. Click Next.
   12. On the Configure Operations Manager Accounts page, type in the DOMAIN\Account for each service account. I am using Users and Groups:svc_scom, Users and Groups:svc_scomread and Users and Groups:svc_scomwrite. Please note that appropriate database permissions are configured by the installer. Click Next.
   13. On the Diagnostic and Usage Data screen, click Next.
   14. On the Microsoft Update screen, choose Off and click Next.
   15. On the Installation Summary screen, review your changes, then click Next.
   16. Your server will successfully be installed, however you will receive a warning that the Management Server must be licensed. Open up the SCOM console and go to Help > About. You can use the activate button to type in your product key. You will need to restart the System Center Data Access Service to see that it is activated.
6. Install Audit Collection Services
   1. Install Microsoft ODBC Driver 18 if you are utilizing SQL 2022, otherwise installation will fail. In theory, the included ODBC 17 driver should work, but after troubleshooting and installing ODBC 18, installation went off without a hitch.
   2. From the Main installation screen under Optional Installations, click the Audit Collection Services link.
   3. On the Welcome screen, click Next.
   4. Accept the license terms on the Microsoft Software License Terms page. Click Next.
   5. On the Database Installation Options screen, select Create a new database and click Next.
   6. On the Data Source screen, accept the default OpsMgrAC data source name and click Next.
   7. Select Database server running locally on the the Database screen. The default OperationsManagerAC database name is fine. Click Next.
   8. On the Database Authentication screen, select Windows Authentication, then click Next.
   9. Select Use SQL Server's default data and log file directories on the Database Creation Options screen. This will use the SQL server's default directories specified above. Click Next.
   10. On the Event Retention Schedule, the default 2:00am time frame is ok, however, I changed the Number of days an event is retained in the database from the default of 14 to 30 days. Click Next.
   11. Choose Local time on the ACS Stored Timestamp Format. It is easier to line up with device logs in my environment. Please note, you cannot change this later. Click Next.
   12. On the Summary page, click Next.
   13. There will be a windows that pops up asking for credentials. Choose Windows Integrated and ensure encryption is set to optional, otherwise it will fail.
7. Install Audit Collection Services for Unix/Linux
   1. Open Services from the Start menu and find Microsoft Monitoring Agent Audit Forwarding. Ensure this service is set to automatically start and start the service.
   2. On the main installation screen of the Operations Manager installer, click the Audit Collection Services for Unix/Linux link.
   3. This is a very simple next, next, finish type installer. Click through the prompts and the service should be installed correctly.

Updates