Dışarıya aktar (0) Yazdır
Tümünü Genişlet
EN
Bu içerik dilinizde bulunmamaktadır ancak İngilizce sürümüne buradan bakabilirsiniz.

Use PowerShell to Create an Azure VM With SQL Server BI and SharePoint 2013

Updated: August 24, 2013

This topic and the supporting Windows PowerShell Scripts, step you through creating an Azure Virtual Machine (VM) that runs Microsoft SQL Server Business Intelligence (BI) features and Microsoft SharePoint 2013. The procedures and scripts assume that you have an Azure subscription, installation files for SQL Server 2012 Service Pack 1 (SP1), and installation files for SharePoint 2013. The document includes a procedure to create virtual hard disks (.vhd) to contain your installation files. For more information on requirements, see the Prerequisites section of this topic.

For similar content on a single VM that utilizes SharePoint 2010 and SQL Server 2012, see Use Windows PowerShell to Create an Azure VM with SQL Server BI and SharePoint 2010.

For similar content on a multi-server farm, see the white paper Deploy SQL Server Business Intelligence in Azure Virtual Machines (http://msdn.microsoft.com/en-us/library/dn321998.aspx).

Recommended Experience:The topic and scripts assume that you have some familiarly working with Windows PowerShell scripts and Azure subscriptions.

The following diagram illustrates the workflow of preparing your computer, running the Windows Azure PowerShell scripts from your computer, and then running Windows PowerShell Scripts on the VM:

worklfow of powershell scripts

 

In this topic:

Download the Windows PowerShell Scripts and supporting text files from CodePlex. The script project does not include SQL Server or SharePoint installation files. See the Prerequisites section for other requirements.

PowerShell To Download:

  1. Browse to Use Windows PowerShell to Create an Azure VM with SQL Server BI.

  2. Download WA_BI_VM2013.zip.

  3. Extract all the files to C:\WA_BI_VM2013.

  

For related projects, see the main site page Azure SQL

Arrow icon used with Back to Top link Top

 

Prerequisite Description

SQL Server and SharePoint Installation files

The scripts require you to supply installation files and license keys for the following:

Note: The scripts assume uncompressed installation files. The scripts do not work with .iso images.

Certificate

The procedures require a management certificate. The Makecert.exe utility creates certificates and it is installed with Visual Studio 2012 and Visual Studio 2010. If you already have an X.509 certificate to upload to the Azure subscription, then you do not need Visual Studio.

Azure PowerShell

The scripts have been tested with version 0.6.16 of Azure PowerShell.To verify the version, run the following command:

(Get-Module azure -ListAvailable).Version

For more information on Azure Powershell revisions, see WindowsAzure/azure-sdk-tools (https://github.com/Azure/azure-sdk-tools/wiki).

Install Azure PowerShell cmdlets from the Command the line tools section of the following download page: Azure Downloads (http://azure.microsoft.com/en-us/downloads/?fb=en-us).

Azure Subscription Core Quota

Azure subscriptions have a computing core quota. The 2_CreateVM.ps1 script in this project creates an ExtraLarge virtual machine, which requires 8 cores. Before you begin using the scripts, verify that your subscription quota can support the additional cores.

If your subscription does not have enough cores to run the scripts, the 2_CreateVM.ps1 script fails with a message similar to the following:

  • New-AzureVM: Failed: The subscription policy limit for resource type 'cores count' was exceeded. The limit for resource type 'cores count' is 20 per subscription, the current count is 18, and the requested increment is 4.

For more information on virtual machine sizes, see the following:

Azure Subscription is enabled for the Virtual Machine service.

Verify which of the Azure locations available to your subscription, have access to the Azure Virtual Machine service. The location is a required parameter for the 2_CreateVM.ps1 script. For more information on how to use Windows PowerShell to verify available services, see the section Verify the Azure Geographical locations in this topic.

If none of the locations show “PersistentVMRole” as an available service, see the “What you Can Do” section of Azure Purchase Options http://www.windowsazure.com/en-us/pricing/purchase-options/).

Azure Virtual Network

The scripts assume that you are using a subscription that does not already contain a virtual network. If The subscription you are using contains a virtual network that you cannot delete, see the Virtual Network Conflicts section in this topic.

Arrow icon used with Back to Top link Top

The steps in this section prepare your local computer with the settings and files needed to complete the scripts.

In this section:

This section walks you through the creation of a management certificate and uploading the certificate to your Azure subscription. If you do not have Makecert.exe, see the section Create a certificate from Azure .Publishsettings File

The following are points of interest when using Azure subscriptions and management certificates.

  1. You can upload more than one certificate for each subscription.

  2. You can use a single certificate on more than one subscription. Users should consider the security implications and potential surface area for security threats.

  3. A best practice is to create and use one certificate for each subscription, so a one to one relationship.

Arrow icon used with Back to Top link Prepare the environment

Arrow icon used with Back to Top link Top

Create a X.509 certificate with the Makecert.exe utility and upload the certificate to your Azure Subscription. Makecert.exe is installed with Visual Studio and with the Windows SDK. The following paths are the common locations to find Makecert.exe:

  • C:\Program Files\Windows Kits\8.0\bin\x86

    C:\Program Files\Windows Kits\8.0\bin\x64

To Create a Certificate:

  1. Create folder C:\Temp if it does not exist.

  2. Open a Visual Studio command prompt with administrative privileges, using one of the following procedures:

    • Windows 8 or Windows Server 2012

      1. From the Windows 8 Start screen, type Developer.

      2. Right-click the Developer Command Prompt for VS 2012 and click Run as administrator

    Or

    • Windows 7 or Windows Server 2008 R2

      1. Click Start and then click All Programs.

      2. Click Visual Studio and then click Visual Studio Tools.

      3. Click Visual Studio Command Prompt.

  3. Navigate to a directory where you want the certificate created. For example cd C:\temp

  4. To create a certificate with the name cloudbi, in a certificate store with the name My:

    makecert -r -pe -a sha1 -n "CN=cloudbi" –ss –my -len 2048 -sp "Microsoft Enhanced RSA and AES Cryptographic Provider" -sy 24 cloudbi.cer
    
    If you see an error message regarding “Too many parameters”, verify the “-“ character pasted as the ‘minus’ sign. For more information, see the forum post MakeCert Error: Too many parameters(http://social.msdn.microsoft.com/Forums/vstudio/en-US/1e41910f-2f89-439c-93a6-57e5c391d7ca/makecert-error-too-many-parameters).

Arrow icon used with Back to Top link Prepare the environment

Arrow icon used with Back to Top link Top

  1. Sign into the Azure Management Portal: Management portal (http://manage.windowsazure.com).

  2. In the SUBSCRIPTION dropdown list, ensure that the proper subscription is selected.

  3. In the left pane, click SETTINGS. settings

  4. In the top navigation menu, click MANAGEMENT CERTIFICATES.

  5. In the bottom navigation menu, click UPLOAD. upload to windows azure

  6. Click the FILE text box and then browse to C:\temp\cloudbi.cer, and then click Open. For example C:\temp\cloudbi.cer

  7. Click the OK checkbox. ok

  8. To see the certificate in the list, refresh the browser window.

Note: For information on how to use the certificate on another computer, see the section Use the Management Certificate on another computer.

Arrow icon used with Back to Top link Prepare the environment

Arrow icon used with Back to Top link Top

If you do not have access to the Makecert.exe utility, you can use Azure PowerShell cmdlets to generate a certificate from your Azure subscription. For more information, see the following:

securitySecurity Note
The Publishsettings file contains the credentials (unencoded) that are used to administer your Azure subscriptions and services. A security best practice is to store the file temporarily outside your source directories (for example in the Libraries\Documents folder). Then, when the import is complete, delete the publishsettings file. A malicious user that gains access to the publishsettings file can edit, create, and delete your Azure services.

Arrow icon used with Back to Top link Prepare the environment

Arrow icon used with Back to Top link Top

 

Verify the location of Azure.psd1 on your local computer. Verify that the path is correct in the Import-Module section of C:\WA_BI_VM2013\offbox\1_CreateStorage_Network.ps1 and C:\WA_BI_VM2013\offbox\4_Unmountdata.ps1. The following are typical paths for Azure.psd1:

C:\Program Files\Microsoft SDKs\Azure\PowerShell\Azure\Azure.psd1

Or

C:\Program Files (x86)\Microsoft SDKs\ Azure\PowerShell\Azure\Azure.psd1

Arrow icon used with Back to Top link Prepare the environment

Arrow icon used with Back to Top link Top

The 2_CreateVM.ps1 script uses the $Azurelocation parameter to supply the name of the Azure Location that hosts the Azure objects. For example the virtual machine and the virtual network. The location needs to support the PersistentVMRole as an AvailableService. For example, East Asia. If you are not sure what Azure location to use, you can edit and then run the Azure PowerShell script GetGalleryImageList_andLocationList.ps1. The script returns a list of locations and the supported services that are available to the current Azure subscription. Edit the script with your Azure subscription information.

For example, the GetGalleryImageList_andLocationList.ps1 script returns the following list. In this example, you update 2_CreateVM.ps1 to use either “East Asia” or “Southeast Asia”.

Name             DisplayName      AvailableServices                   
----             -----------      -----------------                   
South Central US South Central US {Compute, Storage}                  
East Asia        East Asia        {Compute, Storage, PersistentVMRole}
Southeast Asia   Southeast Asia   {Compute, Storage, PersistentVMRole}

 

If none of the locations show PersistentVMRole as an available service, see the “What you Can Do” section of Azure Purchase Options (http://www.windowsazure.com/en-us/pricing/purchase-options/).

TipTip
For information on preparing the script GetGalleryImageList_andLocationList.ps1, see the Update Script Parameters section.

Arrow icon used with Back to Top link Prepare the environment

Arrow icon used with Back to Top link Top

The Windows PowerShell scripts in this project build an Azure virtual machine that runs Microsoft Windows 2012 image. The image is in the Azure Virtual Machine gallery. The script 2_CreateVM.ps1 builds the virtual machine based on a specific image name. The images available in the gallery change over time so verify the current image names available and update the 2_CreateVM.ps1 script as needed.

Run the Windows PowerShell script GetGalleryImageList_andLocationList.ps1 to get a list of the current Azure Virtual Machine Gallery images. Verify the ‘ImageName’ property of the Windows Server 2012 image and update the $vmImageName parameter of the 2_CreateVM.ps1 script.

For example, the GetGalleryImageList_andLocationList.ps1 script returns the following:

 

Label ImageName

Windows Server 2012 Datacenter, May 2013

a699494373c04fc0bc8f2bb1389d6106__Windows-Server-2012-Datacenter-201305.01-en.us-127GB.vhd

 

Therefore update the 2_CreateVM.ps1 script:

$vmImageName =" a699494373c04fc0bc8f2bb1389d6106__Windows-Server-2012-Datacenter-201305.01-en.us-127GB.vhd"

Arrow icon used with Back to Top link Prepare the environment

Arrow icon used with Back to Top link Top

  1. Storage Account: The Azure Storage Account name must be unique within Azure. The name is the prefix of the storage DNS name, which can be used to access objects in the storage account.Update the 1_CreateStorage_Network.ps1 script and 2_CreateVM.ps1 script with a storage account name that is unique.$storageAccountName = "azurebistorage"

    There is an Azure Service Management REST API you can use to verify the availability of a storage account name. For more information, see Check Storage Account Name Availability (http://msdn.microsoft.com/en-us/library/windowsazure/jj154125.aspx).

  2. Virtual Machine Name: The virtual machine service same must be unique within Azure. Update the 2_CreateVM.ps1 script with a unique service name. Modify $vmServiceName = "IaaS-BI-onsharepoint".

Arrow icon used with Back to Top link Prepare the environment

Arrow icon used with Back to Top link Top

The scripts assume an azure subscription that contains zero Azure virtual networks. If the subscription you want to use already contains an Azure network, the existing Networkconfig.netcfg could create a conflict. There can be only one Networkconfig.netcfg for each Azure subscription. If you upload the Networkconfig.netcfg file per the steps in this document, Azure will first try to delete the existing virtual network. Therefore the 1_CreateStorage_Network.ps1 script may modify the network environment of your subscription based on the following behavior:

  1. If your Azure subscription does not contain an existing virtual network, the 1_CreateStorage_Network.ps1 script creates a new Virtual network that uses the NetworkConfig.netcfg file provided in the scripts project in the offbox folder.

  2. If a virtual network exists but the network is NOT associated with any Azure objects, 1_CreateStorage_Network.ps1 successfully deletes the existing virtual network and then creates a network based on the configuration file NetworkConfig.netcfg.

  3. If a virtual network exists and it is associated with objects, 1_CreateStorage_Network.ps1 will FAIL to delete the existing virtual network and the script will FAIL to create a network based on the configuration file NetworkConfig.netcfg.

    • If you want to preserve existing network information, download the NetworkConfig.netcfg from your Azure subscription and then merge the <DnsServers> and <VirtualNetworkSite> sections with the NetworkConfig.netcfg provided with this project.

    • Copy the modified NetworkConfig.netcfg to C:\Temp. If you want to use a different folder, update the following entry in 1_CreateStorage_Network.ps1.

      -ConfigurationPath "C:\Temp\NetworkConfig.netcfg"

Arrow icon used with Back to Top link Prepare the environment

Arrow icon used with Back to Top link Top

This section summarizes the parameters you modify for each script. Some of the parameters you modified as part of the other preparation steps. Modify the Scripts at C:\WA_BI_VM2013. In a later step, you copy the script files to a .vhd that is uploaded to the Azure VM.

 

Script Parameter Description

GetGalleryImageList_andLocationList.ps1

$subscriptionID

This script is optional and retrieves information from your Azure subscription to help you populate parameters in the other scripts.

The subscription ID, subscription name, and thumbprint are listed on the Settings, Certificate page of Azure Management Portal.

GetGalleryImageList_andLocationList.ps1

$subscriptionName

Provide your subscription name.

GetGalleryImageList_andLocationList.ps1

$thumbPrint

Provide your certificate thumbprint. See the Settings, Certificate page of Azure Management Portal.

GetGalleryImageList_andLocationList.ps1

$certificate

The Script uses the “MY” store, that is specified with the -ss parameter on the MakeCert prepare step. If you use a different store, update the script.

------------

------------

------------

1_CreateStorage_Network.ps1

$subscriptionID

1_CreateStorage_Network.ps1

$subscriptionName

1_CreateStorage_Network.ps1

$thumbPrint

1_CreateStorage_Network.ps1

$certificate

1_CreateStorage_Network.ps1

$Azurelocation

The geographic data center location where the virtual machine is to be created.

1_CreateStorage_Network.ps1

$storageAccountName

This parameter must be a unique value.

------------

------------

------------

2_CreateVM.ps1

$subscriptionID

2_CreateVM.ps1

$subscriptionName

2_CreateVM.ps1

$thumbPrint

2_CreateVM.ps1

$certificate

2_CreateVM.ps1

$Azurelocation

Use the same location you used in 1_CreateStorage_Network.ps1.

$vmImageName

Required: Name of the VM gallery image to use for the base of the virtual machine. To retrieve a list of image names, see script GetGalleryImageList_andLocationList.ps1.

2_CreateVM.ps1

$storageAccountName

Use the same location you used in 1_CreateStorage_Network.ps1.

2_CreateVM.ps1

$vmServiceName

This parameter must be a unique value.

------------

------------

------------

3_Add_disks.ps1

$subscriptionID

3_Add_disks.ps1

$subscriptionName

3_Add_disks.ps1

$vmServiceName

Use the same name from 2_CreateVM.ps1.

3_Add_disks.ps1

$storageAccountName

Use the same location you used in 1_CreateStorage_Network.ps1.

------------

--------------

------------

OnBoxScript7.ps1

Update the three references to the Cloud Service name used in 2_CreateVM.ps1. OnBoxScript7.ps1 configures an IIS certificate based on the Cloud Service name.

------------

--------------

------------

UnmountData.ps1

$subscriptionID

UnmountData.ps1

$subscriptionName

UnmountData.ps1

$thumbPrint

UnmountData.ps1

$certificate

UnmountData.ps1

$vmServiceName

UnmountData.ps1

$vmName

Arrow icon used with Back to Top link.Prepare the environment

Arrow icon used with Back to Top link Top

This section walks you through creating virtual hard disks that contain your SQL Server and SharePoint 2013 installation files.

The following steps work on Windows 7, Windows 8, Windows Server 2008 R2, Windows Server 2012.

To create a drive X, open Windows PowerShell with administrative privileges and run the following commands:

New-vhd c:\BitsForCloud2013.vhd –SizeBytes 130GB -Dynamic
Mount-VHD –Path c:\BitsForCloud2013.vhd -PassThru | Initialize-Disk -PartitionStyle MBR  -PassThru | New-Partition -UseMaximumSize -DriveLetter x | Format-Volume -FileSystem NTFS -NewFileSystemLabel BitsForCloud2013 -confirm:$false

Arrow icon used with Back to Top link Prepare the environment

Arrow icon used with Back to Top link Top

Create folders on the X: drive to contain the scripts and installation files. To create the following folders, open a Windows PowerShell window and run the following commands:

New-Item -Path X:\ -name "scripts" -ItemType "directory"
New-Item -Path X:\ -name "bits" -ItemType "directory"
New-Item -Path X:\bits\ -name "Sharepoint2013" -ItemType "directory"
New-Item -Path X:\bits\ -name "SQLServer2012sp1" -ItemType "directory"

Arrow icon used with Back to Top link Prepare the environment

Arrow icon used with Back to Top link Top

Copy the installation files for SQL Server 2012 SP1 and SharePoint Server 2013 to the VHD file.

  1. Copy SharePoint 2013 server files to X:\Bits\SharePoint2013.

  2. Copy SQL Server 2012 files to X:\Bits\SQLServer2012sp1.

  3. Copy the scripts folder C:\WA_BI_VM2013\OnBox to X:\Scripts, the resulting folder is X:\Scripts\onbox.

Arrow icon used with Back to Top link Prepare the environment

Arrow icon used with Back to Top link Top

Add your SQL Server License key to the /PID parameter in the following scripts that install instances of SQL Server. Update each instance of the /PID parameter. Add your key inside the double quotes. /PID Specifies the product key for the edition of SQL Server. If this parameter is not specified, Evaluation is used and the Evaluation license is not allowed on Azure Virtual Machines:

  • X:\Scripts\onbox\OnBoxScript_3.ps1: Update one instance of the SQL Server PID.

  • X:\Scripts\onbox\OnBoxScript_4.ps1: Update three instances of the SQL Server PID.

For more information on using /PID, see Install SQL Server 2012 from the Command Prompt (http://msdn.microsoft.com/en-us/library/ms144259.aspx#Install).

  1. Edit the SharePoint silent installation file with your SharePoint license key: x:\bits\SharePoint2013\Files\SetupFarmSilent\config.xml

  2. Add your license key and remove the comment characters:

    <!--<PIDKEY Value="Enter Product Key Here" />-->

    To look like the following:

    <PIDKEY Value="your license key”/>

For more information on SharePoint command-line setup and the Confg.xml file, see the following:

  1. Config.xml reference (SharePoint Server 2010) (http://technet.microsoft.com/en-us/library/cc261668(v=office.14).aspx).

  2. Setup command-line reference (SharePoint Server 2010) (http://technet.microsoft.com/en-us/library/cc262897(v=office.14).aspx).

Arrow icon used with Back to Top link Prepare the environment

Arrow icon used with Back to Top link Top

The .vhd cannot be copied while it is attached. To detach the .vhd, open Windows PowerShell with administrative privileges and run the following:

  • Dismount-VHD –Path c:\BitsForCloud2013.vhd
    

Arrow icon used with Back to Top link Prepare the environment

Arrow icon used with Back to Top link Top

This section walks you running and verifying Azure PowerShell scripts that create and configure Azure objects.

The following table summarizes the scripts used to configure the Azure environment.

 

Run from Script Name Description of script tasks

Local, Windows Azure PowerShell

GetGalleryImageList_andLocationList.ps1

This script is optional and it retrieves information from your Azure subscription to help you populate parameters in the other scripts. The script returns the following:

  • A list of locations and services available to your Azure subscription.

  • A current list of the Azure virtual machine gallery images.

1_CreateStorage_Network.ps1

  • Creates an Azure Affinity group.

  • Creates an Azure virtual Network.

  • Creates an Azure Storage Account.

  • Uploads the .vhd file that you created in the preparation steps.

Local, Windows Azure PowerShell Local

2_CreateVM.ps1

  • Creates an Azure Virtual Machine

3_Add_disks.ps1

  • Creates a data disk for a domain controller.

  • Creates a data disk for SQL Server.

  • Creates a data disk for the uploaded .vhd.

  • Creates an SSL EndPoint.

  • Secures the RDP Endpoint by changing the port# used for the public port.

Arrow icon used with Back to Top link Script Summary

Arrow icon used with Back to Top link Top

This script completes the following tasks:

  1. Creates an Azure Affinity group.

  2. Creates an Azure virtual Network.

  3. Creates an Azure Storage Account.

  4. Uploads the .vhd file.

  

WarningWarning
This script assumes that you are using a subscription that does not already contain an Azure virtual network. If your subscription does contain an existing virtual network that you cannot delete, see the section Virtual Network Conflicts in this topic.

  

Steps:

  1. Create folder C:\Temp if it does not exist.

  2. Copy C:\WA_BI_VM2013\OffBox\NetworkConfig.netcfg to C:\Temp. If you want to use a folder other than C:\Temp, update the -ConfigurationPath parameter in the 1_CreateStorage_Network.ps1 script.

  3. The first time you open the Azure PowerShell command shell, run the following command to set the execution policy to RemoteSigned.

    Set-ExecutionPolicy RemoteSigned
    
    To verify the current execution policy, run the following command:

    Get-ExecutionPolicy
    
  4. Open Windows Azure PowerShell and run the following command:

    C:\WA_BI_VM2013\OffBox\1_CreateStorage_Network.ps1
    
    Note: the text file c:\WA_BI_VM2013\file_paths.txt contains the path of all of the scripts to make it easier to copy and paste.

  5. The script runs for 5 to 15 minutes, depending on the speed of your internet connection. A majority of the script run time is due to copying the .vhd file to Azure. You see a status message similar to the following:

      

    • Bits Disk: Does Not Exist...Creating

      Windows(R) Azure(TM) Upload Tool version 1.8.0.0

      for Microsoft(R) .NET Framework 3.5

      Copyright (c) Microsoft Corporation. All rights reserved.

      Using the saved connection string...

      MD5 hash is being calculated for the file 'C:\BitsForCloud2013.vhd'.

      Progressing: 45.4% complete; Remaining Time: 00:08:49; Throughput: 1073.4Mbps

      

    The script checks for the existence of Azure objects that have the same name as the objects created by the scripts. If the objects exist, the script skips the creation step and it writes a verification message to the Windows PowerShell window similar to Affinity Group Exists….Moving On.

Verification:

    1. Browse to Azure Management Portal and click All Items in the left navigation pane.

      all items
    2. Verify the storage account (iaasbistorage2) and virtual network (Iaas-BI-Network) exist.

    1. Click Settings in the left navigation pane.

      settings
    2. Click Affinity Groups in the top menu and then verify that the Iaas BI Affinity group exists.

    1. Click Storage in the left navigation pane and then click the iaasbistorage2 storage account.

      windows azure iaas storage icon
    2. Click Containers in the top menu and then click the container vhds.

    3. Verify the BitsForCloud2013.vhd .vhd was uploaded.

  1. Note: For a brief explanation of the Azure Storage Hierarchy, see the section An Overview of Azure Storage.

This script creates an Azure Virtual Machine, based on a Microsoft Windows Server image available in the Azure virtual machine gallery.

  

Steps:

  1. Open Windows Azure PowerShell and run the following command:

    C:\WA_BI_VM2013\OffBox\2_CreateVM.ps1
    
  2. If your subscription does not have enough cores to run the scripts, the 2_CreateVM.ps1 script fails with a message similar to the following:

    • New-AzureVM : Failed: The subscription policy limit for resource type 'cores count' was exceeded. The limit for resource type 'cores count' is 20 per subscription, the current count is 18, and the requested increment is 4.

Verification:

    1. Refresh the Azure Management portal and click All Items.

      all items
    2. Verify that the virtual machine Iaas-BI-Full exists.

  1. ImportantImportant
    It is recommended you run windows Update on the VM before running more scripts. The number of updates installed depends on the age of the base operating system image used to build the VM. Determining the operating system image was one of the preparation steps. To Run Windows Update:

    1. In the Azure Management portal, click the Virtual Machines icon in the left pane.

      windows azure virtual machines
    2. The new Virtual machine Iaas-BI-Full is selected by default. Click the Connect icon on the bottom of the screen.

      connect to azure virtual machine
    3. Log on as the user:

      • User: testuser

      • Password: Testword!1

    4. Open Windows Update in control panel.

    5. Click Check for updates.

  2. After installing updates, you may need to restart the virtual machine.

For more information on Azure PowerShell cmdlets used by the 2_CreateVM.ps1 script, see the following:

  • New-AzureVM (http://msdn.microsoft.com/en-us/library/windowsazure/jj152815.aspx).

  • New-AzureVMConfig (http://msdn.microsoft.com/en-us/library/windowsazure/jj152883.aspx).

Arrow icon used with Back to Top link Script Summary

Arrow icon used with Back to Top link Top

This script completes the following tasks:

  • Creates a data disk for a Domain Controller.

  • Creates data disk for SQL Server.

  • Creates a data disk for the .vhd that was uploaded by 1_CreateSorage_Network.ps1.

  • Creates an SSL EndPoint.

  • Changes the remote desktop (RDP) endpoint public port number.

Steps:

  1. Open Windows Azure PowerShell and run the following command:

    C:\WA_BI_VM2013\OffBox\3_Add_disks.ps1
    

Verification:

    1. Refresh the Azure Management portal and click the Virtual Machines icon in the left pane.

      windows azure virtual machines
    2. Click Disks in the top menu.

    3. Verify that there are 4 disks that list Iaas-BI-Full in the Attached To column. The URL in the Location column includes the .vhd name that a disk is using. For example, https://iaasbistorage2.blob.core.windows.net/vhds/BitsForCloud2013.vhd.

    4. An alternative method to verify the disks is to run the following script from the Windows Azure Powershell window:

      C:\WA_BI_VM2013\Offbox\GetGalleryImageList_andLocationList.ps1
      
  1. Click the Virtual Machines icon in the left pane.

    windows azure virtual machines
    1. Select the Virtual machine Iaas-BI-Full and click the Connect icon on the bottom of the screen.

      connect to azure virtual machine
    2. Log on as the user:

      • User:testuser

      • Password:Testword!1

    3. Verify the drive F:\ is attached and contains the F:\scripts folder and the F:\Bits folder.

This section walks you through running and verifying Windows PowerShell scripts on the VM to install and configure SQL Server and SharePoint.

 

Run from Script Name Description of script tasks

On VM, Windows PowerShell

OnBoxScript_1.ps1

  • Formats Disk 2 and assigns drive letter Z.

  • Formats Disk 3 and assigns drive letter S.

OnBoxScript_1a.ps1

Configures the virtual machine as a domain controller (DC).

On VM, Windows PowerShell

OnBoxScript_2.ps1

  • This script runs the SharePoint 2013 prerequisite installer and restarts the VM. Run this script twice.

On VM, Windows PowerShell

OnBoxScript2a.ps1

  • This script runs the SharePoint 2013 prerequisite installer one more time and then it installs SharePoint 2013. The script uses the installation files you copied to the .vhd.

On VM, Windows PowerShell On VM

OnBoxScript_3.ps1

  • Creates Active Directory users.

  • Installs SQL Server Features: Database Engine, Reporting Services SharePoint mode, Reporting Services add-in for SharePoint, SQL Server Data Tools, and Management Studio.

  • Creates several accounts for the SQL Server services and SharePoint.

On VM, Windows PowerShell

OnBoxScript_4.ps1

  • Installs three instances of SQL Server Analysis Services. The script runs SQL Server setup three times to install the following:

  • Analysis Services – MultiDimensional

  • Analysis Services – Tabular

  • PowerPivot

On VM, Windows PowerShell On VM

OnBoxScript_5.ps1

  • Core SharePoint Farm configuration, including SharePoint Central Administration.

  • Deploys the two PowerPivot solutions.

  • Installs the three PowerPivot SharePoint features.

On VM, Windows PowerShell

OnBoxScript_6.ps1

  • Creates PowertPivot Service application, creates web application, and deploys solution.

  • Creates a site and enables features.

  • Configures Secure Store Service.

  • Configures Excel Services.

On VM, Windows PowerShell

OnBoxScript_7.ps1

  • Creates an IIS certificate.

  • Binds the certificate to the site.

  • Creates Alternate Access Mapping for https.

On VM, Windows PowerShell

OnBoxScript_8.ps1

  • Configures Reporting Services in SharePoint mode

Arrow icon used with Back to Top link Script Summary

Arrow icon used with Back to Top link Top

This script partitions and formats drive “Z” and drive “S”.

Steps:

  1. Browse to the Azure Management Portal and connect to the Virtual Machine Iaas-BI-Full and log on as the user:

    • User:testuser

    • Password:Testword!1

  2. On the virtual machine, open Windows PowerShell or Windows PowerShell ISE. Windows PowerShell 3.0 does not require you to open with the system modules because Windows PowerShell 3.0 automatically loads modules the first time a relevant cmdlet runs.

  3. To verify the current execution policy, run the following command:

    Get-ExecutionPolicy
    
  4. If the returned value is Restricted, run the following command to change the configuration:

    Set-ExecutionPolicy RemoteSigned
    
  5. Type Y to confirm the execution policy change.

  6. Run the following command:

    F:\scripts\OnBox\onboxScript_1.ps1
    

If you see an error message similar to the following, set the executionpolicy:

  • F:\scripts\OnBox\OnBoxScript_1.ps1 : File F:\scripts\OnBox\OnBoxScript_1.ps1 cannot be loaded because running scripts is disabled on this system.

If you see an error message similar to the following, close the Windows PowerShell window and reopen it with administrative privileges:

  • Get-Disk : Access to a CIM resource was not available to the client.At line:1 char:1+ Get-Disk+ ~~~~~~~~ + CategoryInfo : PermissionDenied: (MSFT_Disk:ROOT/Microsoft/Windows/Storage/MSFT_Disk) [Get-Disk], CimException + FullyQualifiedErrorId : MI RESULT 2,Get-Disk

Verification: To verify the script succeeded:

  1. In the Azure Management portal, connect to the virtual machine and log on as the user:

    • User: testuser

    • Password: Testword!1

  2. To verify the volumes were created, complete one of the following:

    • Run the following Windows PowerShell command and verify the Z, S, and F drives exist:

      Get-Volume
      
      • DriveLetter FileSystemLabel FileSystem DriveType HealthStatus SizeRemaining Size

      • ----------- --------------- ---------- --------- ------------ ------------- ----

      • Z NTFS Fixed Healthy 59.9 GB 60 GB

      • S NTFS Fixed Healthy 109.89 GB 110 GB

      • F BitsForCloud2013 NTFS Fixed Healthy 120.52 GB 127 GB

    • Open Windows File Explorer and verify the F:, S:, and Z: drives exist.

Arrow icon used with Back to Top link Script Summary

Arrow icon used with Back to Top link Top

This script Configures the VM as a domain controller (DC).

Steps:

  1. Browse to the Azure Management Portal and connect to the Virtual Machine Iaas-BI-Full and log on as the user:

    • User:testuser

    • Password:Testword!1

  2. On the virtual machine, open Windows PowerShell or Windows PowerShell ISE.

  3. Run the following command:

    F:\scripts\OnBox\onboxScript_1a.ps1
    
  4. The script runs for 5-10 minutes and the output message looks similar to the following:

    • Message : You must restart this computer to complete the operation.

    • Context : DCPromo.General.4

    • RebootRequired : True

    • Status : Success

  5. Restart the VM before running the next script.

Verification: To verify the script succeeded:

  1. In the Azure Management portal, connect to the virtual machine and log on as the user:

    • User: testuser

    • Password: Testword!1

  2. To verify the Domain controller, complete one of the following:

    • On the VM, open a Windows PowerShell window and run the following:

      $computerdomain = [System.DirectoryServices.ActiveDirectory.Domain]::GetCurrentDomain() ; $computerdomain.name
      
      The output is Iaas-BI.local

    • Run the System application in Windows Control Panel and verify that the Domain is IaaS-BI.local.

  3. TipTip
    It is recommended you run Microsoft Windows Update before running more scripts. The number of updates varies depending on the base image that used to create the VM. Windows update may require the virtual machine to reboot after updates are installed.

For more information on the Active Directory Windows PowerShell cmdlets, see Install-ADDSForest http://technet.microsoft.com/en-us/library/hh974720.aspx.

Arrow icon used with Back to Top link Script Summary

Arrow icon used with Back to Top link Top

This script completes the following tasks:

  • Runs the SharePoint prerequisite installer and then restarts the VM.

  • Run this script twice.

Steps:

  1. In the Azure Management portal, connect to the virtual machine and log on as the user:

    • User: testuser

    • Password: Testword!1

  2. On the virtual machine, open Windows PowerShell.

  3. Run the following command:

    F:\scripts\onbox\OnBoxScript_2.ps1
    
  4. The SharePoint Products Preparation tool (the prerequisite installer) opens and runs.

  5. Note: The last step in the script restarts the VM, and therefore the remote connection closes.

  6. Connect to the VM in the Azure Management portal. On start, the VM configures Windows features that were installed by the SharePoint prerequisite installer.

  7. Run the script a second time. Again, the VM restarts and closes the remote connection window.

Arrow icon used with Back to Top link Script Summary

Arrow icon used with Back to Top link Top

This script completes the following tasks:

  • Runs the SharePoint prerequisite installer a third time.

  • Installs SharePoint 2013, using the installation files you copied to the .vhd in the preparation steps.

Steps:

  1. In the Azure Management portal, connect to the virtual machine and log on as the user:

    • User: testuser

    • Password: Testword!1

  2. On the virtual machine, open Windows PowerShell and run the following command:

    F:\scripts\onbox\OnBoxScript_2a.ps1
    
  3. The SharePoint Products Preparation tool (the prerequisite installer) opens and runs.

  4. After the Prerequisite installer completes, the script installs SharePoint. The SharePoint installation is a silent installation and there are no dialogs visible. The SharePoint installation process runs for 10-15 minutes.

    • The Prerequisite installer should complete with ExitCode: 0.

    • TipTip
      If the SharePoint installation quickly exits with ExitCode 30030, verify you updated the f:\bits\SharePoint2013\Files\SetupFarmSilent\config.xml file with your SharePoint license PIDKey. For more information, see the section Update the SharePoint Config.xml Installation File with Your SharePoint PIDKEY.

    • The SharePoint installation runs for several minutes and if it exits with ExitCode 3010, a restart of the VM is required before you run the next script.

Verification: To verify the script succeeded:

  1. To see a list of the SharePooint services that are installed, run the following Windows PowerShell command:

    Get-Service -DisplayName *sharepoint* | Format-Table -autosize status,displayname
    
    The services all have a status of ‘stopped’. The services do not run until you run the next several scripts, which install the SQL Server database engine and configure the SharePoint farm.

    • Status DisplayName

    • ------ -----------

    • Stopped Document Conversions Launcher for Microsoft SharePoint Server 2013

    • Stopped Document Conversions Launcher for Microsoft SharePoint Server 2013

    • Stopped Document Conversions Load Balancer for Microsoft SharePoint Server 2013

    • Stopped SharePoint Server Search 15

    • Stopped SharePoint Administration

    • Stopped SharePoint Search Host Controller

    • Stopped SharePoint Timer Service

    • Stopped SharePoint Tracing Service

    • Stopped SharePoint User Code Host

    • Stopped SharePoint VSS Writer

  2. Verify in Start, All programs you see the Microsoft SharePoint Products group.

  3. To trouble shoot SharePoint installation issues, see the SharePoint installation logs files. The location of the log files depends on the Logging Type setting in the following configuration file:

    • F:\bits\SharePoint2013\Files\SetupFarmSilent\config.xml

    The default value for Logging Type is the following:

    • <Logging Type="verbose" Path="%temp%" Template="SharePoint Server Setup(*).log"/>

    Which resolves to the path of: C:\Users\<User Name>\AppData\Local\Temp\2.

    Note:AppData is a hidden folder by default.

Arrow icon used with Back to Top link Script Summary

Arrow icon used with Back to Top link Top

Your SQL Server license needs to be in the OnBoxScript_3.ps1 script file. Editing the script was a step in the preparation section. If you have not added your SQL Server key to the /PID=, see Update Scripts with your SQL Server License Key. This script completes the following tasks:

  • Creates Active Directory (AD) users. Creates the following accounts for the SQL Services and SharePoint. The accounts are all created with the same password of Testword!1.

    • SQL_Engine

    • SQL_Agent

    • SQL_Reporting

    • SQL_AS_MD

    • SQL_AS_Tabular

    • SQL_PowerPivot

    • SP_Farm

    • SP_Root

  • Installs the following SQL Server Features:

    • Database Engine

    • Reporting Services SharePoint mode

    • Reporting Services add-in for SharePoint

    • SQL Server Data Tools

    • SQL Server Management Studio

Steps:

  1. In the Azure Management portal, connect to the virtual machine and log on as the user:

    • User: testuser

    • Password: Testword!1

  2. On the virtual machine, open Windows PowerShell.

  3. Run the following command:

    F:\scripts\onbox\OnBoxScript_3.ps1
    
  4. The Script runs 10-15 minutes.

    For information on where to find and view SQL Server Setup log files, see View and Read SQL Server Setup Log Files (http://msdn.microsoft.com/en-us/library/ms143702.aspx).

  5. If SQL Server installation completes, install exits with Setup result: 0

  6. ImportantImportant
    Note: Restart the virtual machine and run Windows update before running more scripts.

Verification:

SQL Server: To verify the script successfully installed the SQL Server components, complete the following.

    • To verify from Windows PowerShell:

      • get-service -displayname sql*
        
        • Status Name DisplayName

        • ------ ---- -----------

        • Running MSSQL$SHAREPOINT SQL Server (SHAREPOINT)

        • Running SQLAgent$SHAREP... SQL Server Agent (SHAREPOINT)

        • Running SQLBrowser SQL Server Browser

        • Running SQLWriter SQL Server VSS Writer



    • To verify with the user interface:

      1. Click Start and then click All Programs.

      2. Click Microsoft SQL Server 2012 and then click Configuration Tools.

      3. Click SQL Server Configuration Manager.

      4. In the SQL Server Configuration Manager, in the left pane, click SQL Server Services. Note the SQL Server (SharePoint) and SQL Server Agent (SharePoint) instances are installed and running.

Accounts: To verify the script successfully created the “SQL” and “SP” accounts, complete the following:

  • From Windows PowerShell: Open Windows PowerShell and then run the following command:

    Get-ADUser -filter * | format-table name,enabled,distinguishedname –autosize
    
      • name enabled distinguishedname

      • ---- ------- -----------------

      • SQL_Engine True CN=SQL_Engine,CN=Users,DC=IaaS-BI,DC=local

      • SQL_Agent True CN=SQL_Agent,CN=Users,DC=IaaS-BI,DC=local

      • SQL_Reporting True CN=SQL_Reporting,CN=Users,DC=IaaS-BI,DC=local

      • SQL_AS_MD True CN=SQL_AS_MD,CN=Users,DC=IaaS-BI,DC=local

      • SQL_AS_Tabular True CN=SQL_AS_Tabular,CN=Users,DC=IaaS-BI,DC=local

      • SQL_PowerPivot True CN=SQL_PowerPivot,CN=Users,DC=IaaS-BI,DC=local

      • SP_Farm True CN=SP_Farm,CN=Users,DC=IaaS-BI,DC=local

      • SP_Root True CN=SP_Root,CN=Users,DC=IaaS-BI,DC=local

Arrow icon used with Back to Top link Script Summary

Arrow icon used with Back to Top link Top

Your SQL Server license needs to be in the script file. Editing the script was a step in the preparation section. If you have not added your SQL Server key to the /PID= parameter in OnBoxScript_4.ps1, see Update Scripts with your SQL Server License Key.

This script completes the following tasks:

Runs SQL Server setup three times to install the following three instances of Analysis Services.

  • Analysis Services – Multi-Dimensional

  • Analysis Services – Tabular

  • PowerPivot

If you do not plan to use Analysis Services Multi-Dimensional mode or Analysis Services Tabular mode, you can comment out the appropriate lines by adding # to the beginning of the lines (.\setup.exe) in the OnBoxScript_4.ps1 script. PowerPivot is required for later scripts that configure the farm, PowerPivot, and Reporting Services SharePoint mode.

 

Note: The SQL Server setup command lines used by the OnBoxScript_4.ps1 script, disables error reporting with the parameter /ERRORREPORTING=0. Modify the values if you need to trouble shoot installation. Supported values for /ERRORREPORTING=0 1=enabled or 0=disabled. You may also find the parameter /INDICATEPROGRESS useful. /INDICATEPROGRESS configures setup to pipe the verbose setup log file to the console. For more information, see Install SQL Server 2012 from the Command Prompt (http://technet.microsoft.com/en-us/library/ms144259.aspx).

 

Steps:

  1. In the Azure Management portal, connect to the virtual machine and log on as the user:

    • User:testuser

    • Password:Testword!1

  2. Run the following command:

    F:\scripts\onbox\OnBoxScript_4.ps1
    
    If SQL Serve setup completes successfully, the result code is Setup result: 0.

  3. noteNote
    Before you run the next script, close and reopen the Windows PowerShell window. The PowerPivot cmdlets added by the OnBoxScript_4.ps1 script are not available until the Windows PowerShell environment is restarted.

Verification: To verify the three instances of Analysis Services were installed, complete on of the following:

  • To verify with Windows PowerShell:

    • Get-service -displayname 'sql server analysis*'
      
      • Status Name DisplayName

      • ------ ---- -----------

      • Running MSOLAP$AS_MD SQL Server Analysis Services (AS_MD)

      • Running MSOLAP$AS_TAB SQL Server Analysis Services (AS_TAB)

      • Running MSOLAP$POWERPIVOT SQL Server Analysis Services (POWER...

  • To verify with the user interface:

    1. Click Start and then click All Programs.

    2. Click Microsoft SQL Server 2012 and then click Configuration Tools.

    3. Click SQL Server Configuration Manager.

    4. In the SQL Server Configuration Manager, in the left pane, click SQL Server Services. Note the three instances of Analysis Services are installed and running.

      sql services installed

Arrow icon used with Back to Top link Script Summary

Arrow icon used with Back to Top link Top

This script completes the following tasks:

  • Core SharePoint Farm configuration that includes the SharePoint Central Administration site.

  • Deploys the PowerPivot farm solution and the PowerPivot application solution.

  • Installs the three PowerPivot SharePoint features.

Steps:

  1. On the virtual machine, open Windows PowerShell.

  2. Run the following command:

    F:\scripts\onbox\OnBoxScript_5.ps1
    
  3. Close and reopen the Windows PowerShell window before running the next script.

Verification: To verify the script succeeded:

  1. To verify the three PowerPivot features are installed, complete the following steps:

    1. In All Programs click Microsoft SharePoint Products.

    2. Click SharePoint Management Shell.

    3. Run the following command:

    Get-spfeature | where {$_.displayname –like “PowerP*”}
    
    DisplayName Id Scop

    ----------- -- ----

    PowerPivotSite 1a33a234-b4a4-4fc6-96c2-8bdb56388bd5 Site

    PowerPivotAdmin e9c4784b-d453-46f5-8559-3c891d7159dd Web

    PowerPivot f8c51e81-0b46-4535-a3d5-244f63e1cab9 Farm

  2. To verify the SharePoint solutions are installed, open the SharePoint Management Shell and run the following command:

    Get-SPSolution
    
    Name SolutionId Deployed

    ---- ---------- --------

    powerpivotfarm14solution.wsp 20556862-2287-4547-ae18-66e95a471271 True

    powerpivotfarmsolution.wsp 28201e83-6a35-4237-9ac0-4323f3d28497 True

    powerpivotwebapplicationsol... e51f7fb9-2272-4e77-a2af-7a070edd82b6 True

  3. On the virtual machine, verify you can browse to SharePoint Central Administration. Use one of the following methods:

    1. The default url is http://iaas-bi-full:8080. Use the testuser user name and Testword!1 password to log on.

    2. Click Start, and type SharePoint 2013 Central Administration.

Arrow icon used with Back to Top link Script Summary

Arrow icon used with Back to Top link Top

This script completes the following tasks:

  • Creates a PowertPivot Service application and creates a web application.

  • Creates a site and enables features.

  • Configures Secure Store Service.

  • Configures Excel Services.

Steps:

  1. On the virtual machine, open Windows PowerShell.

  2. Run the following command:

    F:\scripts\onbox\OnBoxScript_6.ps1
    

Verification: To verify the script succeeded:

  1. To verify the PowerPivot system service is installed, use Windows PowerShell. Open the SharePoint Management Shell and run the following command:

    PowerPivotSystemServiceInstance
    
    • TypeName Status Id

    • -------- ------ --

    • SQL Server PowerPivot System ... Online a79ba103-048c-4a47-a6fb-61c3c66f7f82

  2. To verify the PowerPivot service application exits, use Windows PowerShell. Open the SharePoint Management Shell and run the following command:

    get-PowerPivotServiceApplication
    
    • DisplayName TypeName Id

    • ----------- -------- --

    • Default PowerPivo... PowerPivot Servic... 1d89c0da-ab9f-4329-bc21-ca106c701817

  3. To verify that the Execel Services service application exists, use of one the following methods:

    1. In SharePoint Central Administration, click Manage Service Applications. If you are prompted for credentials, use the testuser and Testword!1 credentials to log on. Verify the Excel Service Application ExcelServiceApp1 is Started.

    2. Run the following Windows PowerShell command from the SharePoint Management shell:

      get-SPExcelServiceApplication
      
      • DisplayName TypeName Id

      • ----------- -------- --

      • ExcelServiceApp1 Excel Services Ap... e46e2ce0-5f85-47e6-b5da-a7ac9c96a960

  4. To verify that the site exists, use one of the following methods:

    1. Run the following Windows PowerShell command from the SharePoint Management shell:

      Get-spsite
      
      • Url CompatibilityLevel

      • --- ------------------

      • http://iaas-bi-full 15

    2. Browse to the PowerPivot site, http://iaas-bi-full/SitePages/Home.aspx.

Arrow icon used with Back to Top link Script Summary

Arrow icon used with Back to Top link Top

This script completes the following tasks:

  • Create an IIS certificate

  • Binds the certificate to the site

  • Creates and alternate access mapping (AAM) for https

Steps:

  1. On the virtual machine, open Windows PowerShell.

  2. Run the following command:

    F:\scripts\onbox\OnBoxScript_7.ps1
    

Verification: To verify the script succeeded:

  1. To verify that the binding exists, run the following Windows PowerShell command from the SharePoint Management Shell:

    Get-WebBinding
    
    • protocol bindingInformation sslFlags

    • -------- ------------------ --------

    • https *:443: 0

  2. To verify the <your cloud service name>.cloudapp.net mapping exists, run the following Windows PowerShell command from the SharePoint Management Shell:

    Get-Spalternateurl
    
    The result:

    IncomingUrl Zone PublicUrl

    ----------- ---- ---------

    https://iaas-bi-onsharepoint2.cloudap... Extranet https://iaas-bi-onsharepoint2.cloudap

Arrow icon used with Back to Top link Script Summary

Arrow icon used with Back to Top link Top

This script completes the following tasks:

  • Installs and starts the Reporting Services Service.

  • Creates a Reporting Services service application, application pool, and proxy.

  • Associates the Reporting Services service application proxy to the default website.

  • Grants the web application rights to the Reporting Services application pool.

Steps:

  1. On the virtual machine, open Windows PowerShell.

  2. Run the following command:

    F:\scripts\onbox\OnBoxScript_8.ps1
    
    noteNote
    To create a managed service account, the script retrieves the credentials for the IaaS-BI\SQL_Reporting service account. This step causes a credential verification dialog to appear. Type the password Testword!1, unless you changed the password in earlier scripts.

    If you want to run these scripts in a more automated way and not have the confirmation dialog appear, review the following for a workaround proposed by the community, Get-Credential at the command line (http://www.powershellmagazine.com/2013/02/11/pstip-get-credential-at-the-command-line/).

credential request

Verification: To verify the script succeeded:

To verify that the Reporting Services service application exists, use one of the following methods:

  • Run the following command from the SharePoint Management Shell:

    Get-SPRSServiceApplication
    
    • Name Id UEAccountName

    • ---- -- -------------

    • Reporting Services ... e36f8012-a002-4007-b913-114c387d6d1a

    1. In SharePoint Central Administration, click Manage Service Applications.

    2. If you are prompted for credentials, use testuser and the Testword!1 password to log on.

    3. Verify that the Reporting Services Application and Reporting Services Application Proxy are installed and Started.

To verify that the Reporting Services service application pool exists, complete the following:

  1. Run the following command from the SharePoint Management Shell:

    Get-SPServiceApplicationPool | where {$_.name -like "reporting*"}
    
    • Name ProcessAccountName

    • ---- ------------------

    • Reporting Services IaaS-BI\SQL_Reporting

To verify that the Reporting Services service application proxy exists, complete the following:

  1. Run the following command from the SharePoint Management Shell:

    Get-SPRSServiceApplicationProxy
    
    • DisplayName TypeName Id

    • ----------- -------- --

    • Reporting Service... SQL Server Report... d8acc98a-fa0d-4453-8741-d56bafd8b46a

Arrow icon used with Back to Top link Script Summary

Arrow icon used with Back to Top link Top

This section includes configuration steps you complete from the virtual machine, and a Windows PowerShell script you run from your local computer to detach the .vhd that contained the SQL Server and SharePoint installation files.

This script completes the following tasks:

  • Unmounts the F: drive, the .vhd that contains the SQL Server and SharePoint installation files. The drive is removed from the VM but the .vhd is still in Azure storage. The last sets of steps are optional and will delete the disk (.vhd) from Azure storage and will reduce the storage used by your Azure subscription.

Steps:

  1. On your local computer, open Windows Azure PowerShell.

  2. Run the following command:

    C:\WA_BI_VM2013\offbox\4_UnmountData.ps1
    

Verification: To verify the script succeeded:

  1. In the Azure Management portal, connect to the VM and log on as:

    • User: testuser

    • Password: Testword!1

  2. Open Windows File Explorer and verify the F: drive is not listed.

  3. Note: If you do not plan to use the BitsForCloud2013.vhd again, complete the following steps to delete the .vhd from Azure storage so you minimize storage costs.

    1. Browse to the Azure Management Shell.

    2. Click Virtual Machines and then click Disks in the top menu.

    3. Click the filter icon and then type bits in the filter box.

      filter disks for the bits vhd
    4. Click disk name and then click Delete in the bottom menu.

    5. Click Delete associated .vhd.

Arrow icon used with Back to Top link Cleanup script and additional configuration

Arrow icon used with Back to Top link Top

Verify you can access the following URLs on the server. Update the URL as appropriate for your installation. If a credential dialog appears, use the testuser name and password. Sometimes the browser will timeout the first time you browse to the site. If a time out occurs, refresh the browser.

  1. SharePoint Central Administration: http://iaas-bi-full:8080/default.aspx.

  2. The PowerPivot Site: http://iaas-bi-full/SitePages/Home.aspx.

The first time you click PowerPivot Gallery in the SharePoint left navigation pane, you see a message indicating the need to install Silverlight.

Browse to the PowerPivot Gallery, replacing the portion of the URL as appropriate for your installation: http://iaas-bi-full/PowerPivot%20Gallery/Forms/Gallery.aspx.

If a credential dialog appears, use the testuser name and password. Sometimes the browser will timeout the first time you browse to the site. If a timeout occures, refresh the browser.

Before you download Silverlight, complete the following steps to configure Internet Explorer on the virtual machine to allow downloads.

  1. Open Internet Explorer browser.

  2. Go to the Tools menu.

  3. Select Internet Options.

  4. Go to the Security tab.

  5. Select Internet zone.

  6. Click Custom level.

  7. Under the Downloads category, select enable for File download.

  8. Click OK, and then click OK again.

  9. Close and restart Internet Explorer.

  10. Browse to the PowerPivot Gallery, http://iaas-bi-full/PowerPivot%20Gallery/Forms/Gallery.aspx click the icon Install Microsoft Silverlight.

  11. When the Silverlight installation is complete, refresh the browser to see the PowerPivot Gallery view.

It is recommended that after the Silverlight installation is complete, that you change the browser security configuration back to a state that prevents downloads.

Arrow icon used with Back to Top link Script Summary

Arrow icon used with Back to Top link Top

Reporting Services provides content types that are used to manage shared data source (.rsds) files and report definition (.rdl) files. Adding the content types to a library enables the Reporting Services options in the New menu.

Browse to the document library, replacing the portion of the URL as appropriate for your installation: http://iaas-bi-full/Shared%20Documents/Forms/AllItems.aspx.

For more information, see Add Report Server Content Types to a Library (Reporting Services in SharePoint Integrated Mode) (http://msdn.microsoft.com/en-us/library/bb326289.aspx).

Arrow icon used with Back to Top link Cleanup script and additional configuration

Arrow icon used with Back to Top link Top

The following is a list of links to client tools that leverage the SQL Server and SharePoint BI platform:

Arrow icon used with Back to Top link Top

For information on how to export a certificate with the private key and import the certificate to another computer so that computer can also manage your Azure Subscription, see How to: View Certificates with the MMC Snap-in (http://msdn.microsoft.com/en-us/library/ms788967(v=vs.110).aspx).

You can also export and import certificates from Internet Explorer. For example to Export:

  1. Click Internet options.

  2. Click the Content tab.

  3. Click Certificates.

  4. Select the certificate you want to export, and click Export

  5. In the Certificate Export Wizard, select the option to export the private key.

Arrow icon used with Back to Top link More Resources

Arrow icon used with Back to Top link Top

Run the following command from an Azure PowerShell window to see a list of Azure cmdlets:

'help azure'

To get command line help for a specific command, use the –full switch, for example:

get-help New-AzureVMConfig  -full

Arrow icon used with Back to Top link More Resources

Arrow icon used with Back to Top link Top

This section describes steps to ‘clean up’ the subscription in case you want to re-run the scripts starting with createvm.ps1. In Azure Management Portal, click All Items, and delete the following in the order listed: all items

  1. Click Virtual Machines, and then click the virtual machine Iaas-BI-Full. Click Delete.

  2. Click Virtual Machines and then in the top menu, click Disks. Click Delete, and then click Delete the associated VHD. Repeat for all the disks. Note: If can choose not to delete the associated .vhd for the bits disk, then the .vhd will not have to be uploaded again to Azure storage.

  3. Click Networks, and then click the network Iaas-BI-network. Click Delete.

  4. Click Cloud Services and then select the name of the service. Then click Delete.

  5. Click Storage, and then click the iaasbistorage. Click Delete.

  6. Click Settings and then click Affinity Groups. settings

  7. Click Iaas BI Affinity Group and then click Delete.

Arrow icon used with Back to Top link More Resources

Arrow icon used with Back to Top link Top

This section is a brief overview of the hierarchy and objects that comprise the Azure storage environment.

Azure Virtual Machines use .vhd files, similar to what is used in on-premises Windows Server Hyper-V environment. The .vhd files are stored in Azure Blob Storage as page blobs.

When you create an Azure virtual machine, a .vhd is automatically created for you. You can also upload a .vhd, such as the process covered in this document. Azure uses containers to store blobs. When you are working with virtual machines, a vhds container is automatically created for you. The following diagram illustrates the Azure objects that are part of the storage environment:

windows azure storage overview

For more information on Azure storage, see How to use the Azure Blob Storage Service (http://www.windowsazure.com/en-us/develop/net/how-to-guides/blob-storage/).

Arrow icon used with Back to Top link Top

Show:
© 2014 Microsoft