I had the privilege recently to go with a team from my church on a mission trip to Jamaica. It was not to a resort area, and was definitely not a vacation. We had no hot water at the place where we stayed although I didn’t miss it at all! We worked daily with a local church in Mandeville, Jamaica to do vacation Bible school for kids during the day and revival services at night. It was both a challenge and a blessing.
Needless to say, I had zero contact with anyone from the U.S. for 7 full days, and honestly didn’t miss my cell phone ringing or getting email very much at all. However, when I got home, it was right back into the swing of things and working hard at catching up on what had been going on while I was away.
It took a few days to get back in the swing of things, and I think I might have finally caught up with myself, but it’s been a challenge. As I was playing catch up at work, a friend of mine was trying to get a server to catch up. The server was one of two load balanced web front end servers in a SharePoint 2007 farm. At some point, the SharePoint services had been all turned off on this server for some troubleshooting and they had not been turned on for quite some time. During this time solutions were deployed, new web applications and sites had all been created. So I was asked “How do I get this back to normal?”
There were lots of theories that sprung to mind, and I shared a couple of them, then thought, well, why do we have to make it hard. When a new web front end is added to an existing farm, all of that stuff is put on it automatically. So why not remove it from the farm using the SharePoint Products and Technologies Configuration Wizard and add it back? My friend tried it and boom… all solutions, web applications and sites were there and load balanced again!
The steps are pretty simple. Run the configuration wizard on the server that you want to remove from the farm and it will ask “do you want to remove this server from the farm” and you can select to do that. Then run it again and you will be prompted to create a new farm or join an existing one. When you join an existing one, you will need to know the database server where the configuration database exists for that farm along with the configuration database name and the account that central administration uses to be able to connect.
Pretty simple solution for what seemed at first like it would take quite some time to correct.
This post is cross posted from here.