The SharePoint Config Wizard again and instead of connecting it to an existing farm, create a new one. The important step is to give the new ConfigDB a different name than the old one. The server will now essentially be reset with a fresh version of SharePoint. Dan walked through the steps and it did exactly what he wanted. Now he was free to do whatever horrible, torturous things that devs do to SharePoint. Another dev/admin cooperation success story.
Here are screenshots of what it looks like: 
The normal config wizard welcome screen.
This is the old, bad farm information. Make sure when you rerun the wizard you use a different name for your ConfigDB than what is listed here.
Click yes, this is exactly what you want to do.
That's all there is to it. The SharePoint binaries are still installed, but it's no longer configured. If you go into IIS you'll notice all your SharePoint related sites have been removed.
Now rerun the Config Wizard and create a new farm.
Click Next.
Click "Create a new server farm."
On the next screen input your farm information. Make sure your Database name is different than what your old ConfigDB was.
You'll have to set up a new farm passphrase, since this is a new farm.
You'll also need to set up Central Admin, since the previous Central Admin instance was removed when the server was removed from your old farm.
That's all there is to it. Look over your settings and hit Next.
No comments:
Post a Comment