another great news today. Microsoft made System Center 2016 TP5 and Windows Server 2016 TP5 available for download.
TP 5 is the last technical preview before the official release, which we think could be in Q3/Q4 2016.
To read more about what’s going on with technical preview 5, please click here.
my friend Stanislav Zhelyazkov and his peers Pete Zerger (@PZerger), Tao (@MrTaoYang), Anders (http://contoso.se) wrote an awesome book the last month. Within the book they give you some insides in Microsoft OMS.
Description: This preview release of “Inside the Microsoft Operations Management Suite” is an end-to-end deep dive into the full range of Microsoft OMS features and functionality, complete with downloadable sample scripts (on Github). The chapter list in this edition is shown below:
Chapter 1: Introduction and Onboarding
Chapter 2: Searching and Presenting OMS Data
Chapter 3: Alert Management
Chapter 4: Configuration Assessment and Change Tracking
Chapter 5: Working with Performance Data
Chapter 6: Process Automation and Desired State Configuration
Chapter 7: Backup and Disaster Recovery
Chapter 8: Security Configuration and Event Analysis
Chapter 9: Analyzing Network Data
Chapter 10: Accessing OMS Data Programmatically
Chapter 11: Custom MP Authoring
Chapter 12: Cross Platform Management and Automation
You can download it via Stanis blog.
today a short day to day helper regarding cluster networks.
Last weekend I had a question from my coworker, if it is possible to react on failed networkconnections within a cluster even if the cluster is still running.
As you know Hyper-V is running as long as the cluster heartbeat is available and the storage is reachable. Only if these connections fail, Hyper-V Cluster forces a node to failover his roles.
My answer, yes it is possible with some tricks. First thing you need to know is, that if a network connection in the cluster failes, we get an error event.
Event ID 1129 — Cluster Network Connectivity Partitioned https://technet.microsoft.com/en-us/library/dd353962%28v=ws.10%29.aspx?f=255&MSPPError=-214721739
This event is also noticed in the event viewer of your Hyper-V Host. Now you can attach a task to that event and for example run a script which forces a failover.
The script to set the node in maintenance mode and force a failover could look like:
$VMHost = Get-SCVMHost -ID "Hyper-V Host ID"
Disable-SCVMHost -VMHost $VMHost -MoveWithinCluster -RunAsynchronously
You can achieve the same effect when you use System Center Operations Manager by configuring an Agent Task for your Hyper-V Host.
Find more info here: https://technet.microsoft.com/en-us/library/hh563486.aspx