Changing current ADFS 2.0 (for Office 365) from SQL DB to WID

Hi all. I have a current ADFS 2.0 that is using SQL locally installed for Office 365 as well as federated venders. It is in farm mode, but only one node currently. I want to add another server to the farm. Since SQL is used locally on the first server, changed from WID, if that server fails, the DB will not be available. I realize under the current scenario, I would have to move the SQL DB to another server, preferably a SQL cluster, and then add the second server pointing to this DB. There really is no need for SQL though here and the high cost of license for a Cluster because the AD object count is not that high. If I deploy the farm using WID DBs, they will have fault tolerance built in to the primary/secondary components of this.

My Question is, is there anyway to change my current farm to go back to WID from SQL? I cant find anything on the Internet that states this. I see dozens of articles on how to go from WID to SQL...

If I cannot do this, can I add another new farm using WID and reconnect to Office 365 without much downtime?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vasil Michev (MVP)Commented:
Could not find anything either. You cannot have more than 1 AD FS in your org, so you will need to remove the existing one first. Which is not as simple as uninstalling the AD FS, it will leave the database and the rest of the config. If you feel adventurous enough to do so, read these:

Jorge's blog is very useful btw, you might also contact him directly to get an answer to this (make sure to post back here too)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RobguadAuthor Commented:
I actually was able to install a second ADFS 2.0 infrastructure in the same forest. I used a different name space. Once I was ready for the cut over, I just ran the commands to connect this new namespace to Office365. It worked just fine.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Office 365

From novice to tech pro — start learning today.