opsmode

When you try to edit Company Knowledge on a rule or a monitor you need Word installed from Office Professional, not standard professional! And then you need to install “Visual Studio Tools For Office runtime”. If you don’t have VSTOR installed you will get the following error:
Visual Studio Tools For Office runtime is not installed.

Download for VSTOR is here: Visual Studio Too………
Be sure to grab the one for the same language your Office installation is in, otherwise you’ll end up with the same error as above.
Supported version of Word is Professional Edition 2003, 2007 or 2010. Only 32-bit is supported!

Also, be sure that it is the Visual Studio 2005 Tools!

When installing OpsMgr on SQL 2008 R2 the installation will not find the SQL instance and give the following error: Microsoft SQL Server is required. Please see details

To go around this requirement, use the DBCreateWizard.exe that you find on the OpsMgr media \SupportTools\<architecture>\DBCreateWizard.exe

Observe that this is NOT TESTED OR SUPPORTED by Microsoft!!!

And that one will find the instance.

Observe that this is NOT TESTED OR SUPPORTED by Microsoft!!!

Some times when installing X-plat agents you get an error:

The server certificate on the destination computer (server:1270) has the following errors:    
The SSL certificate contains a common name (CN) that does not match the hostname.

The problem here is that Operations Manager uses the FQDN in the DNS, but the certificate will contain the server name taken from the server.
To solve this issue you can change the DNS record, change the server name or you can add the server name to the HOSTS file on the Root Management Server or the Management Server.

Example:
192.168.80.37 name.in.certificate

When scheduling an Operations Manager PowerShell script you have to load the powershell snapins.

Insert this in the beginning of your script

$ServerName = “hostname”
add-pssnapin “Microsoft.EnterpriseManagement.OperationsManager.Client”;
set-location “OperationsManagerMonitoring::”;
new-managementGroupConnection -ConnectionString:$ServerName;
set-location $ServerName;

When downloading from MSDN/TechNet use the “Top download” if your product is available there. The download speed is higher.

Today when installing OpsMgr R2 agents on a couple of Solaris servers we ran in to a problem on the Solaris 9 servers.

The error we got in OpsMgr:
<![CDATA[Executing command: echo -e mail=\ninstance=overwrite\npartial=nocheck\nidepend=quit\nrdepend=quit\nconflict=nocheck\naction=nocheck\nbasedir=default\n > /tmp/scx-$USER/scx;uncompress -f /tmp/scx-om_unix/scx-1.0.4-248.solaris.9.sparc.pkg.Z

We found this on the Solaris box:
[ verifying class <config> ]
## Executing postinstall script.
ld.so.1: .scxsslconfig: fatal: libssl.so.0.9.7: open failed: No such file or directory
Killed
pkgadd: ERROR: postinstall script did not complete successfully
Installation of <MSFTscx> failed.
bash-2.05# ssh –version
Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090700f
Bad escape character ‘rsion’.

And if you look in Appendix A in the Operations Manager 2007 R2 Operations Guide you se that OpenSSL is required. So after installing OpenSSL the agent install went fine!
Sun does not provide a version of OpenSSL for Solaris 9 SPARC. There is a version available from Sunfreeware.

Based on the data you get from the cmdlet get-agent you can list all agents with a specific setting.

This line for example, will list all agents with the Agent Proxy setting enabled:
get-agent | where {$_.ProxyingEnabled -like $true}

Change $_.ProxyingEnabled to $_.ManuallyInstalled and you’ll get a list with all manually installed agents.

In OM2007 SP1 there is a bug on updating the ManuallyInstalled property, so that wont work. This is corrected in R2.
If you dont have to use powershell there is a workaround in this thread.

 
Your options are:
PrimaryManagementServerName
Id
LastModified
Name
DisplayName
HostComputer
HostedHealthService
HealthState
PrincipalName
NetworkName
ComputerName
Domain
IPAddress
Version
RequestCompression
CommunicationPort
MaximumSizeOfAllTransferredFilesBytes
MaximumQueueSizeBytes
ManuallyInstalled
InstallTime
InstalledBy
CreateListener
AuthenticationName
ActionAccountIdentity
HeartbeatInterval
ProxyingEnabled
ManagementGroup
ManagementGroupId

I have been trying to fix an issue with a SQL 2008 cluster node restarting the Health Service every 10 minutes. Logging EventID: 6024 with the description:
RestartHealthService.js : Restarting Health Service. Health Service exceeded Process\Private Bytes threshhold.

It didnt mater if I did an override on the monitor Health Service Private Bytes Threshold. I got the event anyway

Then I realized that this is a multi-homed agent, so when I did an override on the same monitor but in the other management group as well, the problem was resolved.

I wrote a post about the name change of the Health Service in SCOM 2007 R2. Apparently there is a couple of more services that have changed name.
The guys over at http://www.systemcenterforum.org got a post about that: link

When importing a Management Pack directly from the Management Pack Catalog to OpsMgr 2007 R2 you don’t get the chance to read the MP documentation. Becouse you do the download and import of the MP at the same time.
Most of the Management Packs got pre-install instructions in the documentation that you want to read.

So, to be able to download the documentation:

In the Select Management Packs from Catalog, search for the MP that you are about to import.
Mark the product and klick to Properties on the right.

And there you have a link to download the doc.

Good Luck!