You are browsing the archive for Public Cloud.

Microsoft Azure Backup Server: Error when installing on Windows Server 2016 – The Single Instance Store (SIS) component is not installed

3:36 pm in Azure, Azure Backup, hybrid cloud, MABS, Microsoft Azure Backup, Microsoft Azure Backup Server, PowerShell, Public Cloud, SIS, SIS-Limited, Windows Server 2016, WS2016 by Wim Matthyssen

 
Hi All,

Last week I was contacted by a customer who tried to install Microsoft Azure Backup Server (MABS) on an on-premise Windows Server 2016. However, when he started the installation he always received an error because a prerequisite was not installed, namely the Single Instance Store (SIS) component.

 
clip_image002

When opening the DpmSetup.log with PowerShell (as Administrator), you could see the following error:

 

clip_image004

However, when you try to install this missing component through PowerShell it gives you an Error: 0x800f080cFeature name SIS-Limited is unknown.

clip_image006

The reason for this is that because from Windows Server 2016 the SIS-Limited component is replaced by Microsoft’s deduplication or data footprint reduction (DFR) technology, like you can read in the following article from MVP Greg Schulz: http://storageioblog.com/rip-windows-sis-single-instance-storage-or-at-least-in-server-2016/

Also, when you go to the Microsoft Azure Backup Server download page and you expand System Requirements you can see that Windows Server 2016 at the present time is not listed as a supported Operating System (OS) to deploy MABS, probably because it does not have this SIS component.

clip_image008

Conclusion

Currently you’re not able to use Windows Server 2016 as OS for you MABS server. Probably in the near future Microsoft will release a new version of MABS which will allow it, but until then you need to stick with Windows Server 2012 (R2) or Windows Server 2008 R2 to install your MABS on.

Hope this helps you with this error.

Wim Matthyssen (@wmatthyssen)

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: Move an Azure IaaS VM between different Azure Subscriptions

11:22 am in Azure, Azure subscription, Cloud, IaaS, Microsoft Azure Storage Explorer, Public Cloud by Wim Matthyssen

From time to time, customers ask me to migrate Azure IaaS virtual machines (VMs) between Azure Subscriptions (for example moving a VM between the Dev subscription and the Prod subscription). There are several ways to accomplish this move, you can use Azure PowerShell or Azure Site Recovery (ASR), but mostly I do it the way that I will describe below.

1) First of all, you need to download an Azure Storage Explorer which enables you to move the VHD (page blob) which is used by the IaaS VM from one storage account (Azure Subscription 1) to another (Azure Subscription 2). Mostly I use the Microsoft Azure Storage Explorer which you can download for free via following link: http://storageexplorer.com/

clip_image002

2) When downloaded and installed you’ll need to add the two Azure Blob Storage Accounts, the one you want to move the VHD from and the one you want to move the VHD to. Open up the Microsoft Azure Storage Explorer, right click Storage Accounts and select Connect to Azure storage…

clip_image004

3) To find the Storage Account name and the Account key, just logon to the Classic Azure portal (https://manage.windowsazure.com/). Go to STORAGE select the correct Storage Account and click MANAGE ACCESS KEYS.

clip_image006

clip_image007

4) Fill in the correct Account name (STORAGE ACCOUNT NAME) and the Account key (PRIMARY ACCESS KEY)

clip_image009

clip_image011

5) Repeat steps 3 to 5 also for the Storage Account in the other Azure Subscription. At the end two Storage Accounts should be available to use in the Microsoft Azure Storage Explorer

clip_image013

6) Now stop the VM (logon trough RDP and choose shutdown) and you are good to copy/paste your VM’s VHD from one Storage Account to another

clip_image015

7) Open up Microsoft Azure Storage Explorer, right click the VHD for the VM you just stopped and select Copy

clip_image017

8) Open the other Storage Account’s Blob container (in my example azureos01 – Blob Containers – vhds) and select Paste. Be aware that this copy can take some time depending on the size of the VHD

clip_image019

clip_image021

clip_image023

9) When the VHD is completely copied, open the Azure classic portal and logon to the second Azure Subscription. Go to VIRTUAL MACHINES, then DISKS and select CREATE A DISK

clip_image025

10) Fill in a NAME (for example AZ-VM-SUB2) and select the correct VHD URL from the storage you just moved your VHD file to. Mark “The VHD contains an operating system.” and select Windows. Click the check mark to finish

clip_image026

clip_image028

clip_image030

clip_image032

11) As the next step create a new VM. Click NEW – COMPUTE – VIRTUAL MACHINE – FROM GALLERY

clip_image034

12) Select MY DISKS and select the newly created disk (in my example AZ-VM-SUB2)

clip_image036

13) In the next screen choose a proper VIRTUAL MACHINE NAME, the TIER and the VM SIZE

clip_image038

14) Create a new CLOUD SERVICE or select an existing one, choose the correct VNET and SUBNET. If an AVAILIBILITY SET is required, select or create it

clip_image040

15) Select the ENDPOINTS you require and finally press the check mark icon to start provisioning the VM

clip_image042

16) Like you can see the VM is created and starts Running. You should now able to connect to it again with RDP

clip_image044

image

17) If the VM looks and reacts like it should, you can delete the original VM with the attached VHD in the first Azure Subscription. Also don’t forget to delete the Cloud Service

This concludes this blog post, hope it helps!

Wim Matthyssen (@wmatthyssen)

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

7:07 am in Azure, Azure Backup, DC, IaaS, Microsoft Azure Backup Server, PowerShell, Public Cloud by Wim Matthyssen

After setting up a Microsoft Azure Backup Server (MABS) running on an IaaS v1 VM for a customer, I encountered a problem with a System State backup. The server having the problem was a Domain Controller (DC) also running as an Azure IaaS v1 VM and a member of the Domain Controller Protection Group on the MABS server. You can see the error message found on the MABS server in the screenshot below

clip_image002

“DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 546, WSB Error Code: 0x1751870). (ID 30229 Details: Internal error code: 0x80990ED0)”

On the DC itself following error message was found:

clip_image004

“The backup operation attempted at ‘‎2016‎-‎05‎-‎10T14:00:28.139491000Z’ has failed to start, error code ‘2155348032’ (The backup storage location is invalid. You cannot use a volume that is included in the backup as a storage location. ). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.”

To fix this problem I followed the steps below:

1) On the server with the problem, verify if no other backup or recovery operation is running by opening a PowerShell window (as administrator) and typing:

clip_image006

If the command output indicates that no operation is running, then you can proceed to step 2. Otherwise wait until the current job is completed and retry the failed System State backup job

2) In the same PowerShell windows type the following command:

clip_image008

Verify of the writer named System Writer is running Stable and without any errors. If so proceed to step 3. Otherwise manually restart the VSS Writer, if it fails again it’s necessary to reboot the server

3) Open Services and verify if the Cryptographic Services is running and set to startup Automatically.

clip_image009

clip_image011

4) The check if Windows Server Backup (WSB) is able to take a local System State Backup, open up PowerShell (as an administrator) and run the below command. When asked press (Y). Be aware it could take a while before the job completes:

clip_image013

clip_image015

clip_image017

If the backup is successfully proceed to step 5. Otherwise check the Windows event viewer for other errors

5) Open the registry editor and go to the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wbengine. Create a key called SystemStateBackup and set the values of this entry as follows:

Name: AllowSSBToAnyVolume
Data type: DWORD
Value data: 1

clip_image018

clip_image020

You also can use PowerShell (as an administrator) to create the registry key, to do so run following command:

6) When done, logon to the MABS server and retry the failed System State backup job by right-clicking and selecting Perform consistency check … Verification will start and at the end the job will complete with success

clip_image022

image

This concludes this blog post, hope it’s useful. Till next time!

Wim Matthyssen (@wmatthyssen)

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

8:00 pm in Azure, Azure Backup, Cloud, IaaS, Microsoft Azure Backup Server, PowerShell, Public Cloud, Windows Server Backup by Wim Matthyssen

Last week I was setting up a Microsoft Azure Backup Server (MABS) for a customer running on an Azure IaaS v1 VM for taking disk and System State backups which are stored in an Azure Backup vault for long-term retention. After done all of the configuration, like deploying the agents and creating the Protection Group(s), most of the backup jobs ran without any issues, only the System State backups were failing. This is shown in the screenshot below.

clip_image002

For those who not know, I will first list some extra information to clarify what a System State backup really is:

  • A System State backup uses the Windows Server Backup (WSB) feature to take a snapshot of the system state and saves it locally to the server before moving it to the MABS server storage pool
  • It contains the following system components: System Registry, SYSVOL directory, Boot files including the system files, Active Directory, COM + Class Registration Database, Certificate Services, Cluster service information, IIS Metadirectory and System files that are under Windows File Protection (some of these items are only included if the specified service is installed – AD, ISS, Certificates)
  • §System state backup and restore operations include all system state data: you cannot choose to backup or restore individual components due to dependencies among the system state components. However, you can restore system state data to an alternate location in which only the registry files, Sysvol directory files, and system boot files are restored.

Troubleshooting a System State backup failure can be frustrating as there are a lot of underlying components that come into play during the process. To figure out what was causing the System State backup(s) to fail, I followed the steps below:

1) Check out the Critical alerts for a specific server having the issue in the Monitoring pane on the MABS server. Here I found the following error:

clip_image004

2) After reading the description carefully, you can see there should be enough free space on the target server and also WSB should be installed. So to verify,  first logon to the specific server trough RDP

3) Check out the free disk space by opening Disk Management

clip_image005

4) Like you can see, there is plenty enough of free disk space to store a local System State backup

clip_image007

5) To check if WSB is installed, run following cmdlet in PowerShell (as an Administrator)

clip_image009

6) Like you can see WSB is not installed and probably causing the failure of the System State backup

7) Install WSB trough PowerShell (as an Administrator)

clip_image011

clip_image013

8) Check if this fixes the issue by opening the Microsft Azure Backup MMC on to the MABS server. Go to Protection and select Perform consistency check …

clip_image015

9) Click Yes to perform the consistency check

clip_image016

10) You will see the Protection Status changing to “Replica is inconsistent, verification in progress”

clip_image018

11) To be sure everything is working like it should, you can logon to the specific server and open WSB locally by opening the Run box and typing wbadmin.msc

clip_image019

12) Select Local Backup. If all is running fine, their should be a local backup job running at the moment

clip_image021

13) After a while the job should complete Successful

clip_image023

14) You should also verify the successful System State backup in the MABS console. Like you can see the Protection Status of the job is OK now (also for all other System State jobs, after WSB was installed locally on all those servers)

clip_image025

This concludes this blog post, hope it helps!

Wim Matthyssen (@wmatthyssen)

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

4:43 pm in Azure, Cloud, DC, IaaS, PowerShell, Public Cloud by Wim Matthyssen

This blog post is part of the step by step to deploy replica DCs on Azure which can be found here: http://scug.be/wim/2015/09/28/deploying-replica-dcs-in-windows-azure/

In this part I will setup the replica DC VMs with the use of an Azure PowerShell script. To do so follow the steps below:

1) Download the Built_DCs.xlsx file here. When downloaded rename the extension from .xlsx to .csv and adjust the file to your needs. In my example I saved it in the following folder C:\Temp\Azure_setup_DC

 

clip_image003

2) To check if the Cloud Service name used in the .csv already exists on Azure, run the below PowerShell cmdlet. If the name exists, the cmdlet returns $True. If the name does not exist and can be used, it returns $False

 
3) Deploy both Azure IaaS VMs with the following Azure PowerShell script, in my example named Azure_built_DCs.ps1. This file is also stored under the folder C:\Temp\Azure_setup_DC. This script accesses the previously created Built_DCs.csv file were all necessary variables are declared. Both VMs will be built from the Azure Windows Server 2012 R2 Datacenter image, will be placed in an Availability Set and an extra data disk will be attached (stored in the azudata01 Storage Account) with a size of 1023 GB and the host-cache mode set to None

 

clip_image005

4) When the script has run you can verify if all settings are applied correctly from the Azure classic portal

clip_image007

clip_image009

clip_image011

clip_image013

5) You should also be able to RDP into both VMs

clip_image015

image

That ends the second part of this series. Please continue through the rest of the series to complete the setup (if all are available).

Till next time!

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)