Last updated by at .

  • Microsoft Azure
  • Virtual Machine Manager

Tag: System Center

SCVMM Bare-Metal Fails

Add drivers to SCVMM Bare-Metal WinPE Image

A long time ago I wrote a blog post on how you can use System Center Virtual Machine Manager Bare-Metal Deployment to deploy new Hyper-V hosts. Normally this works fine but if you have newer hardware, your Windows Server Image does may not include the network adapter drivers. Now this isn’t a huge problem since you can mount and insert the drivers in the VHD or VHDX file for the Windows Server Hyper-V image. But if you forget to update the WinPE file from Virtual Machine Manager your deployment will fails, since the WinPE image has not network drivers included it won’t able to connect to the VMM Library or any other server.

You will end up in the following error and your deployment will timeout on the following screen:

“Synchronizing Time with Server”

SCVMM Bare-Metal Fails

If you check the IP configuration with ipconfig you will see that there are no network adapters available. This means you have to update your SCVMM WinPE image.

First of all you have to copy the SCVMM WinPE image. You can find this wim file on your WDS (Windows Deployment) PXE Server in the following location E:\RemoteInstall\DCMgr\Boot\WIndows\Images (Probably your setup has another drive letter.

WDS SCVMM Boot WIM

I copied this file to the C:\temp folder on my System Center Virtual Machine Manager server. I also copied the extracted drivers to the C:\Drivers folder.

After you have done this, you can use Greg Casanza’s (Microsoft) SCVMM Windows PE driver injection script, which will add the drivers to the WinPE Image (Boot.wim) and will publish this new boot.wim to all your WDS servers. I also rewrote the script I got from using drivers in the VMM Library to use drivers from a folder.

Update SCVMM WinPE

This will add the drivers to the Boot.wim file and publish it to the WDS servers.

Update WDS Server

After this is done the Boot.wim will work with your new drivers.

 

 

 

 

 



Microsoft System Center Logo

Technical Documentation for Getting Started with System Center 2012 R2

Marcel van den Berg just posted a blog post about the availability of the Technical Documentation for Getting Started with System Center 2012 R2 which was just released by Microsoft. The Technical Documentation covers the Support Matrix and Upgrade Sequence for System Center 2012 R2.

System Center 2012 R2 Requirements

You can download the documents on the Microsoft Download website.



Cisco Microsoft

Cisco and Microsoft Announce Sales and Go-to-Market Agreement

At the Worldwide Partner Conference 2014 Cisco and Microsoft announced a multi-year sales and go-to-market agreement designed to modernize data centers through the delivery and acceleration of integrated solutions. This will focus on bringing a deeper integration between the datacenter technologies of both companies. This includes Cisco UCS and Nexus products as well as Microsoft’s CloudOS solutions based Windows Server, Hyper-V, System Center, SQL Server and Microsoft Azure.

Highlights:

Go-to-Market:

  • Cisco and Microsoft agree to a three-year go-to-market plan focused on transforming data centers through the delivery of integrated solutions for enterprise customers and service providers.
  • In year one, the companies will focus on six countries — the United States, Canada, UK, Germany, France, and Australia — with expansion to additional countries in the following years.
  • Cisco and Microsoft will align partner incentive programs to accelerate solutions selling via mutual channel partners.
  • Cisco and Microsoft sales teams will work together on cloud and data center opportunities, including an initial program focused on the migration of Windows 2003 customers to Windows 2012 R2 on the Cisco UCS platform.

Integrated Solutions:

  • Integrated solutions will focus on private cloud, server migration, service provider, and SQL Server 2014
  • Cisco technologies to include Cisco UCS, Cisco Nexus switching, Cisco UCS Manager with System Center integration modules, and Cisco PowerTool.
  • Cisco-based integrated infrastructure solutions will include FlexPod with NetApp and Cisco Solutions for EMC VXPEX.
  • Microsoft technology includes Windows Server 2012 R2, System Center 2012 R2, PowerShell, Microsoft Azure and SQL Server 2014
  • Cisco Application Centric Infrastructure and Cisco InterCloud Fabric to be integrated in the solutions in future releases

Source and More information: www.streetinsider.com

As you may know I am a Microsoft MVP and a Cisco Champion and I really like doing project with Cisco Hardware since they do a lot of integration with the Microsoft Stack especially System Center and PowerShell. In my opinion this could be a strong partnership and will make life of a lot of people a lot easier.



Windows Azure Pack Feedback

Feedback for Windows Azure Pack

Since the release of Windows Server 2012 R2 and System Center 2012 R2 I worked on several different Windows Azure Pack deployments for Service Providers. Windows Azure Pack delivers Microsoft Azure technologies for you to run inside your datacenter. It offers rich, self-service, multi-tenant services and experiences that are consistent with Microsoft’s public cloud offering. Together with technologies like Hyper-V Network Virtualization and Microsoft Storage Spaces Windows Azure Pack becomes a powerful framework for Service Providers.

You can help shape the future of Windows Azure Pack. The Windows Azure Pack team has created a user voice site where you can post feature suggestions and vote on the suggestions of others.

You can find the Azure Pack user voice site here http://feedback.azure.com/forums/255259-azure-pack

 

 

 



InovatiX

Back from inovatiX Amsterdam 2014

A little over 24 hours the itnetx team arrived at the Zurich airport. At the end of last week some of you may have seen a lot of tweets around Microsoft System Center with the hashtag #inovatiX. Well the name inovatiX comes from the company names of inovativ and itnetx. Both companies do focus on Microsoft Cloud solutions based on System Center, Windows Server, Hyper-V and Microsoft Azure. So what is behind that inovatiX event. InovatiX was the first run of the know-how sharing event between inovativ.nl, inovativ.be and itnetx.ch. In different focus groups around topics like Windows Azure Pack, Hyper-V, Config Manager, Windows InTune, Operations Manager, VMM or Microsoft Azure,  the cloud experts of those companies shared knowledge and experience with real world deployments.

InovatiX

For me personally I had some great talks about Windows Azure Pack, Hyper-V, VMM, Storage Spaces, Scale-Out File Servers, Network Virtualization and a lot more. And it was fun to finally meet the guys from inovativ in person.

InovatiX

This event was a perfect example how different companies can collaborate with each other to evolve and to make the quality even better, and help employees to Thanks here to the management of Inovativ and itnetx for organizing this.



Azure Site Recovery

Microsoft Azure Site Recovery Preview

Microsoft today announced the preview of Disaster Recovery to Azure called Microsoft Azure Site Recovery. This also replaces HRM (Hyper-V Recovery Manager). Microsoft Azure Site Recovery (ASR) allows you to orchestrate disaster recovery to a second site or directly to Azure.

Microsoft ASR

Both solutions use Microsoft on-prem technology like Windows Server Hyper-V Replica and System Center Virtual Machine Manager and you can start using them via the Microsoft Azure Management Portal.

In addition to enabling Microsoft Azure as a DR site in multiple geographies, this preview also includes an impressive list of features for enabling virtual machine replication to Azure:

  • At-Scale Configuration
    You can configure the protection and replication of VM settings in a private cloud and configure and connect on-prem networks with Azure Networks. Those VM’s are then only replicated to customer-owned and managed geo-redundant Azure Storage.
  • Variable Recovery Point Objective (RPO)
    This feature provides support for near-synchronous data replication with RPOs as low as 30 seconds. You can also retain consistent snapshots at desired frequency for a 24-hour window.
  • Data Encryption
    VM Virtual Hard Disks can be encrypted at rest using a secure, customer-managed encryption key that ensures best-in-class security and privacy for your application data when it is replicating to Azure. This encryption key is known only to the customer and it is needed for the failover of VM’s to Azure. Simply put: All of this service’s traffic within Azure is encrypted.
  • Self-Service Disaster Recovery
    With ASR you get full support for DR drills via test failover, planned failover with a zero-data loss, unplanned failover, and failback.
  • One-Click Orchestration
    ASR also provides easy-to-create, customizable Recovery Plans to ensure one-click failovers and failbacks that are always accurate, consistent, and help you achieve your Recovery Time Objective (RTO) goals.
  • Audit and Compliance Reporting with Reliable Recovery
    DR testing and drills can be performed without any impact to production workloads. This means you get risk-free, high-confidence testing that meets your compliance objectives. You can run these non-disruptive test failovers whenever you like, as often as you like. Also, with the ability to generate reports for every activity performed using the service, you can meet all your audit requirements.

ASR does not only help you in terms of Disaster Recovery, it also allows you to quickly and easily migrate your Virtual Machines to Azure or create a new dev environment.

Check out the ASR session at TechEd 2014 and Brad Andersons blog about the release of the Azure Site Recovery Preview.

Once you’re ready to see what ASR can do for you, you can check out pricing information, sign up for a free trial, or learn more about the product specs.

 

 



SMA Author RunBooks in Windows Azure Pack

Service Management Automation – The Next Step in Cloud and Datacenter Automation

With System Center Orchestrator Microsoft already had an datacenter automation engine in his portfolio. Microsoft acquired Opalis added it to the System Center Suite, after a while Microsoft renamed Opalis to System Center Orchestrator. As we have a look at modern datacenters and our cloud environment automation is a key part of it. With the latest release of System Center 2012 R2 and Windows Azure Pack, Microsoft release a new automation engine based on PowerShell Workflows called Service Management Automation (SMA).

Windows Azure Pack Automation with SMA

SMA is integrated as one of the key Resource Provider in Windows Azure Pack, and allows you to manage your PowerShell Workflows in so called Runbooks. Service Management Automation enhances PowerShell Workflows in several different ways.

  • Centralized management
  • Centralized store for variables, credentials, certificates, connections, modules, workflows, checkpoints and schedules.
  • High availability workflow execution
  • Versioning
  • Odata web service (HTTP API)
  • Historical view of workflow jobs and their output

Architecture

SMA is build form several different components.

  • Web Service – HTTP/HTTPS API which distributes runbook jobs to runbook workers and builds the connection to Widnwos Azure Pack
  • Runbook worker – Executes Runbooks
  • PowerShell module – Enables SMA to be managed by Windows PowerShell
  • Windows Azure Pack - UI for administrators to create and manage runbooks
  • SQL database – Store for Runbooks and settings

SMA Architecture

  • The Automation web service communicates with Windows Azure Pack and authenticates users.
  • The SQL Server databases store and retrieve runbooks, runbook assets, activities, integration modules, and runbook job information.
  • Runbook workers run the runbooks, and they can be used for load balancing.
  • The management portal in Windows Azure Pack is where you author, debug, and start and stop runbooks.

Source: TechNet

One of the greats enhancements Service Management Automation together with Windows Azure Pack brings is the possibility to link runbooks to SPF and VMM activates used in the Virtual Machine Cloud. What does this mean? For example you link a runbook to a Create Virtual Machine activity, so every time a VM gets created the runbooks starts and also gets as input object the VM which was created. This is just one example what you can do with SMA and Windows Azure Pack VM Cloud, there are a lot of other possibilities as well.

If you compare System Center Orchestrator to Service Management Automation, SMA looks a little bit more complex if you have used a lot of Integrations Packs in SCORCH but if you have done a lot of work in PowerShell you will really like SMA and see the advantages of it.

Service Management Automation does not offer an user interface by itself, instead it is using the Windows Azure Pack portal, where admins can author, run, schedule and link runbooks.

SMA Author RunBooks in Windows Azure Pack