none
SP2013 Installation using AutoSPInstaller, BUT, Product key dialog shows up during installation and stuck ?

    Question

  • Hello Forum,

    I wanna install simple single-server SP2013 farm (Enterprise edition) using the latest famous AutoSPInstaller script from CodePlex.

    I have created the XML configuration file using this cool tool (https://autospinstaller.com/), and I have checked several times that all values are 100% accurate.

    Nevertheless, When I run the script, Unfortunately at the stage: "- Installing SharePoint 2013 binaries......." the Product key dialog shows up. Why this this behavior?

     
    Shouldn't the installation proceeds smoothly by itself and picks the value from the XML file? Why it doesn't?


    One-Single farm Parameters:

    Windows Server 2012 R2
    User Access Control (UAC) is set to its Minimum “Never Notify”
    SQL Server 2012 SP2 and configured properly
    SP2013 media: SP1 Slipstream (Meaning the downloading ISO from MSDN contains SharePoint with SP1 together)


    The XML Config:

    <Configuration Environment="SP2013Farm" Version="3.99.51">
    <Install SPVersion="2013">
        <ConfigFile>SP2013Farm.xml</ConfigFile>
        <InstallDir>C:\Program Files\Microsoft Office Servers</InstallDir>
        <DataDir>C:\Program Files\Microsoft Office Servers\SharePoint2013\Data</DataDir>
        <PIDKey>MY-100%-CORRECT-KEY-VALUE</PIDKey>
        <SKU>Enterprise</SKU>
        <OfflineInstall>false</OfflineInstall>
        <PauseAfterInstall>false</PauseAfterInstall>
        <RemoteInstall Enable="false">
            <ParallelInstall>false</ParallelInstall>
        </RemoteInstall>
        <AutoAdminLogon Enable="true">
            <Password>P@ssword!</Password>
        </AutoAdminLogon>


    Could you help me out, Please ? Am I missing anything?

    Thank you all !


    Tuesday, September 22, 2015 6:30 PM

Answers

  • In the old versions of AutoSPInstaller we had to add the product key to the Config.XML file with the SharePoint binaries. Really, all AutoSPInstaller does is call standard PS cmdlets in a specified order. So, it is just calling the Install-SharePoint cmdlet. I've used AutoSPInstaller a lot and never run into this but if you want to try to work around it, I would try to add your product key to your config.xml file directly. If that doesn't work you can check the PS script that AutoSPInstaller uses to install the binaries see if for some reason it has the -PIDKey switch after the Install-SharePoint command. This will cause it to prompt for a product key during installation. Below is some info on the config.xml and Install-SharePoint command.

    http://www.informit.com/articles/article.aspx?p=1729267&seqNum=2


    Lance

    Tuesday, September 22, 2015 7:35 PM

All replies

  • In the old versions of AutoSPInstaller we had to add the product key to the Config.XML file with the SharePoint binaries. Really, all AutoSPInstaller does is call standard PS cmdlets in a specified order. So, it is just calling the Install-SharePoint cmdlet. I've used AutoSPInstaller a lot and never run into this but if you want to try to work around it, I would try to add your product key to your config.xml file directly. If that doesn't work you can check the PS script that AutoSPInstaller uses to install the binaries see if for some reason it has the -PIDKey switch after the Install-SharePoint command. This will cause it to prompt for a product key during installation. Below is some info on the config.xml and Install-SharePoint command.

    http://www.informit.com/articles/article.aspx?p=1729267&seqNum=2


    Lance

    Tuesday, September 22, 2015 7:35 PM
  • If you copy your config file contents into AutoSPInstallerInput.xml file and delete your config file from AutoSPInstaller folder the tool will not ask for Product Key. Looks like tool is confused between which file to use.
    Thursday, May 26, 2016 3:34 AM
  • AutoSPInstaller doesn't use the cmdlet referenced in the answer above. Rather it uses its own function, found in AutoSPInstallerFunctions.ps1, InstallSharePoint (no hyphen). It checks whether SharePoint is installed, and if not, executes Setup.exe from the SharePoint media.

    There is a discussion of the key prompt issue here, explaining that the Config.XML file used by SharePoint setup differs from the configuration file AutoSPInstaller uses.


    <font color="blue">If puzzles are good for your </font><font color="red">BRAIN</font><font color="blue"> then SharePoint will keep it really healthy!<br/> <hr> Ramona Maxwell MCPD <a href="http://sharepointsolver.com/index.php/All/?disp=authdir&author=218"> SharePoint</a> 2010, MCITP <a href="http://sqlsolver.com/index.php/All/?disp=authdir&author=218"> SQL Server</a> 2008</font>

    Friday, February 10, 2017 3:49 AM