Maarten Damen has released a Management Pack for Trend Micro IMSS.

Trend Micro IMSS (Interscan Messaging Security Suite) is a mail gateway solution, which includes anti-spam and anti-virus solutions. With this Management Pack you are able to monitor the health and performance of your IMSS server(s).

Download: Trend Micro IMSS Operations Manager Management Pack

In this article I will explain a challenge I experienced while installing the OpsMgr web-console on a management server. After installation of the OpsMgr webconsole I got the following error: "Server error in '/' Application". And as it turned out finding the problem wasn't that easy.

I had a strange problem while installing the OpsMgr web-console at a customer. Within their test environment I decided to install the OpsMgr web-console on the management server which runs on Windows Server 2008. So I started with installing the AJAX component, and adding the webserver role with the needed role features.(see: reference1 at the end of this article)

After the prerequisites were installed I started the System Center Operations Manager R2 installation and made the choice to modify the installation in order to include the web-console.

After the installation was finished I tried to start the web-console by using the shortcut in the Start Menu, but unfortunately I was presented with the following error.

Most of the time, when I have strange errors related to OpsMgr I start to google/bing right away. One of the advantages of OpsMgr is that it has a wide community and a lot about problems and caveats is blogged about or can be found on the forums.

I tried several provided answers from the blog posts and forum topics, but none of them helped. And then I remembered something. User Account Control (UAC) was turned-on on the Management Server.
I turned off UAC during the installation of OpsMgr but turned it back on again after the installation was successful.

So for a test, I installed the web console on the RMS where I first turned UAC off, rebooted and started exact the same installation of the OpsMgr web console. And to my surprise after installation I could successfully start the Web Console.

So I successfully determined that the reason that the web-console wouldn't install on my Management Server had something to do with the fact that UAC was turned on.

Normally having UAC turned on shouldn't be a problem though, because when Administrative rights are needed by the setup program you will get a prompt which asks you if you want to grant permissions for the action. I also noticed that during the "UAC off" installation I had other installation screens, the screen asking if I wanted to provide data to Microsoft for the Customer Experience. Strange..

So I did a file compare using Windiff (see: reference 2) on the web-console folders of a working web-console installation and a non-working web-console installation and I found out that in the non-working web-console installation a few files were missing:

.\bin\corgent.diagramming.commandresources.dll
.\bin\corgent.diagramming.customelements.dll
.\bin\microsoft.reportviewer.common.dll
.\bin\microsoft.reportviewer.webforms.dll

So I copied these files from the working Web console server to the non-working Web console server and guess what… It almost worked. Because there is another caveat, you have to enable Constrained Delegation on the computer object of the Management Server (see: reference 3)

Conclusion

Turn UAC off during installation of System Center Operations Manager and also when installing additional components, or start the installation with the "Run as Administrator" option. Or in this case use my workaround, but you have to dig-up the missing files somewhere.

References:
1. How to install IIS on Server 2008 to support OpsMgr Web Console and Reporting, by Kevin Holman: http://blogs.technet.com/kevinholman/archive/2008/09/26/how-to-install-iis-on-server-2008-to-support-opsmgr-web-console-and-reporting.aspx
2. Windiff: http://www.grigsoft.com/download-windiff.htm
3. Installing the Web Console on a 2008 Management Server - using Windows Authentication, by Kevin Holman: http://blogs.technet.com/kevinholman/archive/2008/09/24/installing-the-web-console-on-a-2008-management-server-using-windows-authentication.aspx
4. OpsMgr R2 WebConsole won’t start after installation, by Marnix Wolf: http://thoughtsonopsmgr.blogspot.com/2009/08/opsmgr-r2-webconsole-wont-start-after.html

The System Center Operations Manager team released an update for the OpsMgr R2 Management Pack on the 19th of Februari. The version is 6.1.7599.0. and can only be installed if you have System Center Operations Manager R2 installed.

The Operations Manager management pack helps you to monitor the health of your Operations Manager environment, now that's a nice "Chicken-Egg" scenario.

Before you install this management pack, read the Management Pack Guide, which can be downloaded from the link below. The Management Pack guide contains important information about what to do before and after the installation of the Management Pack.


Download the OpsMgr R2 Management Pack and the Management Pack guide

After upgrading to SCCM 2007 SP2, AD discovery methods will fail to bind across external trusts.

The failure occurs because of a change made in Service Pack 2 which makes the product more secure by requiring authentication for AD binds. As discovery is performed by the site server System account, authentication on the network requires Kerberos which is not supported across external trusts.(continue at source)

The System Center Operations Manager 2007 R2 Cross Platform Cumulative Update 2 includes System Center Operations Manager 2007 R2 Cross Platform Agent Update (KB973583) and additional bug fixes.

Note: Keep in mind that the Management Packs associated with this release have not yet been published, so you'll have to wait to use the full functionality of this update.

Note 2: The Updated Management Packs have been posted, you can find them here

Download: System Center Operations Manager 2007 R2 Cross Platform Cumulative Update 2

As you know the most recent SCOM documentation can be found on Technet, see: http://technet.microsoft.com/en-us/opsmgr/bb498235.aspx.

Sometimes though it's handy to have the documentation available offline. Microsoft provides a download where you can download the documentation for reference.

Download: System Center Operations Manager 2007 R2 Documentation

The Release Candidate for DPM 2010 is now available for public download.

Download: System Center Data Protection Manager 2010 Release Candidate

A Superflow is an interactive content model which provides a structured and interactive interface for viewing documentation. Each SuperFlow includes comprehensive information about a specific dataflow, workflow, or process.

The following superflows have been (re)released:

* SuperFlow for Configuring Software Updates
* Software Update Deployment SuperFlow
* SuperFlow for Creating SRS Report Models in Configuration Manager 2007

When designing an System Center Operations Manager infrastructure, depending on the situation you should make a decision on how you are going to deploy the agents to the servers (and perhaps even workstations) you are going to monitor.

In this article I will give an overview of the different installation options, and try to summarize the advantages and advantages of using them. This is important because the method used to deploy your agents will what you can do with the agent once deployed.

System Center Operations Manager provides several ways to deploy Agents to your servers, you can use a manual installation which covers the following scenario's:

• Start the Operations Manager Agent installation from the SCOM 2007 setup media (SetupOM.exe)
• Run the MomAgent.msi on each server from the AgentManagement subfolder of the SCOM installation folder an a RMS or MS.
• Script an automatic installation, which uses the MomAgent.msi, and deploy it using your Software Distribution mechanism (SCCM, SMS, Altiris, Tivoli etc..), you can check this article for all the command line options available.
• Deploy the agent using AD group policies

You can also use the console push though, which gives you the ability to either discover "to be installed" resources from your AD, or provide a list of computers on which you want to push the agent. And you can initiate an install from the Operations Manager console in order to deploy the agent to the server using by default the Management Server Action account or an account provided with enough rights to install the software.

Depending on the infrastructure available you should pick an installation method that meets your needs, below is an overview of the advantages and disadvantages of each option which can help you to determine the best option for your environment.

Console Installation

Advantages
• Easy method to install agents using discover
• Automatically approved
• Repair option available
• Prerequisites automatically installed

Disadvantages
• Additional Firewall rules must be enabled in order for discovery and installation of agent to work
• No active directory integration
• Failover automatic but to any Management Server available.

Manual Installation

Advantages
• Implement in server staging procedure (SCCM, Altiris etc..)
• Implement in current software distribution method
• Make use of Active Directory information to determine (predefined) backup management server and provide automatic failover
• Further automation possible (script Agent installation in case of non AD joined servers )

Disadvantages
• No Change Primary Management Server from console
• No repair from console
• No uninstall from console
• No upgrade from console
• MSXML not automatically installed
• AD MP helper object not automatically installed if target is Domain Controller and AD MP is not already installed.

Other things to consider:
• Domain Controllers can't make use of Active Directory integration, so when using manual installation you should use other options when it concerns DC's



Conclusion:

Keep in mind that the method you use to install your OpsMgr agents has consequences on what you can do with the agent once deployed. Therefore choosing an installation method should really be considered in the design phase, and tested before implementing the solution to all your servers.

Please contact me, if you see any additional advantages or disadvantages, I will integrate it into this document so that it can serve as a reference.

References:
• Experiences from my colleagues at INOVATIV
• Ways to Deploy Agents in SCOM by Clint Boessen
• Getting and keeping the SCOM agent on a Domain Controller – how do YOU do it? By Kevin Holman
• How to get your agents back to “Remotely Manageable” in OpsMgr 2007 R2

The DFS Namespaces Management Pack monitors servers running Windows Server® 2008, Windows Server 2003 R2, and Windows Server 2003. It can also be configured to monitor the health of DFS Namespaces from client computers running Windows Vista® or Windows® XP. This management pack monitors events that are recorded in the System event log by DFS Namespaces. It also monitors the overall health of DFS Namespaces and alerts you to critical issues.

Download: DFS Namespaces Management Pack for System Center Operations Manager 2007

The Application Compatibility Toolkit Connector (ACT Connector) assists administrators with collecting the necessary computer and application compatibility information to help plan for a Windows deployment.act and vista

With this connector update, Administrators will be able to utilize valuable Application Compatibility information right from within the Configuration Manager console.

Download: Application Compatibility Toolkit Connector Update

The annual Microsoft Management Summit (MMS) is the premier event of the year for deep technical information and training on the latest IT Management solutions from Microsoft, Partners, and Industry Experts. In a year packed with new management product releases, MMS 2010 will provide the latest technical updates on Desktop, Datacenter, Device and Cloud management features and solutions from Microsoft. The event will share more expert knowledge and information than ever, covering current System Center products as well as Windows platform management solutions for Virtualization of servers and desktops and applications.

From executive keynotes providing product overviews and detailed roadmaps for 2010 and beyond to deep technical sessions packed with new solutions and best practices, there's something for everyone at MMS 2010, no matter what your IT Management specialty. MMS 2010 will again feature more than 8,000 Hands-on Lab places during the week, with most being led by experts providing a guided tour of the latest management releases and technologies.

Meet the Experts. MMS 2010 will offer face-to-face access to Microsoft and industry IT management experts through a variety of networking opportunities. With Birds-of-a-feather, Speaker Q&A, and the Microsoft Experts pavilion there are many opportunities to speak 1:1 with experts from Microsoft and the industry at large. In addition, the MMS 2010 Expo will host over 60 sponsors and exhibitors showcasing their latest management products, services, and solutions. (more)

Now available for download, the Operations Management Pack for Windows Server 2008 R2 Direct Access Server supports a rich set of Alarms, Monitors and Agent Tasks that can be used to successfully and efficiently manage a Direct Access server.

Download: Operations Management Pack for Windows 2008 R2 Direct Access Server

This article describes how to move the Site Database in Microsoft System Center Configuration Manager 2007 from a computer that is running Microsoft SQL Server 2005 to another drive on the same computer, or to another computer that is running SQL Server 2005.(continue at source)

Backup is one task in IT that no one looks forward to, so if you've been looking for a comprehensive, low maintenance solution, Data Protection Manager (DPM) from Microsoft might just be the ticket.

DPM is specifically designed to protect Microsoft workloads: Exchange, SharePoint, SQL Server, AD and Hyper-V. It also follows the paradigm shift for data protection sweeping through the IT industry: rely on hard disks for backup and recovery; only use tape for long-term archiving.(continue at source)

The File Services Team is proud to announce the beta release of our File Services Management Pack for System Center Operations Manager 2007. This management pack provides health monitoring for SMB shares, NFS shares, DFS Namespaces, DFS Replication and File Server Resource Manager including the File Classification Infrastructure.

Download Instructions

1. Log on to Microsoft Connect and create a profile if you have not already created a profile
2. Navigate to Connection Directory
3. Search for  File Services and Storage and select Apply Now
4. Fill-out application survey
5. Log on to File Services and Storage connection
6. Click the announcement: Beta release of SCOM Management Pack for File Services in Server 2008 R2
7. Follow instructions to download the Management Pack

Vincent Dipippo: "What You Write Is Not Necessarily What You Get"

OpsMgr 2007 has a fairly substantial library of discovery module types and monitor types that ship with it. Even with that library, it seems that the single most important extensibility point in OpsMgr today is the ability to use custom scripts to perform discovery and monitoring tasks. As I've developed scripts for OpsMgr, I have learned a great deal about how OpsMgr processes scripts. This article describes some important concepts regarding how scripts are processed by OpsMgr. (continue at source)