I configured my AutoSPInstallerInput.xml to install a SharePoint farm with two SharePoint 2013 servers. One server is the application server and the other one is an WFE and active query component. I placed the AutoSPInstaller files on a network share.
I run the AutoSPInstaller from a third non-farm server so for both servers the installation process is done by powershell remoting (remote and parallel is set true in my AutoSPInstallerInput.xml).
Basically the AutoSPInstaller does a very good job on that, but there is one thing I really do not like:
No matter if you start from a patched or unpatched Windows Server 2012 there is a minimum of two restarts for every server when installing the prerequisites.
Already after the first reboot (when the PrerequisiteInsaller installs the necessary server roles and features, basically IIS and AppServer) the powershell remote session ends of cource. After the remote machine is back online the powershell remote session
is not reestablished, but the scripts start on the remote machine.
That is not what I would call a remote installation, because after that first reboot I have to go directly to every machine and finish the installation there.
For a start I found some workaround for that. Before starting the AutoSPInstaller I install all necessary server roles first on every server and then all SharePoint 2013 Prerequisites (http://social.technet.microsoft.com/wiki/contents/articles/14582.sharepoint-2013-install-prerequisites-offline-or-manually-on-windows-server-2012-a-comprehensive-guide.aspx
Unfortunately I am not very familiar with powershell remoting, so I still have to do some things manually on every server (maybe someone could script the remoting stuff around what is seen at the offline installation post, please).
After this is done it is possible to finish the AutoSPIntaller without any reboots on the remote machines and I can control the installation from one single point.
Of course the AutoSPInstaller can't do anything about these restarts, because they are simly needed.
But couldn't it reestablish the powershell remote session instead of starting the scripts on the remote server? That would be nice.