Leverage the Mobile Device Extension for ad rms

Preparing the local environment for Azure

Microsoft Azure PowerShell is the module for Windows PowerShell that you can use to control and automate the deployment and management of the workloads in Azure.

Installing and configuring Azure PowerShell

The configuration of Azure PowerShell on a local computer consists of:

• 
  Installing Azure PowerShell,
  
• 
  Verifying that Azure PowerShell can run scripts, and enabling scripts to run in Windows PowerShell,
  
• 
  Verifying that WinRM allows Windows PowerShell to connect, and configuring WinRM to support basic authentication.
  

Note that this local computer must have Internet connectivity.

Installing Azure PowerShell

To install the Azure PowerShell module, proceed with the following steps:

1. 
   Open a browsing session and navigate to the Azure Downloads⁴⁴ page.
   
2. 
   Scroll down to Command line tools.
   

3. 
   Under Windows downloads, click Windows Azure PowerShell.
   

4. 
   When prompted to run or save the .exe installation file (WindowsAzurePowerShell.3f.3.3fnew.exe), choose the Run button.
   
5. 
   A User Account Control dialog brings up. Click Yes. This launches the Web Installer Platform 5.0 as of this writing.
   

6. 
   Click Install and follow the online instructions to complete the installation.
   

7. 
   Click I Accept. The package is downloaded and installed.
   

8. 
   Click Finish.
   
9. 
   Click Exit.
   

You can run then the cmdlets from the Azure PowerShell console.

To connect to your Azure subscription with the Azure PowerShell console, proceed with the following steps:

1. 
   Open an Azure PowerShell command prompt.
   

2. 
   Run the following command.
   

PS C:\> Add-AzureAccount

3. 
   A Sign in to Azure dialog brings up.
   

4. 
   Type the email address and click Continue. You’re redirected to a Sign In page
   
5. 
   Type the password associated with your account and click Sign in.
   
6. 
   Azure authenticates you, saves the credential information, and then closes the dialog. A message states that your subscription is now selected has the default subscription.
   

PS C:\> VERBOSE: Account "your email address" has been added.

PS C:\> VERBOSE: Subscription "xxx" is selected as the default subscription.

PS C:\> VERBOSE: To view all the subscriptions, please use Get-AzureSubscription.

PS C:\> VERBOSE: To switch to a different subscription, please use Select-AzureSubscription.help azure

PS C:\>

7. 
   Once connected to your default subscription, you can use the built-in Help system to list and get help about the cmdlets in the Azure PowerShell module. To list the available cmdlets, run the following command:
   

PS C:\> help azure

You can then display help about a specific cmdlet by typing help followed by the name of the cmdlet, for example “help New-AzureVM”.

Note For instructions, see the Microsoft TechNet articles How to install and configure Windows Azure PowerShell⁴⁵ and Get Started with Windows Azure Cmdlets⁴⁶.
Note For more information about the cmdlets in the Azure PowerShell module, see the Microsoft MSDN article Windows Azure Management Cmdlets⁴⁷.

Enabling Windows PowerShell scripts

To verify that Azure PowerShell can run scripts, proceed with the following steps;

1. 
   Open an elevated Azure PowerShell command prompt, and run the following command:
   

PS C:\> Get-ExecutionPolicy

2. 
   If the value returned is anything other than RemoteSigned, you need to change the value to RemoteSigned.
   

Note A digital signature is required from a trusted publisher on scripts and configuration files that are downloaded from the Internet (including email and instant messaging programs) so that they can run. However, a digital signature isn’t required on scripts that you have written on the local computer (not downloaded from the Internet). Finally, you can run scripts that are downloaded from the Internet and not signed, if the scripts are unblocked, such as by using the Unblock-File cmdlet. For more information, see the Microsoft TechNet article about_Execution_Policies.⁴⁸.

Run the following command if needed:

PS C:\> Set-ExecutionPolicy RemoteSigned

When asked, press “Y” to confirm the operation.

Enabling WinRM for remote PowerShell shell

To verify that WinRM allows Windows PowerShell to connect, proceeds as follows:

1. 
   In the above elevated Azure PowerShell session, run the following command to check the status of the WinRM service:
   

PS C:\> sc query winrm

2. 
   If the WinRM service isn’t running, start it with the following command:
   

PS C:\> net start winrm

3. 
   Run the following command:
   

PS C:\> winrm get winrm/config/client/auth

4. 
   In the results, look for the value “Basic =”. If the value is “Basic = false”, you must change the value to “Basic = true”.
   

If the value has to be changed, run the following command:
PS C:\> winrm set winrm/config/client/auth @{Basic="true"}
The value between the braces { } is case-sensitive. In the command output, verify the value “Basic = true”.

5. 
   If you started the WinRM service in step 2, run the following command to stop it:
   

PS C:\> net stop winrm

You are now ready to setup the Windows Server 2012 R2 Base Configuration needed for the test lab.

This is the purpose of the next section.