Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

My experience installing a SCOM Management server on Windows Server 2008

My experience installing a SCOM Management server on Windows Server 2008

  • Comments 7
  • Likes

Figured I might as well chronicle the process.

 

1.  First - starting off with a generic install of Server 2008 x64 Enterprise.  Since this is running on Hyper-V, I installed the Hyper-V additions to make it run correctly under the hyper-v host.  Gave it a static IP, joined my domain, enabled remote management so I can TS into it.  I will be logging in as an account that is a member of the OpsMgr admins group, local admin on all servers, and SA over all databases.

2.  Left UAC, Windows Firewall, and IE ESC enabled and in their default configurations.  I added my SCOM Admins global group to the local admins group, and I explicitly added the domain SDK and management server action accounts to the local admins group.

3.  Ran Windows Update and updated to all critical updates.  The first batch after a clean install was 12 updates totaling 127MB as of this writing.

4.  Ran the 3 required Server 2008 hot-fixes to support OpsMgr Server roles on Windows 2008:  951327  and  952664  and  953290

5.  Ran OpsMgr's SetupOM.exe - and kicked off the pre-req checker.  It failed:

 

image

 

Luckily - those are built into the OS.....  so I run Server Manager, add features, and check the boxes next to .NET Framework 3.0 and Windows Powershell.

That didn't take long... now the pre-req checker again - and all greens....  so let's kick off the install.

 

6.  During setup - I de-selected the DB and Web Console.... leaving the Management Server, User Interfaces, and Command Shell.

7.  I gave it the database location, Action account, SDK account, anf joined the CEIP program.  Said No to Microsoft Update and away the install goes.  I *have* seen issues where customers need to run SetupOM.exe "as an Administrator" from the right click menu... so if you get an error about not being able to verify accounts - try that.  I did not get that error.

8.  Install was a success!   I have had customers state this failed... with configuring Windows Firewall errors, but I did not get any errors.

9.  A quick look at the console to make sure things look good.  My new management server shows Healthy in the Administration pane of the console.  No major alerts in the console with regard to the new MS.  I hit the Management Server State dashboard view, and pulled up Health Explorer for the new MS.  All good.

10.  I spot check the new MS event log.... in the OpsMgr log... some funny business is going on..... all my agents are reporting in this log that they are not heart-beating.  However - this is a new MS and no agents are even assigned to it.  This could be a temporary issue, as the new configuration is becoming active.  If I check all those agents in the console - they are still heart-beating just fine, and no heartbeat alerts were generated.

11.  I checked the Windows Firewall configuration - and the OpsMgr install configured the firewall to open Inbound ports for access to the management server:

 

image

 

12.  Before we add any agents on this management server - we need to get it patched up to spec with the other management servers in my environment.  I currently am running 951380 and 954049.... so both will need to be applied to this management server.  This is to make sure this MS is patched, and to apply the update files the the management server's \AgentManagement folder... so any subsequent agents that are push from this MS will get the updates that are consistent with my environment.  I start with 951380... run the MSI - accept all defaults, then kick of the hotfix update from the installer splash screen.  Then I kick off 954049 roll-up for Server 2008...

13.  Another quick spot check of the OpsMgr event log... looks good.  No major issues.  I checked the \Health Service State folders.... we have a current OpsMgrConnector.Comfig.xml.... and it lists the RMS as the Parent, and has all my agents as Children.  Good.  I spot check the Management Packs folder, and I can see all my MP's have downloaded.

14.  Time to move agents....  I moved them in the console... to load balance my environment.

 

On the new MS event log - as agents get updated config... they will move to this management server, and we will see the following type events for each agent:

Log Name:      Operations Manager
Source:        OpsMgr Connector
Date:          8/4/2008 10:33:34 PM
Event ID:      20020
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      OMMS3.opsmgr.net
Description:
The health service {33196DB1-42DB-7D62-A12F-9C6A4620CF80} running on host dc2.opsmgr.net and serving management group OPS with id {E7850522-67DF-F9E6-888A-38C99239AB74} is available.

Doesn't get much easier than this.  :-)

 

 

Update....

As an afterthought... I went back and double-checked my \AgentManagement folder... and found that 951380 msp was present - but 954049 msp was missing.  I did install it - and I don't think I got any errors..... the hotfix utility was there - but I could not find the MSI log from it.....   I tried to reinstall it manually, by running the MSP file in the hotfix folder, but this gave a weird error.... so I just uninstalled the hotfix utilities from control panel/programs and features, and then re-ran the MSI for this hotfix.  It installed just fine, and now shows up in all places.  It appears that the management server did not like getting patched with 951380 and 954049 without a reboot in between - even thought they did not request or prompt for one.  Oh well.

Comments
  • The first thing you’ll probably want to do in preparation for your callback is gather up any relevant

  • I was wondering if you had any issues with the firewall aspect of the install . . . I have disabled the firewall via server manager, but the prereq check still comes up with an alert . . .?

    dfkon@mednet.ucla.edu

  • What does the pre-req checker *specifically* say?

  • FYI...the 3 KBs identified in step 4 are included with Windows 2008 Service Pack 2.

  • Thanks Chris - this is also called out on my hotfix post:

    http://blogs.technet.com/kevinholman/archive/2009/01/27/which-hotfixes-should-i-apply.aspx

  • Hello,

    Step13. I have the RMS listed as Parent which is fine but also the old name of the current server I am reinstalling... the old server has been rename to the current one...

    Anything to remove?

    Should I uninstall and reinstall MS?

    Thanks,

    Dom

  • Hi Kevin,

    The server is already renamed. If I

    - uninstall Operations Management Server (Add/Remove Program) even may be some registires if any remain...

    - delete the old name from the RMS

    - I have only Network devices on this Management Server there is no agent.

    - Install Management Server

    Will it work?

    Thanks,

    Dom

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Search Blogs