Yo Pros! We have found this fantastic tool to help setup farms quickly that we had to share with you!
It’s our fifth project now requiring multiple SharePoint farms to support the ALM process for Dev, Test, Production; which was needed to built quickly whilst maintaining best practice and consistency.
We can unknowingly introduce small differences in deploying each farm. Lunch, tea breaks, consulting, distraction, distraction, distraction…. this is common in the workplace, but if you miss a step then the farms can become further apart in their quality and thus introduce risk and artifacts in deployments that were not expected.
In numerous projects I have seen development environments that resemble nothing like production. Only to result in a problematic transition through the ALM process, bugs caused by inconsistency, significant differences in SharePoint updates, configuration and even permissions.
I am not saying that you shouldn’t write your app to “expect a specific configuration” or to avoid best practices around handling configuration issues. However, to reduce issues down the line, as a minimum, environments should be setup with the following:
Restoring archived VMs, only to find that the trust relationship between the VM and AD has failed. This is an age old problem that I have encountered throughout my time working with VMs and SharePoint development environments.
I have found a great reference for fixing this issue by Thomas Balkeståhl and his blog post: Fix: The trust relationship between this workstation and the primary domain failed
The key take-away from this blog: