Hands-on Lab: Build a SharePoint Dev/Test Farm in the Cloud using Windows Azure Infrastructure ServicesWindows Azure Infrastructure Services provides cloud-based storage, virtual networks and virtual machines that can be provisioned on-demand to support lab, pilot or production application workloads.

In this Hands-on Lab, you’ll build a functional Dev/Test lab environment for SharePoint Server 2013 that consists of three virtual machines on a common virtual network running in Windows Azure Infrastructure Services.

You’ll be leveraging our Windows Azure FREE Trial Subscription program to build a free cloud-based lab environment for SharePoint Server 2013.

Lab RequirementsThe following components are required to successfully complete this Hands-on Lab:

A modern web-browser with HTML5 and Javascript enabled Remote Desktop Client connection software Internet connectivity

1 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

In addition, this hands-on lab guide assumes that lab participants are comfortable with performing the steps involved in implementing Windows Server 2012 and Active Directory in an on-premises datacenter environment. But, if you have questions along the way, feel free to ask today’s presenter for assistance!

Lab ConventionsIn this lab, we’ll be using a naming convention of XXXlabYYY01, where XXX will be replaced with your unique initials and YYY will be replaced with an abbreviation representing the function of a virtual machine or Windows Azure configuration component (ad, db or app).

Let’s Get Started!In this step-by-step guide, you will learn how to:

1. Get Started with Windows Azure Infrastructure Services2. Register a DNS Server in Windows Azure3. Define a Virtual Network in Windows Azure4. Configure Windows Server Active Directory in a Windows Azure VM5. Configure SQL Server 2012 in a Windows Azure VM6. Configure SharePoint Server 2013 in a Windows Azure VM7. Challenge Exercise: Scripted Provisioning with Windows PowerShell

Estimated time to complete: 1 hour, 45 minutes

Exercise 1: Get Started with Windows Azure Infrastructure ServicesIn this exercise, you will activate a free Windows Azure Trial Subscription and then setup two components that will be needed for the other exercises in this lab: a Windows Azure Affinity Group and a Windows Azure Storage Account.

1) Sign-up for your FREE Windows Azure Trial Account. Sign-up for a FREE trial of Windows Azure at http://aka.ms/iaas so that you can follow along with the steps in this Hands-on Lab. When signing up for a Free Trial subscription, you will be prompted to login with Microsoft Account (formerly Windows Live ID) credentials. If you do not have valid Microsoft Account credentials, you may create new credentials at https://signup.live.com. Note: During the Free Trial sign-up process, you will be asked for credit card information to confirm that you are a legitimate free trial subscriber. Your credit card information is only used to confirm your identity and you will NOT be charged for any Windows Azure services unless you explicitly

2 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

convert your trial subscription to a paid subscription at a later date.

2) Login to the Windows Azure Management Portal. Login to the web-based Windows Azure Management Portal at http://manage.windowsazure.com with the same logon credentials you used to sign-up for the FREE Trial above.

Once you’ve logged in, you should see the main Windows Azure Management portal dashboard.

On the blue side navigation bar of the Windows Azure Management Portal, you’ll find the options for managing Virtual Machines, Virtual Networks, Storage and Settings in the cloud. These are the items we’ll be primarily working with in this hands-on lab.

You may need to scroll the blue side navigation bar up and down to see all of the options.

3) Define a new Windows Azure Affinity Group. Affinity Groups in Windows Azure are used to group your cloud-based services together, such as Virtual Machines, Virtual Networks and Storage, in order to achieve optimal performance. When you use an affinity group, Windows Azure will keep all services that belong to your affinity group running within the same data center as close as possible to each other to reduce latency and increase performance.

a) Create a new Affinity Group by selecting Settings from the blue side navigation bar in the Windows Azure Management Portal. You may need to scroll the blue side navigation bar down to see this selection.

b) On the Settings page, select the Affinity Groups tab on the top navigation bar (you will probably have to scroll down; scroll bar is hidden and can be found by hovering over the right part of the blue NAV pane on the left.

c) Click the +ADD button on the bottom navigation bar.

d) On the Create Affinity Group form, enter the following details: Name: Enter a unique name for your new Affinity Group, such as XXXlab01 (where XXX is replaced with your initials) Region: Select the “East US” datacenter sub-region. Click the button to create a new Affinity Group.

4) Create a new Windows Azure Storage Account. Virtual Machines that are provisioned in Windows Azure are stored in the world-wide cloud-based Windows Azure Storage service. In terms of high availability, the Storage service provides built-in storage replication capability – where every VM is replicated to three separate locations within the Windows Azure data center region you select. In addition, Windows Azure Storage provides a geo-

3 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

replication feature for also replicating your VMs to a remote data center region.

a) Create a new Storage account by clicking the +NEW button on the bottom toolbar in the Windows Azure Management Portal and then click Data Services | Storage | Quick Create.

b) Complete the following fields for creating your Storage account:

URL: Enter a unique name for your new storage account, such as XXXlabstor01 (where XXX is replaced with your initials) Region/Affinity Group: Select the Affinity Group you created in Step 3 above. Enable Geo-Replication: By default, this option is selected. Leave the default option in place. Click the CREATE STORAGE ACCOUNT button to create your new Windows Azure Storage account.

Exercise 2: Register a DNS Server in Windows AzureRegister the internal IP address that our domain controller VM will be using for Active Directory-integrated Dynamic DNS services by performing the following steps:

1) Sign in at the Windows Azure Management Portal with the logon credentials used when you signed up for your Free Windows Azure Trial.

2) Select Networks located on the side navigation panel on the Windows Azure Management Portal page.

3) Click the +NEW button located on the bottom navigation bar and click Networks | Virtual Network | Register DNS Server.

4) Complete the DNS Server fields as follows: NAME: XXXlabdns01

DNS Server IP Address: 10.0.0.4

5) Click the REGISTER DNS SERVER button.

Exercise 3: Define a Virtual Network in Windows AzureDefine a common virtual network in Windows Azure for running Active Directory, Database and SharePoint virtual machines by performing the following steps:

4 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

1) Sign in at the Windows Azure Management Portal with the logon credentials used when you signed up for your Free Windows Azure Trial.

2) Select Networks located on the side navigation panel on the Windows Azure Management Portal page.

3) Click the +NEW button located on the bottom navigation bar and select Networks | Virtual Network | Quick Create.

4) Complete the Virtual Network fields as follows: NAME: XXXlabnet01

Address Space: 10.---.---.---

Maximum VM Count: 4096 [CIDR: /20]

Affinity Group: Select the Affinity Group defined in Exercise 1 above.

DNS Server: Select XXXlabdns01 – the DNS Server registered in Exercise 2 above.

5) Click the CREATE A VIRTUAL NETWORK button.

Exercise 4: Configure Windows Server Active Directory in a Windows Azure VMProvision a new Windows Azure VM to run a Windows Server Active Directory domain controller in a new Active Directory forest by performing the following steps:

1) Sign in at the Windows Azure Management Portal with the logon credentials used when you signed up for your Free Windows Azure Trial.

2) Select Virtual Machines located on the side navigation panel on the Windows Azure Management Portal page.

3) Click the +NEW button located on the bottom navigation bar and select Compute | Virtual Machines | From Gallery.

4) In the Virtual Machine Operating System Selection list, select Windows Server 2012 Datacenter and click the button.

5) On the Virtual Machine Configuration page, complete the fields as follows: Version Release Date: Select the latest version release date to build a new VM with the latest OS updates applied.

5 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

Virtual Machine Name: XXXlabad01 Size: Small (1 core, 1.75GB Memory)

New User Name: Choose a secure local Administrator user account to provision.

New Password and Confirm Password fields: Choose and confirm a new local Administrator password. (guru1309) Click the button to continue. Note: It is suggested to use secure passwords for Administrator users and service accounts, as Windows Azure virtual machines could be accessible from the Internet knowing just their DNS. You can also read this document on the Microsoft Security website that will help you select a secure password: http://www.microsoft.com/security/online-privacy/passwords-create.aspx.

6) On the Virtual Machine Configuration page, complete the fields as follows: Cloud Service: Create a new cloud service

Cloud Service DNS Name: XXXlabad.cloudapp.net

Region/Affinity Group/Virtual Network: Select XXXlabnet01 – the Virtual Network defined in Exercise 3 above.

Virtual Network Subnets: Select Subnet-1 (10.0.0.0/23) Storage Account: Select the Storage Account defined in Exercise 1 above. Availability Set: Create an availability set Availability Set Name: XXXlabad Click the button to continue.

7) On the Virtual Machine Configuration - Endpoints page, click the button to accept the default firewall endpoint values and begin provisioning the new virtual machine. As the new virtual machine is being provisioned, you will see the Status column on the Virtual Machines page of the Windows Azure Management Portal cycle through several values including Stopped, Stopped (Provisioning), and Running (Provisioning). When provisioning for this new Virtual Machine is completed, the Status column will display a value of Running and you may continue with the next step in this guide.

8) After the new virtual machine has finished provisioning, click on the name (XXXlabad01) of the new Virtual Machine displayed on the Virtual Machines page of the Windows Azure Management Portal.

6 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

9) On the virtual machine Dashboard page for XXXlabad01, make note of the Internal IP Address displayed on this page located on the right-side of the page. This IP address should be listed as 10.0.0.4. If a different internal IP address is displayed, the virtual network and/or virtual machine configuration was not completed correctly. In this case, click the DELETE button located on the bottom toolbar of the virtual machine details page for XXXlabad01, and go back to Exercise 2 and Exercise 3 to confirm that all steps were completed correctly.

10) On the virtual machine Dashboard page for XXXlabad01, click the Attach button located on the bottom navigation toolbar and select Attach Empty Disk. Complete the following fields on the Attach an empty disk to the virtual machine form: File Name: XXXlabad01-data01

Size: 10 GB

Host Cache Preference: None Click the button to create and attach the new virtual hard disk to virtual machine XXXlabad01.

11) On the virtual machine Dashboard page for XXXlabad01, click the Connect button located on the bottom navigation toolbar and click the Open button to launch a Remote Desktop Connection to the console of this virtual machine. Logon at the console of your virtual machine with the local Administrator credentials defined in Step 5 above. Accept authorization message(s)

12) From the Remote Desktop console of XXXlabad01, create a new partition on the additional data disk attached above in Step 10 and format this partition as a new F: NTFS volume. This volume will be used for NTDS DIT database, log and SYSVOL folder locations. Step-By-Step: Once inside Server Manager, go to Tools (upper right corner menu) then select Computer Management. Inside Computer Management select Disk Management. An “Initialize Disk” window will pop up, make sure the new disk is selected and click OK. Right click unallocated space on Disk 2 and select “New Simple Volume…” Click Next: then Next for the Specify Volume Size. The drive letter should be preconfigured to “F”, click Next: Change the Volume Label to DATA and click Next: Click Finish. (it may take a bit to see the drive in computer explorer). Once you see the new F: drive in the upper volume window you can close computer management.

13) Using the Server Manager tool, install Active Directory Domain Services Step-by-Step:

a) Active Directory domain services is installed by simply adding the role: b) In Server Manager, click Manage (upper right corner menu) then click Add Roles and

Features to start the Add Roles & Features Wizard. c) On the Before you begin page, click Next. d) On the Select installation type page, click Role-based or feature-based installation

and then click Next.e) The current server should already be selected, click Next.f) On the Select server roles page, click Active Directory Domain Services, then on the

Add Roles and Features Wizard dialog box, click Add Features, and then click Next. g) On the Select features page, click Next.

7 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

h) On the Active Directory Domain Services page, click Next.i) On the Confirm installation selections page, Turn on the "Restart the destination

server automatically if required" check box. On the restart popup alert, select Yes. Then click Install. It could take a few minutes to do the install.

j) Once installation finishes, Click Close. We will configure AD in the next step.

14) Promote this server to a domain controller in a new forest with the following parameters: Active Directory Forest name: contoso.com Volume Location for NTDS database, log and SYSVOL folders: F:

Step-By-Step:

a) Server Manger – Flag (upper right corner near Manage) – Post deployment configuration – Click “Promote this server to a domain controller”

b) On the Deployment Configuration page click Add a new forest then type contoso.com for the Root domain name. then click Next

c) On the Domain Controller options page type a secure password and confirm password (you will have to remember this) then click Next.

d) On the DNS page, click Next (you can ignore the warning)e) On the Additional Options page, click Nextf) On the Paths page, change the C:\... paths to F:\... then click Nextg) On the Review Options page click Nexth) On the Prerequisites Check page, review issues then click install. You can ignore the

warnings; the last line should say all prerequisites checks passed successfully.i) This will take some time to complete and will reboot your server once complete

15) After Active Directory has been installed, create the following user accounts that will be used when installing and configuring SharePoint Server 2013 later in this hands-on lab:

CONTOSO\sp_farm – SharePoint Farm Data Access Account

CONTOSO\sp_serviceapps – SharePoint Farm Service Applications Account Step-By-Step:

a) Login to server (Connect) b) Server Manager – Tools – Active Directory Users and Computersc) Create sp_farm: Expand contoso.com; Right-Click Users Select New then User

i) On the New Object – User page: (1) Last name: sp_farm(2) User logon name: sp_farm(3) Full name: SharePoint Farm Data Access Account

ii) Click Nextiii) Enter a secure password in password and confirm password fieldsiv) Turn off checkbox User must change password at next logon v) Click Next; then Finish

8 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

d) Create sp_serviceapps: Right-Click Users (under contoso.com) Select New then Useri) On the New Object – User page:

(1) Last name: sp_serviceapps(2) User logon name: sp_serviceapps(3) Full name: SharePoint Farm Service Applications Account

ii) Click Nextiii) Enter a secure password in password and confirm password fieldsiv) Turn off checkbox User must change password at next logon v) Click Next; then Finishvi)

The configuration for this virtual machine is now complete, and you may continue with the next exercise in this hands-on lab guide.

Exercise 5: Configure SQL Server 2012 in a Windows Azure VMProvision a new Windows Azure VM to run SQL Server 2012 by performing the following steps:

1) Sign in at the Windows Azure Management Portal with the logon credentials used when you signed up for your Free Windows Azure Trial.

2) Select Virtual Machines located on the side navigation panel on the Windows Azure Management Portal page.

3) Click the +NEW button located on the bottom navigation bar and select Compute | Virtual Machines | From Gallery.

4) In the Virtual Machine Operating System Selection list, select SQL Server 2012 SP1 Enterprise on WS 2012 and click the button.

5) On the Virtual Machine Configuration page, complete the fields as follows:

Version Release Date: Select the latest version release date to build a new VM with the latest OS updates applied. Virtual Machine Name: XXXlabdb01

Size: Large (4 cores, 7GB Memory) New User Name: Choose a secure local Administrator user account to provision.

New Password and Confirm Password fields: Choose and confirm a new local Administrator password.

9 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

Click the button to continue.

6) On the Virtual Machine Configuration page, complete the fields as follows: Cloud Service: Create a new cloud service

Cloud Service DNS Name: XXXlabfarm.cloudapp.net

Region/Affinity Group/Virtual Network: Select XXXlabnet01 – the Virtual Network defined in Exercise 3 above.

Virtual Network Subnets: Select Subnet-1 (10.0.0.0/23) Storage Account: Select the Storage Account defined in Exercise 1 above.

Availability Set: Create an availability set Availability Set Name: XXXlabdb Click the button to continue.

7) On the Virtual Machine Configuration - Endpoints page, click the button to accept the default firewall endpoint values and begin provisioning the new virtual machine. As the new virtual machine is being provisioned, you will see the Status column on the Virtual Machines page of the Windows Azure Management Portal cycle through several values including Stopped, Stopped (Provisioning), Starting, and Running (Provisioning). This will take several minutes. When provisioning for this new Virtual Machine is completed, the Status column will display a value of Running and you may continue with the next step in this guide.

8) After the new virtual machine has finished provisioning, click on the name (XXXlabdb01) of the new Virtual Machine displayed on the Virtual Machines page of the Windows Azure Management Portal.

9) On the virtual machine Dashboard page for XXXlabdb01, make note of the Internal IP Address displayed on this page. This IP address should be listed as 10.0.0.5. If a different internal IP address is displayed, the virtual network and/or virtual machine configuration was not completed correctly. In this case, click the DELETE button located on the bottom toolbar of the virtual machine details page for XXXlabdb01, and go back to Exercise 2 and Exercise 3 to confirm that all steps were completed correctly.

16) On the virtual machine Dashboard page for XXXlabdb01, click the Attach button located on the bottom navigation toolbar and select Attach Empty Disk. Complete the following fields on the Attach an empty disk to the virtual machine form: File Name: XXXlabdb01-data01

10 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

Size: 50 GB Host Cache Preference: None

Click the button to create and attach the new virtual hard disk to virtual machine XXXlabdb01.

10) On the virtual machine Dashboard page for XXXlabdb01, click the Connect button located on the bottom navigation toolbar and click the Open button to launch a Remote Desktop Connection to the console of this virtual machine. Logon at the console of your virtual machine with the local Administrator credentials defined in Step 5 above.

11) From the Remote Desktop console of XXXlabdb01, create a new partition on the additional data disk attached above in Step 10 and format this partition as a new F: NTFS volume. After formatting this new volume, create the following folders: a) Create F:\MSSQL folder

b) Create F:\MSSQL\DATA folder

c) Create F:\MSSQL\LOGS folder

d) Create F:\MSSQL\BACKUP folder

Step-By-Step: Once inside Server Manager, go to Tools (upper right corner menu) then select Computer Management. Inside Computer Management select Disk Management. An “Initialize Disk” window will pop up, make sure the new disk is selected and click OK. Right click unallocated space on Disk 2 and select “New Simple Volume…” Click Next: then Next for the Specify Volume Size. The drive letter should be preconfigured to “F”, click Next: Change the Volume Label to DATA and click Next: Click Finish. Once you see the new F: drive in the upper volume window you can close the computer management window and continue.

Step-By-Step: Click on the Folder on the task bar to open Computer. Double-Click Data (F:) Click Home | New Folder type MSSQL press Enter. Press Enter again to drill down to the MSSQL folder then repeat the process to create the remaining folders (DATA; LOGS; BACKUP)

12) Open SQL Server Management Studio from the Start Screen and update default folder locations to the F: volume. Tip! On the Windows Start Screen, you can quickly find the application tile for SQL Server Management Studio beginning to type the name of this application to automatically search for matching tiles. a) Connect to the SQL Server 2012 default instance using your Windows Account.

11 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

b) Now, you will update the database's default locations for DATA, LOGS and BACKUP folders. To do this, right click on your SQL Server instance and select Properties.

c) Select Database Settings from the left side pane.

d) Locate the Database default locations section and update the default values for each path to point to the new folder paths defined above in Step 11. Click OK

e) Right-Click XXXlabdb01 and select Restart; if you go back into properties; you should see the change took place.

f) Close SQL Server Management Studio.

13) In order to allow SharePoint to connect to the SQL Server, you will need to add an Inbound Rule for the SQL Server requests in the Windows Firewall. To do this, open Windows Firewall with Advanced Security from Server Manager (Tools menu)

a) Select Inbound Rules node, right-click it and select New Rule to open the New Inbound Rule Wizard.

b) In the Rule Type page, select Port and click Next.

c) In Protocols and Ports page, leave TCP selected, select Specific local ports, and set its value to 1433. Click Next to continue.

d) In the Action page, make sure that Allow the connection is selected and click Next.

e) In the Profile page, leave the default values and click Next.

f) In the Name page, set the Inbound Rule's Name to SQLServerRule and click Finish

g) Close Windows Firewall with Advanced Security window.

14) Using the Server Manager tool, join this server to the contoso.com domain and restart the server to complete the domain join operation. Step-By-Step: Server Manager | Local Server | WORKGROUP | Change… | Domain | contoso.com | OK. Enter your domain credentials (CONTOSO\YourUserName) click OK then on Welcome to consoto.com click OK; on restart popup click OK; Click Close on System Properties then click Restart Now on the popup.

15) After the server restarts, connect again via Remote Desktop to the server’s console and login with the local Administrator credentials defined above in Step 5.

16) Open SQL Server Management Studio from the Start Screen type SQL click SQL Server Management Studio and then Connect (default credentials). Then we need to add the CONTOSO\YourUserName (defined when setting up XXXLabad01) user to SQL Server with the Sysadmin server role selected.

12 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

a) Expand Security folder within the SQL Server instance. Right-click Logins folder and select New Login.

b) In the General section, set the Login name to CONTOSO\YourUserName, and select the Windows Authentication option. Click Search Click Locations… Enter your domain credentials (credentials you defined ealier) expand entire directory, click contoso.com click OK enter the username in the “object name” field click Check Names if the name resolves correctly, click OK.

c) Click Server Roles on the left pane. Select the checkbox for the Sysadmin server role.

d) Click the OK button and then close SQL Server Management Studio.

The configuration for this virtual machine is now complete, and you may continue with the next exercise in this hands-on lab guide.

Exercise 6: Configure SharePoint Server 2013 in a Windows Azure VMProvision a new Windows Azure VM to run SharePoint Server 2013 by performing the following steps:

1) Sign in at the Windows Azure Management Portal with the logon credentials used when you signed up for your Free Windows Azure Trial.

2) Select Virtual Machines located on the side navigation panel on the Windows Azure Management Portal page.

3) Click the +NEW button located on the bottom navigation bar and select Compute | Virtual Machines | From Gallery.

4) In the Virtual Machine Operating System Selection list, select SharePoint Server 2013 Trial and click the button.

5) On the Virtual Machine Configuration page, complete the fields as follows: Virtual Machine Name: XXXlabapp01 Size: Extra Large (8 cores, 14GB Memory)

New User Name: Choose a secure local Administrator user account to provision.

New Password and Confirm Password fields: Choose and confirm a new local Administrator password. Click the button to continue.

13 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

6) On the Virtual Machine Configuration page, complete the fields as follows: Cloud Service: XXXlabfarm.cloudapp.net (Select the existing Cloud Service provisioned in Exercise 5) Region/Affinity Group/Virtual Network: Select XXXlabnet01 – the Virtual Network defined in Exercise 3 above. Virtual Network Subnets: Select Subnet-1 (10.0.0.0/23) Storage Account: Select the Storage Account defined in Exercise 1 above. Availability Set: Create an availability set Availability Set Name: XXXlabapp Click the button to continue.

7) On the Virtual Machine Configuration - Endpoints page, add an additional firewall endpoint for web (HTTP) network traffic by completing the following fields: Name: WebHTTP Protocol: TCP Public Port: 80 Private Port: 80 Click the button to begin provisioning the new virtual machine. As the new virtual machine is being provisioned, you will see the Status column on the Virtual Machines page of the Windows Azure Management Portal cycle through several values including Stopped, Stopped (Provisioning), and Running (Provisioning). When provisioning for this new Virtual Machine is completed, the Status column will display a value of Running and you may continue with the next step in this guide.

8) After the new virtual machine has finished provisioning, click on the name (XXXlabapp01) of the new Virtual Machine displayed on the Virtual Machines page of the Windows Azure Management Portal.

9) On the virtual machine Dashboard page for XXXlabapp01, make note of the Internal IP Address displayed on this page. This IP address should be listed as 10.0.0.6. If a different internal IP address is displayed, the virtual network and/or virtual machine configuration was not completed correctly. In this case, click the DELETE button located on the bottom toolbar of the virtual machine details page for XXXlabapp01, and go back to Exercise 2 and Exercise 3 to confirm that all steps were completed correctly.

14 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

10) On the virtual machine Dashboard page for XXXlabapp01, click the Connect button located on the bottom navigation toolbar and click the Open button to launch a Remote Desktop Connection to the console of this virtual machine. Logon at the console of your virtual machine with the local Administrator credentials defined in Step 5 above.

11) In the Server Manager tool, click on Local Server in the left navigation pane and click on the Workgroup option. Join this server to the contoso.com domain and restart the server to complete the domain join operation. Step-By-Step: Server Manager | Local Server | WORKGROUP | Change… | Domain | contoso.com | OK. Enter your domain credentials (CONTOSO\YourUserName) click OK then on Welcome to consoto.com click OK; on restart popup click OK; Click Close on System Properties then click Restart Now on the popup.

12) After the server restarts, re-establish a Remote Desktop connection to the server and logon with the CONTOSO\YourUserName domain user credentials defined earlier in Exercise 4.

13) In the Server Manager tool, click on Local Server in the left navigation pane and select IE Enhanced Security Configuration. Turn off enhanced security for Administrators and click the OK button. Note: Modifying Internet Explorer Enhanced Security configurations is not good practice for production environments and is only for the purpose of this particular hands-on lab guide.

14) On the Desktop, double-click on the SharePoint 2013 Products Configuration Wizard shortcut to launch the configuration wizard. Click the Next button to continue. If prompted to start or reset services, click the Yes button.

15) In the SharePoint Products Configuration Wizard, when prompted on the Connect to server farm dialog, select the option to Create a new server farm.

16) On the Specify Configuration Database Settings, specify the following values for each field: Database Server: XXXlabdb01

Username: CONTOSO\sp_farm

Password: Type the password specified when the sp_farm domain user account was created earlier in Exercise 4.

17) Click the Next > button. On the Specify Farm Security Settings screen enter a passphrase and then enter it again to confirm. You can use whatever you like but please remember what you used. Click Next. Accept all other default values in the SharePoint Products Configuration Wizard. After some time, you should get a Configuration Successful Screen. Click the Finish button to complete the wizard. Note that SharePoint may require many minutes to complete the initial provisioning process.

18) The SharePoint 2013 Central Administration web page should launch automatically. You can skip the IE configuration for now. You do not need to enroll in customer experience. When prompted,

15 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

click the Start the Wizard button to begin the Initial Farm Configuration Wizard.

19) When prompted for Service Account, type the CONTOSO\sp_serviceapps domain username and password specified when this account was created earlier in Exercise 4.

20) Accept all other default values, scroll down and click the Next > button to continue.

21) On the Create a Site Collection page, create a new top-level Intranet site collection using the following field values: Title and Description: Enter your preferred Title and Description for the new site collection

URL: Select the root URL path – http://XXXlabapp01/ (from the dropdown list)

Select experience version: 2013

Select a template: Publishing | Publishing Portal Click the OK button to provision a new top-level Intranet site collection. After the new top-level Intranet site collection is provisioned, test navigating to the URL for this site collection from within the Remote Desktop session to the server. You can do this by simply right-clicking on the Site URL: link on the final page of the Farm Configuration Wizard and select Open in new Window. Click Finish on the Farm Configuration Wizard.

22) On the SharePoint 2013 Central Administration site, configure a Public URL alternate access mapping for accessing the new top-level Intranet site collection from the Internet. a) On the Central Administration site home page, click the Configure alternate access mappings

link.

b) On the Alternate Access Mappings page, click the Edit Public URLs link.

c) On the Edit Public Zone URLs page, select and specify the following values: Alternate Access Mapping Collection: SharePoint – 80 (click No Selection to change)

Internet: http://XXXlabfarm.cloudapp.net Click the Save button to complete the Alternate Access Mapping configuration.

23) Close the Remote Desktop session to the server.

24) Test browsing to the following public URL to confirm that you are able to access the Intranet site collection that is configured on SharePoint: URL: http://XXXlabfarm.cloudapp.net

16 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

Credentials: Contoso\YourUserName (defined in Exercise 4)

If you are unable to successfully browse to this SharePoint site collection, carefully review Step 6, Step 7 and Step 22 to ensure that you have completed the steps correctly.

The configuration for this virtual machine is now complete, and you may continue with the next exercise in this hands-on lab guide.

Challenge Exercise: Scripted Provisioning via Windows PowerShellIn this exercise, you will leverage a Windows PowerShell script to automate the provisioning of a SharePoint Dev/Test Farm on Windows Azure Infrastructure Services.

Note: This exercise will require a Windows 7 or later PC to complete. If you are not currently using Windows 7 or later, you may complete this challenge exercise by connecting to the remote desktop of the XXXlabad01 virtual machine provisioned earlier in this hands-on lab. If you will be using this virtual machine instead of your local PC for this exercise, you will need to turn off IE Enhanced Security prior to attempting to download the Windows Azure PowerShell Module.

1. Download and install the Windows Azure PowerShell Module from the following link location: http://www.windowsazure.com/en-us/downloads/#cmd-line-tools

2. Restart your PC after installing the Windows Azure PowerShell Module.

3. Download and extract the PowerShell Script files to the Documents folder on your local PC from the following link location: http://aka.ms/ITCamp-SP13Cloud

4. Launch PowerShell ISE (Integrated Scripting Editor) on your local PC.

5. In PowerShell ISE, open the .ps1 script file that was extracted in Step 1 to your local Documents folder.

6. Review the comments in the script.

7. Test each block of code individually by selecting each code block and pressing F8 to run only the highlighted code block.

17 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

Lab Completed. Shut down your VMs.Your functional SharePoint lab environment is now complete, but if you’re like me, you won’t be using this lab environment 24x7 around-the-clock. As long as the virtual machines are running, they will continue to accumulate compute hours against your Windows Azure subscription.

To preserve your compute hours for productive lab work, be sure to shut down each VM from the Windows Azure Management Portal when not in use. (Virtual Machines – Click on the status of the machine, then click Shut Down). After each VM is successfully shutdown, the status of each VM will be listed in the portal as “Stopped (Deallocated)” and compute charges will not accumulate for VMs in this state. You should shutdown in the following sequence: XXLabApp01, XXXLabDB01, XXXLabAD01. You may get a message: “If you continue, the IP addresses that were assigned to this virtual machine will be released. Are you sure you want to shut down virtual machine that the IP addresses assigned to the machine will be released.” This is fine. A new IP address will be assigned when it is brought back online. Also, you should make sure each machine shuts down completely before you start the shutdown of the next.

When you start the machines up again (Virtual Machines – Click on the status of the machine, then click Start), you will want to start them in reverse order. Start XXXLabAD01, then XXXLabDB01, then finally XXLabApp01. You should make sure that each machine is up and running before you start the next.

NOTE: It is important to shut down the VMs from the Windows Azure Management Portal to properly de-allocate compute resources and prevent compute charges from accumulating. If you shutdown VMs from within the Guest OS, the VMs will be placed in a “Stopped” state where compute resources are not de-allocated and compute charges in this state will still apply.

18 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m

Additional ResourcesCongratulations! You’ve completed this Hands-on Lab for Building a SharePoint Dev/Test Farm in the Cloud using Windows Azure Infrastructure Services.

If you enjoyed this Hands-On Lab, be sure to check-out our full set of Cloud Step-By-Step Guides for building other common hybrid cloud scenarios at:

Cloud Labs Step-by-Step Guides http://aka.ms/CloudLab

Guided Hands-On Lab: Build a Cross-Premises Site-to-Site VPN http://aka.ms/VNetCloudLab

Guided Hands-On Lab: Migrate VMs from VMware to Windows Azure http://aka.ms/VMWCloudLab

Guided Hands-On Lab: Migrate VMs from Amazon AWS to Windows Azure http://aka.ms/AWSCloudLab

Guided Hands-On Lab: Orchestrate Private Cloud Failover with Windows Azure Hyper-V Recovery Manager http://aka.ms/HVMCloudLab

Build Your Private Cloud in a Month http://aka.ms/BuildYourCloud

19 | P a g e B u i l d a S h a r e P o i n t D e v / T e s t F a r m