And what about SCOM in multiple forests: design SCOM in multiple forests

Ok,

I have posted a nice amount of posts about SCCM in multiple forests, it looks like I have gave away all of the required info, not sure if I missed something but sure I recall anything I will post it.

 

For SCOM deployment across forests, it is very easy. More than SCCM, you have 2 options either allow the agent to talk directly to the RMS/MS servers or deploy a opsmgr gateway in the remote forest, based on studying here is the factors the controls your decisions:

-          If you have a small amount of agents with acceptable bandwidth and network connectivity I would go to allow them to connect directly t the SCOM server.

-          If you have a large amount of servers or WAN connectivity, I would go for deploying a GW in the other forest, check and Google about top 10 benefits of using GW servers, as data will be compressed better, less administrative overhead…etc

In both cases you will need a CA around, you cannot use self signed certificates, an enterprise or standard certificate will do the job, once certificates in place and configured communication will flow smoothly and here is 2 tips:

-          You will need to import and configure a certificate on the RMS/MS server in the original forest. And import the certificate using the certificate import utility, it is not clear in the document and people didn’t pay attention to this point.

-          You don’t need a trust in place between forests.

-          In the other forest where the GW installed you don’t need certificates for agents as long as servers are joined to the forest, agents will communicate with the GW using mutual authentication, GW to RMS communication will be secured using certificates.

-          Note the AD MP will not work across forests.

This is the major points I wanted to highlight, I will start posting about transitioning from SMS to SCCM soon, so keep reading J.

New Cluster MP released

It has been released yesterday, this is a very important update to implement in your infrastructure, it has a lot of fixes and improved cluster performance monitoring.

The download is here http://www.microsoft.com/downloads/details.aspx?FamilyId=AC7F42F5-33E9-453D-A923-171C8E1E8E55&displaylang=en&displaylang=en you will have to uninstall the previous cluster MP before installing this one, check the MP guide file first.

 

RSS feed added

Hi,

I just added RSS feeds to my blog, you will find it in the upper left corner, you will be able to subscribe, see latest feeds, add to your favorite news reader, so have fun with it. And keep following the blog.

Design SCCM in multiple forests - more notes

This is will grow and grow, but here we go:

You don’t need to have native mode across the forests to be able to manage the other forests, as long as each forest as its own site. If you have single site that covers the 2 forest you will need SCCM in native mode.

 

If you have any questions please post a comment on any of my blog entries.

 

Bye.

Install/FIX reporting after upgrading RMS to SP1

Went yesterday through a nice SCOM installation, install SCOM then reporting then SP1 for SCOM and reporting, however I had an issue as reports were not showing, tried everything, and went to google and found that most of those cases solved using reporting reinstallation, uninstalled reporting, reset SRS, now I am trying to load the reporting to install, but it gets interrupted, checked the error log and found that reporting cannot be installed as it tries to load MP Warehouse library version that is old and the version will not load. And setup fails.

It gives the following error:

ImportMomManagementPack: Loading management pack C:\Program Files\System
Center Operations Manager
2007\Reporting\Microsoft.SystemCenter.DataWarehouse.Internal.mp. 5:26:43 AM
ImportMomManagementPack: We are using the Client API to load the MP.
ImportMomManagementPack: Error: Unable to load management pack C:\Program
Files\System Center Operations Manager
2007\Reporting\Microsoft.SystemCenter.DataWarehouse.Internal.mp
: Cannot import ManagementPack
<<Microsoft.SystemCenter.DataWarehouse.Internal, 31bf3856ad364e35,
6.0.6246.0>>. A newer version of this ManagementPack <6.0.6246.0> is already
imported in the database.

To fix this issue follow the following steps:

-          Uninstall SCOM reporting

-          Reset SRS if you

-          Export the default MP and remove the WH library reference and overrides.

-          Import it back

-          Delete the WH library and ORD library MP.

-          Install the reporting.

-          Import the original MP

This is a complex solution, I had a reply from the product team, to run the Reporting2007.msi directly and this should solve the problem, didn’t try this one so you have the both solutions now

 

OpsMgr 2007 SQL MP version 6.0.6278.8 Released

This fixes and changes introduced in this release were thanks in large part to the feedback that all of you have provided to us. 

http://blogs.technet.com/momteam/archive/2008/04/01/opsmgr-2007-sql-mp-version-6-0-6278-8-released.aspx

The OpsMgr 2007 MP for SQL 2000 and 2005 has been updated and was released to the MP Catalog on 3/31/2008 (version 6.0.6278.8).  This version includes the fixes from all previous versions of the MP and is supported on both OpsMgr 2007 RTM and OpsMgr 2007 SP1. The table below is an excerpt from the MP guide detailing the changes and fixes that were made in this release.  I'd like to specifically call out the final bullet in the "Changes to SQL Server 2005 Management Pack" as the behavior of the "Database Status" monitor has been updated to have three states now so it can more appropriate handle DB restore and recovery states.

Changes in this Update

The March 2008 update to the SQL Server Management Pack includes the following changes:

General changes	·       The “Transaction Log Space Free (%)” monitor was made public for both SQL 2000 and SQL 2005 to allow for further customization. ·       Some corrections were made and additional detail provided in the “Key Monitoring Scenarios” sections of this guide. ·       Removed the hard-coded exception for jobs with a specific name from the “A SQL job failed to complete successfully” rules for both SQL 2000 and SQL 2005. ·       Fixed an issue with the scripts used to calculate DB free space which was preventing some databases from having their free space correctly monitored on SQL installations that did not have DBs with contiguous IDs. ·       Corrected typographical errors.
Changes to SQL Server 2000 Management Pack	·       Fixed an issue where incorrect free space values were being calculated for some SQL 2000 databases.
Changes to SQL Server 2005 Management Pack	·       A fix was made to address issues with collection of performance data from specific instances of Analysis Services. ·       Significant changes were made to the “Database Status” monitor in the SQL 2005 MP.  The monitor now has three states reflecting good, bad, and neither.  The possible database states have been realigned into these categories which will reduce “false-positive” alert volumes specifically when log-shipping and database backups are occurring.

 

 

Design SCCM in multiple forests - notes

Hi All,

I have some notes on my previous post here they are:

-          If you use 2 way forest trust between the forests, then SCCM can use the SCCM machine account in the sender configuration, so you don’t need to create an account, this is a note as I stated that there is must be a trust between forests

-          If you don’t have a trust, then the account used could be a local account, so the trust is not required to configure SCCM across forests.

 

C ya