search

brianlala / AutoSPInstaller

Automated SharePoint 2010/2013/2016/2019/SE PowerShell-based installation script.
https://autospinstaller.com
MIT License
171 stars 81 forks source link

v3.99.60 fails to install binaries #27

Open Kettoch opened 6 years ago

Kettoch commented 6 years ago

Clean run fails to copy the config file to the local directory so never creates the XML files needed to start the binary installation

LINE 276 should use $env:TEMP and not $env:dp0 LINE 279 should use $env:TEMP and not $env:dp0

Kettoch commented 6 years ago

Sorry, from AutoSPInstallerModule.psm1

brianlala commented 6 years ago

I just had a colleague run into a similar issue. The confusion lies in the fact that we have the 'master' AutoSPInstaller*.XML file (with all the install/account/app/service parameters etc.), and also the setup XML file that's used for installing the binaries in an unattended fashion.

Now, in the overwhelming majority of cases, AutoSPInstaller itself generates the setup XML, and includes the product key you provided in the master XML. But it seems sometimes the ConfigFile element points to a pre-existing setup XML (either the defaulit "config-AutoSPInstaller.xml", or one of your choosing. And if this setup XML includes no or an invalid PID, then the process stalls and prompts you for one.

Hope this makes sense.

iamguptarishi commented 6 years ago

I am trying to install SP 2016 Single server Farm using this script. I have created xml file using https://autospinstaller.com/FarmConfiguration and specified the KEY in the file. When I run the bat file it prompts me to enter PIDKey and specify all other configurations. Am I missing anything?

existentia commented 5 years ago

I am trying to install SP 2016 Single server Farm using this script. I have created xml file using https://autospinstaller.com/FarmConfiguration and specified the KEY in the file. When I run the bat file it prompts me to enter PIDKey and specify all other configurations. Am I missing anything?

I had the same issue and I made the mistake of updating the value to be the same name as my AutoSPInstaller XML config file that I had customised for my SP 2016 single server farm. Once I changed this value back to the default (config-AutoSPInstaller.xml), it worked fine.