A new feature just popped up in my Recovery Services Vault named Backup Reports:
It is the last day of the year but it is not too late for a new blog post. When applying Update Rollup for System Center 2012 R2 I’ve encountered an issue when updating the VMM Management Pack and I’ve blogged about it in my tips. Continue reading “Report Deployment Error After Updating VMM Management Packs with 2012 R2 Update Rollup 3”
Reporting in System Center 2012 Virtual Machine Manager is achieved trough the integration with OpsMgr 2012. In order to run some of the VMM reports that have forecasting you have to configure the VMM to SCOM integration to use SQL Analysis Services instance. This instance should be the same instance with Reporting Services for SCOM. So I’ve installed SQL Analysis Services on the same instance with Reporting Services for SCOM. It is not the default instance on the server so I’ve configured SQL Analysis Services to use a specific static port instead of using a dynamic one (I like using static ports for SQL servers ). I’ve opened the VMM console. Went to settings, than System Center settings and I’ve opened the properties of Operations Manager Server. Click on the SQL Server Analysis Services tab and entered the SQL server name, the SQL instance, the port that I had set and the credentials to connect. To my surprise I’ve received and error to my surprise I’ve received an error message:
The SQL Server Analysis Server %ComputerName; is not reachable.
I’ve opened CMD and checked if there is a connection to the SQL server and the port via Telnet. Connection was OK. Than I’ve replaced the port with 0 and connection was successful. SQL Analysis Services were configured successfully. To me this is a bug and I will try to log it.
Peter F. Sheppard from MSFT introduces first one of series of solutions that will provide more advanced monitoring for Service Manager. You can find the description of the solution here.
Not so long ago I’ve wrote an article titled SCVMM Maintenance mode for host does not put the computer object in maintenance mode in SCOM reported as fixed in SC 2012 SP1. I’ve reported the bug described in the article and that report was closed on Microsoft Connect site as fixed before the official release of SC 2012 SP1. As I do not trust blindly and always verify any information I’ve tested if this bug is fixed after the release of SC 2012 SP1 UR1. After I’ve made the test in my home lab I was experiencing the same bug again. My test was verified also by Steve Beaumont so the issue is not in my TV screen only. To me in 99% of the cases when you put Hyper-V host in maintenance mode in VMM you will probably want to restart that host and not to receive SCOM alerts about it. I think it is highly unprofessional someone to report to you an bug and you to close that report as fixed without actually fixing it. But as stubborn guys I’ve logged this bug again. If you want to join you can vote for fixing this bug here. I suggest to hurry with your vote before someone closing that report as fixed again .