mountainss SystemCenter Blog

Microsoft SystemCenter blogsite about virtualization on-premises and Cloud


Leave a comment

What’s New in the Windows Server Technical Preview #Windows #Winserv #Hyperv #sysctr #SCVMM

Windows 10 Family

What’s New in the Windows Server Technical Preview :

  • What’s New in Active Directory Federation Services. Active Directory Federation Services (AD FS) in Windows Server Technical Preview includes new features that enable you to configure AD FS to authenticate users stored in Lightweight Directory Access Protocol (LDAP) directories. For more information, see Active Directory Federation Services Overview.
  • What’s new for Hyper-V in the Technical Preview. This topic explains the new and changed functionality of the Hyper-V role in Windows Server Technical Preview, Client Hyper-V running on Windows 10 Technical Preview, and Microsoft Hyper-V Server Technical Preview.
  • Windows Defender Overview. Windows Defender is installed and enabled by default in Windows Server Technical Preview, but the user interface for Windows Defender is not installed. However, Windows Defender will update antimalware definitions and protect the computer without the user interface. If you need the user interface for Windows Defender, you can install it after the operating system installation by using the Add Roles and Features Wizard.
  • What’s New in Remote Desktop Services in the Windows Server Technical Preview. For the Windows Server Technical Preview, the Remote Desktop Services team focused on improvements based on customer requests. We added support for OpenGL and OpenCL applications, and added MultiPoint Services as a new role in Windows Server.
  • What’s New in Storage Services in Windows Server Technical Preview. This topic explains the new and changed functionality of Storage Services. An update in storage quality of service now enables you to create storage QoS policies on a Scale-Out File Server and assign them to one or more virtual disks on Hyper-V virtual machines. Storage Replica is a new feature that enables synchronous replication between servers for disaster recovery, as well as stretching of a failover cluster for high availability..
  • What’s New in Failover Clustering in Windows Server Technical Preview. This topic explains the new and changed functionality of Failover Clustering. A Hyper-V or Scale-out File Server failover cluster can now easily be upgraded without any downtime or need to build a new cluster with nodes that are running Windows Server Technical Preview.
  • What’s New in Web Application Proxy. Web Application Proxy now supports preauthentication for applications using the HTTP Basic protocol, wildcards in external URLS of applications, redirection from HTTP to HTTPS, use of pass-through authentication with HTTP applications, publishing of Remote Desktop Gateway apps, a new debug log, propagation of client IP addresses to backend applications, and improvements to the Administrator console.
  • What’s New in Windows PowerShell 5.0. Windows PowerShell 5.0 includes significant new features—including support for developing with classes, and new security features—that extend its use, improve its usability, and allow you to control and manage Windows-based environments more easily and comprehensively. Multiple new features in Windows PowerShell Desired State Configuration (DSC) are also described in this topic.
  • What’s New in Networking in Windows Server Technical Preview. With this topic you can discover information about new networking technologies, such as Network Controller and Generic Routing Encapsulation (GRE) Tunneling, and new features for existing technologies, including IP Address Management (IPAM), DNS, and DHCP. Detailed information about what’s new is available for these networking technologies:


Leave a comment

#Microsoft System Center 2012 Management Pack for Windows Server 2012 R2 Remote Access #sysctr #SCOM

SCOM 2012 R2Microsoft System Center 2012 R2 Operations Manager

What’s New
System Center Management Pack for Remote Access combines monitoring for DirectAccess and RRAS into a single management pack. This management pack retains the monitoring capabilities of RRAS 2012 management pack. This management monitors Remote Access role in Windows Server 2012 R2 only. This management pack monitors the following conditions:
DirectAccess Monitoring
• Issues with internal and external network adapter connection and settings such as forwarding
• Teredo server state and configuration
• Isatap availability and configuration such as name publishing and route publishing
• 6to4 adapter and forwarding state
• Heuristics around network security such as DOS attack, spoof attack and replay attack and state of IPSec
• State of network infrastructure like DNS servers, Management servers configured for DirectAccess
• IP-Https state and configuration
• State of various underlying services such as BFE, IPHelper etc needed for Remote Access
• Heuristics related to OTP
Most of the health monitoring scenarios that can be monitored using the native DirectAccess UI have been included in the management pack.

VPN Monitoring
Existing capabilities for RRAS management pack have been included in the unified management pack as well. We’ll summarize the monitoring capabilities for RRAS included in the unified management pack:
• Remote access (VPN) connection failures due to erroneous configuration.
• Demand-dial (site-to-site) connection failures due to erroneous configuration.
• Erroneous configuration of VPN tunnels:
• Point-to-Point Tunneling Protocol (PPTP)
• Layer Two Tunneling Protocol (L2TP/IPSec)
• Secure Socket Tunneling Protocol (SSTP)
• Internet Key Exchange version 2 (IKEv2)
• Connection licenses, registry corruption, authentication, and accounting issues for remote access
• VPN network access protection (NAP) enforcement and Network Access Quarantine Control access issues
• Erroneous configuration and setup issues involved with various routing protocols that are exposed through RRAS, such as the following:
• Routing Information Protocol (RIP) v1 and v2
• DHCP Relay Agent
• Internet Group Management Protocol (IGMP)
• DHCPv6 Relay Agent
• Monitors and alarms to notify the administrator about erroneous conditions. These conditions include the following:
• Hardware device error
• Protocol initialization failure
• Remote Access Connection Manager (RASMAN) service unexpected termination
• Routing and Remote Access service unexpected termination
• Routing and Remote Access service monitor
• Authentication or accounting failures
• Configuration failures
• IPsec-related failures
• Packet filter-related failure
• IPCP negotiation failure
• Memory allocation monitor
• Memory allocation failure
• No more licenses monitor
• Port open failures
• Support for monitoring performance counters and instrumentation, including the following:
• Total number of remote access connections
• Total number of timeout and serial overrun errors for this connection
• Total number of alignment errors for this connection (alignment errors occur when a byte received is different from the byte expected)
• Total number of buffer overrun errors for this connection (buffer overrun errors occur when the software cannot handle the rate at which data is received)
• Total number of bytes received for this connection
• Number of bytes received per second
• Total number of bytes transmitted for this connection
• Number of bytes transmitted per second
• Total number of cyclic redundancy check (CRC) errors for this connection (CRC errors occur when the frame received contains erroneous data)
• Total number of data frames received for this connection
• Number of frames received per second.

You can download the Microsoft System Center 2012 Management Pack for Windows Server 2012 R2 Remote Access here

System Center Market Place

Find more System Center Center Management Packs in the Market Store of System Center here

For instructions about importing a management pack, see How to Import a Management Pack in Operations Manager 2012 R2

Tuning Monitoring by Using Targeting and Overrides

When you import a management pack, System Center 2012 – Operations Manager discovers the objects defined by the management pack and begins applying the management pack’s rules and monitors to the discovered objects. You should always import a new management pack in a pre-production environment first so that you can evaluate the management pack and adjust or tune the management pack as necessary to meet your business needs.

To tune a management pack effectively, you should involve the service owner or subject matter experts, the operations team members who monitor the alerts and events and take action when something requires attention, and the engineering team responsible for the Operations Manager infrastructure. Depending on the service that is monitored by the management pack, you might also include the networking or security teams.  Those responsible for the Operations Manager infrastructure might not have the knowledge and experience with the service to effectively tune the management pack without expert input.

Tuning Approach

For servers or applications, tune from the highest severity alerts and dependencies to the lowest. Look at alerts first, then open the Health Explorer to gather more detailed information for the problem. Validate results of the alerts generated, verify scope of monitoring against intended targets (servers or services), and ensure the health model is accurate.

Each rule should be evaluated according to the following criteria:

  • Actionability: An alert is actionable if it tells you what went wrong and how to fix it. When alerts are generated that do not require any action, consider disabling alerting for the rule.
  • Validity: An alert is valid if the issue that generated the alert can be confirmed and the issue actually occurred at the moment the alert was generated.
  • Suppression: There should be only one alert stating the issue occurred.

What to Tune

  • Discovery frequency
  • Monitor thresholds
  • Targets
  • Intervals
  • Parameters

Tips

  • Import a single management pack at a time.
  • Review any new alerts reported for servers monitored with the new management pack. You can use the Alerts and Most Common Alerts reports to help you discover your most common alerts. When you first install a management pack, it tends to discover a multitude of previously unknown issues. Monitor the alerts to determine potential areas of concern
  • Override the monitor or rule as applicable for a particular object type, a group, or a specific object.
  • Disable the monitor or rule if the issue is not severe enough to warrant an alert and you do not need to be made aware of the specific situation being monitored.
  • Change the threshold of the monitor that is generating the alert if you want the underlying condition to be monitored, but the alert is being generated before the condition is actually a problem for your particular environment.
  • When you set overrides for a management pack, save them to a management pack that is named ManagementPack_Override, where ManagementPack is the name of the sealed management pack to which the overrides apply. For example, overrides to the management pack Microsoft.InformationWorker.Office.XP.mp would be saved to Microsoft.InformationWorker.Office.XP_Overrides.xml.

Tuning Monitoring by Using Targeting and Overrides topics

Using Classes and Groups for Overrides in Operations Manager
How to Override a Rule or Monitor
How to Enable or Disable a Rule or Monitor
Using the Enforced Attribute in Overrides
How to Enable Recovery and Diagnostic Tasks

Other resources for this component

TechNet Library main page for Operations Manager
System Center Operations Manager Engineering Blog
Managing Discovery and Agents
Using Management Packs

You can find also awesome information about Microsoft System Center 2012 R2 Operations Manager on Technet wiki here :

The System Center 2012 R2 Operations Manager Survival Guide

System Center 2012 R2 logo new


Leave a comment

Community event of the year EXPERTS LIVE 2014 => JOIN US #sysctr #Hyperv #Azure #SQL #Winserv and More

ExpertsLive 2014

Subscribe now for the event of the year Experts Live , for and by the community with excellent speakers.

Experts_Live_logo_2014

Experts Live 2014 Programs


Leave a comment

I will replace my EliteBook Laptop for the Surface Pro 3 I7 512GB to manage the #HybridCloud ! #Surface #Mobility

Surface Pro 3Surface pro 3 8GB – I7 – 512GB

I’m changing my EliteBook 8740W Mobile Workstation because Microsoft made this New Surface Pro 3 I7 512GB Tablet which can replace my Laptop to manage HybridCloud Datacenters.
I see a lot of benefits for me like :

  • The weight of my EliteBook is 4000 Gram and the Surface Pro 3 weights 800 gram.
  • Mobility is for me important and the battery of my EliteBook keeps me Online for 30 minutes which is too short.
  • When you are in a meeting, It’s really handy to make notes with the pen in OneNote.

Here you see the specifications of the Surface Pro 3 :

Specs

Surface Pro 3 Specs

Surface penWrite real natural on your Surface Pro 3

Keyboard CoverKeyboard Cover of the Surface Pro 3

Docking stationThe Dockingstation is important for me at work for Datacenter Administration.

Here you can choose your own Microsoft Surface Pro 3 model


Leave a comment

Rebuilding and Upgrading Microsoft Testlab and Start with #Hyperv Recovery Manager with #Azure #HybridCloud

With our testlab ICTCUMULUS we made awesome Microsoft solutions with Private and Public Cloud and learned a lot.
Here are some blogposts I made earlier :

Starting : From Microsoft Private Cloud to Hybrid Cloud Services

From Microsoft Private Cloud to Hybrid Cloud Services: Hyperv Clustering

From Microsoft Private Cloud to Hybrid Cloud Services : SCVMM 2012 R2

Making a NVGRE Gateway with System Center 2012 R2 Virtual Machine Manager

SQL 2014 Guest Cluster with Shared VHDX on Hyperv 2012 R2 Cluster for WAPack

Windows Azure Pack for Windows Server 2012 R2 Guide

Now it’s time for upgrading and rebuilding our Testlab ICTCUMULUS with extra memory and new Microsoft Hyper-v 2012 R2 Hypervisors.

Upgrade 1

Upgrade 2We have enough Memory now ;-)

Here are the Visio drawings of ICT CUMULUS and we Changed some things like :

  • A Dedicated Hyper-V Cluster 2012 R2 for a virtual SQL 2014 Guest Cluster.
  • A Dedicated Switch for I-SCSI storage traffic.

ICTCUMULUS RackICT CUMULUS Rack for HybridCloud
Memory Upgrades

ICTCUMULUS Rack  2ICTCUMULUS Rack Networking

When we are ready with rebuilding ICTCUMULUS Testlab, we will start with Microsoft Azure Site Recovery Manager and my next blogpost:

Azure replication

Follow

Get every new post delivered to your Inbox.

Join 2,387 other followers