I’ve decided to make you a Christmas present and developed a S2D solution for OMS.
Both Cluster Management Pack and Virtual Machine Management Pack provide monitoring for Virtual Machine but from different perspective. In some situations the Cluster MP can be very noise as it is monitoring Resource Groups and Resources which could be down just because some virtual machines are shut down. Continue reading “Disable Discovery of Virtual Machine Resource Groups in Cluster MP”
Not so long ago I’ve reported an issue where Multi-Tenant RRAS (Windows Server Gateway) is not discovered by by the Multi-Tenant RRAS Management Pack. This problem has been fixed in Update Rollup 2 for System Center 2012 R2 Virtual Machine Manager. If you add Windows Server Gateways as Network Service in VMM as usual you will not notice a difference in the wizard and after the gateway is added successful you will probably had to create that Client Access Point resource manually. That is because the fix is not exposed directly in the wizard, it is actually a parameter that you have provide in the connection string. And actually the parameters are two: Continue reading “Adding Windows Server Gateway Cluster as Network Service in VMM 2012 R2 UR2 for Monitoring with SCOM”
This blog post is to inform you that several MPs have been updated with some important fixes/features. You can find all the information here.
My personal best improvement is:
- Add Task launch PowerShell session on the remote machine for All Computers
Recently I’ve had some VMs that went trough some failovers and after that I’ve noticed that the network adapters on some of these VMs were missing in Network Connections window. Running ipconfig I was able to see the adapters and their configuration. Also some of the VMs were part of cluster and the cluster roles couldn’t be moved to the nodes where the network adapters were missing in network connections. On those VMs I couldn’t open the admin share also. Continue reading “Tips From the Field: Network Adapters are Missing in Network Connections”
In the past I’ve tried Multi-Tenant RRAS Management Pack with NVGRE Gateway that was not in the cluster. Recently I was able to try the MP with NVGRE Gateway cluster but I’ve met some challenges. Continue reading “NVGRE Gateway Cluster Not Discovered Completely by the Multi-Tenant RRAS MP”
If you look at the title you probably think I’ve switched to the dark side and from System Center Specialist I’ve become SQL Specialist . Nope it is not that. If you are dealing with System Center you know the clash with SQL is inevitable. Sooner or later you have to learn a thing or two in SQL. So I’ve been playing these days with installing SQL instances for System Center on a cluster and I’ve bumped into two issues:
- The Cluster Resource ‘Analysis Services (Instance_Name) Could Not Be Brought Up
I’ve received this error during the installation of SQL instance with Analysis Services on the first node. The error is received at the end of the installation when the cluster role is being brought online.
Reason for the error: Analysis Services files during the setup are set to a location that is different than the default one. Because of that it seems permissions to the folder/s where Analysis Services are put are not set during installation.
Resolution: To all folders where Analysis Services is placed add full NTFS permissions for the Analysis Services service account.
- No Connection Could Be Made Because The Target Machine Actively Refused it IP:Port
I’ve received this error after installing SQL instance with Analysis services on the first node. In order to check if everything is OK with Analysis Services I’ve started up SQL Management Studio and tried to connect to the SSAS instance but I’ve received the error above. To troubleshoot this error I’ve tried telnet to the IP and the Port but no connection was made.
Reason for the error: SQL Analysis Services sets port 0 during the installation which means dynamic port.
Resolution. In order to be able to connect I’ve set a static port to the SSAS instance. You cannot do that trough SQL Management Studio so you have to find a file named msmdsrv.ini. This file is located in folder named Config of the root directory of where you’ve installed your SSAS instance. Open the file and edit the line <Port>0</Port> by replacing 0 with a port of your desire.
I’ve only seen these error when I have clustered instances. As you know SSAS instance can be required for SCOM or SCSM.