Using a Script Configuration to SharePoint -vs- Using the Configuration Wizard.

I’ve been deploying SharePoint for years, I’ve always used the Microsoft Office SharePoint Configuration Wizard to configure the farm. Recently I had a customer ask me how they could customize the name of the AdminContent database that the wizard randomly names it something like:

SharePoint_AdminContent_d9843542-d33d-43f7-a820-d8803f8f3fc5

I’ve never minded this much; however, if you happen to be using the same SQL server instance for multiple SharePoint deployments, it could get confusing as to which AdminContent goes with which farm, or maybe you want ALL your your SharePoint databases to follow a certain naming convention.

Whatever the reason might be, I put together this small script that will allow you to customize the AdminContent database name as well as being able to offer the ability to hand your customer or whoever a sure way of configuring SharePoint the same every time: