I’m essentially mirroring this from the original one on my blog, but since I’ve decided to transition to a tech blog and a non-tech blog, it seems like a good idea.

I’ve taken the listing of SQL queries from Kevin Holman’s original post, cleaned them up a bit, and made it into one file which you can download and load into SQL Studio Manager, instead of copying and pasting individual queries. I’ll also be showing you how to automate a lot of these with PoSh, but right now I’m swamped and haven’t had the time to clean things up proper – so you’ll just have to wait.

Useful SCOM SQL Queries | Pavleck.NET

Updated: May 22, 2009

Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1

After the initial deployment of Microsoft System Center Operations Manager 2007, you might need to move the Operations Manager database from one Microsoft SQL Server-based computer to another.

SQL Server 2005 and SQL Server 2008 support the ability to change the location of the data files and of the log files between SQL Server-based computers, between instances on the same SQL Server-based computer, and different volumes on the same SQL Server-based computer. For more information about using this function in SQL Server, see the SQL Server documentation (http://go.microsoft.com/fwlink/?LinkId=93787).

The high-level steps of moving the OperationsManager database are as follows:

1. Back up the OperationsManager database.
2. Uninstall the OperationsManager database.
3. Delete the Operations Manager database.
4. Restore the OperationsManager database.
5. Update management servers with the new database server name.
6. Update the Operations Manager database with the new database server name.
7. Update the Operations Manager database logins on the new database server. Ensure that for the root management server, the SDK Account and the Action Account are included in the logins and that they have appropriate permissions. If reporting is installed, ensure that the Data Warehouse Action Account has appropriate permissions.
8. Set ENABLE_BROKER if needed.
9. Verify that the move is successful by ensuring that the console is displaying valid data.

How to Move the OperationsManager Database in Operations Manager 2007

New Base OS MP 6.0.6667.0 adds file fragmentation monitor to all Logical Disks

I recently blogged about the new Base OS MP that was recently released:  HERE

One of the things you will notice RIGHT off the bat… is that a huge percentage of your logical disks will go into a warning state, if you don’t already have some sort of scheduled defragmentation set up.  This will be true for virtual machines and physical machines…. anything over 10 percent file fragmentation (or the OS recommended setting) will get hit:

Kevin Holman’s OpsMgr Blog : New Base OS MP 6.0.6667.0 adds file fragmentation monitor to all Logical Disks

Designing a custom performance report

On February 27th 2009 I presented a TechNet Webcast to show how to author your own custom performance reports using Operations Manager 2007.

The webcast can be viewed from

https://www.livemeeting.com/cc/mseventsbmo/view?id=1032399073&role=attend&pw=9CAB8380

Attached to this blog are the step by step instructions and sample files that accompany the webcast. Extract files to view.

Using both the webcast and instructions you should be able to walk through and create your own report.

Daniel

http://blogs.technet.com/momteam

System Center Operations Manager : Designing a custom performance report

Microsoft has played a major role in the development of the Content Management Interoperability Specification (CMIS) that is currently in the hands of the OASIS working group. Committed as the team has been, they (including Microsoft) have not provided much information or examples of how CMIS will work with Microsoft’s SharePoint Server 2007 (MOSS). Until now.

A new MSDN article has arrived that demonstrates how one can integrate an external document repository with MOSS (or the free version of SharePoint, WSS) — which is exactly what the CMIS spec is all about. Our interest piqued, we took a look and in the following article, we share what we found.

How To: Connecting SharePoint (MOSS) to a CMIS Repository

Project Description
Find faulty FeatureDefinitions and cleanly uninstall them.
Find Feature remainders in Sites, SiteCollections, WebApps and in the Farm, from e.g. forcefully uninstalled Features from farm without deactivating them before, causing errors.
Also, de-/activate Features Farm wide.
Screenshots
Feature View – remove Features

SharePoint Feature Administration and Clean Up Tool

Mike here again to help bring clarity to something we are seeing with Windows Server 2008 R2 and existing Group Policy central store. Before that discussion, let us cover some background information.

ADMX Files and the Group Policy Central Store

Microsoft introduced the ADMX file format with Windows Vista and Windows Server 2008. This XML-based file format replaced the token-based ADM file format used by earlier versions of Windows to define administrative templates. Group Policy uses administrative templates to represent registry-based policy settings that appear when editing Group Policy. The content included in administrative templates describes the user interface used by Group Policy editors and registry locations where Windows stores policy settings. Windows Server 2008 R2 and Windows 7 provide a new set of administrative template files in the ADMX format.

Ask the Directory Services Team : Windows 7, Windows Server 2008 R2 and the Group Policy Central Store

Great tip if you ave issues removing WSP solution packages and web parts from third parties and find they don’t install or uninstall properly.  You may also have trouble activating or deactivating features in site settings when these invalid features crop up.

Errors that could be shown in SharePoint when installing or activating a feature "An unexpected error has occurred", "Failed to compare two elements in the array" or various other error messages may be shown while activating, deactivating, or browsing to a recently failed deployment of a WSP solution .

To check or remove invalid features on SharePoint 2007 site:

1. First, run the WssAnalyzeFeatures tool and view the Problems Log for invalid feature id (guids)
2. Try running STSADM -o deactivatefeature -id %featureIdFromLogFile% -force
3. Run the WssAnalyzeFeatures tool and see if the problems we’re resolved.
4. If feature can’t be removed or is in a subsite for a failed WSP solution uninstall…try running the WssRemoveFeatureFromSite to forcefully invalid old features.
5. Remove the feature ID’s until WssAnalyzeFeatures shows no errors.

Removing Invalid SharePoint 2007 Features due to a Failed, Missing, or Unsuccessful Activation SharePoint WSP – Gilham Consulting Microsoft Notepad

Consider the following scenario.  You have an Internet Information Services (IIS) 6.0 web server running on Windows Server 2003 Service Pack 2.  The Microsoft update KB973917 gets installed on the server.  After installing KB973917, the IIS 6.0 application pools cannot start up successfully.  An inspection of the event logs show that the IIS worker processes are terminating unexpectedly, showing event messages similar to the following:

Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1009
Date:  12/9/2009
Time:  10:55:01 AM
User:  N/A
Computer: WEBSERVER01
Description:
A process serving application pool ‘DefaultAppPool’ terminated unexpectedly. The process id was ‘1234′.
The process exit code was ‘0xffffffff’. 

Internet Information Services 6.0 may not function correctly after installing KB973917

This is how I setup user profile sync for SharePoint Server 2010 Beta on my machine. You should not take this as an official guide. But the steps may help if you have been drive crazy.

You should also check out TechNet article and the steps on our team blog first, they are more "official". And it’s not come from "another MS guy in the wild" like me:)

[Update - we are considering to gather all information and put it back to TechNet article, could be video walkthrough, screenshots, and hope that could help. After that is done, i may remove the content here.]

The following steps in done on Windows Server 2008 R2. But it also applies to Windows Server 2008. The WCF fix for R2 and Win7 is not currently available to public but it will be released in coming days here.

1. Start with a fresh SharePoint Farm installation, make sure WCF fix (Please refer to my pervious post) is already applied on the machine.
2. A web application is already created at port 80. A site collection is also created.
3. Don’t do anything on User Profile Service Application now…If you did, you may need to rebuild the farm. (am i kidding? no… this is beta.)

Jie Li’s GeekWorld : User Profile Sync Setup in SharePoint Server 2010 Beta