You are browsing the archive for Private Cloud.

2016: My blog year in an overview

2:37 pm in Azure, Azure Backup, Azure RemoteApp, Client Hyper-V, Cloud, DC, Hyper-V, IaaS, PowerShell, Private Cloud, Public Cloud, Replica DC, SCAC 2012 R2, SCVMM 2012 R2, System Center 2016, W2K12R2, Windows 10 by Wim Matthyssen

Hi all,

As a blogger completely focused on Microsoft technologies, it was a fun year of writing about all those interesting and ever changing products and services. As we almost end the year 2016 and are preparing for 2017 to start, I wanted to make a list of all the blog posts I wrote throughout the twelve months of 2016. During the year, I’ve published 26 blog posts mostly about Azure, the System Center Suite and Hyper-V. Below you can find them all divided by technology.

 

clip_image002

Azure Compute – IaaS (ASM)

Step-by-step: Move an Azure IaaS VM between different Azure Subscriptions

Clean up Azure PowerShell when using different Azure subscriptions

Replica DCs on Azure – Removing the Azure Endpoints

Replica DCs on Azure – Transferring FSMO roles to the IaaS DCs

Replica DCs on Azure – Manage the Time Configuration settings on the DCs

Replica DCs on Azure – Domain Controller Health Check

Replica DCs on Azure – Promote the Azure IaaS VMs to a domain controller

Replica DCs on Azure – Add the Active Directory Domain Services role

Replica DCs on Azure – Adjustment of some server settings before promoting the DCs

Replica DCs on Azure – Initialize and format the additional data disk

Replica DCs on Microsoft Azure – Create the VMs with Azure PowerShell

Step by step: Change the drive letter of the Temporary Storage on an Azure IaaS v1 VM

 

Azure Networking

How to connect an Azure ARM VNet to an ASM VNet using VNet Peering

Replica DCs on Azure – Switch DNS servers for the VNet

Replica DCs on Azure – Create the Active Directory site for the Azure VNet

 

Azure Backup

Microsoft Azure Backup Server: Install a new version of the Microsoft Azure Recovery Services Agent

Microsoft Azure Backup Server: System State backup fails with WSB Event ID: 546

Microsoft Azure Backup Server: System State backup fails with the message replica is inconsistent

Step by step: How to install Microsoft Azure Backup Server (MABS)

 

Azure RemoteApp

An RDP connection to the Azure RemoteApp custom VM fails with the following error: “No Remote Desktop License Servers available”

 

Windows 10

How to deploy Windows 10 from a USB flash drive

 

System Center

System Center 2016 evaluation VHDs download links

Step by step: How to connect SCAC 2012 R2 to SCVMM 2012 R2 and Microsoft Azure

Step by step: Installing SCAC 2012 R2

 

Hyper-V

A list of tools that can be used to do a V2V from VMware to Hyper-V

Client Hyper-V – Using nested virtualization to run Client Hyper-V on a Windows 10 VM

 

Before I wrap up this blog post, I want to thank you all for reading my blog posts in 2016, and I really hope you will keep doing so in 2017. I wish you all a healthy, successful and outstanding New Year! See you all in 2017!

Wim Matthyssen (@wmatthyssen)

Step by step: How to install Microsoft Azure Backup Server (MABS)

3:11 pm in Azure, Azure Backup, Cloud, Hyper-V, IaaS, Private Cloud, Public Cloud, SCDPM by Wim Matthyssen

Microsoft Azure Backup Server (MABS) previously known as “Project Venus”, which was released by Microsoft on October 7th 2015 is a disk-to-disk-to-cloud backup (D2D2C) product, which uses an Azure Backup vault for long-term offsite retention. Basically it’s a lightweight customized version of System Center Data Protection Manager 2012 R2 (SCDPM) which offers centralized management and monitoring for your Azure Backup setup(s) and agents in a single console. Just like SCDPM, it can protect business applications workloads such as Exchange, SQL Server, Active Directory, IIS, Hyper-V virtual machines (VMs), VMware VMs, physical servers and Windows clients which can be running on premise or in the Azure cloud. MABS also comes with support for backup of large data sources, long-term retention up to 99 years and the capability to recover data in your Azure Backup vault using an alternate server. As part of the Operations Management Suite (OMS), one of the primary use cases for MABS will be for hybrid cloud backup scenarios.

clip_image001

 

Before we start whit the installation also a list of some things to keep in mind:

  • MABS is included as a free download with Azure Backup (link on your Azure Backup vault page) or you can download it directly via following link: https://www.microsoft.com/en-us/download/details.aspx?id=49170
  • MABS can be installed as an on premise standalone physical server or VM, but also as an Azure IaaS VM (size A2 or higher).
  • When you run MABS on an Azure VM you can only protect workloads also running on Azure VMs.
  • MABS will run on following supported Operating Systems: W2K8 R2 SP1, W2K12 or W2K12 R2 (is recommended).
  • MABS must be domain joined. Be sure to add the server to the domain before the MABS installation, because adding this server to the domain after the MABS installation is not supported.
  • MABS must have .Net 3.5, .Net 4.0 and .Net 3.5 SP1 features installed as a prerequisite.
  • The processor minimum requirements for a MABS server are 1GHz dual-core CPU, recommended 2.33 GHz quad-core CPU.
  • The minimum RAM needed by a MABS server is 4GB, recommended is 8 GB.
  • A free SQL Server 2014 license, which can only be used with MABS is included.
  • MABS will not work with a remote SQL Server instance. The instance being used needs to be local.
  • MABS cannot be installed on a server already running SCDPM or a SCDPM agent. It also cannot be installed on a server running any Microsoft Azure backup agent version.
  • A valid Windows Server license is needed for the MABS server.
  • You need to add  local backup storage to use MABS, because in the current architecture of MABS, the Azure Backup vault holds the second copy of the data while the local storage holds the first (and mandatory) backup copy.
  • An Azure Subscription and an Azure Backup vault needs to be in place before setting up the MABS server.
  • The MABS sever needs to have access to the Internet because Microsoft Azure should be accessible.
  • In contrast to SCDPM there is no support for tape drives
  • Some scratch space is needed to temporarily store the largest restore from the Azure cloud when needed. So keep approximately 5 % of the total amount of data that needs to be backed-up to the cloud free on the C: drive.
  • MABS doesn’t integrate with products of the System Center suite.
  • A separate data disk for the backup storage pool is needed. Like every other backup product the recommendation for the size of this disk is 1.5 times the size of the data you’re going to protect.
  • The default storage replication setting (storage redundancy option) when you create an Azure Backup vault is Geo Redundant Storage (GRS), be aware that for most customers Locally Redundant Storage (LRS) is more than enough.
  • There will be no charges for restores, outbound bandwidth and storage transactions when you use MABS.
  • If the MABS server fails with errors during the setup or while taking a backup or restoring data, refer to following link to find more information: https://support.microsoft.com/en-us/kb/3041338
  • You can find Azure Backup pricing details via following link: https://azure.microsoft.com/en-in/pricing/details/backup/
  • In my example I’m installing MABS on a W2K12 R2 Hyper-V VM. Before starting I first added the .NET Framework 3.5 Features via the Add Roles and Features Wizard.

So after this brief introduction and things to keep in mind, it’s time to setup the MABS sever. To do so follow the steps described below:

 

1) First we need to setup an Azure Backup vault. So logon to your Azure Subscription via the classic portal (https://manage.windowsazure.com/). When your logged go to the bottom of the screen and click New, select Data Services, select Recovery Services and select Backup Vault

clip_image003

2) Next select Quick Create and fill in a Name and the proper Region (in my case the region is West Europe).

clip_image005

clip_image007

clip_image009

3) When the Azure Backup vault is created you can change the storage replication setting if preferred. In my example I will switch it to LRS. To switch select Recovery Services, select your Azure Backup vault, select Configure, select Locally Redundant and click Save at the bottom of the screen

clip_image011

4) Download the vault credential and when downloaded, place it the C:\Temp folder on the MABS server. To do so click on DASHBOARD and click Vault credentials. When you’re asked to open or save the vault credentials, click Save. After the download move it to the correct folder

clip_image013

clip_image015

clip_image017

5) When the Azure Backup vault is created we need to download the necessary files to install MABS. In my example I will download all necessary software packages from the separate link. When you go to this link select all files and click Next. Be aware that because of the size of all files together (approximately 3 GB), this download could take a while

clip_image019

6) I’ve stored all the files under my C:Temp folder on the MABS server

clip_image021

7) Run MicrosoftAzureBackupInstaller.exe from the download folder (C:\Temp) as an administrator

clip_image022

8) Click Next

clip_image023

9) Leave the default location and click Next

clip_image024

10) Click on Extract to begin extracting the setup files

clip_image025

clip_image026

11) Select Execute setup.exe (if not already selected) and click Finish

clip_image027

12) Click Microsoft Azure Backup to launch the setup wizard

clip_image029

13) The Microsoft Visual VC++ 2010 Redistributable Package (x64) will be installed in the foreground

clip_image030

14) On the Welcome screen click the Next

 

clip_image032

15) This opens up the Prerequisite Check section. On this screen, click on the Check button to determine if the hardware and software prerequisites for Azure Backup Server have been met. If all of is OK, you will see a message indicating that the machine meets the requirements. Click Next

clip_image034

16) On the SQL Settings page select Install new Instance of SQL Server with this Setup, to install SQL 2014 Standard. Click Check and Install. You could encounter some error messages. If so follow the instructions and most likely you should reboot the server and start the MABS installation all over again

clip_image036

clip_image038

17) If the computer meet the software and hardware requirements click Next

 

clip_image040

18) Provide a location for the installation of all the files and click Next. In my example I changed all locations to my E: drive

 

clip_image042

19) Provide a strong password for restricted local user accounts (this password will not expire) and click Next

 

clip_image044

20) It’s strongly recommended to use Microsoft update when you check for updates because this will offer all security and important updates for MABS. Select whether to use Microsoft Update or not and click Next

clip_image046

21) Review all settings and if all are OK click Install

clip_image048

clip_image050

22) Click Next to start the Microsoft Azure Recovery Service Agent installation

clip_image052

23) Click Install

clip_image054

clip_image056

24) When the agent installation is completed, click Next

clip_image058

25) Provide your vault credentials to register the machine to the Azure backup vault. Click Next

 

clip_image060

26) Provide a passphrase to encrypt/decrypt the data sent between Azure and your premises. You can automatically generate a passphrase or provide your own minimum 16-character passphrase. Also enter a location to save the passphrase. If all is done click Next

clip_image062

27) Once registration is done, the wizard proceeds with the installation and configuration of SQL Server 2012. This could take some time

clip_image064

clip_image066

28) When the installation is completed with success, click Close

 

clip_image068

29) Go to your desktop, were you will see two new icons. Double click the Microsoft Azure Backup server icon to launch MABS

clip_image069

clip_image071

Now you’re ready to start backing up with MABS. Have fun and till next time!

Wim Matthyssen (@wmatthyssen)

Step by step: How to connect SCAC 2012 R2 to SCVMM 2012 R2 and Microsoft Azure

10:43 am in Azure, Cloud, hybrid cloud, Private Cloud, Public Cloud, SCAC 2012 R2, SCVMM 2012 R2 by Wim Matthyssen

11-02-2016 16-14-33What’s a System Center App Controller (SCAC) server without a connection to System Center Virtual Machine Manager (SCVMM) or Microsoft Azure … right nothing! That’s why in this blog post I will show you how you can connect your SCAC server to your private (SCVMM) and public cloud (Microsoft Azure) environments.

Before we start some things to keep in mind:

To connect SCAC to SCVMM, complete these steps:

1) Open the SCAC web portal, expand Settings and click Connections. On het menu bar, click Connect and select SCVMM

clip_image002

2) In the Add a new VMM connection screen, enter a Connection name (this is the name the user sees), a Description, the SCVMM server name in FQDN format, and the TCP port of that same SCVMM server (default is 8100). Check the “Automatically import SSL Certificates” check box if you plan to copy files and templates to and from SCVMM libraries (this option is recommend). Click OK

clip_image003

3) SCAC establishes the connection and begins a session with the SCVMM server. You can follow the completion in the Jobs section

clip_image004

clip_image006

clip_image008

4) If all is setup without any errors, you will be able to connect to your different on premise Clouds and Virtual Machines (VMs)

clip_image010

clip_image012

To connect SCAC to your Azure Subscription, complete these steps:

1) To create the Self-Signed Certificate open up the IIS Manager on the SCAC server. Double-click on Server Certificates

clip_image014

2) In the Actions pane select Create Self-Signed Certificate

clip_image016

 

3) Name the certificate (in my example AzureSCACCert) and click OK

clip_image018

4) Now we need to export this certificate as a .pfx file. To do so, right-click on the certificate and choose Export…

clip_image020

5) Choose a file name, a location and set a password. If all is filled in click OK

clip_image021

6) In my example the .pfx file is created under the C: root

clip_image023

7) Now open run an type mmc and add the Certificates Snap in for the “Local Computer Account”

 

clip_image025

8) Go to Personal, right-click Certificates and under All Tasks select Import…

 

clip_image027

9) Follow all steps to import the .pfx file (AzureSCACCert) in the personal certificate store

clip_image028

clip_image030

10) To generate the .cer file by right clicking on the certificate, and under All Tasks, select Export

 

clip_image032

 

11) Use the defaults trough the wizard, as file name I used AzureSCAC.cer and as location C: At the end of the wizard press Finish

clip_image033

12) As a next step we need to upload the .cer file to Azure. To do so logon into your subscription in the classic portal (https://manage.windowsazure.com). When logged on, select Settings at the bottom left, select MANAGEMNT CERTIFICATES and finally select Upload at the bottom

clip_image035

13) Browse to the .cer file (located under the C: drive) select it, and click the check box. After a few seconds you should see a notification telling you that your upload is successful and the certificate should be added to the list of management certificates

clip_image036

clip_image038

clip_image040

14) Before we can connect SCAC to this Azure Subscription we need the Azure subscription ID. Because were already at the MANAGEMENT CERTIFICATES page, you can find this ID under the field SUBSCRIPTION ID. Copy the subscription ID to the clipboard

clip_image042

15) Open up the SCAC web console again, in the Overview pane, under Public Clouds, select Connect a Windows Azure Subscription

 

clip_image044

 

16) Fill in a Name and a Description, past the Azure Subscription ID, and select the correct certificate and add the password. If all is foreseen click OK

clip_image045

17) If all went well, you can see that you have an Azure subscription is now connected in the Overview page

clip_image047

18) Under the Virtual Machines section you can see your Azure IaaS VMs running

clip_image049

This concludes this blog post, hope it helps. Till next time!

Wim Matthyssen (@wmatthyssen)

Step by step: Installing SCAC 2012 R2

3:31 pm in Azure, Cloud, hybrid cloud, Private Cloud, scac by Wim Matthyssen

Even in these fast changing times where everybody speaks about Windows Azure Pack (WAP) and the just released Microsoft Azure Stack Technical Preview, there are still customers interested in using System Center App Controller (SCAC) 2012 R2 for easily controlling their clip_image002hybrid cloud environment. Like you probably already know, SCAC is a self-service web portal which enables users (mostly application and service owners) to manage their virtual machines (VMs) and services on their private (System Center Virtual Machine Manger –SCVMM) or public cloud infrastructures (Windows Azure). Shortly said it’s a web console (Microsoft Silverlight web application) which provides users with a self-service experience and which simplifies the management of their VMs across their private and public cloud(s). In this blog post I will go through the installation process for setting up a standalone SCAC configuration on a dedicated VM.

To start, I will list some things up which need to be kept in mind:

  • In contrast to the other System Center products, which can be used independently, SCAC highly depends on SCVMM. So to setup the SCVMM server I will refer you towards a previous post of mine: http://scug.be/wim/2015/12/20/step-by-step-installing-a-standalone-scvmm-2012-r2-management-server/
  • The SCAC server needs to be a member of your Active Directory domain.
  • For complete SCAC software and hardware requirements go to the following Microsoft TechNet page: https://technet.microsoft.com/en-us/library/dn249764.aspx
  • The name of the server can have a maximum length of 15 characters.
  • You can setup a high available (HA) deployment by load-balancing multiple SCAC servers.
  • The SCAC database can reside on a SQL server with other application databases. For example, in combination with the SCVMM database.
  • The SCAC database must be in the same domain as the SCAC server or a two-way trust must be in place.
  • Choose the port for the web portal with care, because the only way to change it is by uninstalling and reinstalling SCAC.
  • Always install all necessary Windows updates before starting the installation
  • Create all necessary account(s) in advance: SCAC service account.
  • For easy access afterwards you can create a  DNS alias record (CNAME) for the SCAC website URL. For exampe: AppController.
  • For security SCAC depends on SCVMM, so all available options for a user depends completely on the rights and permissions that that user has in SCVMM.
  • The SCAC server will be installed on a W2K12 R2 VM with the Windows Firewall disabled.
  • For the installation, log on with a domain account which is a member of the SCVMM Administrators group and which has membership in the local Administrators group. Also insure this account has sufficient rights to access the SQL server.
  • When SCAC is installed all users and groups in the local Administrator group are automatically added to the SCAC Administrator role and by this they will have unrestricted access to all SCAC resources.
  • The SCAC PowerShell module is automatically installed when you install SCAC.
  • If the installation is completed with success, don’t forget to install the latest Update Rollup package for the SCVMM console, you can do this via Windows Update or manually.

After this brief introduction and remarks, let’s start with the installation.

1) Open run and type lusrmgr.msc

clip_image003

2) Add the SCVMM administrators group and the SCAC service account to the local Administrators group

clip_image005

clip_image006

3) Attach the SCVMM installation disk and select setup to Run as administrator

clip_image008

4) Select Install

clip_image010

5) Select the VMM console and press Next

clip_image012

6) Agree to the terms and press Next

clip_image014

7) On the CEIP screen, click Next

clip_image016

8) Accept the default installation location and press Next

clip_image018

9) Accept the default port number and press Next

clip_image020

10) Review the settings and if all are good click Install to start the VMM console installation

clip_image022

clip_image024

clip_image026

11) Attach the SCAC installation disk and select setup to Run as administrator

 

clip_image028

12) Select Install

clip_image030

13) Fill in the license key and press Next

clip_image032

14) Agree to the terms and press Next

clip_image034

15) On the “Install missing software” page click Install to install all prerequisites

clip_image036

clip_image038

16) Leave the default path and click Next

clip_image040

17) Type in the SCAC service account under which the App Controller services will run. Leave the default port and press Next

clip_image042

18) Configure the binding settings and select the correct SSL certificate and click Next

clip_image044

19) Configure the database connection and press Next

clip_image046

20) Choose to participate in CEIP or not and click Next

clip_image048

21) Review the settings and if OK click Install

clip_image050

clip_image052

clip_image054

22) After setup is completed, you can connect to your App Controller website

clip_image056

clip_image057

clip_image059

This concludes this blog post, till next time!

Wim Matthyssen (@wmatthyssen)

Useful PowerShell commands for Hyper-V management

5:48 pm in Hyper-V, PowerShell, Private Cloud by Wim Matthyssen

Hi all,

In this blog post I will list some PowerShell commands I use from time to time on customers Hyper-V hosts to get some work done a little bit easier and faster. You can just run these commands directly in PowerShell (run as administrator) or you can copy them and save them as a .PS1.

This list is a work in progress and will be expanded in the future. So be sure to bookmark this post if you find it useful.

For the moment PowerShell v4 already includes 178 Hyper-V related cmdlets. If your interested in het entire list you can go to the following link: https://technet.microsoft.com/en-us/library/hh848559.aspx

In my commands I use the virtual machine (VM) CON-VM-01 as an example. If you want use the command just change the name to the name of your VM. Also for IP Addresses I use the 192.168.0.0 range, so if your IP range is different just change it.

Below you can find the PowerShell commands:

1) Show what PowerShell Hyper-V cmdlets are available

Get-Command –Module Hyper-V

image

2) List the current configuration of the Hyper-V host

Get-VMHost | Format-List *

image

3) Listing all VMs on a Hyper-V host

Get-VM

image

4) Listing all running VMs on a Hyper-V host

Get-VM | where {$_.state -eq 'running'} | sort Uptime | select Name,Uptime,@{N="MemoryMB";E={$_.MemoryAssigned/1MB}},Status

image

5) Check if a VM has the processor compatibility mode enabled. You can find more info about this mode via following link: https://technet.microsoft.com/en-us/library/dn859550.aspx

Get-VMProcessor -VMName * | select VMName, CompatibilityForMigrationEnabled

image

6) Enable Offload Data Transfer (ODX). You can find more info about ODX via following link: https://technet.microsoft.com/en-us/library/hh831628.aspx

Set-ItemProperty hklm:\system\currentcontrolset\control\filesystem -Name "FilterSupportedFeaturesMode" –Value 0

7) Change the default location where VMs and virtual hard disks are stored on your Hyper-V host

Set-VMHost -VirtualHardDiskPath E:\VMs -VirtualMachinePath E:\VMs

8) Retrieve information about all network adapters on the Hyper-V host

Get-NetAdapter -Name * | Format-List -Property Name, InterfaceDescription, InterfaceName

image

9) Write the Hyper-V host event log to a txt file (also applicable for other servers)

Get-EventLog application -Newest 1000 | where {$_.EntryType -eq "Error"} | Out-File "$env:systemdrive\eventlog.txt" -width 300
Notepad "$env:systemdrive\eventlog.txt"

10) Get the IP Adress of a certain VM

Get-VMNetworkAdapter -VMName CON-VM-01 | Select -expand IPAddresses

11) List the IP4 Adresses of all currently running VMs

Get-VM | where { $_.state -eq 'running'} | Get-VMNetworkAdapter | Select VMName,SwitchName,@{Name="IP";Expression={$_.IPAddresses | where {$_ -match "^192\."}}} | Sort VMName

image

12) Remove a VM with all folders and virtual hard disks

Get-VM CON-VM-01 | %{ Stop-VM -VM $_ -Force; Remove-VM -vm $_ -Force ; Remove-Item -Path $_.Path -Recurse -Force}

As a final remark I want to mention that PowerShell can’t prevent mistakes and like you all probably know they’re easy to make. So keep your eyes open when your running these commands on production Hyper-V hosts.

Till next time!

Wim Matthyssen (@wmatthyssen)

TCP Chimney Offloading on Hyper-V hosts

6:24 pm in Hyper-V, Private Cloud by Wim Matthyssen

From time to time I’m pulled into a discussion whether or not you should disable TCP Chimney offloading on Hyper-V hosts. To be completely honest, when I just started working with Virtual Server on W2K3 (R2) it was a best practice to just disable it. Like a good ITPro, I followed that recommendation and I kept on doing it when I switched to running Hyper-V on W2K8 (R2). It just became a habit when deploying a new Hyper-V host. Furthermore like you probably already know, when your running servers with W2K12 R2 (also Hyper-V hosts) it’s turned off by default anyway (like you can see in the screenshot below). So in this blog post I will show you how you can disable it should it be enabled.

clip_image002

Before going into the practical part, first a little bit of information about the feature in general. TCP Chimney Offload is a networking technology that allows the work associated with moving data across a network to be offloaded from the server’s CPU to the network interface (NIC). This helps improve the processing of the network tasks such as packet segmentation without the need for additional programs or any loss to manageability or security. Programs that are currently bound by network processing overhead will generally scale better when used with TCP Chimney Offload. This allows the servers operating system (OS) to perform quicker and also speed up the processing of network traffic. Be aware that Offloading TCP tasks is only effective with a physical NIC and not with virtual ones.

As an important remark, I just want to say that it is always wise to use the latest NIC drivers and firmware on your Hyper-V hosts. In this way your always ensured the NIC manufacturers latest updates are in place and most of the latest bugs are solved.

After this short intro, it is time to get started with the real stuff.

1) To show the status of the TCP-IP Chimney Offloading on a host, open PowerShell (as an Administrator) and type cmd

clip_image004

2) Next run following command:

netsh int tcp show global

 

clip_image006

Like you can see the TCP Chimney Offload State is enabled

3) To disable it run following command:

netsh interface tcp set global chimney=disabled

 

clip_image008

Like you can see it’s now disabled

It’s also possible to disable TCP Chimney Offload using the registry by changing following registry keys (not applicable for all server OS versions):

4) First of all, open the registry by typing regedit in the Run bar

clip_image009

5) Next change following registry keys:

  • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCPIP\Parameters\DisableTaskOffload

Setting this value to 1 disables all task offloads from the TCP/IP transport. Setting this value to 0 enables all task offloads.

  • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Ipsec\EnabledOffload

Setting this value to 0 disables Internet Protocol security (IPsec) offloads from the TCP/IP transport. The offloading of TCP/IP checksum tasks and the offloading of large TCP packets for segmentation are not affected. Setting this value to 1 enables IPsec offloads.

This concludes this blog post, hope it helps!

Wim Matthyssen (@wmatthyssen)

The Service Principal Name could not be registered in AD DS for the SCVMM 2012 R2 Management Server

11:14 am in Private Cloud, SCVMM 2012 R2, SPN by Wim Matthyssen

 

Sometimes when installing a new System Center Virtual Machine Manager (SCVMM) 2012 R2 Management server you can receive following message at the end of the installation: “Setup completed successfully with warnings”. Like you can read in the error message, this means the installation was successful only the Service Principal Name (SPN) could not be registered in Active Directory Domain Services (AD DS) for the SCVMM Management Server. If the SPN and SCP are not registered, SCVMM consoles on other computers will not be able to connect to this SCVMM Management Server and deploying a Hyper-V host to a bare-metal computer will not work. This problem occurs when your installing your SCVMM Management Server with an account that has insufficient rights to make chances to AD.

clip_image001

To fix this problem run following commands as a domain administrator from a command prompt:

1) Use setspn.exe to create SPN for SCVMM server using the following command:

"C:\Windows\system32\setspn.exe  -S SCVMM/hostname.domain accoutname".

As example:

"C:\Windows\system32\setspn.exe -S SCVMM/VMM-01.contoso.local CONTOSO\mgrscvmm".

2) Add SPN values to following registry key "Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Setup\VmmServicePrincipalNames".

3) Run "C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\setup\ConfigureSCPTool.exe -install" to configure SCP.

clip_image002

This should fix the issue and also concludes this blog post.

Hope it helps, till next time!

Wim Matthyssen (@wmatthyssen)

Step by step: Installing a standalone SCVMM 2012 R2 Management Server

4:34 pm in Private Cloud, scvmm, SCVMM 2012 R2 by Wim Matthyssen

clip_image002Installing the System Center Virtual Machine Manager (SCVMM) 2012 R2 Management Server is pretty straightforward and is very much like installing a new Windows Server. Its main focus is to run the SCVMM service, which processes all commands and handles all communication between the SCVMM database, the SCVMM library server(s) and the Hyper-V hosts. The SCVMM server is cluster-aware, and you can deploy it as highly available (HA) if your virtualization environment is large. But in this blog post I will go to the installation process for setting up a standalone SCVMM Management server. I will also list up all prerequisites and components to get all things up and running.

But first of all, I will start with listing some things up which need  to be kept in mind when planning your deployment:

  • The topology for a SCVMM deployment will vary according to each company’s needs. Consider the following before taking off: numbers of Hyper-V hosts, number of branch sites with hosts, security, administrative groups, self-service experience, availability and recovery time for each of the components.
  • For complete SCVMM software and hardware requirements go to the following Microsoft TechNet page: https://technet.microsoft.com/library/dn771747.aspx
  • If you are deploying SCVMM, you should consider that the SCVMM database no longer supports SQL Express. Therefore, you must use a supported version of SQL server (full version) to run this database.
  • At least one SCVMM library server is necessary, but you should consider foreseeing more separate servers for each external site with a low bandwith link.
  • When you are naming the SCVMM Management server, the computer name cannot contain the character string “SCVMM”.
  • The SCVMM database can reside on a SQL server with other application databases. For example, in combination with the App Controller database.
  • The SCVMM database must be in the same domain as the SCVMM server or a two-way trust must be in place.
  • Be sure to join the SCVMM Management server to the domain.
  • Create all necessary accounts in advance: SCVMM service account, RunAs account for managing hosts, SCVMM Administrators security group. Add the security group to the Local Administrator group on the SCVMM Management Server.
  • You can deploy the SCVMM Console on the same server as the SCVMM Management server, or on another server or workstation that is running a supported operating system (OS).
  • The SCVMM Management Server will be installed on a W2K12 R2 virtual machine (VM) with the Windows Firewall disabled.
  • Configure SCVMM 2012 R2 Distributed Key Management (DKM) in advance. If you do not know how, read all about it in my previous blog post: http://scug.be/wim/2015/07/05/configure-scvmm-2012-r2-distributed-key-management/
  • For the installation log on with a domain account which is a member of the SCVMM Administrators security group and insure this account has sufficient rights to access the SQL and the AD container.

SCVMM has five major components of architecture and these are setup accordingly for this standalone installation:

  • SCVMM Management Server -> will be setup as standalone server
  • SCVMM console -> will be installed on the same server as the SCVMM Management Server
  • SCVMM Self-Service portal -> is been replaced by System Center App Controller (SCAPP)
  • SCVMM database -> will be placed on a separate SQL cluster
  • SCVMM library -> tempory local, will be replaced by a share on a separate file server

After this brief intro, it’s time to setup the SCVMM Management server. We will start off with the installation of all the required Prerequisites.

1) Install Microsoft SQL Server 2008 R2 Command Line Utilities, which can be downloaded over here: http://www.microsoft.com/en-us/download/details.aspx?id=16978

2) Scroll down the page, until you find the exact download

clip_image004

clip_image006

3) If you right-click and install, you may receive following error

clip_image008

4) If so download the Microsoft SLQ Server 2008 R2 Native Client (X64 Package) and run Install

clip_image010

clip_image012

clip_image014

clip_image016

clip_image018

clip_image020

clip_image022

clip_image024

5) Now install the SQL Server 2008 R2 Command Line Utilities

clip_image026

clip_image028

clip_image030

clip_image032

clip_image034

clip_image036

6) Download the Windows Assessment and Deployment Kit (Windows ADK) for Windows 8.1, you can find it via following link:

http://www.microsoft.com/en-US/download/details.aspx?id=39982

clip_image038

7) Run the file as Administrator

clip_image040

8) Leave the default installation path and click Next

clip_image041

9) We don’t join the Customer Experience Improvement Program (CEIP), so we select No and click Next

10) Accept the License Agreement

11) For SCVMM 2012 R2 we only need to install the Deployment Tools and the Windows Preinstallation Environment. Select those and click Next

clip_image042

clip_image043

12) To make sure things are still ticking along under the covers, you can navigate to %temp%/adk to look at the installation log file to make sure that things are still progressing behind the scenes. The installation can be quite large up to 5.1 GB, so if you are on a slow Internet connection, you may be stuck at 0% complete for up to 15 minutes or more before you see any change in the progress bar. In the log file, look for the time that you kicked off the installation and also the time of the last log entry. You should be able to see some activity, namely ‘acquiring package’. This will mean that it’s downloading the package in the background.

clip_image045

Windows Assessment and Deployment Kit for Windows 8.1_20140224141443.log

Check your proxy settings if download doesn’t start or doesn’t work

13) Install the Microsoft Visual C++2010 x86 Redistributable Maintenance. You can locate the executable on the SCVMMR2VMM ISO under the folder “Prerequisites”

After all prerequisites are installed it is now time to freshly install the SCVMM Management Server

14) Go to the DVD or ISO, open it and select setup.exe

clip_image046

15) Click Install

clip_image047

16) Select VMM management server (automatically VMM console is also selected)

clip_image048

17) After the selection of the roles, you have to provide the information about the name of the administrator installing the product, organization details and last but not least the product key. If you don’t provide the product key during installation, you can provide it later. But be aware your installation will only be valid for a 180-day trial period

clip_image049

18) On the next screen, read and accept the licensing agreement and press Next

clip_image050

19) We will not join the Customer Experience Improvement Program (CEIP). So select No, I am not willing to participate and press Next

clip_image051

20) Leave the Installation location to the default and press Next

clip_image052

21) On the prerequisites checker, if there is any prerequisite missing, SCVMM setup will inform you about that. If so, install any missing prerequisite and re-run the checker

22) In the next screen you need to specify the database configuration. Because were installing the SCVMM database on a separate SQL cluster, we need to fill in het Server name and the proper SQL Server Instance name. In addition to this, we also have to specify the correct SQL Server listening port and the user name and domain used to connect to it

clip_image053

23) On the next screen we need to fill in the domain account used by the VMM service and the location for the DKM

clip_image054

24) In the next section leave all ports to the default and press Next

clip_image055

25) For the Library configuration also leave everything to the default. After installation is complete you can add a separate library shared on a file server and delete this default

clip_image056

26) On the last screen, a summary of all the configuration-related settings provided is shown. If everything is OK, you can click Install to start the installation

clip_image057

clip_image058

clip_image059

27) Like you can see installation is completed and you can Close the screen. If you mark the to open the VMM console when this wizard closes this will be opened. Here you are required to provide the right credentials

clip_image061

This concludes this blog post, hope it helps and till next time!

Wim Matthyssen (@wmatthyssen)

Quick overview of Channel 9 Ignite sessions about Hyper-V and Private Cloud

6:15 pm in Azure, Hyper-V, Microsoft Ignite, Private Cloud, scvmm by Wim Matthyssen

clip_image002 channel9

Hi all,

Like you probably all know Microsoft Ignite 2015 was held in Chicago last week. During this event, Microsoft made several new announcements, such as the Microsoft Azure Stack, Microsoft Operations Management Suite (OMS) and Windows Update for Business. Besides all that, Technical Preview (TP) 2 for both Windows Server 2016 and System Center 2016 were released.

All these great sessions were recorded  and published on Channel 9 where they are ready for download or streaming. But even with all those recordings available, it’s quit hard to find the links to all topics you’re interested in.

That’s why below I summarized most of the sessions concerning Hyper-V and Private Cloud in general. Each link gives you direct access to the Channel 9 page where you can find the video recording and the slide deck.

Code Title
KEY01 Microsoft Ignite Keynote
BRK3461 What’s New in Windows Server Hyper-V
C9-45 Hyper-V Next
BRK3492 Deploying Hyper-V Network Virtualization
BRK3504 Hyper-V Storage Performance with Storage Quality of Service
BRK3506 The Hidden Treasures of Windows Server 2012 R2 Hyper-V?
BRK2463 Hyper-V Network Virtualization: 100+ Customer Service Provider Deployments
BRK3493 Migrating to Microsoft: VMware to Hyper-V and Microsoft Azure
BRK3453 Virtualizing Linux and FreeBSD Workloads on Windows Server Hyper-V
BRK3457 Harden the Fabric: Protecting Tenant Secrets in Hyper-V
BRK2466 Platform Vision & Strategy (2 of 7): Server Virtualization Overview
BRK3575 Veeam Software: Availability Strategies for Microsoft Azure and Hyper-V, A Deep Dive
BRK2473 Microsoft System Center Virtual Machine Manager: Technical Overview and Roadmap
BRK3502 Managing and Securing the Fabric with Microsoft System Center Virtual Machine Manager
BRK3498 Managing Storage with Microsoft System Center Virtual Machine Manager: A Deep Dive
BRK3477 Datacenter Integration Using Automation in Microsoft System Center Orchestrator
BRK1454 Hybrid Partnerships: Enabling On-Premises Scenarios in Microsoft Azure
BRK3904 Exam Prep Session for Exam 70-246 and Exam 70-24: Private Cloud (Part 1)
BRK3903 Exam Prep Session for Exam 70-246 and Exam 70-24: Private Cloud (Part 2)
BRK2493 Microsoft’s New Windows Server Containers
BRK3853 An Insider’s Guide to Desktop Virtualization
BRK3483 Taking advantage of Identity capabilities in the Azure Pack
BRK3466 Extending Virtual Machines in the Windows Azure Pack
BRK2468 NetApp, Inc.: Datacenter Transformation, Head into the Cloud While Keeping Your Feet on the Ground
BRK2469 The Power of the Windows Server Software Defined Datacenter in Action
BRK3337 Sysinternals Primer: Ignite 2015 Edition
BRK3489 Exploring Storage Replica in Windows Server vNext
BRK3474 Enabling Private Cloud Storage Using Servers with Local Disks
BRK3496 Deploying Private Cloud Storage with Dell Servers and Windows Server vNext
BRK3484 Upgrading Your Private Cloud to Windows Server 2012 R2 and Beyond!
BRK3503 Best Practices for Deploying Disaster Recovery Services with Microsoft Azure Site Recovery
BRK2479 Cloud Integrated Backup with Microsoft System Center and Azure Backup
BRK3119 Turning the Infrastructure Inside Out and IT Practices Upside Down: Microsoft IT’s Cloud Adoption
BRK2472 Overview of the Microsoft Cloud Platform System
FND1451 Windows Server & System Center Futures—Bring Azure to your Datacenter (Platform Vision & Strategy)
C9-31 The Microsoft Azure Stack
BRK2461 Nano Server: The Future of Windows Server Starts Now
THR0480 Nano Server
THR0488 Datacenter Management from the Microsoft Point of View
C9-03 Jeff Woolsey on the Microsoft Datacenter Platform vNext
C9-41 Availability on Demand – Site Recovery
C9-40 Availability on Demand – Backup
C9-20 Microsoft’s Storage Strategy & Capabilities in Datacenter vNext
C9-21 Microsoft’s Networking Strategy & Capabilities in vNext
C9-13 Microsoft’s Security and Assurance strategy in vNext

Before I close off, some quick tips.

For those interested in reading all about OMS, just read the quick start guide from my fellow SCUG member and MVP Dieter Wijckmans:
http://scug.be/dieter/2015/05/08/microsoft-operations-management-suite-quickstart-guide/.

People who are interested in downloading all the Ignite sessions (and also from other events like TechEd), I can recommend using the PowerShell script from MVP Michel de Rooij, which you can find over here: https://gallery.technet.microsoft.com/Channel9-Session-04b2558b

To end up, I share you the download links for Windows Server 2016 TP 2 and System Center 2012 TP 2:

https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-technical-preview

https://www.microsoft.com/en-us/evalcenter/evaluate-system-center-technical-preview?WT.mc_id=Blog_SC_Announce_TTD

Have fun watching and I’ll be back soon.

Wim Matthyssen (@wmatthyssen)