A WordPress.com site dedicated to System Center and Cloud Management

Posts tagged ‘System Center Operations Manager’

SCOM Technical Preview in a LAB – Installation Guide (Install SCOM)


Install System Center Operations Manager Technical Preview

In my Lab example, I am using the following:

  • Windows Server Technical Preview
  • SQL Server 2014
  • Web Server (IIS)

These have been setup as per my previous guides for the OS and SQL setup.

IMPORTANT: In order to evaluate the System Center Technical Preview, you MUST be using the Windows Server Technical Preview, and SQL Server 2014; as per the following TechNet article: http://technet.microsoft.com/en-us/library/dn806369.aspx.

Install SCOM

Start by copying the EXE file into the SCOM VM. As of this writing, the Technical Preview EXE is labelled as “en_system_center_technical_preview_operations_manager_x86_x64_5650266.exe“.

Start by running the EXE, on the first screen, click Next.

SCOM vNext - 01 - Setup Wizard

On the Location screen, choose the location to extract the installation files, then click Next.

SCOM vNext - 02 - Location

On the Ready to Extract screen, click Extract.

SCOM vNext - 03 - Extract

On the completion screen, click Finish.

SCOM vNext - 04 - Complete

Once the files are extracted, start the installation by running Setup.exe.

On the splash screen click the Install link.

SCOM vNext - 06 - Splash Screen

On the Select Features screen, select the feature you want to install. In our example, we are installing all features on  the same server, so we will select all of them and click Next.

SCOM vNext - 07 - Select Features

Next chose the location that you want to install the software to, and ensure there is enough space. Then click Next.

SCOM vNext - 08 - Install Location

The Setup Wizard will then check the prerequisites that are needed, based on what features you selected to install. If there are any issues you will need to address these before you can continue. Review the information and the resolution(s) provided.

For example, you will need to install the Web Server (IIS) role, including some non-default elements along with the Microsoft Report Viewer 2012 Redistributable Package.

Once you address all prerequisite needs, the setup wizard should appear as follows. Click Next.

SCOM vNext - 09 - Prereqs

On the Installation Option screen, choose the appropriate option. In our example, since this is the first Management Server that we are installing, we will choose the ‘Create the first Management server in a new management group’ option, and also enter a Management Group Name, then click Next.

SCOM vNext - 10 - Management Group

Next read and accept the license terms, and click Next.

SCOM vNext - 11 - License Terms

On the Configure Operational Database screen, fill in the SQL server and instance name. When you do, the data and log folders paths will auto-populate. Now click Next.

SCOM vNext - 12 - Operational Database

On the Configure Data Warehouse screen, fill in the SQL server and instance name. When you do, the data and log folders paths will auto-populate. Now click Next.

SCOM vNext - 13 - Data Warehouse Database

Next select a SQL server instance to use for the Reporting Services, then click Next.

SCOM vNext - 14 - Reporting Services

Next select the IIS website to use for the Web Console, and then click Next. Note: if you chose to use SSL, you will need a certificate already installed/configured in IIS.

SCOM vNext - 15 - Web Console

For the Authentication Mode, chose the applicable option based on how you plan on using the web console. For our example, we will only use it in an Intranet environment, so we will choose ‘Use Mixed Authentication’ and click Next.

SCOM vNext - 16 - Authentication Mode

For the Operations Manager accounts, fill in the appropriate information and click Next. Note: As part of your preparation for installing SCOM, you can follow your provisioning process and have these accounts pre-created. You should also take note of the level of access each account requires.

SCOM vNext - 17 - Accounts

You can choose if you want to participate in the Customer Experience Improvement Program (CEIP). Make your choices, and then click Next.

SCOM vNext - 18 - Help Improve

For the Microsoft Update screen, choose if you want to automatically apply updates. Note: In a Production environment, you will probably not want to turn this on, because there are applicable change management procedures to follow, and you should test updates in a non-Production environment.

SCOM vNext - 19 - Microsoft Update

On the Installation Summary screen, review the input and selections made, and click Install.

SCOM vNext - 20 - Summary

The installation may take several minutes, but once it has been completed, click Close. Note: If you do not want to launch the SCOM console immediately, then de-select the ‘Start the Operations console when the wizard closes’ checkbox.

SCOM vNext - 21 - Setup Complete

Congratulations, you have now successfully installed SCOM!

As you can see from the About screen, the version of SCOM, even though it shows “System Center 2012 R2”, the version is: 7.2.10015.0 (whereas the actual 2012 R2 product is version 7.1.10226.0).

SCOM vNext - 22 - About

At this point, I haven’t noticed anything new/different with the product. However, as the product is updated, I will keep you informed of any interesting and important changes.

NOTE: The following features have been removed from the System Center Technical Preview, as per the following TechNet article: http://technet.microsoft.com/en-ca/library/dn806370.aspx.

  • Visio based Management Pack Authoring for Operations Manager
    • Status in System Center Technical Preview: Removed.
    • Replacement: Use the complimentary version of Silect’s MP Author to design and develop MPs for Operations Manager or customize existing MPs.

Release Note Issues (as per http://technet.microsoft.com/en-us/library/dn806369.aspx)

See the referenced TechNet article for workarounds.

  • The Management Catalog does not return Management Packs
  • PowerShell Run space failed to start
  • Using sudo elevation with Solaris operating systems requires a configuration change if sudo executable is not in an expected path
  • Namespace value for performance tracking will be ignored
  • Monitor the Windows Server Technical Preview Release
Advertisements

SCOM 2012 R2 Data Access Service (DAS) High Availability – Part 4: Enable NLB on each Management Server > Add A Host to NLB Cluster


In the previous post in this mini-series, we created a NLB cluster, and added the first SCOM Management Server. Now we will add the second SCOM Management Server to the cluster.

Use the following procedure to add hosts to a Network Load Balancing (NLB) cluster.

You can also perform the task described in this procedure by using Windows PowerShell. For more information about using Windows PowerShell for NLB clusters, see http://go.microsoft.com/fwlink/?LinkId=140180.

When you are using Network Load Balancing (NLB) Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running NLB Manager from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

To ensure that Network Load Balancing Manager is displaying the most recent host information, right-click the cluster and click Refresh. This step is necessary because the host properties that Network Load Balancing Manager displays are a copy of the host properties that were configured the last time Network Load Balancing Manager connected to that host. When you click Refresh, Network Load Balancing Manager reconnects to the cluster and displays updated information.

As a reminder, we’ll break the articles/posts down into smaller pieces. Here is a high-level of each piece.

Step 1: Configure A Static IP Address

Step 2: Enable NLB on each Management Server > Install Network Load Balancing

Setp 3: Enable NLB on each Management Server > Create A NLB Cluster

Setp 4: Enable NLB on each Management Server > Add A Host to NLB Cluster

 

Let’s continue with the fourth step.

Enable NLB on each Management Server > Add A Host to NLB Cluster

Now that we have a Network Load Balance Cluster created, we can now add the second SCOM Management server to the cluster.

Let’s log into our first Management Server to begin.

 

Start by launching Server Manager, click on Tools, then click Network Load Balancing Manager.

Server Manager - Launch NLB Manager

 

Right-click the cluster where you want to add the host and choose Add Host To Cluster. If NLB Manager does not list the cluster, connect to the cluster.

Add Host To Cluster

 

Type the host’s name and click Connect. The network adapters that are available on the host will be listed at the bottom of the dialog box.

Add Host To Cluster - Connect

 

Click the network adapter that you want to use for Network Load Balancing and then click Next. The IP address configured on this network adapter will be the dedicated IP address for this host.

Add Host To Cluster - Connect2

 

Configure the remaining host parameters as appropriate, and then click Finish.

Host Parameters

Port Rules

 

Now our second Management Server has been added into the NLB Cluster.

Network Load Balancing Manager

 

When you launch the SCOM Console, enter the NLB Cluster name instead of a specific Management Server.

SCOM Console - Connect To Server

 

We have now successfully made the SCOM Data Access Service highly available.

SCOM 2012 R2 Data Access Service (DAS) High Availability – Part 3: Enable NLB on each Management Server > Create A NLB Cluster


In the previous post in this mini-series, we installed the Network Load Balancing feature on each of our Management Servers. Now we will create a NLB cluster.

To configure the Network Load Balancing (NLB) cluster, you must configure three types of the parameters:

  • Host parameters, which are specific to each host in a NLB cluster.
  • Cluster parameters, which apply to an NLB cluster as a whole.
  • Port rules, which control how the cluster functions. By default, a port rule equally balances all TCP/IP traffic across all servers. Some applications may require different or additional port rules to operate correctly. For example, when using NLB in a Remote Desktop Services environment, you will need to modify these default rules.

You can also perform the task described in this procedure by using Windows PowerShell. For more information about using Windows PowerShell for NLB clusters, see http://go.microsoft.com/fwlink/?LinkId=140180.

When you are using Network Load Balancing (NLB) Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running NLB Manager from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

As a reminder, we’ll break the articles/posts down into smaller pieces. Here is a high-level of each piece.

Step 1: Configure A Static IP Address

Step 2: Enable NLB on each Management Server > Install Network Load Balancing

Setp 3: Enable NLB on each Management Server > Create A NLB Cluster

Setp 4: Enable NLB on each Management Server > Add A Host to NLB Cluster

 

Let’s continue with the third step.

Enable NLB on each Management Server > Create A NLB Cluster

Now that the Network Load Balance feature is installed on each Management Server, we can now create a cluster.

Let’s log into our first Management Server to begin.

 

Start by launching Server Manager, click on Tools, then click Network Load Balancing Manager.

Server Manager - Launch NLB Manager

 

Right-click Network Load Balancing Clusters, and then click New Cluster.

NLB Manager - New Cluster
To connect to the host that is to be a part of the new cluster, in the Host text box, type the name of the host, and then click Connect.

NLB Manager - New Cluster - Connect

 

Select the interface that you want to use with the cluster, and then click Next. (The interface hosts the virtual IP address and receives the client traffic to load balance.)

NLB Manager - New Cluster - Select Interface

 

In Host Parameters, select a value in Priority (Unique host identifier). This parameter specifies a unique ID for each host. The host with the lowest numerical priority among the current members of the cluster handles all of the cluster’s network traffic that is not covered by a port rule.

You can override these priorities or provide load balancing for specific ranges of ports by specifying rules on the Port rules tab of the Network Load Balancing Properties dialog box.

In Host Parameters, you can also add dedicated IP addresses, if necessary.

Click Next to continue.

NLB Manager - New Cluster - Host Parameters
In Cluster IP Addresses, click Add and type the cluster IP address that is shared by every host in the cluster. NLB adds this IP address to the TCP/IP stack on the selected interface of all hosts that are chosen to be part of the cluster.

NOTE: NLB does not support Dynamic Host Configuration Protocol (DHCP). NLB disables DHCP on each interface that it configures, so the IP addresses must be static.

Click Next to continue.

NLB Manager - New Cluster - Cluster IP Addresses

NLB Manager - New Cluster - Cluster IP Addresses (Completed)
In Cluster Parameters, select values in IP Address and Subnet mask (for IPv6 addresses, a subnet mask value is not needed). Type the full Internet name that users will use to access this NLB cluster.

In Cluster operation mode, click Unicast to specify that a unicast media access control (MAC) address should be used for cluster operations. In unicast mode, the MAC address of the cluster is assigned to the network adapter of the computer, and the built-in MAC address of the network adapter is not used. It is recommend that you accept the unicast default settings.

Click Next to continue.

New Cluster - Cluster Parameters

 

In Port Rules, click Edit to modify the default port rules, if needed. Then click Finish.

New Cluster - Port Rules

 

Back in the Network Load Balancing Manager, the new cluster will appear with the IP Address assigned, and the host we added will show as started.

NLB Manager (Completed)

 

Now our first Management Server has been added into the NLB Cluster.

In the next post in this series, we will move onto Step 4: Enable NLB on each Management Server > Add A Host to NLB Cluster.

Tag Cloud

%d bloggers like this: