Archive

Archive for the ‘Configuration Manager’ Category

Microsoft Presents “Enabling Consumerization without Compromising Compliance” at BriForum this Week

BriForum kicks off today in Chicago. BriForum 2013 is the only technical virtualization conference that is 100% dedicated to desktop virtualization, VDI, application virtualization, Remote Desktop Services, and the consumerization of IT.

Later this week Microsoft Product Director Jason Leznek will present, “Enabling Consumerization Without Compromising Compliance”.  Jason’s session is on Thursday morning and will cover Microsoft’s approach to delivering people-centric IT is helping customers enable users to work on devices of their choosing with consistent experiences, and providing IT a unified infrastructure for managing and delivering applications and other resources, all while helping organizations protect what is important to them.  See how innovations in System Center 2012 R2 Configuration Manager, Windows Intune, and Windows Server 2012 R2 helps organizations enable Consumerization without compromising compliance, with a special focus on the technologies which help reduce VDI storage costs and improve the end user and administrator experience to both session and VM based VDI.

If you can’t wait until Thursday to be there live or wait for a recorded replay, be sure and checkout “What’s New in Remote Desktop Services for Windows Server 2012 R2” on the Remote Desktop Services Blog, or “What’s New in 2012 R2: Making Device Users Productive and Protecting Corporate Information” on Brad Andersons blog.  Both blog posts are lengthy but have a ton of good information we think you’ll find interesting.  You might want to view the six minute video below, “Empowering People-centric IT in the age of Consumerization” to learn more about the topic and where we are headed with personal device management.

And for those of you interested in downloading some of the products and trying them, here are some resources to help you:

  • Windows Server 2012 R2 Preview download
  • System Center 2012 R2 Preview download
  • SQL Server 2014 Community Technology Preview 1 (CTP1) download

As always, follow us on Twitter via @WindowsServer

Written by Keith Combs, Microsoft Server and Tools

Enabling Management of Open Source Software in System Center Using Standards

July 24th, 2013 No comments

This post is a part of the nine-part “What’s New in Windows Server & System Center 2012 R2” series that is featured on Brad Anderson’s In the Cloud blog.  Today’s blog post covers standards-based management of open source software with System Center and how it applies to Brad’s larger topic of “Transforming the Datacenter.”  To read that post and see the other technologies discussed, read today’s post:  “What’s New in 2012 R2:  Enabling Open Source Software.”

Whether in the public cloud with Windows Azure, the private cloud with Windows Server and System Center, or a hybrid of both, running and managing open source workloads (such as Linux and JEE applications) is a key tenant of Microsoft cloud solutions. In this post, we will review the standards-based management approach used in System Center to manage open source software, take a detailed look at the management implementation in the UNIX/Linux agents for Operations Manager and Configuration Manager, and introduce System Center 2012 R2 improvements to these agents.

System Center 2012 R2 and Management of Open Source Software

System Center 2012 R2 is a great solution for management of the heterogeneous private cloud with Windows, Linux and UNIX workloads running side by side. With System Center 2012 R2, the portfolio of heterogeneous management capabilities has been substantially expanded and now encompasses:

  • Inventorying and deploying software to Linux and UNIX with Configuration Manager
  • Monitoring UNIX and Linux computers and services with Operations Manager
  • Monitoring JEE Application Servers on Linux, UNIX, and Windows with Operations Manager
  • Deploying Linux virtual machines and services with Virtual Machine Manager (and Windows Server Hyper-V)
  • Backing up Linux virtual machines with Data Protection manager

In enabling the heterogeneous management features of System Center, our focus is on standards-based management. Open standards such as Common Information Model (CIM) and WS-Management play a key role in many of the heterogeneous management capabilities of System Center.

One of the primary benefits of a standards-based approach is that different implementations of similar technologies can be uniformly presented and managed. For example, a Linux server, AIX server, and Windows server may have very different implementations for identifying and reporting on operating system resources and performance (such as processor inventory and utilization), but by managing each of these servers through a management implementation based on CIM, the administrator or management software does not need to understand the specific architectures, APIs, and all details of each operating system’s conventions and implementations. Rather, a common interface and model is used to uniformly present key performance indicators and inventory. In turn, this allows management software, such as System Center, to tightly integrate management for a variety of platforms, with consistent presentation and experience throughout.

OperationsManagerLinuxDiagramView

Figure 1 – A Linux Server Monitored in System Center 2012 R2 – Operations Manager

Implementing the Standards-Based Approach

In System Center 2012 R2, we continue our commitment to standards-based management of open source workloads, and have made a significant improvement in this regard by implementing a common CIM server in both the Operations Manager and Configuration Manager agents for UNIX and Linux.

In the Windows realm, a consistent CIM implementation has been available since the introduction of WMI (as far back as NT 4.0). Likewise, WS-Management (or WS-Man) has been available for Windows in Windows Server 2003 and beyond. However, expanding common management capabilities to a broad array of UNIX and Linux operating systems (and architectures) with these standards required new implementations.

The UNIX and Linux agents for Operations Manager consist of a CIM Object Manager (i.e. CIM Server), and a set of CIM Providers. The CIM Object Manager is the “server” component that implements the WS-Management communication, authentication, authorization and dispatch of requests to the providers. The providers are the key to the CIM implementation in the agent, defining the CIM classes and properties, interfacing with the kernel APIs to retrieve raw data, formatting the data (e.g. calculating deltas and averages), and servicing the requests dispatched from the CIM Object Manager. From System Center Operations Manager 2007 R2 through System Center 2012 SP1, the CIM Object Manager used in the Operations Manager UNIX and Linux agents is the OpenPegasus server. The providers used to collect and report monitoring data are developed by Microsoft, and open-sourced at CodePlex.com.

OperationsManagerUNIXLinuxAgentArchitecture

Figure 2- Software Architecture of the Operations Manager UNIX/Linux Agent

This CIM/WS-Man standards-based approach also brings benefits to the agent implementation itself. The resulting management agent is lightweight, with a small footprint and low impact to the monitored host. Additionally, such a CIM server and provider implementation is quite portable, allowing it to be consistently implemented across a broad matrix of UNIX and Linux operating system distros, versions, and architectures – while returning monitoring data with a uniform presentation. Lastly, the standards-based approach enables the Operations Manager server to UNIX/Linux agent communication with well-defined protocols (WS-Man over HTTPS) and established interfaces (WinRM).

A very similar agent software architecture is employed in the UNIX and Linux agents for Configuration Manager, first available in the System Center 2012 SP1 product. Like the Operations Manager UNIX and Linux agents, the Configuration Manager UNIX and Linux agents implement a lightweight CIM Object Manager and set of providers. While the Operations Manager agent providers are focused on system monitoring metrics, the Configuration Manager agent providers enable scenarios such as hardware inventory.

By adopting a standards-based approach to enabling and managing open source software, System Center 2012 R2 is able to deliver consistency in the standards, protocols, and management interfaces that are employed in managing Windows Server workloads and open source software.

Introducing Open Management Infrastructure in System Center

With System Center 2012 R2, UNIX/Linux agents for both Configuration Manager and Operations Manager are now based on a fully consistent implementation of Open Management Infrastructure (OMI) as their CIM Object Manager. In the case of the Operations Manager UNIX/Linux agents, OMI is replacing OpenPegasus. Like OpenPegasus, OMI is an open-source, lightweight, and portable CIM Object Manager implementation – though it is certainly lighter in weight and more portable than OpenPegasus.

An excellent introduction to OMI can be found on the Windows Server Blog, but some of the key features of OMI include:

  • Very small footprint (the package size for Operations Manager UNIX/Linux agents has been reduced by half)
  • Highly portable
  • Simple provider extensibility

While these are immediately realized benefits in the System Center 2012 R2 UNIX and Linux agents, perhaps the most significant and exciting benefit of OMI can be found in the promise of real and broad cross-platform and standards-based management. OMI has been designed not just to be portable between UNIX, Linux and Windows, but also for devices and embedded systems. As an example, both Cisco and Arista are working on WS-Man/CIM implementations for network device management with OMI. Given the possibility of using a single protocol or mechanism to manage network and storage devices, baseboard management controllers and Windows, UNIX, and Linux servers, one can quickly imagine the scenarios this could unlock in the automation-centric cloud world we now live in. OMI’s portability and standards-based implementation open this management opportunity to a potentially incredible array of managed devices and entities and management platforms and tools with streamlined interoperability. Thusly, it is easy to see why OMI is a foundational implementation element of the Datacenter Abstraction Layer (DAL) concept.

Further discussion of some of the management scenarios that OMI, and a link to a great demo, can be found the PowerShell Team Blog.

Summary

As we continue to broaden the portfolio of management capabilities for open source software in System Center 2012 R2, we are reaffirming our commitment to open standards-based management, and aligning with exciting new models developing in the cloud era. The availability of OMI, and its adoption into the System Center agents for UNIX and Linux is another step forward in the realm of standards-based management. Now, a CIM and WS-Man based implementation used for management of Windows and Linux/UNIX can extend even broader to devices, embedded systems, and applications. This benefits the System Center user, as we continue to provide consistent experiences regardless of the managed platform, and this benefits the management ecosystem – as additional management providers and management tools can more fully and capably interoperate.

To see all of the posts in this series, check out the What’s New in Windows Server & System Center 2012 R2 archive

SCM v2 Beta: What happened to the EC + SSLF?

June 29th, 2011 No comments

I can feel this becoming a FAQ, so I wanted to blog on this early in the Beta . 🙂 I forgot to mention in my Beta announcement anything about the new ‘severity’ you see on settings, whoops. The text below is a copy and paste from the IE9 Security Guide…(read more)

SCM v2 Beta: What happened to the EC + SSLF?

June 29th, 2011 No comments

I can feel this becoming a FAQ, so I wanted to blog on this early in the Beta . 🙂 I forgot to mention in my Beta announcement anything about the new ‘severity’ you see on settings, whoops. The text below is a copy and paste from the IE9 Security Guide…(read more)

SCM v2 Beta: What happened to the EC + SSLF?

June 29th, 2011 No comments

I can feel this becoming a FAQ, so I wanted to blog on this early in the Beta . 🙂 I forgot to mention in my Beta announcement anything about the new ‘severity’ you see on settings, whoops. The text below is a copy and paste from the IE9 Security Guide…(read more)

SCM v2 Beta: What happened to the EC + SSLF?

June 29th, 2011 No comments

I can feel this becoming a FAQ, so I wanted to blog on this early in the Beta . 🙂 I forgot to mention in my Beta announcement anything about the new ‘severity’ you see on settings, whoops. The text below is a copy and paste from the IE9 Security Guide…(read more)

SCM v2 (BETA) + New Baselines Available to Download

June 27th, 2011 No comments

[ UPDATE: September 6th, 2011 ] The Beta review period for SCM2 ended August 31st, 2011 (and the download is no longer available). We’ve been working on stabilizing the build and meeting release requirements. Look for the RTW of SCM2 on September 15th…(read more)

SCM v2 (BETA) + New Baselines Available to Download

June 27th, 2011 No comments

[ UPDATE: September 6th, 2011 ] The Beta review period for SCM2 ended August 31st, 2011 (and the download is no longer available). We’ve been working on stabilizing the build and meeting release requirements. Look for the RTW of SCM2 on September 15th…(read more)

SCM v2 (BETA) + New Baselines Available to Download

June 27th, 2011 No comments

[ UPDATE: September 6th, 2011 ] The Beta review period for SCM2 ended August 31st, 2011 (and the download is no longer available). We’ve been working on stabilizing the build and meeting release requirements. Look for the RTW of SCM2 on September 15th…(read more)

SCM v2 (BETA) + New Baselines Available to Download

June 27th, 2011 No comments

[ UPDATE: September 6th, 2011 ] The Beta review period for SCM2 ended August 31st, 2011 (and the download is no longer available). We’ve been working on stabilizing the build and meeting release requirements. Look for the RTW of SCM2 on September 15th…(read more)

Using the SMSMap tool to document FEP components in your ConfigMgr hierarchy

March 5th, 2011 Comments off

From Jeff Tondt

Visio is one of the most popular tools for creating diagrams that describe effective systems and processes. In every project in which I participate, when it comes to documenting what you did I always have to create a diagram where I defined architecture, server configuration, network, etc. A picture is worth a thousand words and Visio is the tool of choice in these documentation tasks.

With SMSMap you can read FEP components and ConfigMgr/SMS site roles through COM and automate Visio to draw a diagram of the hierarchy including the FEP SQL Reporting Server, FEP Data Warehouse SQL Server, and the FEP Reporting Component.

Developed by Jeff Tondt this free utility is available at http://www.tondtware.com and works on ConfigMgr SP2 / R3 and down to SMS 2003. Seeing the whole FEP/ConfigMgr hierarchy as a picture can help you quickly understand how your infrastructure is laid out. This handy tool automates creation of your infrastructure documentation and frees you up for other Forefront product installations.

Some screenshots of SMSMap:

clip_image002

clip_image006

clip_image004