Tell me more ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.
up vote 1 down vote favorite

I have one SharePoint Farm with two servers:

  • SERVER1
  • SERVER2

I have one web application "SharePoint 80". The alternate access mappings (AAM) for this app are pointing to http://server1

I want to decomission SERVER 1 and host the content on the second server SERVER2 in the same farm.

share|improve this question

3 Answers

up vote 1 down vote accepted

SharePoint is providing a role on each server that is called "Microsoft SharePoint Foundation Web Application". if you check the "services on server" option in central administration you can see which server are currently configured to have the iis sites created.

To unjoin the SERVER1 from the farm you have to update the alternate access mapping for the web application to point to the new server. You have to validate the needed role is started on the new server. Than you have to tell all users the url has changed. Under all circumstanses i would try to avoid such an operation.

I would recommend creating the web application in the first place always with a host header information and create a DNS entry to the server (or servers if some kind of load balancing is used). There are some additional todo's if kerberos is used, but in general not using the servername is a best practice.

share|improve this answer
Thanks for the comments mate. That is basically what I did. I kinda forgot that this is the way to do it. Luckily, the Infrastructure guys were able to do a quick DNS switch to the new server. I actually have one more question if you dont mind. Should I run the "Microsoft SharePoint Foundation Web Application" service on my App Server (I have 2 seperate app servers, 1 for search, and 1 for ad hoc service Apps). Even though these servers will never get hit from a users perspective... does it use resources when it's started? Thanksagain for the answer. – Fox Jul 12 '11 at 15:12
I've submited a question sharepoint.stackexchange.com/questions/12547 i've there is any guidance. If you don't have da dedicated crawl target to reduce traffic during full crawls i would not host this role on any app server. check my question maybe it is helpful. – Marco Scheel Jul 19 '11 at 8:10
up vote 0 down vote

I dont see how you can migrate data by just starting/stopping services. If you don't have any custom solutions, or if your custom solutions are available at server 2, mounting the database is the way to go. Make sure that you have the same buildversion on both servers

additional question: * is it a migration from SP2010 to SP2010? or is it an upgrade too?

share|improve this answer
Hi there. I was correct in starting/stopping the services. The only thing required, was to change my AAMs to point to the new Server. Sharepoint takes cares of Syncronising and configuring IIS Sites when you start the Sharepoint Foundation Web Application Service on that Server. Anyways, I managed to figure it out. All sorted now. – Fox Jul 12 '11 at 12:42
You didn't mention the servers are in one farm. I've send an update request for your questions. Bas answer is misleading, but he didn't have all information. – Marco Scheel Jul 12 '11 at 13:11
Sorry guys for not mentioning that the servers were in the same farm.. No harm intended.. – Fox Jul 12 '11 at 15:13
up vote 0 down vote

I was correct in starting/stopping the services. The only thing required, was to change my AAMs to point to the new Server. Sharepoint takes cares of Syncronising and configuring IIS Sites when you start the Sharepoint Foundation Web Application Service on that Server. Anyways, I managed to figure it out. All sorted now.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.