SPDocKit and AutoSPinstaller Webinar: Wrapping it up

Webinar Wednesday is starting to look like a tradition in Acceleratio, even though our webinars are mostly held on Thursdays. :) The last one was no exception. Our MVP Toni Frankola hosted a session on AutoSPInstaller and SPDocKit integration, which turned out to be quite popular. Of course, with many guests attending, there were some questions. We were more than happy to answer them all, but nevertheless, here is a small recap.

Since in the webinar we talked about using SPDocKit and AutoSPInstaller as a way of creating new farms in an environment, the following questions will be in line with this topic. If you didn't get the chance to see the webinar, navigate to this blog to see what was going on.


Questions & Answers

Q: How do you build a snapshot as presented at the beginning of the webinar? The presenter did not show this.

A: A snapshot is created when you load a farm into SPDocKit. More information about how to load a farm and the loading options can be found in this article. Based on this snapshot and the settings contained in it, the SPDocKit AutoSPInstaller wizard creates an XML input file, which is used in the actual AutoSPInstaller tool.

Q: What about SSL certificates and permissions for service applications? Is the SSL certificate configuration fully supported in AutoSPInstaller?

A: AutoSPInstaller provides some of the initial permission configuration but not custom permissions. If you need to do something like that, you have to create your own script to copy the permissions.

Q: Can it copy the content? Does it copy the content databases to the new farm?

A: AutoSPInstaller performs a base configuration, based on the source farm's setup. It doesn't copy the actual SP content from farm A to farm B. To copy the content, you should restore or use your existing database to restore the content database.

Q: How does this AutoSPInstaller process work on a site collection with custom workflows and solutions, if the solutions and workflows are already globally deployed on the destination farm?

A: It doesn't. The script provisions new web apps and site collections. If you need to provision your existing custom solutions, you would need to restore your DB or provision the solutions from scratch.

Q: Will it copy over master files and other scripts or can I avoid those altogether?

A: The master files are not copied by AutoSPInstaller.

Q: Can it copy branding?

A: The branding and the master files are in the database, so unfortunately AutoSPInstaller cannot copy them automatically.

Q: Can AutoSPInstaller create a PowerPivot service application?

A: It can create a lot of applications, but unfortunately PowerPivot is not one of them.

Q: Does AutoSPInstaller allow installation of third-party solutions?

A: Not that we are aware of, but since it uses a PowerShell script, it's easily manipulated and extended to install your custom solutions.

Q: Are AutoSPInstaller and SPDocKit viable tools for building disaster recovery environments?

A: You can use a combination of the two tools to provision a recovery farm, or do so using just the AutoSPInstaller tool.

Q: Does SPDocKit support the transition from multi-tier to a single tier?

A: The SPDocKit wizard will allow you easily to transition from multi-tier to a single-server environment and vice versa. In the webinar use case, we had two servers for farm A that could easily be mapped and transformed into the single server for farm B.

Q: Is AutoSPInstaller ready for SP 2016? What’s the ETA for SP 2016 support?

A: AutoSPInstaller is definitely up to speed with SP 2016.

Q: Can SPDocKit create an AutoSPInstaller XML file automatically or to a schedule?

A: Currently, this option is not available, since the SPDocKit wizard needs you to provide a lot of information, such as server mappings and stuff, but perhaps this will be available in a future release.

Thanks to all of you who attended, and we hope you'll support us in our future sessions as well. If you wish to know more about AutoSPInstaller, please feel free to contact the man behind the tool, Brian Lalancette, who was among our attendees as well. Contact Brian via Twitter at @brianlala. If you think of any other questions related to SPDocKit, feel free to contact us.