MSFT pulled their most recent update to the Exchange 2010 MP. No one can get the updated version or previous versions. I have had several emails sent to me asking for the previous MP and have sent the file to those who requested it. Since so many people are looking for it and MSFT has not provided it, I have decided to put it up on my spaces page. If you want the pre sp2 Exchange 2010 MP, then go here and get it.
So I am trying to get VMM 2012 really integrated into SCOM 2012. There are a few reports that will not work without SQL Analysis Services and integration from VMM. Well to get VMM to work with this you have to install Analysis Management Objects on your VMM Management Server. So I do this. So I try to connect, but I get the same issue (AMO not installed). I bounce the VMM management server, and when it comes up I try to connect and integrate SSAS and it works.
I am very happy to see that the Exchange team made this issue public and are working on a fix. I am also happy I did not deploy it as soon as it came out. This just goes to show that you really need to test management packs when they first come out. This doesn’t mean just looking at the console, but the application that the management pack touches, as I don’t think people who deployed this had any indication of problems until end users started to complain about mailbox access.
Anyway, let’s hope they release a fix soon, but in the meanwhile if you have deployed it then they post a work around. Here is the link to their blog with a detailed description of the issue and the work around.
Patched our lab this afternoon. All seemed well until I ran the SQL scripts on the OpsDB and DW. When I went back to my RMS to open the console and import the new MP’s, I got an error saying the SDK service had not initialized and could not connect.
I saw a lot of 2115 warnings and 26319 errors. I reached out to my buddy Almquist and he recommended bouncing the SQL service. He said this was an issue that was supposed to be fixed in CU4. Apparently we ran into it during our upgrade from CU3 to CU5.
So if you have this issue, then you know the easy fix, bounce SQL and you will be good to go. Other than that I had no issues in my lab. I hope this continues in our pre-prod environment and then production.
Get it here.
Cumulative Update 5 for Operations Manager 2007 R2 resolves the following issues:
- Restart of non-Operations Manager services when the agent is updated.
- Updated ACS reports.
- TCP Port Probe incorrectly reports negative ping latency.
- MissingEvent Manual Reset Monitor does not work as expected.
- Drillthrough fails because of rsParameterTypeMismatch in the EnterpriseManagementChartControl.
- ACS – Event log message is truncated or corrupted in SCDW.
- UI hang caused by SDK locking.
- ACS Filter fails for certain wildcard queries.
- Edit Schedule button is disabled with SQL 2008 R2.
- Web console times out when you open the left navigation tree.
- Scheduled Reports view for Windows Server 2003 and for Microsoft SQL Server 2005 Reporting Services SP3 CU9 returns “System.IndexOutOfRangeException: Index was outside the bounds of the array.”
- Signed MPs cannot be imported when new attributes are added to existing classes.
Cross Platform Cumulative Update 5 for Operations Manager 2007 R2 resolves the following issues:
- Performance data for LVM managed partitions is not available.
- Process monitor does not keep name if run by using symbolic link.
- AIX with large number of processes crashes with bad alloc.
Cross Platform Cumulative Update 5 for Operations Manager 2007 R2 adds the following feature:
- Support for Red Hat 6
The SCOM team has released the R2 Admin ResKit. Go get it here!
The System Center Operation Manager 2007 Administration Resource Kit provides the following features to aid in management group administration:
- Scheduled Maintenance Mode – Ability to schedule and manage maintenance mode in the management group.
- Clean Mom – Helps remove all installed R2 components.
- MP Event Analyzer – MP Event Analyzer tool is designed to help a user with functional and exploratory testing and debugging of event based management pack workflows like rules and monitors.
Schedule Maintenance Mode is designed to use the Operations Manager platform. Due to this we are able to centrally manage Maintenance Mode instead of using a schedule task solution. Also, all information is stored in the Operations Manager database therefore no information is lost during a disaster if the database has been backed up.
You will find a detailed guide on how to setup and use this tool in the download package.
The tool provides the following features:
- Ability to schedule any type of object to be placed into maintenance mode in the form of a Job
- Group support including nested groups
- Automatically places Health Service Watcher in maintenance with computer
- Blocks RMS from being placed in maintenance
- Support for Run Once, daily, weekly, and monthly schedules (including complex scenarios like “second Tuesday of the month”)
- Ability to cancel a maintenance Job where everything will be removed from maintenance automatically
- History Report
I did the CU3 update yesterday to our infrastructure. Later, in the afternoon, I started to approve and process agent updates. In the evening I got pinged on OCS by our OCS and Group Chat engineer. He asked if I was doing an install on OCS because “SCOM” is restarting all of the OCS and GroupChat services. I told him that this wasn’t possible, that the agent install shouldn’t bounce application services. After looking at one of the boxes, it was apparent that RestartManager was bouncing several services after the SCOM agent update took place. I had patched other Windows 2008 servers earlier that day without any issue. I am still uncertain what caused this to happen on our OCS and GroupChat servers, however if it happens to you here is what you need to look for and what you need to do to resolve it.
Despite the push showing as “Successful” you will find that some of these were not so. The quick way to find them is through an alert view and or this view in the console:
All of the above Critical states are agents that experienced problems during install. Pick one and log onto that box. Checking the SCOM Agent service you will find it in a “Starting State”:
After you verify that the SCOM service is “Starting” open up task manager and you should find the MOMAgentInstaller.exe still operating:
Kill this and the HealthService.exe process:
Now start the SCOM agent service and verify your .dll’s have been updated with the .49 version. If we look at the application and scom event logs we will see what potentially happened. When looking at the application log we notice that after the scom agent install started the RestartManager started to cycle several services and the SCOM agent had been hung since the incident started:
So be careful about pushing agent updates to Windows 2008 servers if the Restart Manager service is running and is allowed to run, as it may cause some application outages for you.