Export (0) Print
Expand All

Phase 4: Configure SharePoint Servers

Updated: November 11, 2014

[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

This is the fourth phase of deploying SharePoint with SQL Server AlwaysOn in Azure, which includes creating the configuring the SharePoint server computers. You must complete this phase before moving on to Phase 5.

For the previous phase, see Phase 3: Configure SQL Server Infrastructure.

For the next phase, see Phase 5: Enable AlwaysOn Availability Groups.

For all of the phases of this deployment, see Deploying SharePoint 2013 with SQL Server AlwaysOn Availability Groups in Azure.

This deployment of SharePoint with SQL Server AlwaysOn is designed to accompany the SharePoint with SQL Server AlwaysOn Infographic and incorporate the latest recommendations.

The following figure shows the configuration resulting from the successful completion of this phase.

Phase 4: Adding SharePoint servers

Create the SharePoint virtual machines in Azure

There are four SharePoint server virtual machines. Two SharePoint Server virtual machines are for the front-end web servers and two are for administration and hosting SharePoint applications. Two SharePoint servers in each tier provide high-availability.

Use the following procedure four times to create the four SharePoint server virtual machines. Note that this procedure uses values from Table M in Phase 2: Configure Domain Controllers and Tables V (for your virtual network settings) and S (for your subnet) in Phase 1: Configure Azure.

Creating a VM from the gallery

  1. In the command bar of the Azure Management Portal, click New > Compute > Virtual Machine > From Gallery.

  2. On the Choose an image page, select Microsoft SharePoint Server 2013 Trial.

  3. Click the next arrow icon to continue.

  4. On the Virtual machine configuration page:

    • In Virtual Machine Name, type the name of this computer from Item 6, 7, 8, or 9 in Table M. This name will be displayed in the Azure Management Portal.

    • In Size, select the size for the virtual machine based on the Minimum size column of Table M. Virtual machines can be reconfigured for their size after creation. To do so, in the Azure Management Portal, click Virtual Machines, click the name of the virtual machine, and then click the Configure menu option.

    • In New User Name, type a user name for a local administrator account. You will use this name to log on to the machine when initially logging on to it through a Remote Desktop connection.

    • In New Password, enter a strong password for the local administrator account.

    • In Confirm Password, re-enter the strong password.

      Record the local administrator account name and password in a secure location for future reference.

  5. Click the next arrow to continue.

  6. On the Virtual machine configuration page:

    • In Cloud Service, select the name in the Cloud service name column of Table M for the virtual machine.

    • In Region/Affinity Group/Virtual Network, select the name corresponding to Item 1 in Table V, your newly-created virtual network.

    • In Virtual Network Subnets, select the name of your subnet corresponding to Item 1 in Table S.

    • In Storage Account, select the storage account that you created for this deployment.

    • For the virtual machine corresponding to the first SharePoint application server, in Availability Set, click Create availability set and type the name from the Availability set column of Table M for Item 6. For the virtual machine corresponding to the second SharePoint application server, select the name of the availability set created for the first SharePoint application server.

      For the virtual machine corresponding to the first SharePoint front-end web server, in Availability Set, click Create availability set and type the name from the Availability set column of Table M for Item 8. For the virtual machine corresponding to the second SharePoint front-end web server, select the name of the availability set created for the first SharePoint front-end web server.

  7. Click the next arrow to continue.

  8. On the Virtual machine configuration page, in Endpoints, click the PowerShell row and delete 5986 from the Public Port column.

    This will tell Azure to generate a random public port for remote Windows PowerShell sessions for this virtual machine. To see this port number in the Azure Management Portal, click Virtual Machines, click the name of the virtual machine, and then click the Dashboard menu option.

  9. Click the check mark to create the machine. Virtual machine creation can take several minutes.

Use the following procedure four times, one for each SharePoint server, to log on using the credentials of the local administrator account.

Logging on to a virtual machine with a Remote Desktop connection

  1. In the Azure Management Portal, in the left panel, click Virtual Machines.

  2. To connect to a VM, click Running in the Status column next to its name.

  3. In the command bar on the bottom of the page, click Connect.

  4. The Management Portal informs you the .rdp file is being retrieved. Click OK.

  5. The browser dialog appears asking, "Do you want to open or save ComputerName.rdp from manage.windowsazure.com." Click Open.

  6. In the Remote Desktop Connection dialog, click Connect.

  7. In the Windows Security dialog, click Use another account.

  8. In User name, type the name of the VM and user name of the local administrator account created with the VM (a local machine account). Use the following format:

    ComputerName\LocalAdministratorAccountName

  9. In Password, type the password for the local administrator account.

  10. Click OK.

  11. In the Remote Desktop Connection dialog, click Yes. The desktop of the new machine appears in a Remote Desktop session window.

Use the following procedure four times, one for each SharePoint server, to test connectivity to locations on your organization network.

To test connectivity

  1. At the PowerShell command prompt, use the ping command to ping names and IP addresses of resources on your organization network.

  2. At the PowerShell command prompt, use the ping command to ping the name of both domain controllers in the virtual network.

This procedure ensures that DNS name resolution is working correctly (that each virtual machine is correctly configured with on-premises DNS servers) and that packets can be sent to and from the cross-premises virtual network.

Use the following procedure four times, one for each SharePoint server, to join the SharePoint server virtual machines to the appropriate Active Directory domain with the following Windows PowerShell commands (removing the text and the brackets for the $domname variable):


$domname="[DNS domain name of the AD domain for which this computer will be a member]"
Add-Computer -DomainName $domname
Restart-Computer

After each virtual machine restarts, connect to it using the same steps as the previous Logging on to a virtual machine with a Remote Desktop connection procedure. Use the credentials (the name and password) in steps 8 and 9 corresponding to the sp_farm_db account created in Phase 4: Configure SharePoint Servers. For example, use the [ADDomainName]\sp_farm_db account name.

Next, use the following procedures to configure the SharePoint farm. For more guidance, refer to Deploying SharePoint 2013 with SQL Server AlwaysOn Availability Groups in Azure.

Configure the first server in the SharePoint farm

  1. From the desktop of the first SharePoint application server, double-click SharePoint 2013 Products Configuration Wizard. When asked to allow the program to make changes to the computer, click Yes

  2. On the Welcome to SharePoint Products page, click Next.

  3. A SharePoint Products Configuration Wizard dialog appears, warning that services (such as IIS) will be restarted or reset. Click Yes.

  4. On the Connect to a server farm page, select Create a new server farm, and then click Next.

  5. On the Specify Configuration Database Settings page:

    • In Database server, type the name of the primary SQL server.

    • In Username, type [DomainName]\sp_farm_db (created in Phase 4: Configure SharePoint Servers). Recall that the sp_farm_db account has sysadmin privileges on the SQL server.

    • In Password, type the sp_farm_db account password.

  6. Click Next.

  7. On the Specify Farm Security Settings page, type a passphrase twice. Store the passphrase in a secure location for future reference. Click Next.

  8. On the Configure SharePoint Central Administration Web Application page, click Next.

  9. The Completing the SharePoint Products Configuration Wizard page appears. Click Next.

  10. The Configuring SharePoint Products page appears. Wait until the configuration process completes, about 8 minutes.

  11. After the farm is successfully configured, click the Finish button. The new administration website starts.

  12. To start configuring the SharePoint farm, click Start the Wizard.

Perform the following procedure on the second SharePoint application server and the two front-end web servers.

Configure the other servers in the SharePoint farm

  1. From the desktop, double-click SharePoint 2013 Products Configuration Wizard. When asked to allow the program to make changes to the computer, click Yes

  2. On the Welcome to SharePoint Products page, click Next.

  3. A SharePoint Products Configuration Wizard dialog appears, warning that services (such as IIS) will be restarted or reset. Click Yes.

  4. On the Connect to a server farm page, click Connect to an existing server farm, and then click Next.

  5. On the Specify Configuration Database Settings page, type the name of the primary SQL server in Database server, and then click Retrieve Database Names.

  6. Click SharePoint_Config in the Database name list, and then click Next.

  7. On the Specify Farm Security Settings page, type the passphrase from the previous Configure the first server in the SharePoint farm procedure. Click Next.

  8. The Completing the SharePoint Products Configuration Wizard page appears. Click Next.

  9. On the Configuration Successful page, click Finish.

After concluding the initial setup, more configuration options are available. Use the documentation found in Planning for SharePoint 2013 on Azure Infrastructure Services to proceed.

Next Steps

For the next phase of the deployment, see Phase 5: Enable AlwaysOn Availability Groups.

For all of the phases of this deployment, see Deploying SharePoint 2013 with SQL Server AlwaysOn Availability Groups in Azure.

Community Additions

ADD
Show:
© 2014 Microsoft