Skip to content

Create Service Applications, Web Applications, and Site Collections for a Dev SP2016 Farm

License

Notifications You must be signed in to change notification settings

veronicageek/Dev-SPFarm-2016

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Dev-SPFarm-2016

Summary

Create Service Applications, Web Applications, and Site Collections for a development single server SharePoint 2016 farm.

Assumptions

  • SharePoint Server 2016 is installed, and Central Administration website is accessible.
  • No other databases are present except the SP Admin Content database & the SP Config database.
  • SharePoint Server is allowed to "communicate" with the database server (firewall rule)
  • Logged into the SharePoint Server 2016 with the "SPInstall" account
  • Application Pool account is already created (if not added in SharePoint as a managed account, the script will try to add it for you.)

What will the script create?

Service Applications

The following Service Applications (SA) will be created:

  • Business Data Connectivity
  • Managed Metadata
  • State Service
  • Usage & Health Data Collection
  • User Profile (UPSA)
  • Search (all components on one server)
  • App Management
  • Word Automation
  • Machine Translation

Each Service Application can be commented out in the script if not needed (e.g.: Word Automation).

Web Applications

The following Web Applications will be created:

  • Portal
  • Sites
  • Search

Site Collections

The following Site Collections will be created:

  • Portal (Team Site template under the Portal Web Application)
  • Sites (Team Site template under the Sites Web Application)
  • Enterprise Search (Enterprise Search Center template under the Search Web Application)

Run the script

  • The script should be run on the SharePoint 2016 Server.
  • The script can be run from the SharePoint Management Shell, or from the regular PowerShell console (Get-PSSnapin will be checked).
  • The -DBServerName parameter uses <Server\Instance> or can be SQLAlias

Running the script:

.\DevSPFarm_2016 -DBServerName <Server\Instance> -LocalDomain "<myDomain.com>" -AppPoolAcct <SPAppPool_Acct> -SPInstallAcct <SPInstall_Acct>

Examples:

.\DevSPFarm_2016 -DBServerName DCSQL\SP01 -LocalDomain "contoso.com" -AppPoolAcct SPAppPool -SPInstallAcct SPInstall

or

.\DevSPFarm_2016 -DBServerName DCSQL02 -LocalDomain "contoso.net" -AppPoolAcct spapppool -SPInstallAcct spinstall

Artifacts

The following artifacts are integrated in the script:

  • Check if the Microsoft.SharePoint.PowerShell snapin is present
  • Check if the Application Pool account is registered in SharePoint as managed account
  • Will log a transcript (using Start-Transcript and Stop-Transcript)
  • Progress bar at the top to know what's happening
  • Will display at the end, how long the script took to run

Screenshots

Please have a look at the Screenshots folder.

Disclaimer

SCRIPT IS PROVIDED AS-IS WITHOUT WARRANTY OF ANY KIND, AND IS MEANT FOR DEVELOPMENT / TESTING PURPOSES.

About

Create Service Applications, Web Applications, and Site Collections for a Dev SP2016 Farm

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published