This section describes how to build a set of Virtual Machines that will later become the SharePoint 2013 servers. We create these SharePoint servers in the Microsoft Azure Virtual Network we created in section III. Most of these steps, however, are the same if you are building a SharePoint farm on your own hardware.
Below are links to all the sections of this Guide.
|
XIV. Configure Business Intelligence
XV. Turn Windows Firewalls Back On for All Servers
|
Who Should Read This Section
This section (Section V) describes how to build a set of Virtual Machines to be your SharePoint 2013 Servers in the Microsoft Azure Virtual Network you created in step III – B.If you obtain your servers in some other way (e.g. physical hardware or provisioned from your corporate data center) you may skip this section and go directly to section VI – A Configure OUs and Group Policy Objects.
This section focuses on provisioning the Virtual Machines in preparation for installation of SharePoint. The actual installation of the SharePoint software comes later, in sections VIII and IX.
A. Create the SharePoint Central Admin Server MBP-CA
This section describes how to provision the SharePoint Central Admin Server -- MBP-CA in this case -- attach a data disk to it, and join it to the domain.
1. Add a new VM in Microsoft Azure for MBP-CA
Creating the VMs for the SharePoint servers is very similar to creating the VM for SQL server as described in section IV – A – 1. As when creating the VM for SQL, take care to join this VM to the mbp.com domain, attach the VM to the Virtual Network mbp-net and assign the Static Private IP Address planned (10.0.0.6 and 10.0.0.7 in this case.)
1. From the Microsoft Azure Portal (portal.azure.com), click the + NEW button in the upper left.
Azure displays the “Create” blade.
2. From the “Create” blade, select Compute.
Azure displays the “Compute” blade.
3. From the “Compute” blade, select Windows Server 2012 R2 Datacenter.
Azure displays the “Create VM” blade.
4. From the “Create VM” blade, enter the Host Name MBP-CA, the user name mbpadmin, and the password as per our plan from section II – D – 4 (Detailed Physical Architecture)
Field
|
Value
|
Description
|
Host
Name
|
MBP-CA
|
From
Plan
|
User
Name
|
mbpadmin
|
Local
machine admin account
|
Password
|
$hareP0int
|
Suitably
strong password
|
5. From the “Create VM” blade, click PRICING TIER
6. From the “Choose your pricing tier” blade, select View All
7. Select A5 Standard or whatever VM size is appropriate based on your performance and capacity planning.
8. From the bottom of the “Choose your pricing tier” blade, click Select
Azure closes the “Choose your pricing” blade. The “Create VM” blade displays the selected pricing tier.
9. From the “Create VM” blade, click OPTIONAL CONFIGURATION.
Azure displays the “Optional config” blade
10. From the “Optional config” blade, click OS SETTINGS
11. From the “OS Settings” blade, click DOMAIN JOIN
Azure displays the “Domain join” blade
12. Specify the domain you created when you created the AD-DC VM in step III - 3 - B (mbp.com in this case)
13. In the User Name and Password fields, enter the credentials for the domain administrator account we planned for in section II – A (Plan Service Accounts) (mbp\mbpadmin in this case).
Domain
|
mbp.com
|
User Name
|
mbp\mbpadmin
|
Password
|
$hareP0int
|
14. At the bottom of the “Domain join” blade, click OK
15. At the bottom of the “OS Settings” blade, click OK
16. From the “Optional config” blade, click NETWORK
Azure displays the “Network” blade. Notice that Azure has defaulted to a Virtual Network with the same name as the Host Name. We must change this default so this server is on our mbp-net virtual network and had the Private Static IP address we planned.
17. From the “Network” blade, click VIRTUAL NETWORK
Azure opens two blades: the “Virtual Network” blade and the “Create a virtual network” blade.
18. From the “Virtual Network” blade, under “Use an existing virtual network”, select mbp-net, the network we created in step III – B – 1.
Note that on the “Network” blade, the DOMAIN NAME setting contains a default value of mbp-ca.cloudapp.net. We can keep this default “domain name” because it is really just the name of by which Azure knows this Virtual Machine in the cloudapp.net name space. This is not the same thing as our MBP.COM domain name.
19. From the “Network” blade, select IP ADDRESS
Azure displays the “IP address” blade
20. From the “IP address” blade, under the “Private IP address” label, change the “IP address assignment” from DHCP to Static.
21. In the “IP Address” field, enter the Static IPV4 address we planned for the Central Admin server back in section II – D – 4 (10.0.0.6 in this case).
22. At the bottom of the “IP address” blade, click OK
23. At the bottom of the “Network” blade, click OK
24. From the “Optional config” blade, click STORAGE ACCOUNT
Select to use existing storage account rather than creating a new one (optional).
25. At the bottom of the “Optional config” blade, click OK
26. From the “Create VM” blade, click RESOURCE GROUP
Azure displays the “Resource group” blade.
27. From the “Resource group” blade, under “Use an existing group”, select the resource group we created in section II, MBPI in this case.
28. At the bottom of the “Create VM” blade, click Create
Azure displays the portal home page with an animated graphic and the message “Creating Windows Server 2012 R2 Datacenter” while it provisions the new machine.
29. When the Azure Management Portal displays the new VM in status "Running" you may proceed to the next step.
2. Attach Additional disk to MBP-CA
Attach an additional disk to the Virtual Machine for the data volume. Make sure Host Caching = NONE on the new disk.
1. In the Azure management portal, select the VM you just created (MBP-CA), and, at the top of the “MBP-CA Virtual machine” screen, click Settings.
Azure displays the “Settings” blade.
2. From the “Settings” blade, click Disks.
Azure displays the “Disks” blade
3. At the top of the “Disks” blade, click the button marked Attach New…
Azure displays the “Attach a new disk” blade
4. From the “Attach a new disk” blade, type the size of hard disk (in GB) you planned, in this case 100 GB. Make sure to keep the Host Caching = NONE
5. At the bottom of the “Attach a new disk” blade, click OK
Azure will close the “Attach a new disk” blade while it provisions the new data disk.
6. At first, the Azure portal displays “No disks found” under DATA DISKS on the “Disks” blade. Wait a minute for the “Disks” blade to display the new data disk. Then you may proceed to the next step.
Now connect to the new VM and configure the new disk as drive F:
7. In the Azure management portal, select the VM you just created (MBP-CA), and, on the control bar at the top of the MBP-CA Virtual machine blade, click the Connect button.
8. Your browser will prompt to save or open the MBP-CA.rdp remote desktop connection. Save this MBP-CA.rdp file to your desktop for future use. Then open the RDP file to connect to the server.
9. Remote Desktop will warn you that, “The publisher of this remote connection can’t be identified”. Click Connect.
10. Windows Security will prompt you for credentials to login to MBP-CA. Click Use another account. Since we configured the VM to be part of the mbp.com domain in the OS Settings, you must login using the account we specified: in this case the MBP domain admin account mbp\mbpadmin.
11. If Remote Desktop displays a certificate error, click Yes
Remote desktop displays the MBP-CA Windows desktop.
Windows displays the Server Manager Dashboard
12. From the Server Manager Dashboard, click File and Storage Services --> Disks
13. On the DISKS list, right-click on the new disk Number 2 (will show Partition = Unknown) and click Initialize, and click Yes to confirm the operation.
14. After initialization is complete, right-click the disk, click New Volume…
15. Click Next Next Next to accept the default values in the first few screens of the New Volume Wizard but when you get to the "Drive letter or folder" page pick drive letter F: to assign to the new volume.
Note drive letter F: is just our convention for consistency because many Azure VM servers have D: used for temporary storage and E: used for a mounted ISO file.
Click Next.
16. On the “Select file system settings” page, set the Volume Label of the volume to data. (optional)
17. Click Next.
18. On the “Confirm selections” screen, click Create
19. When the New Volume Wizard Results screen displays "You have successfully completed the New Volume Wizard" click Close.
3. Create an Installs folder on the F: (data) drive
4. Add Setup and Farm Accounts to Local Administrators Group
1. If you are not already in a Remote Desktop session on MBP-CA, open a remote desktop connection to MBP-CA.
2. Remote Desktop will prompt you for credentials to login to MBP-CA. Use the credentials you specified when you added the VM to the domain in step V – A – 1 (MBP\mbpadmin in this case).
Windows opens the Server Manager.
3. From the upper right corner of Server Manager Dashboard, select Tools -->Computer Management.
4. From Computer Management, under System Tools, expand Local Users and Groups.
5. Open the Groups folder.
6. Double-click on Administrators to open the Administrators properties box.
7. Under Members…, click Add…
8. Add MBP\sp_admin – the SharePoint Setup Account
9. Click OK.
10. Click Add…
11. Add MBP\sp_farm – the SharePoint Farm Account
12. Click OK.
Note: it is a best practice to eventually remove the SharePoint Farm Account (MBP\sp_farm) from the local Administrators group of the SharePoint servers. However, the farm account must be a member of the local Administrators group during initial configuration steps in particular during setup of User Profile Synchronization. After User Profile Synchronization is configured and working, this guide does include an explicit step to remove the SharePoint Farm Account from the local Administrators group.
13. Click OK to close the Administrators Properties dialog.
14. Close Computer Management
15. Sign out as mbpadmin
Now that the SharePoint Setup Account – MBP\sp_admin in this case – is a member of the Administrators group on the server, you should Sign out as mbpadmin and sign in as MBP\sp_admin for all future installation and configuration actions on the server.
5. Create the SQL Server Alias sql_server_alias
One important best practice is to configure a SQL Server Alias on each machine that will be a SharePoint server, including this one (MBP-CA).
The SQL Server Alias is an alias local to the SQL client that stores the connection parameters to the SQL server (MBP-SQL) and the instance (SPDB). In this case the SharePoint Server is the SQL client. We configure SharePoint using the SQL Server alias sql_server_alias rather than the actual SQL Server name and instance name. We configure SharePoint using this SQL Server Alias rather than the actual name of the SQL server so that if we ever need to change what SQL server or instance is hosting the SharePoint databases, the SharePoint configuration can remain unchanged and only the SQL Server Alias needs to be adjusted.
Now is the time to create a SQL Server Alias, and in any case you must do so before running the Create Farm PowerShell script (section IX). This guide tells you to create a SQL Server Alias (sql_server_alias) on this (MBP-CA) and all SharePoint servers in the farm.
1. Open a Remote Desktop Connection to the SharePoint Central Admin server (MBP-CA in this case) and sign in using the SharePoint Setup Account – MBP\sp_admin in this case.
2. Open a command prompt and navigate to C:\Windows\System32
3. Enter cliconfg.exe to launch the SQL Server Client Network utility.
4. From the SQL Server Client Network Utility dialog, select the Alias tab.
5. From the Alias tab, click the Add… button
6. From the Add Network Library Configuration screen, enter sql_server_alias into the Server alias: field
7. In the Network libraries section, select TCP/IP
8. In the Server name: field enter one of the following:
a. If you are using a named instance of SQL -- as we are in MBP -- enter <Server>\<Alias> e.g. MBP-SQL\SPDB in this case.
b. If you are using the default instance of SQL, enter just the server name e.g. SQL2012BI.
9. Click OK to complete creating this alias.
10. Click OK to close the SQL Server Client Network Utility
11. Close the command prompt
Now that you have created a SQL Alias on this SQL client, it is a best practice to test and verify that your server can connect to SQL using this alias now. Use the Windows ODBC Data Source Administrator (64-bit) utility to create a Data Source specifying sql_server_alias as the Server.
12. Open the ODBC Data Source Administrator by clicking the Windows Server 2012 Start icon in the lower left. Then, in the upper right of the Start page, click the Search icon (magnifying glass). Type in “ODBC”. Select ODBC Data Sources (64-bit).
Windows opens the ODBC Data Source Administrator (64-bit)
13. From ODBC Data Source Administrator, click the Add… button
ODBC opens the Create New Data Source dialog. Note that the SQL Server driver is selected by default.
14. Click the Finish button.
ODBC displays the Create a New Data Source to SQL Server dialog.
15. Enter Name = Test1 because you are not going to keep this data source.
16. From the Server drop-down list at the bottom of the dialog, select the alias you just created, sql_server_alias in this case.
17. Click Next>
ODBC displays the next page of the New Data Source Wizard:
18. Click Next> ODBC displays the next page of the wizard.
NOTE: If the wizard displays an error, stop and troubleshoot your connectivity to your SQL Server. A common source of errors at this step is that the SQL Server is not running.
19. Click Next>
ODBC display the last page of the wizard
20. Click the Finish button.
ODBC displays the confirmation page:
21. Click the Test Data Source… button.
Verify the tests completed successfully. This means your SharePoint server can connect with your SQL server. If this test does not complete successfully, you must resolve any errors before attempting to proceed with creation of the SharePoint farm.
22. Click OK.
ODBC displays the New Data Source Wizard again.
23. Now click Cancel because you have verified you can connect to SQL, you do not need this ODBC connection.
24. Click Cancel again to close the “Create a New Data Source” wizard
25. Click OK to close the ODBC Data Source Administrator applet.
6. Temporarily Turn Off Windows Firewall on MBP-CA
By default on Windows Server 2012 R2, Windows Firewall is turned on and blocks incoming connections. Turn off Windows Firewall for the Domain network so that other hosts can connect to MBP-CA during farm configuration. Later, we will turn Firewall back on and add rules to permit connections on certain ports.
1. If you are not already logged in to the SharePoint Central Admin server (MBP-CA), open a Remote Desktop connection to MBP-CA and sign on as the SharePoint Setup Account (mbp\sp_admin in this case).
2. From the Server Manager, on the left side navigator, select Local Server
3. In the Properties area, locate the Windows Firewall setting and click Domain: On
4. From the Windows Firewall applet, on the left side navigator, click Turn Windows Firewall on or off.
5. From the Customize Settings window, in the Domain network settings category, select Turn off Windows Firewall
6. Click OK
7. Close the Windows Firewall applet.
This completes the provisioning of MBP-CA, the server that will become the Central Admin server. In the next few sections, we provision MBP-WFE1 and MBP-WFE2, the servers that will become the Web Front-End servers, and other servers that will fill other roles in the MBP farm. We will return to install SharePoint Prerequisites and SharePoint executables on MBP-CA in sections VIII and IX.
B. Create the SharePoint Web Front-End Servers MBP-WFE1 and MBP-WFE2
This section specifies how to provision the SharePoint Web Front-End Servers -- MBP-WFE1 and MBP-WFE2 -- attach a data disks to them, and join them to the domain.
1. Add new VMs in Microsoft Azure for MBP-WFE1 and 2
1. From the Microsoft Azure Portal (portal.azure.com), click the + NEW button in the upper left.
Azure displays the “Create” blade.
2. From the “Create” blade, select Compute.
Azure displays the “Compute” blade.
3. From the “Compute” blade, select Windows Server 2012 R2 Datacenter.
Azure displays the “Create VM” blade.
4. From the “Create VM” blade, enter the Host Name MBP-WFE1, the user name mbpadmin, and the password as per our plan from section II – D – 4 (Detailed Physical Architecture)
Field
|
Value
|
Description
|
Host
Name
|
MBP-WFE1
|
From
Plan
|
User
Name
|
mbpadmin
|
Local
machine admin account
|
Password
|
$hareP0int
|
Suitably
strong password
|
5. From the “Create VM” blade, click PRICING TIER
6. From the “Choose your pricing tier” blade, select View All
7. Scroll down and select A5 Standard or whatever VM size is appropriate based on your performance and capacity planning.
8. At the bottom of the “Choose your pricing tier” blade, click Select
Azure closes the “Choose your pricing” blade.
The “Create VM” blade displays the selected pricing tier.
9. From the “Create VM” blade, click OPTIONAL CONFIGURATION.
Azure displays the “Optional config” blade
10. From the “Optional config” blade, click OS SETTINGS
Azure displays the “OS Settings” blade
11. From the “OS Settings” blade, click DOMAIN JOIN
Azure displays the “Domain join” blade
12. From the “Domain join” blade, enter into the Domain field the domain name you created when you created the AD-DC VM in step III - 3 - B (mbp.com in this case).
13. In the User Name and Password fields, enter the credentials for the domain administrator account we planned for in section II – A (Plan Service Accounts) (mbp\mbpadmin in this case).
Domain
|
mbp.com
|
User Name
|
mbp\mbpadmin
|
Password
|
$hareP0int
|
14. At the bottom of the “Domain join” blade, click OK
Azure closes the “Domain join” blade.
15. At the bottom of the “OS Settings” blade, click OK
Azure closes the “OS Settings” blade
16. From the “Optional config” blade, click NETWORK
Azure displays the “Network” blade.
17. From the “Network” blade, click VIRTUAL NETWORK
Azure opens two blades: the “Virtual Network” blade and the “Create a virtual network” blade.
18. From the “Virtual Network” blade, under “Use an existing virtual network”, select mbp-net, the network we created in step III – B – 1.
Azure closes the “Virtual Network” blade
19. Leave the default values for DOMAIN NAME (e.g. mbp-wfe1.cloudapp.net).
20. From the “Network” blade, click IP ADDRESSES
Azure displays the “IP addresses” blade
21. From the “IP addresses” blade, under the “Private IP address” label, change the “IP address assignment” from DHCP to Static.
22. In the “IP Address” field, enter the Static IPV4 address we planned for the this server back in section II – D – 4 and duplicated here for your reference:
10.0.0.7 for MBP-WFE1
10.0.0.8 for MBP-WFE2
23. At the bottom of the “IP address” blade, click OK
Azure closes the “IP address” blade.
24. At the bottom of the “Network” blade, click OK
Azure closes the “Network” blade
25. From the “Optional config” blade, click STORAGE ACCOUNT
Select to use existing storage account rather than creating a new one (optional).
26. At the bottom of the “Optional config” blade, click OK
If Azure displays “Message from webpage: Your unsaved edits will be discarded” click OK. This looks like a bug in Azure portal preview.
27. From the “Create VM” blade, click RESOURCE GROUP
Azure displays the “Resource group” blade.
28. From the “Resource group” blade, under “Use an existing group”, select the resource group we created in section II, MBPI in this case.
29. At the bottom of the “Create VM” blade, click Create
Azure displays the portal home page with an animated graphic and the message “Creating Windows Server 2012 R2 Datacenter” while it provisions the new machine.
It takes about five minutes to provision a new virtual machine with this configuration.
Unfortunately, I found that I was unable to multi-task and start provisioning MBP-WFE2 while waiting for Azure to create MBP-WFE1. It seems Azure is only capable of creating one VM at a time.
2. Attach Additional disks to MBP-WFE1 and 2
Attach an additional disk with Host Cache Preference = NONE for the data volume of the new VM.
1. In the Azure management portal, select the VM you just created (MBP-WFE1), and, at the top of the MBP-WFE1 Virtual machine blade, click the Settings button
Azure displays the “Settings” blade.
2. From the “Settings” blade, click Disks.
Azure displays the “Disks” blade
3. At the top of the “Disks” blade, click the button marked Attach New…
Azure displays the “Attach a new disk” blade
4. From the “Attach a new disk” blade, type the size of hard disk (in GB) you planned, in this case 100 GB.
5. Keep the Host Caching = NONE
6. At the bottom of the “Attach a new disk” blade, click OK
7. Wait for the empty disk to be added ok, then follow the steps below to connect to the new VM and configure the new disk as drive F:
8. In the Azure management portal, select the VM you just created (MBP-WFE1), and, on the control bar at the top of the MBP-WFE1 Virtual machine blade, click the Connect button.
9. Your browser will prompt to save or open the MBP-WFE1.rdp remote desktop connection. Save this rdp file to your desktop for future use. Then open the RDP file to connect to the server.
10. Remote Desktop will warn you that, “The publisher of this remote connection can’t be identified”. Click Connect.
11. Windows Security will prompt you for credentials. Click Use another account. You must enter the credentials of the account we specified when we joined the VM to the domain: in this case the MBP domain admin account mbp\mbpadmin and password.
12. Click OK
Remote Desktop Connection will displays a certificate warning. Click Yes.
Remote desktop displays the MBP-WFE1 Windows desktop.
Windows displays the Server Manager Dashboard.
13. From the Server Manager Dashboard, click File and Storage Services --> Disks
14. On the DISKS list, right-click on the new disk Number 2 and click Initialize, and click Yes to confirm the operation.
15. After initialization is complete, right-click the disk, click New Volume…
16. Click Next to accept the default values in the first few screens of the New Volume Wizard but when you get to the "Drive letter or folder" page pick drive letter F: to assign to the new volume.
Click Next.
17. On the Select file system settings page, set the Volume Label of the volume to data. (optional) Next.
18. On the Confirmation screen, click Create
19. When the New Volume Wizard Results screen displays "You have successfully completed the New Volume Wizard" click Close.
3. Create an Installs folder on the F: (data) drive
1. On the Virtual Machine, open Windows File Explorer.
2. Create a new folder named Installs on the data F: drive.
4. Add Setup and Farm Accounts to Local Administrators Group
1. Remote desktop to MBP-WFE1 if necessary
2. Remote Desktop will prompt you for credentials to login to MBP-WFE1. Use MBP\mbpadmin to sign in.
3. From Server Manager select Tools-->Computer Management from the upper right corner.
4. From Computer Management, under System Tools, expand Local Users and Groups.
5. Select the Groups folder.
6. Double-click on Administrators to open the Administrators properties box.
7. Add the Setup user account (sp_admin) and the Farm account (sp_farm) to the Administrators group as you did for MBP-CA.
8. Close Computer Management
9. You may sign out as mbpadmin now. In the future, you will sign in to this server using the Setup user account -- sp_admin -- to perform installation and configuration tasks.
5. Create the SQL Server Alias sql_server_alias
As before (section V - A - 5), create a SQL Server Alias named sql_server_alias on this SharePoint server. The SQL Server Alias stores the connection parameters to the SQL server (MBP-SQL) and the instance (SPDB). Note that when you open a remote desktop connection to the new VM you must enter the credentials for the SharePoint Setup Account – sp_admin – in order to create the SQL Server Alias.
6. Temporarily Turn Off Windows Firewall on MBP-WFE1
Turn off Windows Firewall for the Domain networks so that other hosts can connect during farm configuration. Later, we will turn Firewall back on and add rules to permit connects on certain ports.
1. Sign on in to the SharePoint server (MBP-WFE1) as the SharePoint Setup Account (sp_admin), if necessary.
2. From the Server Manager, on the left side navigator, select Local Server
3. In the PROPERTIES area, locate the Windows Firewall setting and click Domain: On
4. From the Windows Firewall applet, on the left side navigator, click Turn Windows Firewall on or off.
5. From the Customize Settings window, in the Domain network settings category, select Turn off Windows Firewall
6. Click OK
7. Close the Windows Firewall applet.
8. Sign out and close the Remote Desktop connection
This completes the provisioning of MBP-WFE1. We will install SharePoint prerequisites and SharePoint executables in sections VIII and IX.
7. Repeat Steps B1-B6 for Additional WFE Server MBP-WFE2
Repeat all steps in section V – B for the Additional Web Front-End Server MBP-WFE2 if appropriate. Note that DEV or TEST farms likely do not require a second WFE. Also, in production, you may add additional WFE servers to your farm at a later time.
C. Create the SharePoint Search Server MBP-SEARCH
This section specifies how to provision the SharePoint Search Server -- MBP-SEARCH -- attach a data disk to it, and join it to the domain. The Search server is similar to the WFE servers but we configure a larger F: (data) disk for the Search Server to use because it will store a set of Index files locally.
1. Add a new VM in Microsoft Azure for MBP-SEARCH
1. From the Microsoft Azure Portal (portal.azure.com), click the + NEW button in the upper left.
Azure displays the “Create” blade.
2. From the “Create” blade, select Compute.
Azure displays the “Compute” blade.
3. From the “Compute” blade, select Windows Server 2012 R2 Datacenter.
Azure displays the “Create VM” blade.
4. From the “Create VM” blade, enter the Host Name MBP-SEARCH, the user name mbpadmin, and the password as per our plan from section II – D – 4 (Detailed Physical Architecture)
Field |
Value |
Description |
Host Name |
MBP-SEARCH |
From Plan |
User Name |
mbpadmin |
Local machine admin account |
Password |
$hareP0int |
Suitably strong password |
5. From the “Create VM” blade, click PRICING TIER
6. From the “Choose your pricing tier” blade, select View All
7. Scroll down and select A5 Standard or whatever VM size is appropriate.
8. At the bottom of the “Choose your pricing tier” blade, click Select
Azure closes the “Choose your pricing” blade.
The “Create VM” blade displays the selected pricing tier.
9. From the “Create VM” blade, click OPTIONAL CONFIGURATION.
Azure displays the “Optional config” blade
10. From the “Optional config” blade, click OS SETTINGS
Azure displays the “OS Settings” blade
11. From the “OS Settings” blade, click DOMAIN JOIN
Azure displays the “Domain join” blade
12. From the “Domain join” blade, enter into the Domain field the domain name you created when you created the AD-DC VM in step III - 3 - B (mbp.com in this case).
13. In the User Name and Password fields, enter the credentials for the domain administrator account we planned for in section II – A (Plan Service Accounts) (mbp\mbpadmin in this case).
Domain
|
mbp.com
|
User Name
|
mbp\mbpadmin
|
Password
|
$hareP0int
|
14. At the bottom of the “Domain join” blade, click OK
Azure closes the “Domain join” blade
15. At the bottom of the “OS Settings” blade, click OK
Azure closes the “OS Settings” blade
16. From the “Optional config” blade, click NETWORK
Azure displays the “Network” blade.
17. From the “Network” blade, click VIRTUAL NETWORK
Azure opens two blades: the “Virtual Network” blade and the “Create a virtual network” blade.
18. From the “Virtual Network” blade, under “Use an existing virtual network”, select mbp-net, the network we created in step III – B – 1.
Azure closes the “Virtual Network” blade
19. Leave the default values for DOMAIN NAME (e.g. mbp-search.cloudapp.net).
20. From the “Network” blade, click IP ADDRESSES
Azure displays the “IP addresses” blade
21. From the “IP addresses” blade, under the “Private IP address” label, change the “IP address assignment” from DHCP to Static.
22. In the “IP Address” field, enter the Static IPV4 address we planned for the this server back in section II – D – 4 : 10.0.0.9 for MBP-SEARCH
23. At the bottom of the “IP address” blade, click OK
Azure closes the “IP address” blade.
24. At the bottom of the “Network” blade, click OK
Azure closes the “Network” blade
25. From the “Optional config” blade, click STORAGE ACCOUNT
Select to use existing storage account rather than creating a new one (optional).
26. At the bottom of the “Optional config” blade, click OK
If Azure displays “Message from webpage: Your unsaved edits will be discarded” click OK. This looks like a bug in Azure portal preview.
27. From the “Create VM” blade, click RESOURCE GROUP
Azure displays the “Resource group” blade.
28. From the “Resource group” blade, under “Use an existing group”, select the resource group we created in section II, MBPI in this case.
29. At the bottom of the “Create VM” blade, click Create
Azure displays the portal home page with an animated graphic and the message “Creating Windows Server 2012 R2 Datacenter” while it provisions the new machine.
2. Attach Additional disk to MBP-SEARCH
Attach an additional disk with Host Cache Preference = NONE for the data volume. Refer to your Physical Architecture for the size of this disk. Note the MBP farm Physical Architecture plan from section II - D - 4 calls for the data volume on the Search Server to be 256 GB because the Index will reside on that drive.
1. In the Azure management portal, select the VM you just created (MBP-SEARCH), and, at the top of the “MBP-CA Virtual machine” screen, click Settings.
Azure displays the “Settings” blade.
2. From the “Settings” blade, click Disks.
Azure displays the “Disks” blade
3. At the top of the “Disks” blade, click the button marked Attach New…
Azure displays the “Attach a new disk” blade
4. From the “Attach a new disk” blade, type the size of hard disk (in GB) you planned, in this case 256 GB. Make sure to keep the Host Caching = NONE
5. At the bottom of the “Attach a new disk” blade, click OK
Azure will close the “Attach a new disk” blade while it provisions the new data disk.
6. When the “Disks” blade displays the new data disk ok, you may proceed to the next step.
Now connect to the new VM and configure the new disk as drive F:
7. In the Azure management portal, select the VM you just created (MBP-SEARCH), and, on the control bar at the top of the Virtual machine blade, click the Connect button
8. Open the RDP file to open a remote desktop connection to the VM you just created.
9. Remote Desktop will warn you that, “The publisher of this remote connection can’t be identified”. Click Connect.
10. Windows Security will prompt you for credentials to login to MBP-SEARCH. Click Use another account. Enter the credentials for the MBP domain admin account mbp\mbpadmin.
11. If Remote Desktop displays a certificate error, click Yes
Remote desktop displays the MBP-SEARCH Windows desktop.
12. Windows displays the Server Manager Dashboard
13. From the Server Manager Dashboard, click File and Storage Services --> Disks
14. On the DISKS list, right-click on the new disk Number 2 and click Initialize, and click Yes to confirm the operation.
15. After initialization is complete, right-click the disk, click New Volume…
16. Click Next to accept the default values in the first few screens of the New Volume Wizard but when you get to the "Drive letter or folder" page pick drive letter F: to assign to the new volume.
Click Next.
17. On the Select file system settings page, set the Volume Label of the volume to data. (optional) Next.
18. On the Confirmation screen, click Create
19. When the New Volume Wizard Results screen displays "You have successfully completed the New Volume Wizard" click Close.
3. Create an Installs folder on the F: (data) drive
1. On the Virtual Machine, open Windows File Explorer.2. Create a new folder named Installs on the data F: drive.
4. Add Setup and Farm Accounts to Local Administrators Group
1. If not already connected, open a remote desktop connection to the Search server MBP-SEARCH.
2. Remote Desktop will prompt you for credentials. Use MBP\mbpadmin.
3. From Server Manager select Tools-->Computer Management from the upper right corner.
4. From Computer Management, under System Tools, expand Local Users and Groups.
5. Select the Groups folder.
6. Double-click on Administrators to open the Administrators properties box.
7. Click Add… to add the Setup user account (sp_admin) and the SharePoint Farm account (sp_farm) as you did for MBP-CA.
8. Click OK
9. Close Computer Management
10. Sign out as mbpadmin. In the future, you will sign in using the Setup user account -- sp_admin.
5. Create the SQL Server Alias sql_server_alias
Follow the steps documented in section V – A – 5 (Create the SQL Server Alias sql_server_alias) to create a SQL Server Alias on this SharePoint server.
6. Temporarily Turn Off Windows Firewall for MBP-SEARCH
Turn off Windows Firewall for the Domain networks so that other hosts can connect during farm configuration. Later, we will turn Firewall back on and add rules to permit connects on certain ports.
1. If you are not already signed on to the search server, open a remote desktop connection to the Search server MBP-SEARCH.
2. Remote Desktop will prompt you for credentials. Use MBP\sp_admin.
3. From the Server Manager, on the left side navigator, select Local Server
4. In the Properties area, locate the Windows Firewall setting and click Domain: On
5. From the Windows Firewall applet, on the left side navigator, click Turn Windows Firewall on or off.
6. From the Customize Settings window, in the Domain network settings category, select Turn off Windows Firewall
7. Click OK
8. Close the Windows Firewall applet.
9. Sign out and close the remote desktop connection to the Search server.
This completes the provisioning of MBP-SEARCH. We will install SharePoint prerequisites and SharePoint executables in sections VIII and IX.
D. Create the SharePoint BI Server MBP-BI
Provision the SharePoint Business Intelligence Services Server -- MBP-BI -- attach a data disk to it, and join it to the domain. The BI server can be configured similarly to the WFE.
1. Add a new VM in Microsoft Azure for MBP-BI
1. From the Microsoft Azure Portal (portal.azure.com), click the + NEW button in the upper left.
Azure displays the “Create” blade.
2. From the “Create” blade, select Compute.
Azure displays the “Compute” blade.
3. From the “Compute” blade, select Windows Server 2012 R2 Datacenter.
Azure displays the “Create VM” blade.
4. From the “Create VM” blade, enter the Host Name MBP-BI, the user name mbpadmin, and the password as per our plan from section II – D – 4 (Detailed Physical Architecture)
Field Value Description
Host Name MBP-BI From Plan
User Name mbpadmin Local machine admin account
Password $hareP0int Suitably strong password
5. From the “Create VM” blade, click PRICING TIER
6. From the “Choose your pricing tier” blade, select View All
7. Scroll down and select A5 Standard or whatever VM size is appropriate.
8. At the bottom of the “Choose your pricing tier” blade, click Select
Azure closes the “Choose your pricing” blade.
The “Create VM” blade displays the selected pricing tier.
9. From the “Create VM” blade, click OPTIONAL CONFIGURATION.
Azure displays the “Optional config” blade
10. From the “Optional config” blade, click OS SETTINGS
Azure displays the “OS Settings” blade
11. From the “OS Settings” blade, click DOMAIN JOIN
Azure displays the “Domain join” blade
12. From the “Domain join” blade, enter into the Domain field the domain name you created when you created the AD-DC VM in step III - 3 - B (mbp.com in this case).
13. In the User Name and Password fields, enter the credentials for the domain administrator account we planned for in section II – A (Plan Service Accounts) (mbp\mbpadmin in this case).
Domain
|
mbp.com
|
User Name
|
mbp\mbpadmin
|
Password
|
$hareP0int
|
14. At the bottom of the “Domain join” blade, click OK
Azure closes the “Domain join” blade
15. At the bottom of the “OS Settings” blade, click OK
Azure closes the “OS Settings” blade
16. From the “Optional config” blade, click NETWORK
Azure displays the “Network” blade.
17. From the “Network” blade, click VIRTUAL NETWORK
Azure opens two blades: the “Virtual Network” blade and the “Create a virtual network” blade.
18. From the “Virtual Network” blade, under “Use an existing virtual network”, select mbp-net, the network we created in step III – B – 1.
Azure closes the “Virtual Network” blade
19. Leave the default values for DOMAIN NAME (e.g. mbp-search.cloudapp.net).
20. From the “Network” blade, click IP ADDRESSES
Azure displays the “IP addresses” blade
21. From the “IP addresses” blade, under the “Private IP address” label, change the “IP address assignment” from DHCP to Static.
22. In the “IP Address” field, enter the Static IPV4 address we planned for the this server back in section II – D – 4 : 10.0.0.10 for MBP-BI
23. At the bottom of the “IP address” blade, click OK
Azure closes the “IP address” blade.
24. At the bottom of the “Network” blade, click OK
Azure closes the “Network” blade
25. From the “Optional config” blade, click STORAGE ACCOUNT
Select to use existing storage account rather than creating a new one (optional).
26. At the bottom of the “Optional config” blade, click OK
If Azure displays “Message from webpage: Your unsaved edits will be discarded” click OK. This appears to be a bug in Azure portal preview and does not actually discard your edits.
27. From the “Create VM” blade, click RESOURCE GROUP
Azure displays the “Resource group” blade.
28. From the “Resource group” blade, under “Use an existing group”, select the resource group we created in section II, MBPI in this case.
29. At the bottom of the “Create VM” blade, click Create
Azure displays the portal home page with an animated graphic and the message “Creating Windows Server 2012 R2 Datacenter” while it provisions the new machine.
2. Attach Additional disk to MBP-BI
Follow the steps in section V – A – 2 to attach a 100 GB data disk to the BI server and create volume with drive letter F:.
3. Create an Installs folder on the F: (data) drive
Follow the steps in section V – A – 3 to create an Installs folder on the F: (data) drive.
4. Add Setup and Farm Accounts to Local Administrators Group
Follow the steps in section V – A – 4 to add the Setup User Account (sp_admin) and the SharePoint Farm account (sp_farm) to the local administrators group.After the sp_admin account is added to the Administrators group, remember to sign out as mbpadmin and sign back in as sp_admin before performing step 5.
5. Create the SQL Server Alias sql_server_alias
Follow the steps documented in section V – A – 5 (Create the SQL Server Alias sql_server_alias) to create a SQL Server Alias on this SharePoint server.
6. Temporarily Turn Off Windows Firewall for MBP-BI
Follow the steps documented in section V – A – 6 (Turn off Windows Firewall) to turn off the firewall for Domain networks. Later, we will turn Firewall back on and add rules to permit connects on certain ports.
This completes the provisioning of MBP-BI. We will install SharePoint prerequisites and SharePoint executables in sections VIII and IX.
E. Create the Office Web Apps Server MBP-OWA
The Office Web Apps server is not technically part of the SharePoint Farm. SharePoint is not installed on the Office Web Apps Server. (Also, in Central Admin, the list of Servers in the Farm does not include the OWA server.) Nevertheless, I consider Office Web Apps to be a core feature of any good SharePoint intranet. For MBP, our Office Web Apps Server is a single-server Office Web Apps Server farm. In this section we create the Office Web Apps Server -- MBP-OWA -- attach a data disk to it, and join it to the domain.1. Add a new VM in Microsoft Azure for MBP-OWA
1. From the Microsoft Azure Portal (portal.azure.com), click the + NEW button in the upper left.
Azure displays the “Create” blade.
2. From the “Create” blade, select Compute.
Azure displays the “Compute” blade.
3. From the “Compute” blade, select Windows Server 2012 R2 Datacenter.
Azure displays the “Create VM” blade.
4. From the “Create VM” blade, enter the Host Name MBP-OWA, the user name mbpadmin, and the password as per our plan from section II – D – 4 (Detailed Physical Architecture)
Field
|
Value
|
Description
|
Host
Name
|
MBP-OWA
|
From
Plan
|
User
Name
|
mbpadmin
|
Local
machine admin account
|
Password
|
$hareP0int
|
Suitably
strong password
|
5. From the “Create VM” blade, click PRICING TIER
6. From the “Choose your pricing tier” blade, select View All
7. Scroll down and select A5 Standard or whatever VM size is appropriate for your farm.
8. At the bottom of the “Choose your pricing tier” blade, click Select
Azure closes the “Choose your pricing” blade.
The “Create VM” blade displays the selected pricing tier.
9. From the “Create VM” blade, click OPTIONAL CONFIGURATION.
Azure displays the “Optional config” blade
10. From the “Optional config” blade, click OS SETTINGS
Azure displays the “OS Settings” blade
11. From the “OS Settings” blade, click DOMAIN JOIN
Azure displays the “Domain join” blade
12. From the “Domain join” blade, enter into the Domain field the domain name you created when you created the AD-DC VM in step III - 3 - B (mbp.com in this case).
13. In the User Name and Password fields, enter the credentials for the domain administrator account we planned for in section II – A (Plan Service Accounts) (mbp\mbpadmin in this case).
Domain
|
mbp.com
|
User Name
|
mbp\mbpadmin
|
Password
|
$hareP0int
|
14. At the bottom of the “Domain join” blade, click OK
Azure closes the “Domain join” blade
15. At the bottom of the “OS Settings” blade, click OK
Azure closes the “OS Settings” blade
16. From the “Optional config” blade, click NETWORK
Azure displays the “Network” blade.
17. From the “Network” blade, click VIRTUAL NETWORK
Azure opens two blades: the “Virtual Network” blade and the “Create a virtual network” blade.
18. From the “Virtual Network” blade, under “Use an existing virtual network”, select mbp-net, the network we created in step III – B – 1.
Azure closes the “Virtual Network” blade
19. Leave the default values for DOMAIN NAME (e.g. mbp-search.cloudapp.net).
20. From the “Network” blade, click IP ADDRESSES
Azure displays the “IP addresses” blade
21. From the “IP addresses” blade, under the “Private IP address” label, change the “IP address assignment” from DHCP to Static.
22. In the “IP Address” field, enter the Static IPV4 address we planned for the this server back in section II – D – 4 : 10.0.0.12 for MBP-OWA
23. At the bottom of the “IP address” blade, click OK
Azure closes the “IP address” blade.
24. At the bottom of the “Network” blade, click OK
Azure closes the “Network” blade
25. From the “Optional config” blade, click STORAGE ACCOUNT
Select to use existing storage account rather than creating a new one (optional).
26. At the bottom of the “Optional config” blade, click OK
If Azure displays “Message from webpage: Your unsaved edits will be discarded” click OK. This looks like a bug in Azure portal preview.
27. From the “Create VM” blade, click RESOURCE GROUP
Azure displays the “Resource group” blade.
28. From the “Resource group” blade, under “Use an existing group”, select the resource group we created in section II, MBPI in this case.
29. At the bottom of the “Create VM” blade, click Create
Azure displays the portal home page with an animated graphic and the message “Creating Windows Server 2012 R2 Datacenter” while it provisions the new machine.
Wait for MBP-OWA to be running before you proceed to the next step.
2. Add the SharePoint Setup Account to Local Administrators Group
Follow steps documented in section V - A - 4 (Add Setup and Farm Accounts to Local Administrators Group) to add the SharePoint Setup Account (MBP\sp_admin in this case) to the Administrators group.
It is not strictly necessary to make the Setup User Account and administrator on the OWA server. In this guide, for consistency, we use the Setup User account for all server installation and configuration work. Therefore, it’s intuitive to make sp_admin be a local administrator of the OWA server, even though that server is not technically part of the SharePoint farm.
Steps to install Office Web Apps Server 2013 with SP1 begin in section X Configure Office Web Apps.
F. Create the SSAS Server MBP-SSAS
In this section we add a VM named MBP-SSAS to run the PowerPivot instance of SQL Server Analysis Services (SSAS). This SQL Server Analysis Services server is a SQL Server, not a SharePoint server. SharePoint is not installed on this server. However, SQL Server PowerPivot for SharePoint is installed on this server. Excel Services in our MBP farm requires an instance of SSAS to exist somewhere in the network so that Excel Services in SharePoint can perform advanced calculations. We will register this instance of SQL Server Analysis Services with Excel Services in section XI when we configure Business Intelligence.
This section only includes steps to create the VM, add a data drive, and join the VM to the mbp.com domain. Steps to install SQL Server Analysis Services begin in section XIV (Configure Business Intelligence).
1. Add a new VM in Microsoft Azure for MBP-SSAS
1. From the Microsoft Azure Portal (portal.azure.com), click the + NEW button in the upper left.Azure displays the “Create” blade.
2. From the “Create” blade, select Compute.
Azure displays the “Compute” blade.
3. From the “Compute” blade, select Windows Server 2012 R2 Datacenter.
Azure displays the “Create VM” blade.
4. From the “Create VM” blade, enter the Host Name MBP-SSAS, the user name mbpadmin, and the password as per our plan.
Field
|
Value
|
Description
|
Host
Name
|
MBP-SSAS
|
From
Plan
|
User
Name
|
Mbpadmin
|
Local
machine admin account
|
Password
|
$hareP0int
|
Suitable
strong password
|
5. From the “Create VM” blade, click PRICING TIER
6. From the “Choose your pricing tier” blade, select View All
7. Scroll down and select A5 Standard.
8. At the bottom of the “Choose your pricing tier” blade, click Select
Azure closes the “Choose your pricing” blade.
9. From the “Create VM” blade, click OPTIONAL CONFIGURATION.
Azure displays the “Optional config” blade
10. From the “Optional config” blade, click OS SETTINGS
Azure displays the “OS Settings” blade
11. From the “OS Settings” blade, click DOMAIN JOIN
Azure displays the “Domain join” blade
12. From the “Domain join” blade, enter into the Domain field the domain name you created when you created the AD-DC VM in step III - 3 - B (mbp.com in this case).
13. In the User Name and Password fields, enter the credentials for the domain administrator account we planned for in section II – A (Plan Service Accounts) (mbp\mbpadmin in this case).
14. At the bottom of the “Domain join” blade, click OK
Azure closes the “Domain join” blade
15. At the bottom of the “OS Settings” blade, click OK
Azure closes the “OS Settings” blade
16. From the “Optional config” blade, click NETWORK
Azure displays the “Network” blade.
17. From the “Network” blade, click VIRTUAL NETWORK
Azure opens two blades: the “Virtual Network” blade and the “Create a virtual network” blade.
18. From the “Virtual Network” blade, under “Use an existing virtual network”, select mbp-net, the network we created in step III – B – 1.
Azure closes the “Virtual Network” blade
19. Leave the default values for DOMAIN NAME (e.g. mbp-search.cloudapp.net).
20. From the “Network” blade, click IP ADDRESSES
Azure displays the “IP addresses” blade
21. From the “IP addresses” blade, under the “Private IP address” label, change the “IP address assignment” from DHCP to Static.
22. In the “IP Address” field, enter the Static IPV4 address we planned for the this server back in section II – D – 4 : 10.0.0.11 for MBP-SSAS
23. At the bottom of the “IP address” blade, click OK
Azure closes the “IP address” blade.
24. At the bottom of the “Network” blade, click OK
Azure closes the “Network” blade
25. From the “Optional config” blade, click Storage Account
26. Select to use existing storage account rather than creating a new one (optional).
27. At the bottom of the “Optional config” blade, click OK
If Azure displays “Message from webpage: Your unsaved edits will be discarded” click OK. This appears to be a bug in Azure portal preview and does not actually discard your edits.
28. From the “Create VM” blade, click RESOURCE GROUP
Azure displays the “Resource group” blade.
29. From the “Resource group” blade, under “Use an existing group”, select the resource group we created in section II, MBPI in this case.
30. At the bottom of the “Create VM” blade, click Create
31. Azure displays the portal home page with an animated graphic and the message “Creating Windows Server 2012 R2 Datacenter” while it provisions the new machine.
2. Attach additional disk to MBP-SSAS
It is a best practice for Azure environments to attach an additional disk with Host Cache Preference = NONE to the VM for the data volume. You will use this data volume when you install SQL. Unlike the MBP-SQL server, the F: drive (data volume) need not be extra-large. For MBP we planned 100 GB for F.
1. In the Azure management portal, select the VM you just created (MBP-SSAS), and, at the top of the “MBP-SSAS Virtual Machine” screen, click Settings
Azure displays the “Settings” blade
2. From “Settings” blade, click Disks.
Azure displays the “Disks” blade
3. At the top of the “Disks” blade, click the button marked Attach New…
Azure displays the “Attach a new disk” blade
4. From the “Attach a new disk” blade, type the size of hard disk planned, in this case 100 GB. Make sure to keep the Host Caching = NONE
5. At the bottom of the “Attach a new disk” blade, click OK
Azure will close the “Attach a new disk” blade while it provisions the new data disk.
6. When the “Disks” blade displays the new data disk ok, you may proceed to the next step.
Now connect to the new VM and configure the new disk as drive F:
7. In the Azure management portal, select the VM you just created (MBP-SSAS), and, on the control bar at the top of the Virtual machine blade, click the Connect button
8. Open the MBP-SSAS.rdp remote desktop connection.
9. Remote Desktop will warn you that, “The publisher of this remote connection can’t be identified”. Click Connect.
10. Windows Security will prompt you for credentials to login to MBP-SSAS. Click Use another account. Enter the credentials for the MBP domain admin account mbp\mbpadmin.
11. If Remote Desktop displays a certificate error, click Yes
Remote desktop displays the MBP-SSAS Windows desktop.
12. Windows displays the Server Manager Dashboard
13. From the Server Manager Dashboard, click File and Storage Services --> Disks
14. On the DISKS list, right-click on the new disk Number 2 and click Initialize, and click Yes to confirm the operation.
15. After initialization is complete, right-click the disk, click New Volume…
16. Click Next to accept the default values in the first few screens of the New Volume Wizard but when you get to the "Drive letter or folder" page pick drive letter F: to assign to the new volume.
Click Next.
17. On the Select file system settings page, set the Volume Label of the volume to data. (optional) Next.
18. On the Confirmation screen, click Create
19. When the New Volume Wizard Results screen displays "You have successfully completed the New Volume Wizard" click Close.
3. Create an Installs folder on the F: (data) drive
3. On the Virtual Machine, open Windows File Explorer.4. Create a new folder named Installs on the data F: drive.
4. Add SQL Admin Account to Local Administrators Group1. If not already connected, open a remote desktop connection to the server MBP-SSAS.
2. Remote Desktop will prompt you for credentials use MBP\mbpadmin.
3. From Server Manager select Tools Computer Management from the upper right corner.
4. From Computer Management, under System Tools, expand Local Users and Groups.
5. Open the Groups folder.
6. Double-click on Administrators to open the Administrators properties box.
7. Click Add… to add sql_admin as you did for MBP-SQL.
8. Click OK to close Select Users, Computers, Service Account, or Groups dialog.
9. Click OK to close the Administrators properties dialog.
10. Add SP Setup Account (mbp\sp_admin) to the Remote Desktop Users Group.
11. No need to add sp_farm as this is not a SharePoint server.
12. Close the Computer Management tool.
5. Copy ISO file for SQL Server 2012 with SP2 to the Installs folder on F:
Copy the install files for SQL Server 2012 Business Intelligence with Service Pack 2 (x64) to the Installs folder you created on the data drive.
6. Temporarily Turn Off Windows Firewall for MBP-SSAS
In the MBP farm we only need to turn off Windows Firewall in the Domain network settings. For our isolated farm (MBP) we leave Private network settings and Public Network settings in the default state.
Follow the steps described in section V – A – 6 to temporarily turn off Windows firewall for MBP-SSAS in domain network settings.
7. See Section XIV to install SQL Server Analysis Services
Steps to install SQL Server Analysis Services begin in section XIV (Configure Business Intelligence)
You may wish to shut down MBP-SSAS until you are ready for section XIV (Configure Business Intelligence) to save Azure compute costs.
G. Create the Cloud App Model App Server MBP-APP (Optional)
The Detailed Physical Architecture for MBP calls for a Cloud App Model App Server, MBP-APP. The Cloud App Model App Server is a Windows IIS server, not a SharePoint server. Your network will require a Cloud App Model App server if you will be developing custom Provider-Hosted Apps. You may size and configure this Cloud App Model App server in whatever way is appropriate to run the provider hosted apps you develop. Since MBP-APP is not required unless you are building custom Provider-Hosted apps, this guide does not provide details for building and configuring this server.
Next Steps
This concludes section V: Build the SharePoint Server VMs. At this point we have provisioned all the virtual machines we require for the farm, and we have added those machines to the MBP.COM domain.
In the next section, Section VI of the MBP SharePoint 2013 BI Farm Setup Guide, we configure Organizational Units (OUs) in Active Directory and apply Group Policy to ensure SharePoint service accounts retain the permissions they require, such as permission to login as a service.
No comments:
Post a Comment