Quantcast
Channel: Geekswithblogs.net | behavior driven developmen Posts
Viewing all articles
Browse latest Browse all 50

Installing SharePoint 2013 on Windows Server 2012 VM running on Windows 8 Hyper-V – Disconnected and Prerequisite Download Links

$
0
0

 

I will explain the process of installing SharePoint 2013 on a Windows 8 Hyper V in a disconnected scenario.  This matters for the prerequisites which by default downloads the prerequisites if run from the SharePoint 2013 installer.

 

First, I have switched on Hyper-V manager on Windows 8 and created a virtual machine.  I have then installed Windows Server 2012 on the VM from ISO.

 

Now, first think to do is mount the SharePoint 2013 ISO.  For this, open the Hyper-V Manager.

 

hypervManager

 

Right click on the Virtual Machine to open the Settings.

 

settings

 

Add the SharePoint 2013 ISO to the DVD drive by selecting the file:

 

addIso

 

Now go to the Virtual Machine and login.

 

windServer

 

Open the File Explorer and click on the DVD drive to see the SharePoint files.  Note, it is possible to right click on the drive and run it but as this is disconnected the prerequisites will fail.  I will explain later how to get around this.

 

serverDVDContent

To install SharePoint 2013 as ever there are some prerequisites. There is an install prerequisites option in the SharePoint installer but this goes online to download and install the prerequisites. In our case, we are using a Hyper-V virtual machine which is not connected to the internet.

One would expect to find the list of prerequisites, copy them over to the server and simply install them manually. This is exactly what I did. Only to find out that this has problems.

MANUALLY INSTALLING SHAREPOINT 2013 PREREQUISITES DOS NOT WORK

Now first of all, you will not be able to copy your files across to the virtual machine. In Hyper-V you are not allowed to simply copy and paste things from the host machine. I can think of there ways one can achieve getting files onto the server:

· Create an Internal virtual switch and share a folder on the host machine, open the share from the Virtual Machine (VM)

· Again Create the Internal Switch and use Remote Desktop to RDP to the machine and share host machine local drives

· Create an External switch to connect to the internet and use the cloud

I have used the first two approaches. You can go to the Hyper-V manager and use the Action menu to open the Switch Manager where you can create an Internal Switch. Simply create an internal switch. Then go to the Hyper-V manager and select the VM and either right click or use the Action menu while selected to open the Settings.

Select "Add Hardware" on the left and select "Network Adapter" on the right. Select the Internal Switch you have just created.

Now, you can remote to the machine. When I have created my machine the machine was given some default name, I have simply got the machine name from the server by first logging to the server by double clicking the VM in the Hyper-V manager.

Once connectivity is sorted, I have manually installed the prerequisites on the VM and I have right clicked on my DVD drive on the VM Windows Server 2012 and run the SharePoint 2013 Installer only to find out that the SharePoint 2013 Installer does not like manually installing the prerequisites.  Please see below a different way of installing the prerequisites by a script.  I have tried the scripts and hit the problem with machine constantly restarting and there is a Known Issues section copied from the link given which is at the end of this article to sort this issue with the script approach. 

When I tried to simply download all the prerequisites and installed them manually on the server, and stareted the SharePoint 2013 installer, The SharePoint 2013 installer was saying that the AppFabric was installed on the server, I must uninstall AppFabric and run prerequisites installer to install it.

I have uninstalled the AppFabric. And this time I have found out that the SharePoint 2013 prerequisites installer activates and configures certain things, so, I have found the pameters to run the AppFabric installer I have downloaded from the command line, here is what I have run:

WindowsServerAppFabricSetup_x64.exe /i CacheClient, CachingService, CacheAdmin /gac

This time it has not installed at all, there was an errror.

I have found out that one of my environment variables PSModulePath

was corrupted. I opened my Environment Variable and found out that there was a double quote " at the end of the value and deleted this double quote. Then I have run the script above to install the AppFabric and it worked.

I have then run the SharePoint installer from the ISO and it has installed.

Resources

Here is a good link to information on how to install pre-requisites, beware though when the commandline version or PowerShell is run the installer simply keeps restarting the machine, to get around this issue see the Known Issues section in the article below. Also, I have run command line and in my case AppFabric installation was not accepted by SharePoint 2013 Installer, I had to manually uninstall and deal with the Environment Variable issue manually as mentioned above. I would leave AppFabric out of the script and run the line I have above to install it:

http://technet.microsoft.com/en-us/library/ff686793.aspx

The information below provides all the needed switches and parameters for scripts.

Prerequisite installer operations and command-line options

List of Prerequisites (download them all to a folder and share with the VM or Remote to the VM and copy them to the server)

You can run prerequisiteinstaller.exe at a command prompt with the following options. When you run prerequisiteinstaller.exe at a command prompt, you may be asked to restart the server one or more times during the installation process. After rebooting, you should continue the prerequisite installation by running prerequisiteinstaller.exe with the /continue option.

/? Display command-line options

/continue This is used to tell the installer that it is continuing from a restart

/unattended No user interaction

The installer installs from the file that you specify in the command-line options described in the following list. In this list, <file> signifies the file from which you want to install. If you do not specify the <file> option, the installer downloads the file from the Internet and installs it. If the option does not apply to the current operating system, it is ignored.

/SQLNCli:<file> Install Microsoft SQL Server 2008 SP1 Native Client from <file>

/PowerShell:<file> Install Windows Management Framework 3.0 from <file>

/NETFX:<file> Install Microsoft .NET Framework version 4.5 from <file>

/IDFX:<file> Install Windows Identity Foundation (KB974405) from <file>

/IDFX11:<file> Install Windows Identity Foundation v1.1 from <file>

/Sync:<file> Install Microsoft Sync Framework Runtime SP1 v1.0 (x64) from <file>

/AppFabric:<file> Install Windows Server AppFabric from <file> (AppFabric must be installed with the options /i CacheClient,CachingService,CacheAdmin /gac)

/KB2671763:<file> Install Microsoft AppFabric 1.1 for Windows Server (AppFabric 1.1) from <file>

/MSIPCClient:<file> Install Microsoft Information Protection and Control Client from <file>

/WCFDataServices:<file> Install Microsoft WCF Data Services from <file>

Installation options

Certain prerequisites are installed by the prerequisite installer with specific options. Those prerequisites with specific installation options are listed below with the options that are used by the prerequisite installer.

Windows AppFabric

/i CacheClient,CachingService,CacheAdmin /gac

Microsoft WCF Data Services

/quiet

The prerequisite installer creates log files at %TEMP%\prerequisiteinstaller.<date>.<time>.log. You can check these log files for specific details about all changes the installer makes to the target computer.

http://technet.microsoft.com/en-us/library/cc262485.aspx

 

Known issues (How to fix restarting issue with installer)

There are two known issues that affect the use of an arguments file:

  • Using line breaks in the arguments file

    If you create an arguments file and use line breaks to put each switch and argument on a separate line, the prerequisite installer fails. The workaround is to enter all the switch and argument pairs on a single line.

  • After a computer restart, the arguments file is not used

    After a restart, PrerequisiteInstaller.exe executes the startup command file, which contains a /continue flag. The /continue flag forces the installer to ignore the arguments file.

    You must prevent a restart by deleting the startup task in this command file by using one of the following options:

    Option 1

    1. Run PrerequisiteInstaller.exe by double-clicking it. The program will display the first screen with the list of prerequisites.

    2. Click Cancel. PrerequisiteInstaller.exe deletes the startup task.

    Option 2

    1. From the Start menu, choose Run and then type regedit to open the registry.

    2. Open the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders.

    3. Check the value for "Common Startup". This shows the directory where the startup tasks are listed.

    4. Close the registry editor without making any changes.

    5. Navigate to the startup directory, which is usually <systemdir>\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup.

    6. Delete the startup task by deleting "SharePointServerPreparationToolStartup_0FF1CE14-0000-0000-0000-000000000000.cmd".

source: http://technet.microsoft.com/en-us/library/ff686793.aspx


Viewing all articles
Browse latest Browse all 50

Trending Articles