I am an IT Evangelist at Microsoft in Columbus, Ohio ... I enjoy helping IT professionals envision, learn and adopt next generation virtualization and management technologies, Windows Server Platform, System Center and Private Cloud.My specific technology focus areas within the Microsoft ecosystem are:● Private Cloud, Virtualization and Management● Enterprise Desktop Strategies● SharePoint 2010● Messaging● Infrastructure Architecture
Feel free to contact me if I can assist in your evaluation and adoption of Microsoft technologies.
UPDATE: New Test Lab Guide Released: Deploying Windows Server 2012 R2 Network Virtualization with System Center 2012 R2 Virtual Machine Manager.
Network Virtualization, and Software-Defined Networking (SDN) at-large, have been getting a lot of attention recently. After reviewing the network traffic patterns in heavily virtualized datacenters, many IT Pros are beginning to realize that a substantial portion of datacenter network traffic is occurring between virtual machines running on the same virtualization host. In addition, organizations are beginning to evaluate options for defining network-level isolation between virtualized subnets in a manner that provides greater scalability and easier management than a traditional VLAN approach.
Based on this, it makes sense that the networking industry is moving towards bringing layer-3+ networking capabilities directly into the hypervisor. Essentially, network virtualization allows us to abstract routing and switching from a physical network infrastructure, extending benefits similar to what we’ve realized with server workloads via server virtualization.
At VMworld recently, IT Pros were initially impressed with the new network virtualization capabilities that VMware demonstrated in their early pre-release version of the VMware NSX product, based largely on the VXLAN overlay protocol. But, after walking away from the excitement of a big trade show event and pondering network virtualization as it pertains to their environment in more detail, I’ve also heard some early concerns expressed with VMware NSX, such as:
VMware NSX isn’t expected to be available until later this year, so in the meantime, consider evaluating alternatives for network virtualization that are actually shipping today. In this article, I’ve included a learning roadmap for understanding and evaluating our network virtualization solution, Hyper-V Network Virtualization in Windows Server 2012 ...
UPDATE: With the upcoming release of Windows Server 2012 R2, we've announced several changes to RDS CAL licensing. One of these changes is that, by next year, customers with Software Assurance (SA) will be able to leverage their existing RDS CALs with license mobility to apply to either an on-premises Remote Desktop Services installation or a deployment of Remote Desktop Services on Windows Azure. This new RDS licensing option, when available, will provide an additional choice for licensing RDS on Windows Azure, as an alternative to using RDS Subscriber Access Licenses (SALs) noted below in this article.
For more details on the RDS licensing changes in Windows Server 2012 R2, please see the Windows Server 2012 R2 RDS Licensing FAQ on the Microsoft Download Center.
In Part 1 of this two-part article series, we introduced Remote Desktop Session Virtualization on Windows Azure as an attractive alternative to traditional Desktop as a Service ( DaaS ) solutions. Remote Desktop Session Virtualization provides a high-density solution that requires provisioning and managing far fewer VMs than traditional DaaS, while still providing a robust and highly compatible method for delivery of high-fidelity remote desktop and remote application experiences to users.
In this article, we’ll step through the provisioning process for configuring a Remote Desktop Session Virtualization lab environment on the Windows Azure pay-as-you-go cloud platform. Our lab environment will consist of two VMs: one VM configured as an Active Directory Domain Controller and DNS server, and a second VM configured as a Remote Desktop Session Host, Web Access gateway, and Connection Broker.
Update for Windows 8.1: Note that System Image Backup in Windows 8.1 has been moved to the lower left corner of the File History tool in Control Panel as shown below.
In addition, the Windows 7 File Recovery tool in Control Panel has been renamed to the Recovery tool in Windows 8.1.
Have you recently installed Windows 8? In this article, we'll introduce you to the new options available for making Backup and Recovery in Windows 8 easier than ever, including Windows 8 File History, launching Windows System Backup and Windows 8 Refresh & Reset PC.
No matter which virtualization platform you may be using today to power your Private Cloud, storage is probably one of your biggest costs, and perhaps one of your biggest pain points, too. Virtualized environments are, by their very nature, dynamic environments where storage requirements from one VM to the next can grow and evolve over time. Traditional enterprise storage infrastructures, while offering flexibility in provisioning storage, are often built from a more static “set-it-and-forget-it” standpoint – provision your storage pools, LUNs, storage processors and SAN connectivity upfront with the expectation that storage needs on a workload-by-workload basis will not evolve.
When supporting Private Clouds, many administrators require ongoing dynamic control and automation for the storage platforms in use within an enterprise. In this article, we’ll compare and contrast the dynamic storage capabilities that I regularly use in the latest versions of two common enterprise virtualization platforms: VMware vSphere 5.5 and Microsoft Windows Server 2012 R2 Hyper-V.
Specifically, we’ll be reviewing the following dynamic storage capabilities for VMs in this article:
Along the way, we’ll find that Microsoft virtualization solutions can provide substantial cost advantages in this area, as well as provide better storage support for heterogeneous virtualization environments with more than one hypervisor platform …
At a recent community event, I met “Scott”, a savvy IT Pro who was in the process of planning the architecture for a new datacenter location at his company. Scott is an experienced datacenter engineer who manages several other virtualized datacenters. Although he is currently running VMware for the hypervisor platform in his existing datacenters, he was intrigued by Windows Server 2012 and the free Hyper-V Server 2012 enterprise-grade bare-metal hypervisor, primarily because he had been hearing good things about Hyper-V from peers who had been evaluating Microsoft Private Cloud in their organizations.
So, Scott decided to go on a “shopping trip” to explore what would be involved with implementing the Private Cloud solution he was looking for in his next datacenter. What Scott found really surprised him in terms of capabilities and dramatic cost differences when leveraging Microsoft Private Cloud vs the related VMware offerings. Read on to learn about Scott’s findings … you may be shocked too!
This article provides a summary of Scott’s interesting journey and reports on his findings from his research on implementing Private Clouds using Microsoft Private Cloud vs VMware vSphere, vCenter and vCloud offerings ...