Last updated by at .

  • What's new in Hyper-V 2016
  • Microsoft Azure

Category: Windows Server 2008 R2

Veeam FastSCP for Microsoft Azure

Veeam FastSCP for Microsoft Azure

Veeam does some great products for your virtualization and datacenter environment such as their Veeam Backup & Replication suite, Veeam Endpoint Backup FREE and Management Packs for System Center Operations Manager. Now a couple of weeks ago Veeam released a cool free tool call Veeam FastSCP fro Microsoft Azure. With Veeam FastSCP (Secure Copy Protocol) for Microsoft Azure, IT Pros and Azure Developers can simply and reliably copy local files to Azure VMs, and copy files in Azure VMs to on-premises.

Veeam FastSCP for Microsoft Azure Diagram

The utility makes your life way easier when dealing with Virtual Machines running on Microsoft Azure IaaS.

  • Secure file copy with no independent encryption or VPN needed
  • Manual file copy to/from Azure VMs without the need to keep the UI open until the file copy completes
  • Automatic scheduling of file copy jobs for nightly or weekly copies to/from Azure VMs
  • A wizard-driven UI to copy files in just a few clicks – with no scripting needed

If you want to download it, check out the Veeam Website.

To set it up the tool connects to the PowerShell endpoint for your IaaS VM. Just add the Virtual Machine and you are ready to go! With that you can do some great things, like simply copy a file to an Azure IaaS VM or even doing scheduled backups of files from inside Azure VMs like Didier Van Hoye did.

 

 



Powershell

Get name of the PowerShell script file inside the script

When you create a script you sometimes want to create some output for a log file for example. In many cases it makes sense to use the script file name for the log file so you can easily see from which .ps1 the .log file was generated for example. To get the name of the PowerShell ps1. file you can use the following command:

This will return the ps1. file object. To get only the name string you could use:

To create a log file with the script file name you could use the following commands:



Powershell

Move files to folder sorted by year and month with PowerShell

I had to sort a lot of files and put them into folders for each month and year. So for example when the files was created/modified in February 2012, the file had to be moved into the folder 2012 and the subfolder 2 (for February). For this I created this quick and dirty script:

Please as always if you use a PowerShell script from the internet, test it first before you run it against your production environment.



Update Rollup 5 for System Center 2012 R2

Summary: Update Rollup 5 for System Center 2012 R2 and Azure Pack now available

Yesterday Microsoft released a new Update Rollup for System Center 2012 R2 and Azure Pack called Update Rollup 5. Update Rollup 5 has a lot of fixes and new features especially for Windows Azure Pack and System Center Virtual Machine Manager and Data Protection Manager.

Components that are fixed in this update rollup

  • Data Protection Manager (KB3021791)
    • Protect SharePoint with SQL Always on Configuration
    • Protect SharePoint Server, Exchange Server, and Windows Client workloads to Microsoft Azure by using Data Protection Manager
    • Support for multiple retention ranges for long-term backup on Microsoft Azure
    • Ability to transfer initial backup copy offline to Azure
    • Support for protecting Microsoft workloads that are hosted in VMware
    • Display missed SLA alerts on the Data Protection Manager console
    • Enhanced reporting with Data Protection Manager central console
  • Operations Manager (KB3023138)
  • Service Manager (KB3009517)
  • Virtual Machine Manager (KB3023195)
    • Differencing disk as an option in the Windows Azure Pack VMRole deployment
    • New operating system support
    • New ExplicitRevokeRequired parameter to control IP address management when Grant-SCIPAddress is used
    • Support for SQL Server 2014
    • Azure Site Recovery
  • Windows Azure Pack (KB3023209)
    • Adds support for SQL Governor in the SQL Server Resource Provider.
    • Adds administrator support for disabling native Network RP to allow for third-party network provider
    • Provides detail on Virtual Machine Memory type, Memory Startup and Maximum values in the Tenant Portal.
    • Fix to the Get-MgmtSvcRelyingPartySettings PowerShell cmdlet.
    • Fix to the issue of failing to establish Remote Desktop Connection to virtual machines put behind a Network Address Translation (NAT) device.
    • Fix to the Attached Network dialog box where the network entries in the list were disabled.

As you can see you get several new feature with Update Rollup 5. In Data Protection Manager you finally get support for SharePoint, Exchange and Windows Client workload protection to Microsoft Azure, and support for workloads running on VMware infrastructure. Virtual Machines Manager not only brings new features such as support for the Virtual Machine Manager Database to run on SQL Server 2014 it also includes a lot of fixes and a security update (3035898
MS15-017: Vulnerability in Virtual Machine Manager could allow elevation of privilege: February 10, 2015). Some of the most interesting fixes for me are:

  • DHCP extension: Currently, users have to manually update the DHCP extension after update rollup installation on all hosts. This is now automated. After the DHCP extension is replaced in the Virtual Machine Manager server’s installation folder to the latest version, Virtual Machine Manager automatically checks the DHCP extension against all hosts. If the host has an older version of DHCP extensions, the agent version status will be displayed as “DHCP extension needs to be updated in host properties on the Status page.” The user calls the update agent and updates the DHCP extension on the Hyper-V host in the same way that the user did this for the Virtual Machine Manager agent. Also, if the VSwitch is a logical switch, the status will be shown in “logical switch compliance.” The user can remediate the logical switch. This will also update the DHCP extension on the host.
  • Bare-Metal Deployment: If a physical computer profile is created by using vNic (and by using a virtual machine network) and if there are more than one hostgroup for a logical network that also has that virtual machine network when you add a host resource on the “Provisioning Options” page, the host profile will be displayed for only one host group. The profile won’t be displayed for the rest of the host groups.

For Windows Azure Pack also includes some important fixes and improvements on of the is in the Tenant Portal, users can now see details on Virtual Machine Memory type, Memory Startup and Maximum values.

Update Rollup 5 for System Center 2012 R2 brings a lot of new features and important fixes to the table, however before deploying the fixes in your production environment, I recommend to test the Update Rollup and maybe wait for some reports about issues from other users.



Licensing Microsoft Server in a Virtual Environment

Altaro Hyper-V Licensing Microsoft Server in a Virtual Environment webinar recording available

Together with Altaro I did a webinar on “Licensing Microsoft Server in a Virtual Environment” together with Andy Syrewicze (Microsoft MVP Hyper-V). Now the recording of this webinar is now available. You can also download the free eBook for Licensing Microsoft Server in a Virtual Environment from Eric Siron.



Azure Backup Agent

How to Backup a Windows Client to Microsoft Azure

Today Microsoft announced that Microsoft Azure Backup now not only supports Windows Server or System Center Data Protection Manager, it also support Windows Clients, including Windows 7, Windows 8 and Windows 8.1.

To backup your Windows Client machine you have to go to the Azure Portal and create a new Backup Vault.

Create Azure Backup Vault

After that you have to download and install the Microsoft Azure Backup agent and the vault credentials which are needed to register the machine to your Backup Vault.

Azure Backup Agent

Now during the installation of the Azure Backup Agent you have to use the vault credential file to register your server. There are two different ways of registering machines to the backup vaults that store data:

  • Option #1: Register one machine per backup vault. The backup vault is created under Recovery Services in your Azure subscription. Please be aware that only 25 backup vaults can be created per subscription using this option. If you have more machines to backup to Azure, please use the second option.
  • Option #2: Register multiple machines to the same vault. This enables up to 50 machines to be registered with a single backup vault.

In both the options, access to the backup data is controlled using an encryption passphrase. At the time of registering a machine to a backup vault, an encryption passphrase is provided by the user – and this is used to encrypt and decrypt the data being backed up. With different encryption passphrases being used for different machines, isolation is guaranteed.

 

In both the options, access to the backup data is controlled using an encryption passphrase. At the time of registering a machine to a backup vault, an encryption passphrase is provided by the user – and this is used to encrypt and decrypt the data being backed up. With different encryption passphrases being used for different machines, isolation is guaranteed.

Azure Client Backup

Now you can see your machine in the Azure Portal in the recovery vault. After the Agent is installed you can launch the Microsoft Azure Recovery Services Agent to configure your backup.

Microsoft Azure  Backup

After the first Backup is done, you can also start recovering data from Azure.

Azure Backup Recover Data

Some notes:

  • If you are running Azure Backup on your notebook or tablet, the backup will only run if the computer is not on battery mode. If your notebook is running on battery the backup will run the next time the machine is connected to a power source.
  • If you pick the backup time of your machine make sure the machine is not shutdown during that time.


Microsoft Virtual Machine Converter 3.0

Microsoft releases Microsoft Virtual Machine Converter 3.0

Microsoft today released the next version of the Microsoft Virtual Machine Converter (MVMC). (MVMC) is a Microsoft-supported, stand-alone solution for the IT pros or solution provider who wants to convert virtual machines and disks from VMware hosts to Hyper-V hosts and Microsoft Azure.

In MVMC 3.0 Microsoft adds the ability to convert a physical computer running Windows Server 2008 or above server operating systems or Windows Vista or above client operating systems to a Virtual Machine. This feature was highly claimed by the community, since the P2V (Physical to Virtual) Migration feature was removed in System Center Virtual Machine Manager 2012 R2.

MVMC can be deployed with minimal dependencies. Because MVMC provides native support for Windows PowerShell, it enables scripting and integration with data center automation workflows such as those authored and run within Microsoft System Center Orchestrator 2012 R2 or Service Management Automation. It can also be invoked through the Windows PowerShell command-line interface. The solution is simple to download, install, and use. In addition to the Windows PowerShell capability, MVMC provides a wizard-driven GUI to facilitate virtual machine conversion.

This tool can not only help you to migrate from VMware or physical computers to Hyper-V, it also allows you to directly upload the Virtual Machine to Microsoft Azure.

MVMC3 migrate to Hyper-V or Azure

You can get the new version of the Microsoft Virtual Machine Converter 3.0 in the Microsoft Download Center.