Need to Know Podcast–Episode 102

We had a few technical hitches getting this episode out and we apologise for the delay but thanks to the hard work of our producer Marc Kean and guest Paul Ward we have stitched together this episode for you all about Windows 10 deployments.

Marc and I are joined by Paul Ward to talk about Windows 10 deployments as well as tool like System Center. We discuss the update of Windows 10 for consumers as well as enterprise as well as were we see the future of the Windows platform from Microsoft leading. There is also our usual update on all the cloud news around Office 365 and Azure. It’s been almost 12 months since the release of Windows 10 so listen along and join in the anniversary celebrations.

As always don’t forget to send us you questions and feedback as well as leaving review to help grow our audience. We appreciate you taking the time to listen.

or can listen to this episode at:

http://ciaops.podbean.com/e/episode-102-paul-ward/

or subscribe to this and all episodes in iTunes at:

https://itunes.apple.com/au/podcast/ciaops-need-to-know-podcasts/id406891445?mt=2

The podcast is also available on Stitcher at:

http://www.stitcher.com/podcast/ciaops/need-to-know-podcast?refid=stpr

Don’t forget to give the show a rating as well as send me any feedback or suggestions you may have for the show.

Resources

Marc Kean

Robert Crane

Azure cool storage now available

Azure Site Recovery now available via Resource Manager

New SharePoint book – Beyond the Basics

The future of SharePoint

Updates to SharePoint Online are coming

Project Madeira

Miracast

Windows Phone 10 Continuum

System Center Dudes

Windows Noob

Coretech

System Center on Technet

Enabling Azure Remote App

You can think of Azure Remote App as basically Remote Desktop Services (RDS) as a service. At this point in time you will need to enable Azure Remote App using the ‘classic’ portal. Here’s how you do it.

image

Firstly, login to the Azure portal and scroll down the options on the left until you identify the option for Remote App that appears like:

image

Select this.

image

Typically, when you select this you will see that no current RemoteApp collection has been configured as shown above.

Select the Create a RemoteApp Collection link.

image

This will display the configuration dialog as shown above. Enter a collection name, region, plan and template image.

The region is the data center in which you wish to host this Remote App service. Typically you’ll want to select the region that is closest to you.

There are currently four pricing tiers and you can find more information about these here:

Azure Remote App pricing plans

Typically you’ll want to select the Standard or Premium Plan.

You can then select from the template image to use for the remote server. You have the choice of a number of preconfigured images or you can use your own if it has been suitably prepared. In this case the Office Professional Plus (30-day trial) will be select to provide Office applications to users.

When ready, select the Create RemoteApp Collection at the bottom of the page.

image

You should now see that RemoteApp collection has commenced creation as shown above. This process will take 15 – 30 minutes typically.

image

You’ll see that there is also the option to create a RemoteApp collection with a Virtual Network. This allows the RDS server to be placed on an existing Azure LAN so it can share other Azure resources. This article won’t cover this specifically, it will be covered in an upcoming article.

image

You may also see that by default you receive a 30 day trial of RemoteApp. If you want to upgrade to paid subscriptions immediately ensure you select the option provided at the top of the screen as shown above.

image

After the service has been enabled you will a check mark as shown above. Select the service name to view the settings.

image

Under the User Access option you will a list of any users who have access. You can add users that have Microsoft Account or if they are part of the Azure tenant already.

image

Under the Publishing option you can see all the applications that will be available to users. These applications are those that are currently on the virtual machine image used.

image

You can make additional options available by selecting the Publish button and either manually entering the directory path or you can select from the start menu as shown above.

image

Users can then use the appropriate RemoteApp application on their device to access this instance of RemoteApp and run the applications. Above is an example of the Windows 10 Universal App. Remote App device clients can be downloaded from:

https://www.remoteapp.windowsazure.com/en/

That has been only a basic overview of how to get RemoteApp up and running in Azure. Look out for more upcoming articles on RemoteApp including deeper dives into configuration and management.

Creating an Azure Resource Group using PowerShell

At the beginning of my recent post about creating an Azure files backup using Azure Resource Manager (ARM) and the Azure portal I detailed how to create an Azure Resource Group. This is of course not the only way that you can create an Azure Resource Group, you can also use PowerShell.

Before you use PowerShell make sure you have read my article:

Connecting to Azure Resource Manager via PowerShell

and you follow the steps outline to connect to your Azure Resource Manager account.

image

If we look at the Azure portal we see there is currently only one Resource Group called CIA.

image

Once connected to the Azure tenant with PowerShell run the command:

new-azurermresourcegroup –name “name” –location “data-center”

where you need to enter the desired “name” and “datacenter” here I have chosen to create a new Azure Resource group called cia2 located in the Australia East data center (“australiaeast”).

image

Once the command has completed successfully, if you now return to Azure portal and refresh the Resource Group display you should see a new Azure Resource Group has been created as shown above with the name you selected (here cia2)

You can now use this Azure Resource Group to put all sorts of resources into. I’ll cover more on how to do that specifically with PowerShell in an upcoming article, however, that’s how easy it is to create an Azure Resource Group using PowerShell.

Creating a Basic LAN in Azure

I’ve just uploaded a video presentation I gave a while back on creating a basics LAN in Azure. The process uses the Azure Service Manager portal to do this in a ‘classic’ cloud deployment. Note, this is not the same as with the Azure Resource Manager (ARM). I’ll be doing something around that soon.

Hopefully, this will give you a basic idea of what’s involved in creating a LAN in Azure.

Connecting to Azure Resource Manager via PowerShell

There is no doubt PowerShell is the premier way to configure and manage things like Azure. However, there has always been a challenge actually connecting to the environment to get the ball rolling.

The first thing that you need to do to connect to Azure Resource Manager via the command line is ensure that you have PowerShell 5 installed and configured for Azure Resource Manager. This previous article of mine:

Life is far easier with PowerShell 5

which will show you how to not only configure your PowerShell environment on a Windows 2012 R2 server but also install the modules required to access Azure Resource Manager.

image

Once you have launched the PowerShell environment enter the following commands to load the ‘classic’ Azure Service Manager and the newer Azure Resource Manager modules into the session:

import-module azure

import-module azurerm

image

You’ll now need to login to your Azure account and in this case you’ll login to the Azure Resource Manager account using the command:

login-azurermaccount

Typically a dialog will now appear asking you to enter your Azure account login and password.

image

When this has been successfully completed you should details of the account echoed back to you as shown above.

image

If you also want to access the ‘classic’ Azure Service Manager account issue the command:

add-azureaccount

You may need to login again with your Azure account details.

Once complete you’ll again be echoed back the details of that account as shown above.

image

We will continue to work with the newer Azure Resource Manager here. So if you now issue the command:

get-azurermsubscription

You will see the details of the Resource Manager subscription as shown above. The important thing here is typically the subscription name (here ‘Azure Pass’). You’ll typically need to refer to the subscription by name when using PowerShell commands for Azure.

image

The recommendation way to do this easily is to issue the command:

$subscription=get-azurermsubscription

This will store the results of the get-azuresubscription command in a variable called $subscription.

To extract the actual name of the subscription and store it in a variable issue the command:

$subscriptionnname = $subscription.subscriptionname

In this case, the command will store the string ‘Azure Pass’ into a variable called $subscriptionname that can be used later throughout the script.

image

You can then issue the command:

select-azurermsubscription –subscriptionname $subscriptionname

To select the Azure Resource Manager subscription to work with (remembering that it is possible to have multiple different subscriptions inside a single Azure tenant).

You should see the Azure Resource Manager account details echoed back to you as shown above.

image

If you also want to target the older Azure Service Manager subscription then you should issues similar commands:

$subscriptionold = get-azuresubscription

$subscriptionnameold = $subscriptionold.subscriptionname

select-azuresubscription –subscriptionname $subscriptionnameold

as shown above.

Now you can work with you Azure tenant and PowerShell commands for both Azure Resource Manager and the older Azure Service Manager if required.

As you can appreciate with scripting and PowerShell there is lot more we can do to improve the connection experience and I’ll look to detail that in the future but this should at least get you started.

Life is far easier with PowerShell 5

PowerShell is a scripting language that allows you to control and automate a whole lot of technology. It is really the premier administration tool for managing Office 365 and Azure. Unfortunately, because of its ‘programming’ nature many IT Professionals have avoided it.

One of the issues with PowerShell has been configuring the environment to allow access to everything you need. Typically, you needed to download and install separate modules to allow commands to be execute for Office 365 service and Azure. PowerShell 5 has overcome that problem by allowing you to download and install these modules directly from the PowerShell command line.

Thus, you need to firstly have PowerShell 5.0 on your machine. PowerShell 5 is included with the latest versions of Windows 10 but unfortunately it isn’t currently installed by default on Windows Server 2012 R2. This means if you want to use PowerShell version 5 on a server you’ll typically need to firstly download and install it.

image

For a Windows Server 2012 R2 you’ll need to download and install the Windows Management Framework 5,0 which you can find here:

https://www.microsoft.com/en-us/download/details.aspx?id=50395

image

When executed it will scan the machine to determine what updates need to be installed.

image

You’ll then be promoted to install any updates.

image

After these updates have been installed you may need to be reboot the machine.

image

To download and install the Azure module for PowerShell simply open a new PowerShell command prompt now and type:

install-module azure

You maybe be prompted to install the NuGet provider. Enter Y here to accept this.

image

You may also be prompted that you are installing from an untrusted repository. Again, select Y here to continue.

image

You should now see the module package being downloaded and installed as shown above.

When complete you’ll be returned to the command prompt.

image

To install the Azure Resource Manager module now type:

install-module azurerm

You should again see this module being downloaded and installed as shown above.

You’ll again be returned to the command prompt when complete.

image

Now if you issue the command:

get-module –listavailable

You will see all the see all the PowerShell modules that are available to you. In the above example you can see both the Azure and AzureRM modules are listed as available.

image

If you now issue the command:

$psversiontable.psversion

You will see the version of PowerShell installed (here version 5 as expected).

That’s a lot easier than it ever used to be with PowerShell and another reason why you should be using the latest version!

Restoring files and folders with Azure backup

In previous articles I’ve covered how to set up Azure files and folders backup as well as how to actually backup data. I’ll now show you how to recover data backed up using Azure Backup for files and folders.

image

Launch the Microsoft Azure Backup program. In the top right reselect Recover Data.

image

The Recover Data Wizard will now launch. You’ll firstly need to select whether you are restoring files from the current location or whether you are on a different server.

image

If you are on a different server you will need the Azure Recovery Vault credentials for verification as shown above. For information about obtaining those see the previous article.

Select Next to continue.

image

You can now either browse or search for the files you wish to restore. In this case Browse is selected.

Press the Next button to continue.

image

You’ll now need to select a point in time from which to restore your files. In this case there is only one option.

Select Next to continue.

image

Locate the files you wish to restore by placing a check mark next to them.

Press the Next button to continue.

image

You now need to determine where the files will be restored to. In this they will be restored to an alternate location (the desktop). You also need to determine whether you wish to keep any duplicate copies and whether to restore the permissions to those files.

Select the Next button to continue once you have made your selections.

image

You will now receive confirmation of the restore process as shown above. If everything is in order select Recover.

image

The restore process will now commence. The amount of time to restore will depend on factors such as bandwidth and the amount of data you have chosen to restore.

When the restore process is complete you will receive the above notification. Select Close to continue.

image

If you now look in the backup software console you should see a successful backup job has completed and there is information in the Last Recovery area in the lower right as shown above.

image

If you select the View details link under this Last Recovery area you will see a summary of the recover job as shown above.

image

You should also now see your recovered files as shown above.

The important thing to remember is that you can restore data from Azure File backup to any machine, you’ll simply need to have the Vault credentials if you perform this on a machine that wasn’t the original source.

You can use Azure File backup to not only backup servers but also workstations running operating systems such as Windows 10. You can also backup multiple machine to a single Azure Recovery vault if you choose. This makes Azure Files backup a quick and easy method to schedule continual backups to the cloud.

Backup files and folders using Azure

In a previous post I detailed how to set up an Azure Recovery Service Vault using Azure Resource Manager and then installing the Azure files backup client. In this article I’m going to walk through how to actually setup and run a backup to Azure for your files and folders.

image

Run the Microsoft Azure Backup software on the machine to be backed up. If you haven’t configured this yet, read my previous article on setting all this up.

With the Microsoft Azure Backup software running as shown above, select Schedule Backup in the top right.

image

The above dialog will appear. Select Next to continue.

image

You are now taken to a dialog where you need to select the files and folders from the current machine.

Select the Add Items button to select the items you wish to backup.

image

This will then pop up a file explorer like that shown above. Select the locations you wish to backup and press the OK button.

image

You should now see the backup locations you selected  displayed in the top window as shown above. You can also use the Exclusion Settings if you want to filter what is backed up from the locations selected.

When complete, select the Next button to continue.

image

You’ll then be prompted to schedule how often you wish to backup your locations. The most backups you can currently perform is three per day.

Once you have made you selection select Next to continue.

image

You are now prompted to enter the retention policy settings. This determines which backups are retained and for how long.

When you have made your selection press Next to continue.

image

Given that the initial backup of the locations can be quite large you are now presented with the option to perform the initial backup offline to local storage. If your Azure datacenter supports the option, you can then ship this local back to Microsoft so it seed any future backups.

Details on this process can be found here:

Offline backup workflow in Azure Backup

If you leave the option set to Automatically over the network, the backup data will be sent across the Internet to Azure.

Press the Next to continue.

image

You will now see a confirmation screen.

Select Finish to complete the configuration.

image

You will now see the backup schedule being created.

image

and you should receive confirmation that it has been successful.

Select Close to continue.

image

The backup will now run automatically in the background based on the settings you configured. However, if you wish to wish to manually run a backup at any time select the Back Up Now link in the top right.

image

This will launch a dialog as shown above asking you to confirm running a backup.

Select the Back Up button to continue.

image

The backup will now commence by taking a snap shot of the drive.

image

You should then see data being transferred by the program as shown above.

image

When the backup has completed you will receive the above message. Select the Close button to return to the backup software console

image

If you now look at the console you should see a successful backup job has completed.

image

If you select the View details link you will see a summary of the backup job as shown above.

The backups will continue to run on the configured automated schedule. You can of course re-run a manual backup at any point.

In an upcoming post I’ll detail how you restore data from this Azure backup.