Hi
I have tried at least 10 times to get this to work and still having trouble. After provisioning a brand new SP 2016 farm using Powershell and using the New-SPConfigurationDatabase in order to avoid randomly generated GUIDs, all appears well until you create your first site collection on a new web application. It immediately comes up with a Sorry, something went wrong error.
When provisioning using the wizard everything is fine. I read an article about how this could happen on a 2010 farm if you mistakedly added an extra '-' in the powershell script which forced Active Directory Account Creation mode. My script is fine, but it just does not allow the admin content database to have it's own name without causing this error.
has anyone else successfully provisioned a SharePoint 2016 farm in Powershell using their own db names and successfully created site collections? if so, how did you manage it?
Thanks - Jon