It is also possible to install all of the prerequisites with the server not connected to theInternet.
Reasons for such a configuration might include:
- Your corporate IT policies may prevent you from downloading the prerequisites from the server itself (The server cannot browse the Internet).
- You have the need to create multiple servers and do not wish to have each server download its own copy of the components
The solution, then, is to gather the components together into a centralized location andthen install the prerequisites to each server as needed.
This type of installation involves two distinct actions:
- Installing and configuring the Application Server and Web Server (IIS) Roles to thenew servers via PowerShell (requires the Windows Server 2008 R2 or Windows Server2012 media).
- Creating a set of installation switches to run with the prerequisiteinstaller.exe tool,then downloading the components to a file share which is accessible by your newserver.
Installing and configuring the Application and Web Server roles is done via PowerShell.Each of these roles is comprised of a set of features. Before beginning this configuration, youwill need to mount the Windows Server installation disk in an available location (this exampleuses the D: drive).
To install the roles:
- Mount the installation disk
- Open a PowerShell Window (run as Administrator)
- Run the “Import-Module ServerManager” cmdlet
- Next, use the Add-WindowsFeature cmdlet to install each of the features as shown in the following code snippet, specifying the source switch to the location where youmounted the installation disk
Add‐WindowsFeature Net‐Framework‐Features,Web‐Server,Web‐WebServer,Web‐Common‐Http,Web‐Static‐Content,Web‐Default‐Doc,Web‐Dir‐Browsing,Web‐Http‐Errors,Web‐App‐Dev,Web‐Asp‐Net,Web‐Net‐Ext,Web‐ISAPI‐Ext,Web‐ISAPI‐Filter,Web‐Health,Web‐Http‐Logging,Web‐Log‐Libraries,Web‐Request‐Monitor,Web‐Http‐Tracing,Web‐Security,Web‐Basic‐Auth,Web‐Windows‐Auth,Web‐Filtering,Web‐Digest‐Auth,Web‐Performance,Web‐Stat‐Compression,Web‐Dyn‐Compression,Web‐Mgmt‐Tools,Web‐Mgmt‐Console,Web‐Mgmt‐Compat,Web‐Metabase,Application‐Server,AS‐Web‐Support,AS‐TCP‐Port‐Sharing,AS‐WAS‐Support, AS‐HTTPActivation,AS‐TCP‐Activation,AS‐Named‐Pipes,AS‐Net‐Framework,WAS,WAS‐Process‐Model,WAS‐NETEnvironment,WAS‐Config‐APIs,Web‐Lgcy‐Scripting,Windows‐Identity‐Foundation,Server‐Media‐Foundation,Xps‐Viewer –Source D:\sources\sxs
After the Add-WindowsFeature cmdlet has run, the server will advise you that it needs to restart. Type “shutdown /r” when you are ready and the server will restartmomentarily
- When the server restarts, it will complete the configuration
Now that the roles have been configured, you need to download each software component to a central file share location which is accessible by your new server. The names anddownload locations for each component are shown in Table below
|COMPONENT||DOWNLOAD URL||FILE DOWNLOADED|
|Microsoft .NET Framework 4.5||http://go.microsoft.com/fwlink/?LinkId=225702||dotnetfx45_full_x86_x64.exe|
|Windows Management Framework 3.0||http://go.microsoft.com/fwlink/p/?LinkId=273961||Select Windows6.1-KB2506143-x64.msu|
|Microsoft SQL Server 2008 R2 SP1 Native Client||http://www.microsoft.com/enus/download/details.aspx?id=26728||Select the appropriate sqlncli.msi file for your language. For English, the filename is”1033\x64\sqlncli.msi”.|
|Windows Identity Foundation (KB974405)||http://go.microsoft.com/fwlink/p/?LinkID=226830||Windows6.1-KB974405-x64.msu|
|Microsoft Sync Framework Runtime v1.0 SP1(x64)||http://go.microsoft.com/fwlink/p/?LinkID=224449||Synchronization.msi|
|Windows Server AppFabric||http://go.microsoft.com/fwlink/?LinkId=235496||WindowsServerAppFabricSetup_x64.exe|
|Microsoft Identity Extensions||http://go.microsoft.com/fwlink/?LinkID=252368||MicrosoftIdentityExtensions-64.msi|
|Microsoft Information Protection and Control Client||http://go.microsoft.com/fwlink/p/?LinkID=219568||setup_msipc_x64.msi|
|Microsoft WCFData Services 5.0||http://www.microsoft.com/enus/download/confirmation.aspx?id=29306||WcfDataServices.exe|
|Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server(KB2671763)||http://www.microsoft.com/enus/download/details.aspx?id=29241||Select AppFabric1.1-RTM-KB2671763-x86-<XXX>.exe where <XXX> indicates yourlanguage. For English, the filename is AppFabric1.1-RTM-KB2671763-x86-ENU.exe.|
Again, if you are using Windows Server 2012, you can skip downloading the first two itemsas they are already installed in the operating system. All of the other components in this listare required, SharePoint 2013 will not install without them.
Now that all of the components have been downloaded, you can use theprerequisiteinstaller.exe file and some switches to install and configure each component.Running the prerequisiteinstaller.exe file (found at the root of your SharePoint installationmedia location) with the /? Switch displays all of the available switches, as shown in Figure below
Each of these switches can be run individually, but they are most often batched together along with the appropriate file names (in the previous table) to install the components on eachserver. In the following example, a file share has been created on the \\WS2012DC serverwhich contains all of the component download files.
To begin the component installation process
- Mount the SharePoint 2013 media (D:\ in this example).
- Enter the following command and switch, then press <enter>. Note the sharelocation is specified in each switch (\\ws2012dc\prereq).
d:\Prerequisiteinstaller.exe /PowerShell:"\\ws2012dc\prereq\WINDOWS6.1‐KB2506143‐x64.msu" /NETFX:"\\ws2012dc\prereq\dotNetFx45_Full_x86_x64.exe" /IDFX:"\\ws2012dc\prereq\Windows6.1‐ KB974405‐x64.msu" /sqlncli:"\\ws2012dc\prereq\sqlncli.msi" /Sync:"\\ws2012dc\prereq\Synchronization.msi" /AppFabric:"\\ws2012dc\prereq\WindowsServerAppFabricSetup_x64.exe" /IDFX11:"\\ws2012dc\prereq\MicrosoftIdentityExtensions‐64.msi" /MSIPCClient:"\\ws2012dc\prereq\setup_msipc_x64.msi" /WCFDataServices:"\\ws2012dc\prereq\WcfDataServices.exe" /KB2671763:"\\ws2012dc\prereq\AppFabric1.1‐ RTM‐KB2671763‐x64‐ENU.exe"
- The SharePoint 2013 Products Preparation Tool will appear as if you are online(Figure 3-5). Select <Next>, then accept the license agreement.
- The tool installs each of the components (if required).
- When the installation completes, a summary screen appears showing the completed installations
- Select the Finish button to immediately restart the server and complete the prerequisiteinstallation.