Archive

Archive for the ‘OpsMgr 2012’ Category

Operations Manager 2007, 2007R2, 2012, 2012SP1, 2012R2 Hotfixes

August 12, 2014 Leave a comment

Below are the hotfixes and cumulative updates for all versions of Operations Manager and the versions to which they apply.

This post will be continuously updated as new hotfixes become available. Some of these updates are required based on certain conditions. I do not recommend installing each and every single one of these. Please read the KB article and install them only if you are experiencing the problem described in the KB article.

Last Updated 3/20/2015

 

Operations Manager 2007/R2

KB Article Description Applies to Last Revision Date
958936 System Center Operations Manager 2007 cannot receive SNMP trap data when you use a Windows Server 2008-based computer or a Windows Vista-based computer as a proxy agent for SNMP devices January 16, 2015 – Revision: 3.0
960363 Charts in a performance report are incorrectly scaled, or a report that contains multiple charts does not display the charts in the correct order in System Center Operations Manager 2007 SP1 Last Review: January 15, 2015 – Revision: 3.0
936838 After a System Center Operations Manager 2007 agent sends discovery data to a management group, no rules are deployed for monitoring in later management groups Microsoft System Center Operations Manager 2007 January 15, 2015 – Revision: 3.0
936481 You cannot install the System Center Operations Manager 2007 Reporting feature in a disjointed namespace environment Microsoft System Center Operations Manager 2007 January 16, 2015 – Revision: 6.0
938505 Some report information does not appear in Japanese in the Japanese version of System Center Operations Manager 2007 Microsoft System Center Operations Manager 2007 January 14, 2015 – Revision: 3.0
938510 You cannot obtain elevated user rights in management servers and in agents in System Center Operations Manager 2007 or System Center Essentials 2007 environments Microsoft System Center Operations Manager 2007 January 16, 2015 – Revision: 2.0
939585 Some SSL Monitoring monitors display an incorrect status or an incorrect name in System Center Operations Manager 2007 Microsoft System Center Operations Manager 2007 January 15, 2015 – Revision: 3.0
941557 Management servers that are running the release version of System Center Operations Manager 2007 do not process the agent event data from an agent of System Center Operations Manager 2007 Service Pack 1 Microsoft System Center Operations Manager 2007 January 16, 2015 – Revision: 4.0
941811 A memory leak occurs if an agent of the release version of Microsoft System Center Operations Manager 2007 reports to System Center Operations Manager 2007 Service Pack 1 management servers Microsoft System Center Operations Manager 2007 January 15, 2015 – Revision: 2.0
941977 You receive error messages when you try to edit the Web application monitoring settings in System Center Operations Manager 2007 Microsoft System Center Operations Manager 2007 January 15, 2015 – Revision: 2.0
945312 The OpsMgr Health service may incorrectly display the health state of the cluster nodes in System Center Operations Manager 2007 Microsoft System Center Operations Manager 2007 January 15, 2015 – Revision: 2.0
949875 When you run a task in the System Center Operations Manager 2007 Operations Console on a Russian version of Windows Server 2003, the task outputs are displayed in corrupted text Microsoft System Center Operations Manager 2007 January 15, 2015 – Revision: 4.0
949969 Some data partition tables that exceed the data retention period are not groomed from the Audit Collection Services database in Operations Manager 2007 Microsoft System Center Operations Manager 2007 January 16, 2015 – Revision: 3.0
951148 You cannot install Operations Manager 2007 Reporting if the SQL Server Reporting Services instance takes more than 60 seconds to start Microsoft System Center Operations Manager 2007 January 16, 2015 – Revision: 4.0
2878378 OpsMgr 2012 or OpsMgr 2007 R2 generates a “Heartbeat Failure” message and then goes into a greyed out state in Windows Server 2008 R2 SP1
2590414 You are prompted for the latest version of the Microsoft.SystemCenter.Library management pack when you try to edit a new management pack in Operations Manager 2007 R2
950853 A memory leak occurs when you monitor Exchange Server 2007 by using the MOM 2007 agent in System Center Operations Manager 2007 Microsoft System Center Operations Manager 2007 Service Pack 1 January 15, 2015 – Revision: 3.0
951527 Modifications that you try to make to a Web application that was created before you upgrade Microsoft System Center Operations Manager 2007 are not saved Microsoft System Center Operations Manager 2007 Service Pack 1, when used with:Microsoft System Center Operations Manager 2007 January 16, 2015 – Revision: 3.0
951529 System Center Operations Manager 2007 runs scripts in the Rule Name field or in the Description field Microsoft System Center Operations Manager 2007 

Microsoft System Center Operations Manager 2007 Service Pack 1

January 16, 2015 – Revision: 3.0
951380 Some computer properties for a cluster node may not be collected by the discovery process in System Center Operations Manager 2007 Service Pack 1 Microsoft System Center Operations Manager 2007Service Pack 1, when used with:

Microsoft System Center Operations Manager 2007

January 16, 2015 – Revision: 3.0
952857 The Custom Event Report does not list the GenericLog-type events in System Center Operations Manager 2007 Service Pack 1 Microsoft System Center Operations Manager 2007 Service Pack 1 January 15, 2015 – Revision: 3.0
952937 The relative date picker returns wrong dates when you run a report in a month that has less days than the previous month in System Center Operations Manager 2007 Microsoft System Center Operations Manager 2007 

Microsoft System Center Operations Manager 2007 Service Pack 1

January 15, 2015 – Revision: 3.0
953817 The Administrator Console exits when you try to use the “Set Resolution State” option for an alert that is generated in System Center Operations Manager 2007 Microsoft System Center Operations Manager 2007 Service Pack 1 January 16, 2015 – Revision: 4.0
954643 Event ID 31569 is logged after you install a management pack that includes reports on a System Center Operations Manager 2007 SP1 server or on a System Center Essentials 2007 SP1 server Microsoft System Center Operations Manager 2007 Service Pack 1 June 21, 2014 – Revision: 2.0
954823 A custom event report does not display events that are generated by the generic CSV text log collection rules when Parameter 1 to Parameter 20 is included in the Report Field criteria in System Center Operations Manager 2007 Service Pack 1 (SP1) Microsoft System Center Operations Manager 2007 Service Pack 1 January 15, 2015 – Revision: 3.0
956172 The CcmExec.exe process crashes on a Windows 2000-based computer if both a System Center Operations Manager 2007 Service Pack 1 agent and a System Center Configuration Manager 2007 client are installed on this computer Microsoft System Center Operations Manager 2007 Service Pack 1 January 16, 2015 – Revision: 3.0
956240 The SQL Server process may consume lots of CPU resources on the server that hosts the Operations Manager 2007 database after you make Operations Manager 2007 configuration changes Microsoft System Center Operations Manager 2007 Service Pack 1 January 16, 2015 – Revision: 3.0
957123 Hotfix for System Center Operations Manager 2007 SP1 enables monitoring support for IIS 7.0 Microsoft System Center Operations Manager 2007 Service Pack 1 January 16, 2015 – Revision: 3.0
957135 You cannot change the alert resolution state of any alert in the Active Alerts view in System Center Operations Manager 2007 Service Pack 1 Microsoft System Center Operations Manager 2007 Service Pack 1 January 15, 2015 – Revision: 4.0
957199 The System Center Operations Manager 2007 Service Pack 1 operations console cannot display English product knowledge when you open the properties dialog box of an alert: “No product knowledge was available for this Alert” Microsoft System Center Operations Manager 2007 Service Pack 1 January 16, 2015 – Revision: 3.0
957511 Warning alerts and warning monitor state changes do not occur as expected for a Web application that is created by using the Web application template in System Center Operations Manager 2007 Service Pack 1 Microsoft System Center Operations Manager 2007 Service Pack 1 January 16, 2015 – Revision: 4.0
959867 You cannot specify a management pack to store a new override of a monitor or of a rule in the Operations console in System Center Operations Manager 2007 Service Pack 1 Microsoft System Center Operations Manager 2007 Service Pack 1 January 15, 2015 – Revision: 3.0
963005 The Add Object Wizard displays only 500 objects even if more objects exist in System Center Operations Manager 2007 Service Pack 1 Microsoft System Center Operations Manager 2007 Service Pack 1 January 15, 2015 – Revision: 3.0
968082 Error message when you add an agent assignment rule in the System Center Operations Manager 2007 if an Active Directory domain name begins with a numeric digit: “XSD verification failed for management pack” Microsoft System Center Operations Manager 2007 Service Pack 1 January 16, 2015 – Revision: 3.0
969130 The size of the System Center Operations Manager 2007 Service Pack 1 Data Warehouse database may grow if many event collection rules exist within management packs Microsoft System Center Operations Manager 2007 Service Pack 1 January 15, 2015 – Revision: 4.0
970533 The Product Knowledge tab is displayed as the Company Knowledge tab after you import a Language Pack for System Center Operations Manager 2007 Service Pack 1 Microsoft System Center Operations Manager 2007 Service Pack 1 January 16, 2015 – Revision: 2.0
2028594 Description of System Center Operations Manager 2007 Cumulative Update 1 Microsoft System Center Operations Manager 2007 Service Pack 1 July 31, 2010 – Revision: 2.0
2878378 OpsMgr 2012 or OpsMgr 2007 R2 generates a “Heartbeat Failure” message and then goes into a greyed out state in Windows Server 2008 R2 SP1 Microsoft System Center Operations Manager 2007 Service Pack 1 April 17, 2014 – Revision: 3.2
Operations Manager 2007 R2 Cumulative Updates
979257 System Center Operations Manager 2007 R2 Cumulative Update 2
2251525 System Center Operations Manager 2007 R2 Cumulative Update 3
2449679 System Center Operations Manager 2007 R2 Cumulative Update 4
2495674 System Center Operations Manager 2007 R2 Cumulative Update 5
2626076 System Center Operations Manager 2007 R2 Cumulative Update 6
2783850 System Center Operations Manager 2007 R2 Cumulative Update 7

 

Operations Manager 2012/R2

 

RTM Description Applies to Last Revision Date
2878378 OpsMgr 2012 or OpsMgr 2007 R2 generates a “Heartbeat Failure” message and then goes into a greyed out state in Windows Server 2008 R2 SP1    
2674695 System Center Operations Manager 2012 Update Rollup 1
2731874 System Center Operations Manager 2012 Update Rollup 2
2756127 System Center Operations Manager 2012 Update Rollup 3
2785681 System Center Operations Manager 2012 Update Rollup 4
2822776 System Center Operations Manager 2012 Update Rollup 5
  Update rollups 6 & 7 did not contain any updates for Operations Manager    
2878378 OpsMgr 2012 or OpsMgr 2007 R2 generates a “Heartbeat Failure” message and then goes into a greyed out state in Windows Server 2008 R2 SP1
Operations Manager 2012 SP1 Cumulative Updates
2785682 System Center Operations Manager 2012 SP1 Update Rollup 1
2802159 System Center Operations Manager 2012 SP1 Update Rollup 2
2836751 System Center Operations Manager 2012 SP1 Update Rollup 3
2879276 System Center Operations Manager 2012 SP1 Update Rollup 4
2904730 Description of System Center 2012 Service Pack 1 Update Rollup 5
2929885 Description of Update Rollup 6 for System Center 2012 Operations Manager Service Pack 1
2965420 Update Rollup 7 for System Center 2012 Operations Manager Service Pack 1
2991997 Update Rollup 8 for System Center 2012 Operations Manager Service Pack 1 
3023167 Description of Update Rollup 9 for System Center 2012 Operations Manager Service Pack 1
Operations Manager 2012 R2 Cumulative Updates
2904734 Description of Update Rollup 1 for System Center 2012 R2
2929891 Description of Update Rollup 2 for System Center 2012 R2 Operations Manager
2965445  Update Rollup 3 for System Center 2012 R2 Operations Manager    
2992020 Update Rollup 4 for System Center 2012 R2 Operations Manager
3023138 Description of Update Rollup 5 for System Center 2012 R2 Operations Manager

 

 

Categories: OpsMgr 2012

Operations Manager Hotfixes and Cumulative Updates for all versions

December 5, 2013 1 comment

Below are the hotfixes and cumulative updates for all versions of Operations Manager and the versions to which they apply.

This post will be continuously updated as new hotfixes become available. Some of these updates are required based on certain conditions. I do not recommend installing each and every single one of these. Please read the KB article and install them only if you are experiencing the problem described in the KB article.

Last Updated 7/30/2014

2007 RTM

2878378 OpsMgr 2012 or OpsMgr 2007 R2 generates a “Heartbeat Failure” message and then goes into a greyed out state in Windows Server 2008 R2 SP1

2007 SP1

Hotfixes

2878378 OpsMgr 2012 or OpsMgr 2007 R2 generates a “Heartbeat Failure” message and then goes into a greyed out state in Windows Server 2008 R2 SP1

954643Event ID 31569 is logged after you install a management pack that includes reports on a System Center Operations Manager 2007 SP1 server or on a System Center Essentials 2007 SP1 server

Cumulative Updates

2028594 Description of System Center Operations Manager 2007 Cumulative Update 1

2007 R2 RTM

Hotfixes

2878378 OpsMgr 2012 or OpsMgr 2007 R2 generates a “Heartbeat Failure” message and then goes into a greyed out state in Windows Server 2008 R2 SP1

2590414 You are prompted for the latest version of the Microsoft.SystemCenter.Library management pack when you try to edit a new management pack in Operations Manager 2007 R2

Cumulative Updates

979257   System Center Operations Manager 2007 R2 Cumulative Update 2

2251525 System Center Operations Manager 2007 R2 Cumulative Update 3

2449679 System Center Operations Manager 2007 R2 Cumulative Update 4

2495674 System Center Operations Manager 2007 R2 Cumulative Update 5

2626076 System Center Operations Manager 2007 R2 Cumulative Update 6

2783850 System Center Operations Manager 2007 R2 Cumulative Update 7

2012 RTM

Hotfixes

2878378 OpsMgr 2012 or OpsMgr 2007 R2 generates a “Heartbeat Failure” message and then goes into a greyed out state in Windows Server 2008 R2 SP1

Cumulative Updates

2674695 System Center Operations Manager 2012 Update Rollup 1

2731874 System Center Operations Manager 2012 Update Rollup 2

2756127 System Center Operations Manager 2012 Update Rollup 3

2785681 System Center Operations Manager 2012 Update Rollup 4

2822776 System Center Operations Manager 2012 Update Rollup 5

Update rollups 6 & 7 did not contain any updates for Operations Manager.

2012 SP1

Hotfixes

2878378 OpsMgr 2012 or OpsMgr 2007 R2 generates a “Heartbeat Failure” message and then goes into a greyed out state in Windows Server 2008 R2 SP1

Cumulative Updates

2785682 System Center Operations Manager 2012 SP1 Update Rollup 1

2802159 System Center Operations Manager 2012 SP1 Update Rollup 2

2836751 System Center Operations Manager 2012 SP1 Update Rollup 3

2879276 System Center Operations Manager 2012 SP1 Update Rollup 4

2904730 Description of System Center 2012 Service Pack 1 Update Rollup 5

2929885 Description of Update Rollup 6 for System Center 2012 Operations Manager Service Pack 1

2965420 Update Rollup 7 for System Center 2012 Operations Manager Service Pack 1

 

 

 

2012 R2 RTM

Hotfixes

2878378 OpsMgr 2012 or OpsMgr 2007 R2 generates a “Heartbeat Failure” message and then goes into a greyed out state in Windows Server 2008 R2 SP1

Cumulative Updates

2904734 Description of Update Rollup 1 for System Center 2012 R2

2929891 Description of Update Rollup 2 for System Center 2012 R2 Operations Manager

2965445 Update Rollup 3 for System Center 2012 R2 Operations Manager

 

Categories: OpsMgr 2012

Creating OpsMgr 2012 Gateway Server Certificates

November 13, 2013 4 comments

This post will provide step by step instructions on acquiring and importing the Root CA from the Domain where Operations Manager resides, and importing into the Gateway certificate store. This section also details how to request and apply a certificate for the Gateway server.

Prerequisites

  • Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
  • Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012, or Windows Server 2012 Core Installation.
  • Processor Architecture: must be x64.
  • Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell version 3.0.
  • Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required for the management server.
  • .NET 3.51 SP1
  • .NET Framework 4 is required if the Gateway server manages UNIX/Linux agents or network devices.

Installation

Create the Operations Manager Gateway Certificate

This section will provide the process of how to create a certificate to use for the Gateway server(s).

Perform the following steps on the PKI Certificate Server.

Open the Certification Authority program. Expand the CA Server, right click Certificate Templates and select Manage.

The Certificate Templates window will open. Right click IPSec (Offline request) and select Duplicate Template.

The Duplicate Template window will open. Keep the default selection Window Server 2003 Enterprise. Click OK.

The Properties of the New Template window will open. In the Template display name field type in Operations Manager 2012 Gateway Certificate. The Template name will duplicate what is typed in above. Keep the Validity period at 2 years and Renewal period at 6 weeks. Click on the Request Handling tab.

Select Allow private key to be exported.

Click on the Security tab.

Click on Authenticated Users. Check Enroll. Click on the Extensions tab.

Select Application Policies and click Edit.

Remove IP security IKE intermediate. Click Add

Add Client Authentication and Server Authentication. Click OK.

Click OK to close out of the Properties of New Template.

Notice the newly created template. Close out of the Certificate Templates Console.

From the Certificate Authority, right click Certificate Templates. Select New and select Certificate Template to Issue.

The Enable Certificate Templates window will open. Locate the Operations Manager 2012 Gateway Certificate template. Click OK.

The Certificate is ready for issuing. Close out of the Certificate Authority.

Request the Operations Manager Certificate for the Management Server

On the Management Server, we also need to install a certificate. Since we have an Enterprise Root CA, integrated with AD, the root CA certificate is already trusted by our Management Server who is a domain member. This section will walk through requesting the Operations Manager 2012 Gateway certificate.

Perform the following steps on the Management Server.

Open the Local Computer certificate store on the management server.

Import the certificate that was created earlier. Select Request New Certificate

The Certificate Enrollment window will open. Click Next.

The Select Certificate Enrollment Policy window will open. Select Active Directory Enrollment Policy. Click Next

The extra information needed is the Common Name in the first box (opsmgr.lab.ad) and the FQDN in the bottom box with DNS.

Fill in the values and click add under Subject Name and Alternative name.

Type: Common Name:opsmgr.lab.ad

Alternate Name:

Type: DNS: opsmgr.lab.ad

Click OK

Click Enroll

Verify the status succeeded. Click Finish.

The certificate now appears in the Local Computer Personal Certificates Store

Request the Operations Manager Certificate for the Gateway Server

The gateway is not part of the same domain as Operations Manager. And does not trust the Enterprise CA by default. The process below will walk through getting and installing the Root CA certificate from the AD CS.

Perform the following steps on the Gateway Certificate Server.

Open an MMC.

Open the Add or Remove Snap-ins. Select Certificates. Click Add.

The Certificates snap-in window will open. Select Computer account. Click Next.

The Select Computer window will open. Select Local computer. Click Finish.

Repeat the process to add the current user account.

The Certificates snap-in window will open. Select My user account. Click Finish.

Notice both the Certificates (LocalComputer) and Certificates – Current User are listed in the Selected snap-ins column. Click OK.

Expand Trusted Root Certification Authorities. Notice the certificate from the Root CA needs to be added to the Trusted Root Certification Authorities list.

Open a web browser on the Gateway Server, and browse to the Microsoft Active Directory Certificate Services website on the Domain:

http://certificateserver/certsrv Select Download a CA certificate, certificate chain or CRL.

The Web Access Confirmation windows will open. Click Yes.

The Download a CA Certificate, Certificate chain, or CRL window will open. Select Base 64. Click Download CA certificate chain

The File download window will open. Click Save.

Save the file to a location that is easily accessible. Click Save.

Within the MMC import the certificate into the local computer.

The Certificate Import Wizard window will open. Click Next.

Browse to the saved location. Change the file type to PKCS #7 Certificates. Click Open

The file should appear in the File name field. Click Next.

The Certificate will be placed in the Trusted Root Certification Authorities. Click Next.

Click Finish to import the Root Certificate.

The Certificate is now in the list. This means the Gateway Server will trust certificates issued by the Enterprise Root CA.

The Steps below will walk through creating a requesting the Operations Manager Certificate for the gateway server.

Request a Certificate from the CA

Note: For target servers running W2K3, do the following steps from that machine; if target is W2K8, run the following from a W2K3 server instead

Open Internet Explorer and browse to http://<cert server>/certsrv

Select Request a certificate

The Request a Certificate webpage will open.

Select advanced certificate request

The Advanced certificate request webpage will open. Select Create and submit a request to this CA.

Select the template that was created earlier, and fill in the Name and Friendly Name fields with the FQDN of the Gateway Server.

If the Gateway server is in a workgroup, the NetBIOS name is sufficient.

Ensure the Request Format is PKCS10. Click Submit

The Certificate is now generated. Click on Install Certificate.

The Certificate has been successfully installed. Note: this is saved to the Personal certificate store.

We need to authenticate computers, and the certificate is imported in the Personal certificate store. Open the Certificates MMC and copy the certificate from the personal store to the local computer store.

The certificate will now reside in the Local Computer Certificates Store.

The certificate is now installed and you can verify everything is installed correctly by opening the certificate and checking if the certification path is ok.

Import the MOMCertImport to the Management Server

This section provides step-by-step instructions on importing the certificate to the Management Server using the MOMCertImport.exe utility.

Perform the following steps on the Management Server virtual machine.

Copy the MOMCertImport.exe tool from the installation media to the gateway server, into the gateway installation path (IE: D:\Program files\System Center 2012\ Operations Manager\Server).

From the Management Server, browse to the Local Computer Certificate store. Under personal select the certificate and choose Export.

The Certificate Export Wizard window will open. Click Next.

The Export Private Key window will open. Click Yes, export the private key. Click Next.

The Export File Format windows will open. Ensure Export all extended properties is checked. Click Next

The Password window will open. Type and confirm a password. Click Next.

Specify a name and location to save the exported certificate to that is easily accessible. Click Next.

Click Finish to complete the export.

The Certificate Export Wizard window will open. Verify the export was successful. Copy the file to a location that is accessible to the Gateway Server. Click OK.

Open a command prompt with
Administrator Credentials on the Management server. Browse to the installation folder on the Gateway
Server and run tine following command:

Momcertimport.exe D:\Sources\Certificates\opsmgr.pfx

A prompt will appear to Enter certificate password. Enter the certificate password. Hit Enter.

After a few moments, a message will appear. Verify Successfully installed the certificate. Please Check Operations Manager in event viewer to check channel connectivity appears. Close out of the command prompt window

Import the MOMCertImport on Gateway Server

Perform the following steps on the Gateway Server virtual machine.

Copy the MOMCertImport.exe tool from the installation media to the gateway server, into the gateway installation path.

From the Management Server, browse to the Local Computer Certificate store. Under personal select the certificate and choose Export.

The Certificate Export Wizard window will open. Click Next.

The Export Private Key window will open. Click Yes, export the private key. Click Next.

The Export File Format windows will open. Ensure Export all extended properties is checked. Click Next

The Password window will open. Type and confirm a password. Click Next.

Specify a name and location to save the exported certificate.

Click Finish to complete the export.

Verify the export was successful. Copy the file to a location that is accessible to the Gateway Server.

Open a command prompt on the Management Server. Browse to the gateway installation folder and run tine following command:

Momcertimport.exe D:\Sources\Certificates\OpsMgrMS01.pfx

Enter the certificate password.

Verify the certificate installed successfully.

Approve Gateway to communicate with the Management sever

Perform the following steps on the Management Server virtual machine.

Browse the installation media to Supporttools\AMD64.

Select the Microsoft.EnterpriseManagement.GatewayApprovalTool.exe and Microsoft.EnterpriseManagement.GatewayApprovalTool.exe.CONFIG files and Copy

Paste the files to the Operations Manager\Setup folder. (IE: D:\Program Files\System Center 2012\Operations Manager\Setup)

Open a Command Prompt with Run as Administrator

Browse to the Operations Manager installation folder. Configure the command line to match below:

MICROSOFT.ENTERPRISEMANAGEMENT.GATEWAYAPPROVALTOOL.EXE /managementservername=opsmgr.lab.ad /gatewayname=dc01.lab.ad /Action=Create

The process will take a few minutes to complete.

If the approval is successful, you will see the approval of server <GatewayFQDN> completed successfully.

Install Gateway Server

Perform the following steps on the Gateway Management Server virtual machine.

Browse to the media source. Locate the Autorun.exe and double click on it to start the install. The Systems Center Configuration Manager window will open. Select Gateway management server

The Operations Manager Gateway Server Setup window will open.

The Destination Folder window will open. Specify the installation folder. Click Next.

The Management Group Configuration window will open. Specify the information: Click Next.

The Gateway Action Account window will open. Select the type of Action Account to gather the operational data. Local System. Click Next.

The Microsoft Update window will open. Select whether or not to provide feedback. Click Next.

The Ready to Install window will open. Review the installation settings. Click Install.

The installation will take a few Moments to complete.

Click Finish.

Troubleshooting

Perform the following steps on the Gateway Management Server virtual machine.

If an event ID 21006 appears, make sure the firewalls on the gateway and/or on the management server are not blocking communication

Select Allow this server to act as a proxy and discover managed objects on other computers. This one will act as a proxy for other systems that will connect trough the gateway server.

Categories: OpsMgr 2012