SCOM Zombie PSA#13: Zombie Instructions: Installing SQL 2008 R2

 

• I am not a SQL expert, but this the process that I used to establish my Operations Manager 2012 Beta.
• Launch the setup.exe as administrator
• I always like to do checks first to verify that I do not run into problems during the installations so on the SQL Server Installation Center click on Tools & run the System Configurations Checker. If you failed any of the requirements, take care of them now & then come back.
• Installation select New installation or add features to an existing installation.
• The system will first validate the installation process. If you have any errors, correct them first before moving on

• The next screen that will appear is the Product Key. Apply the key and move on.
• Once you decide accept and agree to the License Terms and select Next to move on.
• On the Support File window select the Install button. The setup will install the Setup Support Files. The window may disappear for a second or two

• The warning that I get is because the firewall is turned on. However Since I’ve applied my firewall settings via my Domain Policy, I should be good.

• I have select SQL Server Feature Installation for Operations Manager 2012.

• I am choosing everything for now. I did change the default location since I do not want this installed on my C drive.

• Everything passed or skipped. verify that everything is correct, resolve any errors and then re-run the test.

• I changed the directory once again, and placed it somewhere else other than the C Drive.

• Disk Space validated

• Established NT Authority/Network Service as a default right now.

• I ended up adding my user account to the administrators.

• I’ve added my action and sdk service & my user account.

• Default configurations for the Reporting services

• Next

• Installation Configuration Rules verifications. Again, correct any issues.

• Ready to Install now, the only thing that I was not able  to modify was this part since I do not want anything installed on the C Drive. But no option for me to modify this.

• SQL Server is not being installed.

• & Done

SCOM Zombie PSA#12: Zombie Instructions: SCOM 2012 Firewall Exceptions

 

Here are the firewall ports that are required for a full Operations Manager 2012 deployment. If you are not going to use certain parts of the product, done, enable the ports. Since I did not recognize any new or removed ports I believe they are the same as Operations Manager 2007 R2.

Feature	Exception	Port and Protocol	Configured By
Management server	· System Center Management service · System Center Data Access service · Operations Manager Connector Framework · Operations Manager Customer Experience Improvement · Operations Manager Application Error Monitoring	5723/TCP 5724/TCP 51905/TCP 51907/TCP 51906/TCP	Setup Setup Setup Setup Setup
Web console	Operations Manager web console	51908/TCP	Setup
Web console, forms authentication, http	World Wide Web Services, http	80/TCP	Windows Firewall
Web console, forms authentication, https	Secure World Wide Web Service	443/TCP	Windows Firewall
Operational database	· SQL Server database server · If using a named instance, add	1433/TCP 1434/UDP	Windows Firewall Windows Firewall
Operations Manager data warehouse database	· SQL Server database server · If using a named instance add	1433/TCP 1434/UDP	Windows Firewall Windows Firewall
Operations Manager Reporting	SQL Server Reporting Services	80/TCP	Windows Firewall
Agent, manual installation of MOMAgent.msi	System Center Management service	5723/TCP	Windows Firewall
Agent, push installation	· System Center Management Service · File and Print Sharing · Remote Administration	5723/TCP 137/UDP, 138/UDP, 139/TCP, 445/TCP 135/TCP, 445/TCP	Windows Firewall Windows Firewall Windows Firewall
Agent, pending repair	· System Center Management service · File and Print Sharing · Remote Administration	5723/TCP 137/UPD, 138/UPD, 139/TCP, 445/TCP 135/TCP, 445/TCP	Windows Firewall Windows Firewall Windows Firewall
Agent, pending upgrade	· System Center Management service · File and Print Sharing · Remote Administration	5723/TCP 137/UDP, 138/UDP, 139/TCP, 445/TCP 135/TCP, 445/TCP	Windows Firewall Windows Firewall Windows Firewall
Gateway	System Center Management Service	5723/TCP	Setup
Operations Manager Audit Collection Service database	· SQL Server · If using a named instance, add	1433/TCP 1434/UDP	Windows Firewall Windows Firewall
Operations Manager Audit Collection Service Collector	ACS Collector Service	51909/TCP	Windows Firewall

You can open the firewall management console by Start, Run, firewall.cpl

OR

Command Prompt way:

• Using the netsh command:

• Microsoft Windows Server 2008 also have an advanced firewall helper called advfirewall.

  netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = SUBNET profile = CURRENT
  

• A similar example using the Windows Firewall for Advanced Security helper:

  netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = localsubnet profile = DOMAIN
  

• This might be easier by creating a script with all the enable these firewall rules if you have multiple servers to run this against. Maybe if I have some time, I will write a script, if not, would love for someone to hook me up with one.

SCOM Zombie PSA#11: Zombie Instructions: SCOM 2012 Web Console Settings

 

Here are your Zombie Instructions for configuring the settings for the SCOM 2012 Web Console.

**** Do not install .NET Framework 4; but hey if you did install it ahead of time, like I had, then towards the end is the command line you can run to correct this.

Web Console Requirements:

· Recommended processor speed: 2.8 GHz or faster.

· Minimum memory: not less than 2 GB.

· Operating System: Windows Server 2008 R2

· Processor Architecture: must be AMD64 (sorry intel) but I’m good.

· Internet Information Services (IIS) v7.5 or later, with the IIS Management Console and the following role services installed:

· 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

· Windows Authentication

· Default website: must have an http or https binding configured

· Both .NET Framework 3.5 SP1 and .NET Framework 4 is required for setup to run. For more information, see the following.

· .NET Framework 3.5 SP1 redistributable package

· .NET Framework 4 redistributable package

Installation of the web console requires that ISAPI and CGI Restrictions in IIS be enabled for ASP.NET 4. To enable this, select the web server in IIS, and then double-click ISAPI and CGI Restrictions. Select ASP.NET v4.0.30319, and then click Allow.

****IMPORTANT**** You must install IIS before installing .NET Framework 4. If you installed IIS after installing .NET Framework 4, you must register ASP.NET 4.0 with IIS. Open a Command prompt window by using the Run As Administrator option and then run the following command: (Since I had my server all patched up to the latest I had to run this)

%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –r

Now your system is ready for you to install the Web Console for SCOM 2012.

SCOM Zombie PSA#10: Operations Manager 2012 System Requirements

 

Supported Operating Systems: Windows 7, Windows Server 2003 Service Pack 2, Windows Server 2008 R2, Windows Server 2008 Service Pack 2, Windows Vista Service Pack 2, Windows XP Service Pack 3

• Other Software:
  • Any server role
    • .NET 3.5 and 4.0
  • Management Server, Reporting Server, Web Console, Gateway Server
    • Windows Server 2008 R2 (64 bit)
  • Operational & Data Warehouse
    • SQL 2008 SP1 and above
    • SQL Collation - SQL_Latin1_General_CP1_CI_AS
  • Supported Operating Systems for Operations Manager Agent
    • Windows Server 2003 SP2 and above
    • Windows Server 2008 SP2 and above
    • Windows Server 2008 R2
    • Windows XP Professional SP3 and above
    • Windows Vista SP2 and above
    • Windows 7
    • Red Hat Enterprise Linux 4, 5, and 6 (x86/x64)
    • SUSE Linux Enterprise Server 9 (x86), 10 SP1 (x86/x64), and 11 (x86/x64)
    • Solaris 8 and 9 (SPARC) and Solaris 10 (SPARC and x86)
    • HP-UX 11i v2 and v3 (PA-RISC and IA64)
    • AIX 5.3, 6.1, and 7.1 (POWER)
  
  Supported Hardware Configuration:
  • Operations Manager Operations database: 4 GB of RAM or higher, 50 GB of available hard disk space
  • Management server: 2 GB of RAM or more, 20 GB of available hard disk space
  • Operations console: 2 GB of RAM or more, 20 GB of available hard disk space
  • Reporting data warehouse: 4 GB of RAM or more, 100 GB of available hard disk space
  • Reporting server: 2 GB or more, 20 GB of available hard disk space
  • gateway server: 2 GB of RAM or more, 20 GB of available hard disk space
  • Web console server: 2 GB of RAM or more, 20 GB of available hard disk space
  • Audit database: 4 GB of RAM or more, 100 GB of available hard disk space
  • Management server with audit collector: 2 GB of RAM or more, 50 GB of available hard disk space
  • Management server with Agentless Exception Monitoring file share: 2 GB of RAM or more, 30 GB of available hard disk space
  • Agent: Please refer to the recommended hardware requirement required by the operating system.

SCOM Zombie PSA#9: Operations Manager 2012 BETA!

 

Justin Incarnato released the news today on the System Center Operations Manager Team Blog. You’ll find more information about Operations Manager 2012 Beta. But I wanted to share the links out to everyone.

     I have been waiting for this for a while now, and now that the public beta for Operations Manager 2012 has been released, I am eager to drive right in. I encourage those of you that have the abilities to test this product to do so; I will be deploying it into my lab environment. But first I’ll need to research the documentation.

     As I work with the Operations Manager 2012 Beta and Operations Manager 2007 R2, I’ll provide my updates on how my testing go along with discoveries that are found. It may not be so much on 2007 R2 now.

• Download Operations Manager 2012 Beta
• TechNet Documentation for Operation Manager 2012
• System Center Operation Manager Forums
• System Center Operations Manager Team Blog
• Microsoft Connect Feedback Site

SCOM Zombie PSA#8: Default MP Countermeasure

     In Operations Manager 2007 it’s really easy to apply modifications to the default management pack. This would be all fine except that any updates or re-import to the default management pack reverts everything you have applied to it previously.

     I am not even sure how migrating to Operations Manager 2012 will affect it, other than the default management pack is removed starting in this version. And it is almost impossible in preventing zombies from making poor choices if then modify the system. So I simply counter act by renaming the default management pack.

• I search for the default Management Pack

• I have chosen to rename the Name to “z DO NOT USE !!!!! (Default Management Pack” and apply it.

• When you select a destination management pack to apply your modifications it will place it down at the bottom of the list, with nice notice not to use. If you want to make the extra countermeasures step you could remove the (Default Management Pack) out all together, if you notice zombies are still using it.

SCOM Zombie PSA#7: Operations Manager CEP

 

     I've just received an email stating that I have been accepted into the Operations Manager 2012 Beta Community Evaluations Program. This is very exciting news for me, since I REALLY want to play with the next version of OpsMgr and have a leg up on everyone else.  And since this is my first time in the program I am not sure what to expect.

     I’ve been out for a while attending a Certified Ethical Hacker (CEH) class, in which I will still need to study so that I my get my certification for my employer. This was a great class since it opened my mind up a little more on what the Dark Side of the force operates. So over the next few week I’ll be studying pretty hard on this with hopes of knocking it out of the way.

     With family, work, dogs, a life and zombies, I’ll still will find some time to publish PSAs.