Moving to hybrid cloud

with Windows Azure Virtual Machines & System Center 2012 R2

Hands-On Lab | Step-by-Step Guide

Lab 4 – Hybrid Data Protection

Lab version: 2.0.1

Last updated: November 6, 2013

Important: these VMs were built using evaluation software. To ensure that the labs continue to function after the evaluation period has expired, hosters will start the VMs from a saved state and so the VMs will not resync their time unless they are rebooted. Avoid rebooting any VMs during this lab

For all labs, use the following credentials:

  • Username:    Contoso\Administrator
  • Password:    Passw0rd!

Contents

Contents    2

Overview    3

Lab 4: Hybrid Data Protection    4

Exercise 4.1: DPM Backup to Windows Azure    4

    Create a Windows Azure Backup Vault    4

    Create a Windows Azure Backup Certificate    5

    Configure System Center Data Protection Manager Backup    6

    Backup a file to Windows Azure    8

    Restore a file from Windows Azure    9

Exercise 4.2: Install and configure System Center Operations manager Global Service Monitoring Management Pack    10

    Create a Windows Azure Backup Vault    10

    Create a Windows Azure Backup Certificate    11

    Configure Windows Server Backup    12

    Backup a File to Windows Azure    13

    Restore a File from Windows Azure    13

Exercise 4.3: Configuring the System Center Advisor Connector    14

    Configure the Orchestrator Runbook    14

    Start the runbook and review deprovisioning logic    16

    View the deprovisioning process in the Windows Azure Portal    17

  Read More


Moving to hybrid cloud

with Windows Azure Virtual Machines & System Center 2012 R2

Hands-On Lab | Step-by-Step Guide

Lab 3 – Hybrid and Cloud-only monitoring

Important: these VMs were built using evaluation software. To ensure that the labs continue to function after the evaluation period has expired, hosters will start the VMs from a saved state and so the VMs will not resync their time unless they are rebooted. Avoid rebooting any VMs during this lab

For all labs, use the following credentials:

  • Username:    Contoso\Administrator
  • Password:    Passw0rd!

Contents

Contents    2

Overview    3

Lab 3: Hybrid and Cloud-only monitoring    4

Exercise 3.1: Configuring the Windows Azure Fabric Management Pack    4

    Install the Management Pack    4

    Setup and Configure the Management Pack    7

    Monitoring resources and taking action    16

Exercise 2.2: Install and configure System Center Operations manager Global Service Monitoring Management Pack    27

    Installing the Operations Manager Global Service Monitoring Management Pack    27

    Confirm Windows Server prerequisites for Global Service Monitoring Management Pack    28

    Configure prerequisites for Operations Manager Alert Attachment Management Pack and import into Operations Manager    28

    Import the Operations Manager Global Service Monitor Management Pack    31

    Enable the Global Service Monitor Management Pack and monitor a Windows Azure website.    32

    Review the Global Service Monitor service connection state and Fabrikam Fiber website availability.    36

Exercise 3.3: Configuring the System Center Advisor Connector    39

    Install and Configure the SC Advisor Connector    39

    Explore Solution Components and Results    43

Exercise 3.4: Windows Azure Monitoring and Auto-Scaling    48

    Working with Windows Azure Monitoring    48

    Configure a Azure Service Monitor    49

    Test Windows Azure Monitoring    50

    Working with Windows Azure Auto-Scaling    51

Read More


Moving to hybrid cloud

with Windows Azure Virtual Machines & System Center 2012 R2

Hands-On Lab | Step-by-Step Guide

Lab 2 – Hybrid Using App Controller

Lab version: 2.0.1

Last updated: November 6, 2013

Important: these VMs were built using evaluation software. To ensure that the labs continue to function after the evaluation period has expired, hosters will start the VMs from a saved state and so the VMs will not resync their time unless they are rebooted. Avoid rebooting any VMs during this lab

For all labs, use the following credentials:

  • Username:    Contoso\Administrator
  • Password:    Passw0rd!

  1. Contents

    Contents    2

    Overview    3

    Lab 2: Hybrid Using App Controller    4

    Exercise 2.1: Connect App Controller to Windows Azure    4

        Create Connection Certificate    4

        Upload the certificate to your Azure subscription    4

        Export the certificate to use with App Controller    5

        Connect App Controller to Windows Azure    5

    Exercise 2.2: Working with Windows Azure and App Controller    8

        Copy Fabrikam Fiber Resources to Windows Azure    8

        Deploy Fabrikam Fiber to Windows Azure    9

    Read More


Moving to hybrid cloud

with Windows Azure Virtual Machines & System Center 2012 R2

Hands-On Lab | Step-by-Step Guide

Lab 1 – Automatic Hybrid Using System Center Service Manger and Orchestrator

Important: these VMs were built using evaluation software. To ensure that the labs continue to function after the evaluation period has expired, hosters will start the VMs from a saved state and so the VMs will not resync their time unless they are rebooted. Avoid rebooting any VMs during this lab

For all labs, use the following credentials:

  • Username:    Contoso\Administrator
  • Password:    Passw0rd!

  1. Contents

    Contents    2

    Overview    3

    Lab 1: Automatic Hybrid Using System Center Service Manger and Orchestrator    4

    Exercise 1.1: Provisioning a Development Environment in Azure    4

        Prerequisites    4

        Complete the Self-Service Request Form    4

        Review the Solution Components in SCSM and SCO    8

        View the Results in the Windows Azure Portal    12

    Exercise 1.2: Deploying Resources in Azure IaaS using the System Center 2012 Integration Pack for Azure    14

        Configure a self-signed certificate for use with the Azure Management API    14

        Upload the certificate to your Azure subscription    15

        Update the Azure Integration Pack Global Configuration settings in Orchestrator    15

        Complete the configuration of the VM deployment runbook    16

        Review the runbook worklow and run the runbook to deploy VM    18

        Log into the Windows Azure Portal to verify the VM deployment    19

    Read More


Moving to hybrid cloud

with Windows Azure Virtual Machines & System Center 2012 R2

Hands-On Lab | Step-by-Step Guide

Lab 0 – Provisioning a Windows Azure Virtual Machine

Lab version: 2.0.1

Last updated: November 6, 2013

Important: these VMs were built using evaluation software. To ensure that the labs continue to function after the evaluation period has expired, hosters will start the VMs from a saved state and so the VMs will not resync their time unless they are rebooted. Avoid rebooting any VMs during this lab

For all labs, use the following credentials:

  • Username:    Contoso\Administrator
  • Password:    Passw0rd!

  1. Contents

    Contents    2

    Overview    3

    Lab 0: Provisioning a Windows Azure Virtual Machine    4

    Exercise 0.1: Provisioning a Windows Azure VM    4

        Prerequisites    4

        Create a new Virtual Network    4

        Create a new virtual machine from the gallery image    4

    Exercise 0.2: Deploy Active Directory using GUI in Windows Azure    4

        Deploy a new domain controller in Windows Server 2012 R2    10

    Read More

Cumulative Update 1 (CU1) for System Center 2012 R2 Configuration Manager is now available as a hotfix download fromKB 2938441. This update contains fixes for various issues including Windows PowerShell, and an updated version of the Endpoint Protection client.

For more information about the Windows PowerShell changes, refer to the following knowledge base article:

KB 2932274: Description of PowerShell changes available in Cumulative Update 1 for System Center 2012 R2 Configuration Manager Read More

You cannot stage a Windows PE 3.1 boot image to a Windows XP-based computer in System Center 2012 R2 Configuration Manager

Microsoft has released a hotfix for SCCM 2012 R2 to allow you to deploy Windows 8.1 / Windows 7 to a Windows XP computer.


Assume that you install or upgrade to Microsoft System Center 2012 R2 Configuration Manager on a System Center Configuration Manager site server. When you try to deploy a task sequence that has an associated Windows PE 3.1 boot image to a Windows XP-based computer Read More

Technical Reference for Ports Used in Configuration Manager

After a few days that I have been fighting in my last implementation of ConfigMgr i think its a good idea to refresh the port used in Configuration Manager.

This topic appears n the Site Administration for System Center 2012 Configuration Manager guide and in the Security and Privacy for System Center 2012 Configuration Manager.

System Center 2012 Configuration Manager is a distributed client/server system. The distributed nature of Configuration Manager means that connections can be established between site servers, site systems, and clients. Some connections use ports that are not configurable, and some support custom ports you specify. You must verify that the required ports are available if you use any port filtering technology such as firewalls, routers, proxy servers, and IPsec.


The port listings that follow are used by Configuration Manager and do not include information for standard Windows services, such as Group Policy settings for Active Directory Domain Services and Kerberos authentication. For information about Windows Server services and ports, see Service overview and network port requirements for the Windows Server system.

In this post:

    Configurable Ports

    Non-Configurable Ports

    Ports Used by Configuration Manager Clients and Site Systems

    Additional Lists of Ports

    AMT Out of Band Management Ports

    Client to Server Shares

    Connections to Microsoft SQL Server

    External Connections made by Configuration Manager

    Installation Requirements for Site Systems that Support Internet-Based Clients

    Ports Used by Configuration Manager Client Installation

    Ports Used by Migration

    Ports Used by Windows Server

Configurable Ports

Configuration Manager allows you to configure the ports for the following types of communication:

    Application Catalog Website point to Application Catalog web service point

    Enrollment proxy point to enrollment point

    Client to site systems that run IIS

    Client to Internet (as proxy server settings)

    Software update point to Internet (as proxy server settings)

    Software update point to WSUS server

    Site server to site database server

    Reporting services points

By default, the HTTP port used for client to site system communication is port 80, and the default HTTPS port is 443. Ports for client-to-site system communication over HTTP or HTTPS can be changed during Setup or in the Site Properties for your Configuration Manager site.

The ports in use for the reporting services point site system role are configured in SQL Server Reporting Services. These ports are then used by Configuration Manager during communications to the reporting services point. Be sure to review these ports defining the IP filter information for IPsec policies or for configuring firewalls.

Non-Configurable Ports

Configuration Manager does not allow you to configure ports for the following types of communication:

    Site to site

    Site server to site system

    Configuration Manager console to SMS Provider

    Configuration Manager console to the Internet

    Connections to cloud services, such as Windows Intune and cloud-based distribution points

Ports Used by Configuration Manager Clients and Site Systems

The following sections detail the ports used for communication in Configuration Manager. The arrows in the section title, between the computers, represent the direction of the communication:

    – > indicates one computer initiates communication and the other computer always responds

    < — > indicates that either computer can initiate communication

Asset Intelligence Synchronization Point — > Microsoft

Description UDP TCP
Secure Hypertext Transfer Protocol (HTTPS) 443

Read More

Are you interested in learning how to deploy Windows 8.1 correctly?  Attendees of this Jump Start will find out how to avoid deployment pitfalls and how to streamline theprocess from a team of experts.

The Jump Start is March 12th, 2014 from 9am-1pm PDT.

COURSE OUTLINE:

  • OS Deployment Scenarios
  • OS Deployment Tools Overview
  • Overview of Windows ADK 8.1 and WDS
  • Introduction to the MDT 2013
  • Identify, Build, and Test Master Images
  • Import Master Images
  • Create Deployment Task Sequences
  • Enable Dynamic Deployment (Rules)
  • Configuration Manager 2012 R2

Register today!

When we have to build Servers for many different scenarios, it sure is helpful to have a base Windows OS Image handy to start with. Even though it seems simple, I thought I would share my personal experience and “How To” steps to help those who are still somewhat new to this process. I happen to use Hyper-V for all of my virtualization stuff so my instructions will be based on this.

The first thing I take into consideration is the versions of Windows Operating Systems that I plan on using during my testing, learning and demos.

Based on the different scenarios that I tend to evaluate, I happen to need the following:

Since the process of building the image is pretty much the same for all above operating systems, you will not need to follow all the examples.

Here are my “How To” Steps:

Watch on youtube

Or follow these steps:

  1. On your computer, open Hyper-V Manager
  2. In Hyper-V Manager, in the actions pane, click New and then click Virtual Machine
  3. In the New Virtual Machine Wizard, on the Before You Begin page, click Next

4- On the Specify Name and Location page, in the Name field, type en_base_windows2012R2 and then click Next

Read More

When we have to build Servers for many different scenarios, it sure is helpful to have a base Windows OS Image handy to start with. Even though it seems simple, I thought I would share my personal experience and “How To” steps to help those who are still somewhat new to this process. I happen to use Hyper-V for all of my virtualization stuff so my instructions will be based on this.

The first thing I take into consideration is the versions of Windows Operating Systems that I plan on using during my testing, learning and demos.

Based on the different scenarios that I tend to evaluate, I happen to need the following:

Since the process of building the image is pretty much the same for all above operating systems, you will not need to follow all the examples.

Here are my “How To” Steps:

Youtube video

Step by Steps

  1. On your computer, open Hyper-V Manager
  2. In Hyper-V Manager, in the actions pane, click New and then click Virtual Machine
  3. In the New Virtual Machine Wizard, on the Before You Begin page, click Next
  4. On the Specify Name and Location page, in the Name field, type en_base_windows_8.1, and then click Next

Read More

When we have to build Servers for many different scenarios, it sure is helpful to have a base Windows OS Image handy to start with. Even though it seems simple, I thought I would share my personal experience and “How To” steps to help those who are still somewhat new to this process. I happen to use Hyper-V for all of my virtualization stuff so my instructions will be based on this.

The first thing I take into consideration is the versions of Windows Operating Systems that I plan on using during my testing, learning and demos.

Based on the different scenarios that I tend to evaluate, I happen to need the following:

Since the process of building the image is pretty much the same for all above operating systems, you will not need to follow all the examples.

Here are my “How To” Steps:

Video on youtube

or follow the steps:

  1. On your computer, open Hyper-V Manager
  2. In Hyper-V Manager, in the actions pane, click New and then click Virtual Machine
  3. In the New Virtual Machine Wizard, on the Before You Begin page, click Next

Read More

Azure IT Camp

Hands-On Lab

1- Set Up Azure Environment

2- Setup Virtual Machines

3- Upload VMs from On-Premise to Cloud

4- Deploy app from on-premise VM to PaaS instance

5- Virtual Network

6- Traffic Manager

7- Backup

8- Deploy Active Directory in Windows Azure

Gallery

Azure IT Camp

Hands-On Lab

Deploy Active Directory in Windows Azure

Lab version:    2.0

Last updated:    September 19, 2013

This guide contains step-by-step instructions for the labs and demos for the Azure VM IT Camp.

For all labs, use the following credentials:

  • Username:    Contoso\Administrator
  • Password:    Passw0rd!

  1. Contents

    Contents    2

    Overview    3

    Lab 8: Deploy Active Directory in Windows Azure    4

    Tasks in this Lab Module    4

    Examine the current Domain Controller configuration    4

    (Option A) Create a new Virtual Machine with a data disk – by using the Azure portal    7

    (Option B) Create a new Virtual Machine with a data disk – by using Azure PowerShell    10

    Configure a new data disk    12

    (Option A) Create a Domain Controller – by using Server Manager (GUI)    16

    (Option B) Create a Domain Controller – by using PowerShell    22

    Read More

View Herman Arnedo Mahr's profile on LinkedIn
Español / English
Follow me on Twitter

Enter your email address to subscribe to this blog and receive notifications of new posts by email.