For a long time, SPDocKit has allowed farm configuration to be documented and exported in a Word document. But our customers wanted a little bit more. They wanted to know whether they can provision a new farm based on an existing farm. We thought about how to make this possible, then realized that there was no need for further consideration because an ultimate tool for farm provision already exists: AutoSPInstaller.
We added support for AutoSPinstaller in SPDocKit version 5.3, and our customers were really enthusiastic about it. This made us very happy so we decided to prepare a webinar to explain how to generate an XML configuration file in SPDocKit that you can use along with AutoSPInstaller to create a new SharePoint farm that is the same as or similar to your current farm environment.
Watch the video or read the video transcript summary to learn more.
Table of contents
00:36 Introduction: Toni Frankola
01:34 SPDocKit quick overview
04:38 AutoSPInstaller overview
08:58 Use case: Copy a configuration between farms
10:15 Demo: Generate an XML file in SPDocKit
18:00 Validate the XML file with AutoSPInstaller Online
20:02 Copy the XML file to the destination farm
Video Transcript Summary
In the video, Toni will show you how to easily provision farms using the awesome community tool AutoSPInstaller and how to create templates in SPDocKit for AutoSPInstaller to create a new farm.
What is AutoSPInstaller?
AutoSPInstaller is a community project created by Brian Lalancette and the team. It’s an open-source project that helps SharePoint administrators to automatically provision SharePoint farms. AutoSPInstaller is a set up of PowerShell scripts that you can use to install and configure your SharePoint farm. When you download AutoSPInstaller you’ll see so many options and realize that it’s one of the best things in the SharePoint community.
How does it work?
You prepare an XML file that contains all the desired services and web applications, and anything related to SharePoint that you want to provision and configure. Than you start a PowerShell script that reads all the settings from the XML file and provisions these components in your system.
Use case: Copy a configuration between SharePoint farms
Imagine a situation where developer A has a SharePoint farm (farm A) with an SQL server and two SharePoint servers. As SharePoint system administrator, you have been given the task of creating another two farms with exactly the same configuration as farm A.
With the combination of SPDocKit and AutoSPInstaller, you can easily copy the configuration of SharePoint farm A and deploy it to farms B and C. In order to do that, you need to provision two new farms: farm B for developer B and farm C for developer C. Using SPDocKit and AutoSPInstaller, the configuration of SharePoint farm A can easily be copied and deployed to farms B and C.
Generate an XML file using the SPDocKit AutoSPInstaller Wizard
We wanted to provide you with a tool that can help you to generate an input XML for the AutoSPInstaller based on your existing farm file.
Start SPDocKit on SharePoint farm A, load an existing farm, and create a snapshot that contains the entire documentation of the farm. Open the snapshot and fire up the AutoSPInstaller Configuration File Wizard. Run all the required steps to create an XML file.
- Specify the farm account details for your new farm.
- Define the server mappings.
- Replace your source accounts with other domain accounts.
- Provide passwords for your managed accounts and additional service app settings.
- Map between different accounts in the source and new farm.
- Choose what kinds of application you want to provision with the names you want to use.
- Define the mappings for host names and databases.
- Generate the configuration file.
After you have generated an XML file, visit AutoSPInstaller Online, a web interface that helps you prepare your XML file. Load the template from your XML file. You can see everything that will be provisioned and edit the settings. Once you’re done, download an XML file and copy it to the destination farm.
I have already downloaded AutoSPInstaller and installed SharePoint on machine B. Next, I will run the prepared input file. AutoSPInstaller will validate everything that I configured. I did the same on machine C. When I return to SPDocKit on farm C I can load the farm settings and see what’s inside. Everything has been provisioned as on farm A.
As you can see, it’s easy to create a copy of your existing farm with AutoSPInstaller and SPDocKit.
We hope this video was helpful to you. Check out the Webinar takeaways, below.
- Recreate your farms based on an “image” – a current good setup.
- Use AutoSPInstaller when setting up new environments.
- Create an input for AutoSPinstaller with SPDocKit.
- Make changes to the farm settings if you need to.
- Export your current farm setup in an XML file and use it when needed.
- The files are reusable and can create any number of farms.
Still haven’t tried SPDocKit? Free trial is available for download.