14 Ocak 2017 Cumartesi

INSTALLING SYSTEM CENTER 2016 OPERATIONS MANAGER - Scom 2016

Installing System Center 2016 Operations Manager – Part 1

Installing System Center 2016 Operations Manager – Part 1

A week ago Microsoft announced System Center 2016 products. Microsoft adds most of features of this systems. We will analyze the new features on another article. In this document I Show you how can install System Center 2016 Operations Manager on a Windows Server 2016. Also you can read Single-Server Deployment of Operations Manager 2016 on TechNet.
This article has 2 parts.
  1. Part 1 – Preparing environment
  2. Part 2 – Installing Operations Manager

Part 1 – Preparing Environment

  1. Environment
  2. Requirements and Prerequisites
  3. Scenarios
  4. Install prerequisites

Environment

DC
SCOM16Windows Server 2016System Center 2016
SQL Server 2016

Requirements and Prerequisites

Before install Operations Manager you should check the Firewall Exceptions for Operations Manager article on TechNet. You should also check the prerequisites and system requirements to install operations manager from here. But in summary, you can check the table below

Hardware

RoleCPU (x64)MemoryDisk space
Management Server4-Core 2,66 GHz CPU8 GB10 GB
Gateway Server4-Core 2.66 GHz CPU8 GB10 GB
Web Console server4-Core 2.66 GHz CPU8 GB10 GB
SQL Server Reporting Services server4-Core 2.66 GHz CPU8 GB10 GB
This table is about minimum requirements. You should use “Operations Manager 2012 Sizing helper” tool to determine system requirements for your environment. This tool has not been updated while I wrote this article. But you can use 2012 tool for determine hardware requirements.

Server Operating System

ComponentWindows Server 2012 R2 Standard, DatacenterWindows Server 2016 Standard, DatacenterWindows Server Core 2016
Management Server***
Gateway Server**
Web Console**
ACS Collector**
Operations console**

Microsoft Monitoring Agent for Windows Platforms

Windows Server 2016
Windows Server 2016 Nano Server
Windows 10
Windows 8 Enterprise
Windows 8 Pro
Windows Embedded POS Ready 2009
Windows Embedded Standard 7 Service Pack 1
Windows Server 2003 Service Pack 2
Windows Server 2008 R2
Windows Server 2008 Service Pack 2
Windows Server 2012
Windows XP Professional 64-Bit Edition (Itanium)
Windows XP Service Pack 2
Windows XP Service Pack 3
When you want to install agent on a windows system, this computer has to have
PowerShell 2.0 or PowerShell 3.0 and Net Framework 3.5 or later.

Web Console requirements

Web console can be installed on IIS 7.5 or newer version. You should install IIS Console with the following components. I use PowerShell script to install all windows server features that required for Operations Manager.
Feature
Static Content
Default Document
Directory Browsing
HTTP Errors
HTTP Logging
Request Monitor
Request Filtering
Static Content Compression
Web Server (IIS) Support
IIS 6 Metabase Compatibility
ASP.NET (both the 2.0 and 4.0 versions of ASP.NET are required.)
Windows Authentication
NET Framework 4.0
NET Framework 4.5

Management Server

PowerShell 2.0 or PowerShell 3.0
NET Framework 4.0 or NET Framework 4.5

Console

Reporting Server

Remote registry service must be enabled
Same as SQL Server requirements

SQL Requirements

ComponentSQL Server 2014, SP2 Enterprise/Standard (x64)SQL Server 2016 Enterprise/Standard (x64)
Operational Database**
Data Warehouse Database**
ACS Database**
Reporting Server**

Accounts

AccountDescriptionSpecial Rights
Management Server Action AccountAll systems that monitored with operations manager execute a process called MonitoringHost.exe. this process used for getting information about servers. This process collects event log, performance, WMI data and executes scripts and batches.Should be either Domain User or Local SystemMember of the local Users group
Member of the local Performance Monitor Users group
“Allow log on locally” permission (SetInteractiveLogonRight)
System Center Configuration Service and System Center Data Access Service accountIn setup screen we enter an account information and Operations Manager uses same account for these services. This account used to update information in the OperationsManager database.Should be either Domain User or Local System,Must have local administrative rights on the root management server,
Local user account is not supported,
Data warehouse write accountThe Data Warehouse Write account is the account used to write data from the management server to the OperationsManagerDW database, and it reads data from the OperationsManager database.Should be Domain User,Local System account is not supported,
Local user account is not supported,
Data Reader accountData reader account is used to deploy reports.Should be Domain User,Local System account is not supported,
Local user account is not supported,

In-Place Upgrade

Operations Manager 2016 supports in-place upgrade from previous versions;
VersionUpdate Rollup (Min)
System Center 2016 Technical Preview 5
System Center 2012 R2Update Rollup 9

Scenarios

Single-server deployment

Single server deployment scenario used when you want to test, management pack development or have a small environment. You can install all roles except Gateway server on a single server. All Windows, Unix/Linux agents and network devices report to the management server. All of audit collection forwarder agents send audit data to this management server. Management server also has database role with SQL Server. When you deploy single-server scenario you can monitor limited agent.

Distributed Deployment

Distributed deployment allows for distribution of features across multiple servers. Distributed deployment provides load sharing and fault tolerance options. You can install all roles separate servers. Also you have database high availability options with SQL Always-ON and Cluster.

Installing

High Steps

  1. Windows Server Feature and Role installation
  2. SQL Server installation options
  3. Change SQL Agent service startup state
  4. Installing Report Viewer Controls
  5. Installing Operations Manager 2016

Detailed Steps

Windows Server Feature and Role installation
You can install feature and role prerequisites either via Server manager or via PowerShell. My choice generally using PowerShell. I use PowerShell script to install all prerequisites quickly and correctly.
  1. Open a PowerShell screen with administrative privilege
  2. Replace “sources\sxs” folder address for your computer and copy/paste to PowerShell screen.
    Import-Module ServerManager
    Install-WindowsFeature -Name NET-Framework-Core -Source C:\sources\sxs -Restart:$false
    Add-WindowsFeature Web-Server, NET-HTTP-Activation, NET-WCF-HTTP-Activation45, Web-Mgmt-Console, Web-Net-Ext, Web-Net-Ext45, Web-Static-Content, Web-Default-Doc, Web-Dir-Browsing, Web-Http-Errors, Web-Http-Logging, Web-Request-Monitor, Web-Filtering, Web-Stat-Compression, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Metabase, Web-Asp-Net, Web-Windows-Auth, Windows-Identity-Foundation
SQL Server installation options
We need SQL Server with the following options;
  1. Database Engine Services with Full-Text Search option and Reporting Service with Native Option.
  2. SQL Collation must be SQL_Latin1_General_CP1_CI_AS.
  3. Authentication mode is Windows. You have to add an account at least. I added my domain administrator account. You can create a special group, for example SCOMAdministrators named and add this group as a SQL Server Administrators.
  4. You can install management tools from Microsoft Download Center. Setup file is about 900MB. (SSMS-Setup-Enu.exe)
Change SQL Agent service startup state
  1. On the SQL Server open services.msc mmc console and find “SQL Server Agent (MSSQLSERVER)”
  2. Open properties with Double click.
  3. Change startup type from manual to automatic then click start to start service. Then click OK to close properties screen.
  4. You can close services.msc screen.
Installing Report Viewer Controls
Before starting to install Operations Manager, you must install report viewer controls. You should install this controls if you want to install Operations Manager Console. You can download setup file from Microsoft Download Center (https://download.microsoft.com/download/A/1/2/A129F694-233C-4C7C-860F-F73139CF2E01/ENU/x86/ReportViewer.msi)
  1. Double click to setup file,
  2. Click next,
  3. Accept eula and click next,
  4. Click Install button to install,
  5. Click finish button to close setup.
Installing System Center 2016 Operations Manager – Part 2

Installing System Center 2016 Operations Manager – Part 2

This article has 2 parts.
  1. Part 1 – Preparing environment
  2. Part 2 – Installing Operations Manager

Part 2 – Installing Operations Manager

  1. Accounts
  2. Setup
  3. Initial settings – Licensing

Accounts

When we install Operations Manager, we need 4 account. Action Account and SDK account can be Local System account. But Data warehouse read and write accounts must be domain user account. No account should be a local user. You must be local administrator of Windows Server and system administrator of SQL Server. Operations Manager does not require Domain Admins or equivalent rights to run. But some management packs require administrative privilege to monitor server software. You should read Management Pack guides.
Here is a table for accounts.
AccountDescriptionSpecial Rights
Management Server Action AccountAll systems that monitored with operations manager execute a process called MonitoringHost.exe. this process used for getting information about servers. This process collects event log, performance, WMI data and executes scripts and batches.Should be either Domain User or Local SystemMember of the local Users group
Member of the local Performance Monitor Users group
“Allow log on locally” permission (SetInteractiveLogonRight)
System Center Configuration Service and System Center Data Access Service accountIn setup screen we enter an account information and Operations Manager uses same account for these services. This account used to update information in the OperationsManager database.Should be either Domain User or Local System,Must have local administrative rights on the root management server,
Local user account is not supported,
Data warehouse write accountThe Data Warehouse Write account is the account used to write data from the management server to the OperationsManagerDW database, and it reads data from the OperationsManager database.Should be Domain User,Local System account is not supported,
Local user account is not supported,
Data Reader accountData reader account is used to deploy reports.Should be Domain User,Local System account is not supported,
Local user account is not supported,

Setup

  1. Logon to the server by using an account that has local administrative rights,
  2. Run setup.exe as administrator,
  3. In setup screen click “Install” to start wizard,
  4. In “select features to Install” screen, Select the roles you want to install. In this scenario we select all features. Noticed that, you can select Reporting Server feature only if SQL Reporting service is installed. Click next,
  5. In “select Installation location” screen you don’t have to change location. Click next,
  6. If complete installation of prerequisites in Part 1, In Prerequisites screen you see All prerequisites have passed. Click next,
  7. In “Specify an installation option” screen choose to “Create the First Management Server in a new Management Group” and then give a special name for your Management Group. I chose SCOMMG for management group name. when you install agent software on a Windows Server, you have to specify this management group name. Click next,
  8. Accept the EULA and then click Next,
  9. On the Configure the operational database screen specify SQL Server Name and instance. Our SQL installation is located same server with the management server. So, type SCOM16 to Server Name area. Click Next,
  10. On the Configure the data warehouse database screen specify SQL Server Name and instance. Our SQL installation is located same server with the management server. So, type SCOM16 to Server Name area. Click Next,
  11. SQL Server instance for reporting services screen click next. If you don’t select Reporting Services option on the feature selection screen, this screen will not be shown. Click Next,
  12. Do not change any option in “Specify a web site for use with the Web console” screen and click Next,
  13. Chose mixed authentication for Web console authentication mode then click Next,
  14. On the “configure operations manager accounts fill appropriate user accounts. Create these accounts on the domain controller as domain account. You can use the following table;
AccountDomain\UserAccountPrivilege
Management Server Action AccountDomain\omaction
System Center Configuration Service and System Center Data Access Service accountDomain\omsdkShould be local administrator
Data warehouse write accountDomain\omwriter
Data Reader accountDomain\omreader
  1. On Diagnostic and usage data screen, click next,
  2. On Microsoft update screen click next,
  3. Installation summary screen click next,
  4. When installation finished close the setup window.
Initial Settings – Licensing
After operations manager installation you should do some settings. First we should enter product key to register our product. If you don’t enter license you can use Operations Manager about 180 days, then the trial period ends. Get your product key from Volume Licensing Site.
  1. Logon to operations manager server with local administrative rights and operations manager admin rights.
  2. Click start menu and find “operations manager shell”. Then click to open Shell screen.
  3. Type following command to enter your product key. Change X’s with your product key. You must use elevated permissions to use Set-SCOMLicense cmdlet.
    Set-SCOMLicense -ProductId XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
  4. Type “Y” t confirm license then restart your server to make sure that these changes are applied correctly
  5. You can check license with this command.
    Get-SCOMManagementGroup | ft SkuForLicense, Version, TimeOfExpiration
SkuForLicenseVersionTimeOfExpiration
Retail7.2.11719.012/31/9999 11:59:59 PM
Ref.technet24

INSTALLING SQL 2016 FOR SCOM 2016 (STEP BY STEP)

Installing SQL 2016 for System Center Operations Manager (SCOM) 2016 – Step-by-Step

Installing SQL 2016 for System Center Operations Manager (SCOM) 2016 – Step-by-Step

The following is a guide on how to install SQL 2016 for your System Center Operations Manager (SCOM) 2016 environment. I will be installing SQL 2016 on a brand-new server with Windows Server 2016 installed.

To begin, I am going to set the following accounts as a Local Administrator on the server. Also, I am going to be creating two SQL instances, one for the Operations database, and the other for the Data Warehouse. Since this is for my personal lab, I am not dedicated storage/drives for the databases.
Domain\AccountDescription
domain\SCOM_AASCOM Action Account
domain\SCOM_DASCOM Data Access/SDK Account
domain\SCOM_SQL_READSCOM SQL Reader
domain\SCOM_SQL_WRITESCOM SQL Writer
domain\SQL_SASQL Service Account
1
Next, let’s run the setup wizard as the SQL_SA account to make life easier down the road…
2
First thing I noticed, between SQL 2012/2014 and SQL 2016, a few changes/features have been removed/added. One that stands out is, the SQL Server Management Studio (SSMS)console is no longer here. Hmm.. I guess we can always connect to the databases from a console on another server/PC.
3
As mentioned, I am dedicated an instance for the Operations DB, and one for the Date Warehouse DB.
4
Setting the  SQL Server Agent to Automatic, and specifying the service accounts for the two services.
5
Keeping the database engine collation as default, “SQL_Latin1_General_CP1_CI_AS“.
6
Here, I am adding all the SCOM/SQL service accounts and SQL service accounts as SQL server administrators.
7
This is new for SQL 2016 — being able to create TempDB‘s. Since my VM has 8 vCPU’s, looks like SQL 2016 picked up on that, and has decided to create a one-to-one relationship. Great, let’s get started within the installation…
8
No errors. Keep in mind, we will need to repeat these steps to create the Data Warehouse instance.
15
16
Now we can go ahead with the SCOM 2016 installation! See HERE, for that post.
If you need to install the SQL Server Management Studio (SSMS), continue reading…
Within the SQL Server Installation Center, we have the SQL Server Management Tools as an option, let’s choose that.
9
That takes us here, “https://msdn.microsoft.com/en-us/library/mt238290.aspx“. I guess you can always download SSMS directly from the URL as well. Good to know!
Once downloaded, let’s run the installer…
12
13
14
Rather simple and straight-forward. Let’s launch that sucker!
17
I can see the two SQL instances I just created, SCOM_DW and SCOM_OPSMGR, perfect!
Ref.technet24

9 Ocak 2017 Pazartesi

Hp SiteScope: Dynamic Dates (Url, FileName,...)

Sometimes a monitor will need a dynamic date for it to work correctly.  If the date needs to be dynamic, SiteScope has Dynamic Date Variables.  You can use these in file names, text fields, URLs, POST data, almost everywhere.
SiteScope recognizes a specific set of variables to use in substitute for static date or time values:
VariableRange of Values
$hour$0 – 23
$minute$0 – 59
$month$1 – 12
$day$1 – 31
$year$1000 – 9999
$shortYear$00 – 99
$weekdayName$Sun – Sat
$fullWeekdayName$Sunday – Saturday
$0hour$00 – 23
$0minute$00 – 59
$0day$01 – 31 (two digit day format)
$0month$01 – 12 (two digit month format)
$monthName$Jan – Dec (three letter month format in English)
$fullMonthName$January – December
$ticks$milliseconds since midnight, January 1, 1970

Looking for a Dynamic Date in a Monitor’s Content Match
Say you have a web page that you want to check a timestamp on, to make sure it is being updated every day.  The content match search expression can be:
/Updated on $0month$\/$0day$\/$shortYear$/
The web page returned by the request could include the string:
Updated on 06/01/19
The content match would be successful if the webpage returned the current date when the monitor was run on June 1st, 2019. The match would fail if the content returned does not contain a string matching the current date.

Dates in the Future or the Past
If you want the time to be before or after the current time, you can add  $offsetMinutes=mmmm$ to the expression.  Simply specify the number of minutes into the future (positive number), or the number of minutes into the past (negative number).
For Example:
$offsetMinutes=20160$      = 20160 minutes, or 336 hours, or 14 days into the future.
$offsetMinutes=-20160$      = 14 days ago.
If the current day is June 1st, 2019, and the search expression is:
/$offsetMinutes=1440$Updated on $0month$\/$0day$\/$shortYear$/
the content string that would match would be one day in the future:
Updated on 06/02/19
You can use it in a URL monitor, File monitor, Log monitor, in almost any field that I’ve been able to find except the User-Generated SOAP XML field in the Web Service monitor.  For some reason, development has decided to not keep things consistent with the Web Service monitor.  That monitor sucks anyway.  Don’t use it.

Using Dynamic Dates in a Log Monitor
Here’s an example of me setting a log monitor to look for a filename that contains the date 24 hours ago.  I want this because I don’t care if the file exists or has log entries.  In this case,  I just want to make sure that yesterday’s file exists and contains entries.
s/\\hostname\/f$\/home\/ABC/$offsetMinutes=-1440$MY_APP_LOG_$0month$-$0day$-$shortYear$.log/

Using Dynamic Dates in a File Monitor
You can do the same with the file monitor.  I might have a monitor set to run at a specific time, after a backup job should have completed.  I can set the monitor to look for a file with today’s date, and if it doesn’t exist I could have it generate an alert:
s/\\hostname\/d$\/backups\/MY_DAILY_BACKUP.$year$$0month$$0day$/
Using Dynamic Dates in a URL Monitor’s URL As in the other examples, you just need to wrap the line in s/Your URL/, and replace your year, month, day, etc. with the correct date variable:
s/http://flightsearch.com/search.asp?SearchDate=$year$-$0month$-$0day$/

or
s/http://flightsearch.com/search.asp?$offsetMinutes=1440$SearchDate=$year$-$0month$-$0day$/
There doesn’t seem to be a way to include multiple offsetMinutes in a single line.  So, dynamic dates will have to be the same.  So, if you have a URL like this, that requires different dates in the future, I don’t know of a way to make them both dynamic and different.
s/http:\/\/flightsearch.com\/search.asp?$offsetMinutes=1440$Arrival=$year$-$0month$-$0day$&Departure=$year$-$0month$-$0day$/

becomes
 http://flightsearch.com/search.asp?Arrival=2015-07-01&Departure=2015-07-01

Using Dynamic Dates in a URL Monitor’s HTTP POST Data
In this example, I’ll show you how to use dynamic dates inside of the HTTP POST data field of a URL Monitor.  This is especially strange and not really documented.  This solution comes from a super helpful HP expert named Kenneth Gonzalez in the HP SiteScope forums.
To add dynamic dates, you’ll need to include the whole line within a Regex operation like this:
s|$offsetMinutes=20160$      "DepartDate": "$0month$/$0day$/$year$ "|
This will send the following line:
“DepartDate”: “07/04/2019”
NOTE: I’ve used pipes here to define the regex in this example, because the web service is using forward slashes to define the date.  I don’t recall if I had problems escaping the forward slashes, or if I was just too lazy to type the extra back slashes to escape them.  It should work either way.
Here’s how it looks in the HTTP Post data:
Custom-Header: Content-Type: application/json
Custom-Header: Method: POST
{
  "Trips": [
    {
      "Destination": "SAT",
      "Origin": "IAH",
s|$offsetMinutes=20160$      "DepartDate": "$0month$/$0day$/$year$ "|
    },
    {
      "Destination": "IAH",
      "Origin": "SAT",
s|$offsetMinutes=43200$      "DepartDate": "$0month$/$0day$/$year$ "|
    }
  ]
}


Ref. carlbrahms