Quantcast
Channel: AutoSPInstaller
Viewing all 2279 articles
Browse latest View live
↧

Updated Wiki: Home

May 20, 2015, 6:57 am
$
0
0

Project Description
Automated SharePoint 2010/2013 PowerShell-based installation script.

Introducing AutoSPInstaller v3 with numerous enhancements including:

  • Granular SQL server assignment and aliasing for (almost) every service/web app (for control freaks)
  • Centralized, remote installation to all farm servers
  • Ability to specify any XML input file, by passing it as an argument to AutoSPInstallerLaunch.bat
  • Several tweaks & fixes
  • Experimental support for SharePoint Foundation 2013 (as of 3.98 release)

AutoSPInstaller works with SharePoint 2013 (including SP1) and SharePoint 2010 with Service Pack 1 & 2. It takes advantage of some of the cmdlet updates in the newer SharePoint releases, while remaining largely backward-compatible older versions.

Newer versions often include updates to the input file XML schema, so make sure you compare any of your existing XML files to the newest AutoSPInstallerInput.XML. See below for highlights of changes in v3.x.

AutoSPInstaller has been used as the go-to SharePoint installation method for hundreds of SharePoint practitioners & partners worldwide! If you or your organization find AutoSPInstaller useful, making a donation (any amount) is a great way to support the ongoing development & improvement of the project.

Donate to AutoSPInstaller!

Also be sure to check out the new AutoSPInstaller Online - it's AutoSPInstallerGUI in a browser (& on steroids!)

New! Frequently Asked Questions

This project consists of PowerShell scripts, an XML input file, and a standard windows batch file (to kick off the process) which together provide a quick and near-unattended installation and initial configuration (Service Apps, My Sites) of Microsoft SharePoint Server 2010/2013. Works on Windows 2008 (though I hardly test on that OS these days), 2008 R2 and Windows 2012 / 2012 R2 (x64 only of course).

Perfect for repeated Virtual Machine-based installs/tear-downs, etc., but also great for production installs where you want to guarantee consistency and minimize data entry glitches. The immediate value is for installing and configuring the first/only server in a farm, but also supports using either server-specific input files or a single, all-encompassing input file for running the script on all farm servers (with parameters - e.g. for the service apps - set according to your desired topology).

"But doesn't SharePoint 2010 have a nice wizard now that does all this for me??" - Yes, and it's a huge improvement over what was available in MOSS 2007. However if you've ever seen the 'DBA nightmare' left behind on your SQL server after the Farm Configuration Wizard has completed (GUID'ed databases with inconsistent naming, etc.):



...then you'll see the value in having consistently-named but automatically-created databases:

DatabaseList-Clean

The scripts (Franken-scripts, really...) leverage previously-available resources (as PowerShell has now taken its place asthe automation platform for SharePoint) such as: Zach Rosenfield's blog, Jos Verlinde's script for creating a Farm, Gary Lapointe's Enterprise Search script functions and other miscellaneous tidbits in the wild.

The scripted process will:</form>

  • Re-launch itself in an elevated process to deal with User Access Control
  • Check whether the target server is running Windows 2008 or 2008 R2
  • Prompt you to enter allmost (in progress) service accounts, passwords and the farm passphrase, unless you opt to just specify them in the AutoSPInstallerInput.xml
  • Validate connectivity and permissions to your SQL instance/alias
  • Validate the farm passphrase (for complexity), as well as the service account/password combinations specified in the input XML file
  • Automatically download and install platform-specific pre-requisites (e.g. IIS, .Net Framework) using the SP2010 Prerequisiteinstaller.exe. You can also pre-download all the prerequisites/hotfixes usingthis script, then specify <OfflineInstall>true</OfflineInstall> in your AutoSPInstallerInput.xml instead of having Prerequisiteinstaller try to download fixes at script runtime.
  • Optionally disable some unnecessary Windows services, CRL checking and the dreaded IE Enhanced Security Configuration
  • Install the SP2010 binaries using an (optionally, server-specific) config.xml for input
  • Optionally install the Office Web Applications (OWA) binaries using config-OWA.xml for input
  • Create the Farm (Config & Central Admin content databases, Central Admin site, help collections, etc.)
  • Optionally configure and start many SharePoint services and service applications; currently the script can provision:
    • User Profile Service Application
    • User Profile Synchronization Service
    • Metadata Service Application
    • SharePoint Foundation User Code Service
    • State Service Application
    • Usage and Health Service Application
    • PowerPivot Service Application (removed due to complexity/misunderstandings around order of installation etc.)
    • Secure Store Service
    • Enterprise Search Service Application
    • Web Analytics Service Application
    • Outgoing Email
    • Business Data Connectivity Service Application
    • Excel Service Application
    • Access Service Application
    • PerformancePoint Service Application
    • Visio Graphics Service Application
    • Word Automation (Conversion) Service Application
    • The Office Web Applications service apps:
      • PowerPoint Service Application
      • Word Viewing Service Application
      • Excel Service Application (if not already provisioned by virtue of having an Enterprise license)
  • Create the main Portal web app and site collection (will try to provision and/or assign a certificate, too - all you need is an https://-based URL in the input XML)
  • Create/configure your My Sites web app and site collection (will also try to provision and/or assign a certificate if you have an https://-based URL in the Input XML)
  • Configure paths and options for both IIS and SharePoint (ULS) logging according to your preferences
  • (NEW) Discover other target servers in your farm (based on values in AutoSPInstallerInput.xml) and remote into each of them to perform the installation process (if <RemoteInstall> istrue)
  • Configure PDF indexing and icon display within SharePoint – effectively resolving what many consider to be a long-standing omission in the product in just a few seconds
  • Optionally install ForeFront Protection 2010 for SharePoint if the binaries are found in the correct path (see below)
  • Launch IE to display Central Administration, Portal and My Sites, and view the results of your hard work (just in time for your return from lunch)
  • Log all activity to a file on the current user's desktop, and pop open the log file for review when finished.

There are several input parameters to define in the input XML file (which illustrates how much stuff you really have to plan & gather during a regular SharePoint install). However this is a one-time-per-install effort, and the trade-off includes hours saved and better spent elsewhere (see lunch above) and an avoidance of the risks involved (typos, missed settings etc.) during manual installations.

New in v3:

  • Centralized, remote install of every SharePoint server in your farm using PowerShell remoting
  • Support for parallel binary installations, whether remote install is enabled or not (useful for speeding up multi-server farm installs)
  • Ability to specify a different SQL server/instance for each web application and service application, plus support for creating an alias for each SQL instance
  • Screen output and log both now display the elapsed time to install SharePoint and Office Web App binaries
  • Specify an arbitrary XML input file by passing the XML file name as an argument, or just dragging it onto AutoSPInstallerLaunch.bat

The full v3 change log can be found within the CodePlex source code changesets for the project. Also, see the post on my blog at spinsiders.com that provides an overview of the new features & fixes.

New in v2.5:
The ability to use a single AutoSPInstallerInput.XML file for your entire farm, and simply include the names of servers (comma-delimited) on which you want particular service instances or service applications installed. This works by using the Provision="" and Start="" attributes; for example, to provision the managed metadata service on your 2 app servers, you would specify:

<ManagedMetadataServiceApp Provision="SPAPPSRV1, SPAPPSRV2"
...

Further, the old way of specifying <ManagedMetadataServiceApp Provision="true"... still works, if you want to continue using a different XML input file for each server.

See the release notes associated with the original 2.5 changeset here for a more complete list of changes.

New in v2:

  • MAJOR code and XML schema refactoring effort by Andrew Woodward of 21apps to enable (among other things) easier editing and extending via a custom functions script file.
  • Both the launch batch file and the User Profile Service App creation (as farm account)self-elevate so no more need to right-click, Run as Administrator to successfully run AutoSPInstaller on a server with User Access Control (UAC) enabled!
  • Enterprise Search now properly sets both the service account and the crawl (content access) account
  • Much better multi-server farm support. Services can be tweaked to start on the servers you wish, and service applications won't be erroneously re-created on subsequent servers, etc.
  • Portal super user and super reader accounts can now be configured per best practices
  • Overall the install experience and results are more in line with community best practices; as always, this is a community-inspired and driven effort!

In addition to the scripts, you should create an installation source (local or shared) containingthe entire extracted contents of the SP201x install package. The zip package will by default create most of this folder structure when you extract it. When you're done, your folder structure should look something like this (Note: updated for v3):

\SP\AutoSPInstaller\AutoSPInstallerLaunch.bat
\SP\AutoSPInstaller\AutoSPInstallerInput.xml
\SP\AutoSPInstaller\AutoSPInstallerMain.ps1
\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1
\SP\AutoSPInstaller\AutoSPInstallerFunctionsCustom.ps1
\SP\AutoSPInstaller\AutoSPInstallerConfigureRemoteTarget.ps1
\SP\AutoSPInstaller\config.xml
\SP\201x\SharePoint\<installation files & folders>
\SP\201x\SharePoint\PreRequisiteInstallerFiles\
\SP\201x\SharePoint\Updates\ (extract Service Pack + Cumulative Updates here. NOTE not all updates support slipstreaming!)
\SP\2013\ProjectServer\ (optional; copy/extract the contents of the Project Server 2013 DVD/ISO here)
\SP\2013\ProjectServer\Updates (optional, for slipstreaming Service Packs and Public/Cumulative Updates. NOTE not all updates support slipstreaming!)

\SP\201x\LanguagePacks\xx-xx\ (optional)
\SP\201x\LanguagePacks\xx-xx\Updates\ (optional; extract Language Pack Service Pack / Cumulative Updates here)
OR
\SP\201x\LanguagePacks\<ServerLanguagePack_XX-XX.exe> (optional)
\SP\2010\OfficeWebApps\ (optional; only required/supported with SP2010)
\SP\2010\PDF\ (optional; only required/supported with SP2010)
\SP\2010\ForeFront\<ForeFront Protection 2010 for SharePoint install files> (optional, only required/supported with SP2010)

Note that x in the paths above is a0 or a 3 depending on whether you're installing SP2010 or SP2013. Spaces in the path to AutoSPInstallerLaunch.bat will cause the script to blow up, so avoid them.

Useful references:

  • Config.xml reference (SharePoint Server)
  • List of SharePoint Templates Codes and description
  • ULSViewer - best SharePoint log viewer out there, displays events in real-time and super useful for troubleshooting farm, service and service application provisioning issues.
  • I also highly recommend slipstreaming SharePoint 2010 service packs, cumulative updates and hotfixes into your installation source too, to further automate the process. Just place extracted patches in the\Updates\ path listed above, and they'll be automatically applied during the SharePoint binary installation process! Todd Klindt provides a great overview of the processhere.


Finally, I highly recommend working on your XML input file using a good editor like Notepad++ or good old Visual Studio - this helps a ton, especially to highlight any errors.Be especially mindful of invalid characters such as $ & " in your passwords etc.! Many script blow-up errors can be attributed to illegal characters or syntax errors in the XML. Finally, once you've populated your XML file with your environment/server specifics and before you attempt to run the script, pass the XML through a validator likethis.

↧
Search

Commented Issue: The Secure Store Service is not accessible [17861]

May 21, 2015, 6:06 am
$
0
0
Hello and Regards,
 
When the script is attempting to create the Excel, Visio or or Performance Point service applications I always get this error on the first execution of the script. If I immediately run the script again everything works. I verified that the Secure store Application is created via the "Function CreateSecureStoreServiceApp" runs successfully. The error is always on the Excel, Visio, Performance Point Functions in the following area
 
If ($secureStoreApp -eq $null) {
# Doesn't exist so create.
Write-Host -ForegroundColor White " - Creating Secure Store Application..."
$secureStoreApp = New-SPSecureStoreApplication -ServiceContext $context `
-TargetApplication $secureStoreTargetApp `
-Administrator $adminPrincipal `
-CredentialsOwnerGroup $groupClaim `
-Fields $fields
}
 
It fails on
 
 
$secureStoreApp = New-SPSecureStoreApplication
 
The error I get is below
 
The Secure Store Service application sp_svc_securestore_proxy_1s1 is not accessible. The full exception text is: There was no endpoint listening at https://sp2010:32844/2515e41502ee4dc5bc10b99d1529a24d/SecureStoreService.svc/https that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
 
Again if I run it again it works.
 
regards and thanks
Comments: ** Comment from web user: SamJo **

Hi,

i know this is an elder post, but today i ran into this issue on installing a SP2010 dev environment too and found a simple solution:
After several tries and asking auntie Google in the end i just removed the Secure Store Service Application from the Manage Service Applications site in Central Administration and re-ran AutoSPInstaller successfully!

Btw.: this issue is not caused by AutoSPInstaller script. After not having found a real explanation to this i guess it has bin caused by a hiccup as we all would have seen several times on a SharePoint server ;-)

Hope it helps others too!

BR,
Sam

↧
↧

New Post: AutoSPInstaller Online xml file cannot Connect to Database Server

May 22, 2015, 4:28 am
$
0
0
We have encountered an issue while running the AutoSPInstallerLaunch bat file. Our sharepoint server is unable to connect to the database server even though the alias are correctly configured. Please note that we are able to connect to the database on our first run of the script (using the xml generated from the AutoSPInstaller Online) last May 18, 2015. But since May 19 when we tried to run it again, we are having this issue. We already tested it on another server and the same issue happened. Hope you can check as this might be a product bug. Please help us.
<Farm>
    <Passphrase>Accenture01</Passphrase>
    <Account LeaveInLocalAdmins="false" AddToLocalAdminsDuringSetup="true">
        <Username>ds\sharepoint.lab.admin</Username>
        <Password>mypassword</Password>
    </Account>
    <CentralAdmin Provision="localhost">
        <Database>Content_CentralAdmin</Database>
        <Port>2013</Port>
        <UseSSL>false</UseSSL>
    </CentralAdmin>
    <Database>
        <DBServer>SP2013-SQL2014</DBServer>
        <DBAlias DBPort="" DBInstance="SP2013-SQL2014\MSSQLSERVER" Create="true" />
        <DBPrefix>AutoSPInstaller</DBPrefix>
        <ConfigDB>Config</ConfigDB>
    </Database>
↧

New Post: AutoSPInstaller Online xml file cannot Connect to Database Server

May 22, 2015, 6:27 am
$
0
0
I notice the name you chose for the alias (SP2013-SQL2014) is the same as the actual SQL server name. Normally, you wouldn't do this, since part of the reason for an alias is to de-couple the real SQL server name from the name we use to reference it. But anyhow, can you edit your XML to display as follows instead (although it really shouldn't make any difference):
<Database>
       <DBServer>SP2013-SQL2014</DBServer>
        <DBAlias Create="true"
                        DBInstance="SP2013-SQL2014\MSSQLSERVER"
                        DBPort="" />
        <DBPrefix>AutoSPInstaller</DBPrefix>
        <ConfigDB>Config</ConfigDB>
     </Database>
If this doesn't work, I would compare your version of the XML that did work prior with the newer version that's causing trouble to see where the discrepancy could be.

Brian
↧

New Post: AutoSPInstaller Online xml file cannot Connect to Database Server

May 22, 2015, 7:27 am
$
0
0
Thanks for your quick reply. Upon checking on the XML that worked, one difference I noticed is that on the DBPort field I specified the port number (I used 1433). On the latest one I didn't put anything as the web UI specified that if we leave it blank it will use the default port 1433. I tested it again now specifying the port and it was successful connecting to the database.
<Database>
        <DBServer>SP2013-SQL2014</DBServer>
        <DBAlias DBPort="1433" DBInstance="SP2013-SQL2014\MYSSQLSERVER" Create="true" />
        <DBPrefix>AutoSPInstaller</DBPrefix>
        <ConfigDB>Config</ConfigDB>
    </Database>
↧
↧

New Post: New-SPConfigurationDatabase : Value cannot be null

May 22, 2015, 10:20 am
$
0
0
I have been getting the following error, that I do not understand how to fix. The Configuration Database appears to be created.

PS>TerminatingError(Get-SPFarm): "Cannot access the local farm. Verify that the local farm is properly configured, currently available, and that you have the appropriate permissions to access the database before trying again."
New-SPConfigurationDatabase : Value cannot be null.
Parameter name: password
At C:\Temp\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:1652 char:13
  • New-SPConfigurationDatabase -DatabaseName "$configDB" -DatabaseServe ...
  • ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : InvalidData: (Microsoft.Share...urationDatabase:SPCmdletNewSPConfigurationDatabase) [New
      -SPConfigurationDatabase], ArgumentNullException
    • FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPConfigurationDatabase
PS>TerminatingError(): " - Error creating new farm configuration database"
TerminatingError(): " - Error creating new farm configuration database"
Any assistance to correct this would be appreciated.
↧

New Post: New-SPConfigurationDatabase : Value cannot be null

May 25, 2015, 4:59 am
$
0
0
Few Questions:
Do you face the same error if you are using Configuration Wizard? If yes, try to disconnect that server from the farm, manually deleted the the configuration database and any other database created by the install and retry running the installer?
Do you are account used for running AutoSPInstaller have both DBCreator and SecurityAdmin on the SQL Server instance?
How many servers are there in the farm? If more than one, are you facing this error for the first server or subsequent one?

If you still have the issue, it will be helpful to share your XML.
↧

New Post: New-SPConfigurationDatabase : Value cannot be null

May 25, 2015, 7:34 am
$
0
0
The Configuration Wizard is also failing with more detail in the Event logs:

Failed to create the configuration database.
An exception of type System.ArgumentNullException was thrown. Additional exception information: Value cannot be null.
Parameter name: password
System.ArgumentNullException: Value cannot be null.
Parameter name: password
at Microsoft.SharePoint.Administration.SPFarm.ValidateLogonAccount(String& username, SecureString password)
at Microsoft.SharePoint.Administration.SPManagedAccount.SetPassword(SecureString value)
at Microsoft.SharePoint.Administration.SPApplicationPool..ctor(String name, SPWebService service)
at Microsoft.SharePoint.Administration.SPWebApplication.CreateDefaultInstance(SPWebService service, Guid id, String applicationPoolId, SPProcessAccount processAccount, String iisServerComment, Boolean secureSocketsLayer, String iisHostHeader, Int32 iisPort, Boolean iisAllowAnonymous, DirectoryInfo iisRootDirectory, Uri defaultZoneUri, Boolean iisEnsureNTLM, Boolean createDatabase, String databaseServer, String databaseName, String databaseUsername, String databasePassword, SPSearchServiceInstance searchServiceInstance, Boolean autoActivateFeatures)
at Microsoft.SharePoint.Administration.SPWebApplication.CreateDefaultInstance(SPWebService service, Guid id, String applicationPoolId, IdentityType identityType, String applicationPoolUsername, SecureString applicationPoolPassword, String iisServerComment, Boolean secureSocketsLayer, String iisHostHeader, Int32 iisPort, Boolean iisAllowAnonymous, DirectoryInfo iisRootDirectory, Uri defaultZoneUri, Boolean iisEnsureNTLM, Boolean createDatabase, String databaseServer, String databaseName, String databaseUsername, String databasePassword, SPSearchServiceInstance searchServiceInstance, Boolean autoActivateFeatures)
at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.CreateDefaultInstance(SqlConnectionStringBuilder administrationContentDatabase, SPWebService adminService, IdentityType identityType, String farmUser, SecureString farmPassword)
at Microsoft.SharePoint.Administration.SPFarm.CreateAdministrationWebService(SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword)
at Microsoft.SharePoint.Administration.SPFarm.CreateBasicServices(SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword)
at Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder configurationDatabase, SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword, SecureString masterPassphrase)
at Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder configurationDatabase, SqlConnectionStringBuilder administrationContentDatabase, String farmUser, SecureString farmPassword, SecureString masterPassphrase)
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
↧
Search

New Post: New-SPConfigurationDatabase : Value cannot be null

May 25, 2015, 7:35 am
↧
↧

Source code checked in, #114045

June 1, 2015, 8:27 am
$
0
0
Changes in this release: - Updates to XML version, now at 3.99 to reflect conversion of a lot of attributes to child elements - makes comparison of XML files easier due to formatting. Also for better experience with forthcoming AutoSPInstaller Online (https://autospinstaller.azurewebsites.net). - Corresponding updates to script code to support above change to child elements - Added code to allow specifying site collection compatibility level; XML has not been updated yet with the required attribute though. - Tweaks to function Configure-PDFSearchAndIcon for SP2013 - Other minor changes to AutoSPInstallerFunctions.ps1
↧

Released: AutoSPInstaller for SharePoint 2010 + 2013 (Jun 01, 2015)

June 1, 2015, 8:39 am
$
0
0
Package consisting of AutoSPInstaller (v3.x) files. The SharePoint / CodePlex community as always deserves big thanks for support, input and contributions! This release is stable for both SP2010and SP2013 and supports the latest service packs available for each (currently SP2 for 2010 and SP1 for 2013). Also, SharePoint 2010 w/SP2 is now supported on Windows 2012!

Please see the Changesets for a history of changes up to and including the latest release, as well as theFAQ.

Also, have a read through the Known Issues, particularly if you are going to take advantage of the new v3 remote functionality.
↧

Updated Release: AutoSPInstaller for SharePoint 2010 + 2013 (Jun 01, 2015)

June 1, 2015, 8:39 am
$
0
0
Package consisting of AutoSPInstaller (v3.x) files. The SharePoint / CodePlex community as always deserves big thanks for support, input and contributions! This release is stable for both SP2010 and SP2013 and supports the latest service packs available for each (currently SP2 for 2010 and SP1 for 2013). Also, SharePoint 2010 w/SP2 is now supported on Windows 2012!

Please see the Changesets for a history of changes up to and including the latest release, as well as the FAQ.

Also, have a read through the Known Issues, particularly if you are going to take advantage of the new v3 remote functionality.
↧

Created Unassigned: WARNING: Cannot locate SharePoint binaries [21889]

June 2, 2015, 8:13 am
$
0
0
WARNING: Cannot locate SharePoint binaries; please check that the files are in the \SharePoint subfolder as per new folder structure.

Hi All,

I am getting the error above when attempting to start autospinstaller. I already verified the folder directory should be correct, according to the AutoSPInstallerFolderStructure.txt file in the autospinstaller directory (SP\2013\SharePoint) but my system cannot seem to locate the folder.

P.S. I am using Autospinstaller 3.99 with the latest xml file built from the web.

Thanks!,
Chris
↧
↧

Created Unassigned: Script halted on creating portal site collection [21890]

June 3, 2015, 12:04 am
$
0
0
hi,


The script succesfully creates the webapplication but halts at the creation of the portal site collection.

Start of error: the server was unable to process the request due to an internal error.

Help would be very appreciated.


Greetings,
Pim
↧

Commented Unassigned: Script halted on creating portal site collection [21890]

June 3, 2015, 12:10 am
$
0
0
hi,


The script succesfully creates the webapplication but halts at the creation of the portal site collection.

Start of error: the server was unable to process the request due to an internal error.

Help would be very appreciated.


Greetings,
Pim
Comments: ** Comment from web user: TAITUN **

Succesfully created:

- IIS sites: Central Admin
- SQL Content databases: Config, Central Admin and Portal

My environment:

- Front/Backend: Server 2012 R2
- SQL 2008 R2

↧
Search

Commented Unassigned: WARNING: Cannot locate SharePoint binaries [21889]

June 3, 2015, 7:09 am
$
0
0
WARNING: Cannot locate SharePoint binaries; please check that the files are in the \SharePoint subfolder as per new folder structure.

Hi All,

I am getting the error above when attempting to start autospinstaller. I already verified the folder directory should be correct, according to the AutoSPInstallerFolderStructure.txt file in the autospinstaller directory (SP\2013\SharePoint) but my system cannot seem to locate the folder.

P.S. I am using Autospinstaller 3.99 with the latest xml file built from the web.

Thanks!,
Chris
Comments: ** Comment from web user: cralfano **

Issue solved. I found a problem in my config XML file that needed to be corrected.

↧

New Post: Cannot Locate SP Binaries - Cannot determine version of SharePoint setup binaries, and no Version was specific in xml

June 5, 2015, 12:36 pm
$
0
0
Thanks for the tip regarding invalid XML. Turns out I had an ampersand (&) in an auto-generated password.
↧
↧

Updated Wiki: Home

June 5, 2015, 7:21 pm
$
0
0

Project Description
Automated SharePoint 2010/2013 PowerShell-based installation script.

Introducing AutoSPInstaller v3 with numerous enhancements including:

  • Granular SQL server assignment and aliasing for (almost) every service/web app (for control freaks)
  • Centralized, remote installation to all farm servers
  • Ability to specify any XML input file, by passing it as an argument to AutoSPInstallerLaunch.bat
  • Several tweaks & fixes
  • Experimental support for SharePoint Foundation 2013 (as of 3.98 release)

AutoSPInstaller works with SharePoint 2013 (including SP1) and SharePoint 2010 with Service Pack 1 & 2. It takes advantage of some of the cmdlet updates in the newer SharePoint releases, while remaining largely backward-compatible older versions.

Newer versions often include updates to the input file XML schema, so make sure you compare any of your existing XML files to the newest AutoSPInstallerInput.XML. See below for highlights of changes in v3.x.

AutoSPInstaller has been used as the go-to SharePoint installation method for hundreds of SharePoint practitioners & partners worldwide! If you or your organization find AutoSPInstaller useful, making a donation (any amount) is a great way to support the ongoing development & improvement of the project.

Donate to AutoSPInstaller!

Also be sure to check out the new AutoSPInstaller Online - it's AutoSPInstallerGUI in a browser (& on steroids!)

New! Frequently Asked Questions

This project consists of PowerShell scripts, an XML input file, and a standard windows batch file (to kick off the process) which together provide a quick and near-unattended installation and initial configuration (Service Apps, My Sites) of Microsoft SharePoint Server 2010/2013. Works on Windows 2008 (though I hardly test on that OS these days), 2008 R2 and Windows 2012 / 2012 R2 (x64 only of course).

Perfect for repeated Virtual Machine-based installs/tear-downs, etc., but also great for production installs where you want to guarantee consistency and minimize data entry glitches. The immediate value is for installing and configuring the first/only server in a farm, but also supports using either server-specific input files or a single, all-encompassing input file for running the script on all farm servers (with parameters - e.g. for the service apps - set according to your desired topology).

"But doesn't SharePoint 2010 have a nice wizard now that does all this for me??" - Yes, and it's a huge improvement over what was available in MOSS 2007. However if you've ever seen the 'DBA nightmare' left behind on your SQL server after the Farm Configuration Wizard has completed (GUID'ed databases with inconsistent naming, etc.):



...then you'll see the value in having consistently-named but automatically-created databases:

DatabaseList-Clean

The scripts (Franken-scripts, really...) leverage previously-available resources (as PowerShell has now taken its place asthe automation platform for SharePoint) such as: Zach Rosenfield's blog, Jos Verlinde's script for creating a Farm, Gary Lapointe's Enterprise Search script functions and other miscellaneous tidbits in the wild.

The scripted process will:</form>

  • Re-launch itself in an elevated process to deal with User Access Control
  • Check whether the target server is running Windows 2008 or 2008 R2
  • Prompt you to enter allmost (in progress) service accounts, passwords and the farm passphrase, unless you opt to just specify them in the AutoSPInstallerInput.xml
  • Validate connectivity and permissions to your SQL instance/alias
  • Validate the farm passphrase (for complexity), as well as the service account/password combinations specified in the input XML file
  • Automatically download and install platform-specific pre-requisites (e.g. IIS, .Net Framework) using the SP2010 Prerequisiteinstaller.exe. You can also pre-download all the prerequisites/hotfixes usingthis script, then specify <OfflineInstall>true</OfflineInstall> in your AutoSPInstallerInput.xml instead of having Prerequisiteinstaller try to download fixes at script runtime.
  • Optionally disable some unnecessary Windows services, CRL checking and the dreaded IE Enhanced Security Configuration
  • Install the SP2010 binaries using an (optionally, server-specific) config.xml for input
  • Optionally install the Office Web Applications (OWA) binaries using config-OWA.xml for input
  • Create the Farm (Config & Central Admin content databases, Central Admin site, help collections, etc.)
  • Optionally configure and start many SharePoint services and service applications; currently the script can provision:
    • User Profile Service Application
    • User Profile Synchronization Service
    • Metadata Service Application
    • SharePoint Foundation User Code Service
    • State Service Application
    • Usage and Health Service Application
    • PowerPivot Service Application (removed due to complexity/misunderstandings around order of installation etc.)
    • Secure Store Service
    • Enterprise Search Service Application
    • Web Analytics Service Application
    • Outgoing Email
    • Business Data Connectivity Service Application
    • Excel Service Application
    • Access Service Application
    • PerformancePoint Service Application
    • Visio Graphics Service Application
    • Word Automation (Conversion) Service Application
    • The Office Web Applications service apps:
      • PowerPoint Service Application
      • Word Viewing Service Application
      • Excel Service Application (if not already provisioned by virtue of having an Enterprise license)
  • Create the main Portal web app and site collection (will try to provision and/or assign a certificate, too - all you need is an https://-based URL in the input XML)
  • Create/configure your My Sites web app and site collection (will also try to provision and/or assign a certificate if you have an https://-based URL in the Input XML)
  • Configure paths and options for both IIS and SharePoint (ULS) logging according to your preferences
  • (NEW) Discover other target servers in your farm (based on values in AutoSPInstallerInput.xml) and remote into each of them to perform the installation process (if <RemoteInstall> istrue)
  • Configure PDF indexing and icon display within SharePoint – effectively resolving what many consider to be a long-standing omission in the product in just a few seconds
  • Optionally install ForeFront Protection 2010 for SharePoint if the binaries are found in the correct path (see below)
  • Launch IE to display Central Administration, Portal and My Sites, and view the results of your hard work (just in time for your return from lunch)
  • Log all activity to a file on the current user's desktop, and pop open the log file for review when finished.

There are several input parameters to define in the input XML file (which illustrates how much stuff you really have to plan & gather during a regular SharePoint install). However this is a one-time-per-install effort, and the trade-off includes hours saved and better spent elsewhere (see lunch above) and an avoidance of the risks involved (typos, missed settings etc.) during manual installations.

New in v3:

  • Centralized, remote install of every SharePoint server in your farm using PowerShell remoting
  • Support for parallel binary installations, whether remote install is enabled or not (useful for speeding up multi-server farm installs)
  • Ability to specify a different SQL server/instance for each web application and service application, plus support for creating an alias for each SQL instance
  • Screen output and log both now display the elapsed time to install SharePoint and Office Web App binaries
  • Specify an arbitrary XML input file by passing the XML file name as an argument, or just dragging it onto AutoSPInstallerLaunch.bat

The full v3 change log can be found within the CodePlex source code changesets for the project. Also, see the post on my blog at spinsiders.com that provides an overview of the new features & fixes.

New in v2.5:
The ability to use a single AutoSPInstallerInput.XML file for your entire farm, and simply include the names of servers (comma-delimited) on which you want particular service instances or service applications installed. This works by using the Provision="" and Start="" attributes; for example, to provision the managed metadata service on your 2 app servers, you would specify:

<ManagedMetadataServiceApp Provision="SPAPPSRV1, SPAPPSRV2"
...

Further, the old way of specifying <ManagedMetadataServiceApp Provision="true"... still works, if you want to continue using a different XML input file for each server.

See the release notes associated with the original 2.5 changeset here for a more complete list of changes.

New in v2:

  • MAJOR code and XML schema refactoring effort by Andrew Woodward of 21apps to enable (among other things) easier editing and extending via a custom functions script file.
  • Both the launch batch file and the User Profile Service App creation (as farm account)self-elevate so no more need to right-click, Run as Administrator to successfully run AutoSPInstaller on a server with User Access Control (UAC) enabled!
  • Enterprise Search now properly sets both the service account and the crawl (content access) account
  • Much better multi-server farm support. Services can be tweaked to start on the servers you wish, and service applications won't be erroneously re-created on subsequent servers, etc.
  • Portal super user and super reader accounts can now be configured per best practices
  • Overall the install experience and results are more in line with community best practices; as always, this is a community-inspired and driven effort!

In addition to the scripts, you should create an installation source (local or shared) containingthe entire extracted contents of the SP201x install package. The zip package will by default create most of this folder structure when you extract it. When you're done, your folder structure should look something like this (Note: updated for v3):

\SP\AutoSPInstaller\AutoSPInstallerLaunch.bat
\SP\AutoSPInstaller\AutoSPInstallerInput.xml
\SP\AutoSPInstaller\AutoSPInstallerMain.ps1
\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1
\SP\AutoSPInstaller\AutoSPInstallerFunctionsCustom.ps1
\SP\AutoSPInstaller\AutoSPInstallerConfigureRemoteTarget.ps1
\SP\AutoSPInstaller\config.xml
\SP\201x\SharePoint\<installation files & folders>
\SP\201x\SharePoint\PreRequisiteInstallerFiles\
\SP\201x\SharePoint\Updates\ (extract Service Pack + Cumulative Updates here. NOTE not all updates support slipstreaming!)
\SP\2013\ProjectServer\ (optional; copy/extract the contents of the Project Server 2013 DVD/ISO here)
\SP\2013\ProjectServer\Updates (optional, for slipstreaming Service Packs and Public/Cumulative Updates. NOTE not all updates support slipstreaming!)

\SP\201x\LanguagePacks\xx-xx\ (optional)
\SP\201x\LanguagePacks\xx-xx\Updates\ (optional; extract Language Pack Service Pack / Cumulative Updates here)
OR
\SP\201x\LanguagePacks\<ServerLanguagePack_XX-XX.exe> (optional)
\SP\2010\OfficeWebApps\ (optional; only required/supported with SP2010)
\SP\2010\PDF\ (optional; only required/supported with SP2010)
\SP\2010\ForeFront\<ForeFront Protection 2010 for SharePoint install files> (optional, only required/supported with SP2010)

Note that x in the paths above is a0 or a 3 depending on whether you're installing SP2010 or SP2013. Spaces in the path to AutoSPInstallerLaunch.bat will cause the script to blow up, so avoid them.

Useful references:

  • Config.xml reference (SharePoint Server)
  • List of SharePoint Templates Codes and description
  • ULSViewer - best SharePoint log viewer out there, displays events in real-time and super useful for troubleshooting farm, service and service application provisioning issues.
  • I also highly recommend slipstreaming SharePoint 2010 service packs, cumulative updates and hotfixes into your installation source too, to further automate the process. Just place extracted patches in the\Updates\ path listed above, and they'll be automatically applied during the SharePoint binary installation process! Todd Klindt provides a great overview of the processhere.


Finally, I highly recommend working on your XML input file using a good editor like Notepad++ or good old Visual Studio - this helps a ton, especially to highlight any errors.Be especially mindful of invalid characters such as $ & " in your passwords etc.! Many script blow-up errors can be attributed to illegal characters or syntax errors in the XML. Finally, once you've populated your XML file with your environment/server specifics and before you attempt to run the script, pass the XML through a validator likethis.

↧

Updated Wiki: Documentation

June 5, 2015, 7:22 pm
$
0
0
Miscellaneous documentation, tips & tricks, best practices, etc.!

First & foremost - check the new FAQ

New! Is input XML editing driving you nuts? Looking for a slick graphical way to either produce a new XML file for your farm, or edit/verify an existing XML file? Check out AutoSPInstaller Online, created by the guru of AutoSPInstaller GUIs Ivan Josipovic& myself.
Current Documentation Wiki Pages:

Migrating an existing AutoSPInstallerInput.xml to updated format
Don't run AutoSPInstaller from a user folder!
Known Issues
Known Issues with SharePoint 2013
↧

Updated Wiki: FAQ

June 5, 2015, 7:24 pm
$
0
0

Frequently Asked Questions

  • Is there a friendlier way to edit the XML than good ol' Notepad/Visual Studio/etc.?
    • Yes - check out the new AutoSPInstaller Online. It includes real-time help/guidance, validation & smarts to avoid those "oops" moments during script run-time. We welcome your feedback!
  • Is this thing safe/ready/appropriate for Production?
    • It sure is! I've personally set up many live customer farms with AutoSPInstaller in the past few years. In fact it's even been used by organizations like CloudShare to create SharePoint VM templates. The standard caveats apply though: As the importance of your target farm increases, so should your level of knowledge about how to properly size, architect and build SharePoint. AutoSPInstaller does not mitigate this, it merely eases, standardizes and accelerates the process.
  • Does AutoSPInstaller support SharePoint Foundation?
    • Basically, no. Some folks have had success getting it to work by editing the script themselves (search thru the discussions to find examples) but as I (selfishly) have no need for SPF I have not spent any time researching this. If however someone puts forth a tried, tested & true patch that can (very) easily be integrated, I may consider including it.
  • Can I use AutoSPInstaller to install Office Web Apps 2013?
    • Office Web Apps 2013 (also known as WAC) is now a separate product which is not installed on the same server as SharePoint 2013. As it's technically-speaking no longer part of the SharePoint farm, and because of the complexity it would introduce, I've decided to leave Office Web Apps 2013 out of AutoSPInstaller for the time being.
  • What about the Request Management service (in SharePoint 2013)? Will it be included in AutoSPInstaller?
    • After a discussion with Spencer Harbar, it was agreed that it might be best to leave it out, as there can be some ramifications with provisioning it without full awareness of its intended use - e.g. by folks who want to blindly "turn everything on" in SharePoint 2013.
  • Where's all the #@)%#$ documentation??
  • My SharePoint server(s) and SQL instance are in different, untrusted domains. Can I use SQL authentication instead of Windows Integrated?
    • Although support for SQL auth in SharePoint (especially around things like the User Profile Service) has gotten better, AutoSPInstaller doesn't currently support connecting to your databases using anything other than Windows Integrated authentication. It certainly wouldn't be impossible to make the required modifications, but you'd have to do this yourself or reach out to the community for guidance.
  • I want to make a single/isolated configuration change to an existing SharePoint farm (e.g. provision a service application). Do I really need to re-run the whole script?
    • No - in fact you can usually just run individual functions to achieve what you're after by following the instructions here.
↧
Viewing all 2279 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>