Many organizations do not allow servers to have direct access to the Internet. The Preparation Tool can be directed to install prerequisites from a
specific location, such as a shared folder, rather than downloading prerequisites from the Microsoft Download Center.
First, you must use a system that does have Internet connectivity to download all prerequisites to a shared folder. You can find links to prerequisites by
using one of the following two options:
Links to prerequisites are listed on TechNet:
Run the Preparation Tool and examine the log for error messages that are generated when the tool attempts to download each prerequisite. The URL to
each prerequisite is listed.
PrerequisiteInstaller.exe supports parameters that specify the location of each prerequisite. The syntax of each parameter is /PrerequisiteName:PathToInstallationFile. The path can be a local or Universal Naming Convention (UNC) path to which the setup user (SP_Admin)
account used to run the Preparation Tool has Read permission.
For example, the parameter used to indicate the location of the Microsoft Filter Pack 2.0 installation file is the following:
The /unattended parameter causes the Preparation Tool to run in silent, unattended mode. No prompts or messages are displayed. Use this mode only when you are confident that prerequisite installation will be successful.
You can type PrerequisiteInstaller.exe /? to display the full list of parameters.
You can use PrerequisiteInstaller.exe and its parameters to script the installation of SharePoint prerequisites by using one of two methods:
Start Command Prompt, and then type a command line with PrerequisiteInstaller.exe and all of the parameters on a single command
Start Notepad and enter all parameters on a single line. Save the file as PrerequisiteInstallerArguments.txt in the same folder as
PrerequisiteInstaller.exe. Then, run PrerequisiteInstaller.exe. It automatically looks for the arguments file, called
PrerequisiteInstallerArguments.txt, in the working directory.
[Read more about PrerequisiteInstallerArguments.txt***]
Read more on TechNet