Installing SharePoint 2013 Offline on Windows Server 2012 RTM


SharePoint 2013 won’t install on a Windows 2012 machine that has no connection to the internet by default. This is actually documented @ http://support.microsoft.com/kb/2765260 already and numerous other sites to some extent but I wanted to do a step-by-step guide on the steps in the above article.

There are two workarounds – install via PowerShell or install a patch on the SharePoint-machine-to-be. The patch is this one - http://support.microsoft.com/kb/2771431 and this will allow the pre-requisites installer to finish (apparently, I’ve not tested it). If installing this patch is not possible, continue reading.

Setup SharePoint 2013 Prerequisites

As is quite common for production environments, our servers are held in a virtual bunker – far aware from the evils of the internet & public at large. Here we have an RTM Win2012 machine, with no access outside of 192.168.100.0/24 – its’ local subnet. Just to prove it we do a ping test to bing which fails, but also to prove it’s not just DNS that’s dying we’ll do the IP too (www.bing.com -> 204.79.197.200).

clip_image002

Everything ready to go – no internet at all. That ping error is basically saying “I have no route to where you want to go” – a sure sign we’re isolated indeed.

clip_image004

If you check a network trace you’ll see the wizard tried to connect to Windows Update and failed.

Installing SharePoint Required Roles Offline

The workaround is to supply the source for the side-by-side assemblies on the Windows 2012 DVD. In my case, the DVD ISO is mounted on drive D so the commands to run (on an UAC elevated PowerShell console) are as follows:

  • Import-Module ServerManager
  • Add-WindowsFeature NET-WCF-HTTP-Activation45,NET-WCF-TCP-Activation45,NET-WCF-Pipe-Activation45 -Source D:\Sources\sxs
  • 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-HTTP-Activation,AS-TCP-Activation,AS-Named-Pipes,AS-Net-Framework,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Scripting,Windows-Identity-Foundation,Server-Media-Foundation,Xps-Viewer -Source D:\Sources\sxs

The above only works if the original Windows DVD content is available at drive “D” of course.

clip_image006

It worked! In the same window, restart with “Restart-Computer” (whoever said PowerShell was hard?!).

On restarting, Windows will configure itself.

clip_image008

Install Requisite Software Packages

Now it’s just a case of downloading the rest of the packages for offline installation. There’s lots of useful info on that here if you have to do it in batch - Install prerequisites for SharePoint 2013 from a network share.

In short, the list of packages that need to be installed for Windows 2012 are as so:

Run Installer Using Local Files

Setup needs to be done by the pre-requisite installer still except we’re going to run it passing in the names of the pre-downloaded packages. Copy your SharePoint DVD contents to a writeable disc and then copy all the above downloaded packages into the “prerequisiteinstallerfiles” directory.

Next, run this command to launch the pre-requisite installer so it uses local files:

  • PrerequisiteInstaller.exe /SQLNCli:PrerequisiteInstallerFiles\sqlncli.msi /IDFX:PrerequisiteInstallerFiles\Windows6.1-KB974405-x64.msu /IDFX11:PrerequisiteInstallerFiles\MicrosoftIdentityExtensions-64.msi /Sync:PrerequisiteInstallerFiles\Synchronization.msi /AppFabric:PrerequisiteInstallerFiles\WindowsServerAppFabricSetup_x64.exe /KB2671763:PrerequisiteInstallerFiles\AppFabric1.1-RTM-KB2671763-x64-ENU.exe /MSIPCClient:PrerequisiteInstallerFiles\setup_msipc_x64.msi /WCFDataServices:PrerequisiteInstallerFiles\WcfDataServices.exe

That’s all one line by the way. For Windows 2008 R2 you need extra packages but this guide is strictly for Windows 2012 RTM so we’re just installing components necessary for 2012.

Once that’s launched you may be prompted for confirmation to open one or two setup packages (WCF Data Services randomly seemed to need confirmation) but basically the installer should have everything it needs now.

clip_image010

Restart once done – setup will continue after a reboot but will give an error. That’s because the program was launched from the context “P:\SharePoint\2013\RTM” originally whereas on reboot the context is “C:\windows\system32” so the relative package paths don’t work anymore. No matter, we’ve installed it all anyway – the wizard continuing just checks it’s all OK and in reality can be run from Windows Explorer instead. Run again normally if you want to double-check nothing’s been missed.

clip_image012

Now you can run the setup and it will pass all the pre-requisite checks. You’re ready to install SharePoint 2013!

clip_image013

Well done – your production environment that’s isolated from the internet will now be able to setup SharePoint. Happy SharePointing!

// Sam Betts

Comments (3)

  1. Paul Lynch says:

    You don't need to install this prereq on Windows Server 2012  "/IDFX:PrerequisiteInstallerFilesWindows6.1-KB974405-x64.msu" – it is installed as a Feature "Windows-Identity-Foundation" by the above script

  2. Julie says:

    Windows server 2012 r2 and SharePoint 2013 with SP1.  Prerequisites pass, but SharePoint then fails on install.  Error code 1603 after msi installer rolls back.  Application event error 1000, kernel.dll.  What should be checked next?  

  3. Geetha says:

    Very Useful link and data..

Skip to main content