Happy new year my ninja’s!!!
Going into the tail end of December, I was tasked with rebuilding a SharePoint 2013 environment as there were issues with the current farm that was deployed.
For starters, when using Network Load Balancing, specifically Windows Network Load Balancing, which has been around since Server 2000, its of vital importance that you ensure that the VLAN’s and Core Switches support Unicast and Multicast ARP (Address Resolution Protocol). What this does in short is allow requests to map from the virtual IP addresses to the multicast and or unicast MAC Address of the virtual IP associated with the hosts across the load balancer. If you want an exhaustive explanation of how Load Balancing works, read the article posted on MSDN.
Anyhow, back to AutoSPInstaller. For those who do not know what this is, its a deployment script created by Brian Lalancette back in 2009. Its the be all and end all of SharePoint deployment scripts. In recent years, Ivan Josipovic initially built a UI for configuration and in its current state, it is available online through AutoSPInstaller. It even works offline.
So, jump forward to the installation. There are a plethora of howto’s when using AutoSPInstaller to configure SharePoint and for the most part, all of them work.
What is missing is the following: (Not limited to though, these are the items i encountered, there may be more)
- In order to do remote installations (i.e. you have 4 servers in the farm and you want the installer to run from a single server you need to enable WinRM – Windows Remote Management tools for PowerShell so that you can execute scripts from the source server. Without this, the script will fail.
- Windows Server 2012 R2 automatic updates – By default, Windows Server 2012 R2 will install .NET version 4.6 and SharePoint will complain about requiring .NET 4.5.1. Microsoft has a workaround/fix, which does not work so dont bother trying it. What you need do is uninstall the update, switch off automatic updates, install SharePoint and then set the updates back to automatic afterwards. Firstly, find the version of .NET that has been installed, then hit the control panel and check installed updates and uninstall the corresponding KB that’s associated with the .NET version that was installed. You are going to have to Google to check the corresponding KB that matches your version of .NET.
- Copy the autoSPInstaller binaries to all the servers, it just makes things easier.
So for now, those are the Infrastructure related prerequisites that you must have sorted before you end up going around in circles when attempting to install SharePoint. This is also not specific to just AutoSPInstaller. If you use the default installer per server, you will encounter the .NET problem.
There are a ton of reasons why you want to use AutoSPInstaller, but I am not going to get into that right now.
Drop me a DM on Twitter if you have any questions.
Be cool my ninja’s.