I use my private server for different types of testing, it’s a really a try & fail environment. Some days back I created some new VM’s (I am running a Windows Server 2008 R2 host with Hyper-V enabled) and created an isolated private network that will run SharePoint Server 2010. As i had no problems setting up a new Domain and SQL server (by the way there is an excellent TechNet article which describes how to set up a virtual ADDC), I experienced issues with the SharePoint Server 2010 Prerequisites Installer. As usual I started the installer, this fantastic little app doing the necessary boring stuff on your server making it ready for SharePoint 2010 :). It started off normally but stopped mid-way with a message that it failed on downloading the MS SQL 2008  Analysis Services ADOMD.NET component. Well, no wonder why, running VM’s in a private network makes them Private, no access to the physical network off course. I had to install the prerequisite offline.

The easiest will of course always be to install SharePoint 2010 on a internet connected server where the Prerequisites Installer downloads the necessary stuff. But what if you had a private network as mentioned or just that you wanted to have more control over the software that’s being installed, which version and so on. With a little more manual effort you can install the prerequisites offline.

There is an explanation in this TechNet article, but I have also made a few points you can follow:

1) If you don’t have the local copies of the prerequisites already, go get them. From a internet connected computer you can download them from this TechNet article. Then they

    have to be taken to a server that is reachable from your private network. (Lazy me just packed the files as an ISO image that i easily can mount any VM).

2) Now, from the command line, find the PrerequisitesInstaller.exe on the root of your SharePoint 2010 media disk.

3) Run the command PrerequisitesInstaller.exe /?  (which gives you the following message)


As you can see it lists the different command options and most important the different switch's. A switch is a specific prerequisite identifier which represent an configuration/update for your server.

For example, as described in the screenshot above, the SQLNCli switch represents Microsoft SQL Server 2008 Native Client while the ChartControl switch represents the Microsoft Chart Controls for Microsoft .NET Framework 3.5.

Giving the desired switch you have to enter the path to the software stored locally or on a network share in the following way, i.e: PrerequisitesInstaller.exe /SQLNCli:\\<path to file> which in this case sets the installation path for the MS SQL Server 2008 native client.

If you need to install all prerequisites this way, you can enter several switch’s and their network path in pair and separate them by a space, like this:

Prerequisitesinstaller.exe /SQLNCli:\\<path to file> /ChartControl:\\<path to file> /PowerShell:\\<path to file>….and so on.

Note that the prerequisites installer will only install the prerequisites your OS needs. If the prerequisite is not applicable to your OS it will ignore it. It will of course also check if you have the necessary prerequisite already and if so skip the installation of the specified prerequisite. At last, if there is a prerequisite you need but you don’t specify it the installer will try to download from internet and install which in our scenario will fail because of no internet connection (It will generate an error similar as shown below).


4) In my environment and as shown above, the MS SQL 2008 AS ADOMD.NET installation failed so in this case I entered the following command giving the correct switch and file path:

    PrerequisitesInstaller.exe /ADOMD:\\adds\sp2010prerequisites\SQLSERVER2008_ASADOMD10.msi


5) This time the Prerequisites Installer went trough just fine and I got this successful message



Note: It is also possible to install prerequisites using an arguments file. Please see this TechNet Article section for details.