locked
How to switch URLs between Production MOSS farms RRS feed

  • Question

  • We will stand up an exact duplicate of our Production MOSS farm. The objective is to have two identical farms running simultaneously while we remove some customizations we no longer need, but we don’t want to do this directly in our production environment. Obviously, the new farm can’t have the same URL as the original farm.

    When we’re done we will refresh the content in the new farm and then it will become Production, but first we need to have users reach the web applications in the new farm seamlessly.

    How can we change the URL (host headers) for all the web applications in the new farm to the old farm’s URLs? (for example: if the old farm web app was http://production and the corresponding web app in new farm is http://production-temp by the end of the Maintenance, and after taking the old farm offline,  http://production-temp web app in the new farm will have to be renamed to http://production )

    The requirements are to keep minimal down time as possible and not extending the web applications, we have extended some web applications to enable FBA and we don’t want to add more SP Administration overhead.

    Is it possible to just modify the IIS host headers , update the existing AAMs accordingly and adjust the DNS entries? If so, would this procedure automatically update every SharePoint web app links?

    Environment:

    2 Web Front End Servers (NLB)

    1 Application server (CA, search, indexing)

    1 SQL 2008 server (clustered)

    Friday, May 18, 2012 8:08 PM

Answers

  • Hi,

    "Is it possible to just modify the IIS host headers , update the existing AAMs accordingly and adjust the DNS entries? If so, would this procedure automatically update every SharePoint web app links?"

    Yes.

    Obviously this needs to be done after hours with a very specific well written plan followed by the admin (s). Friday evening is a good time to start so that just in case you encounter any unforeseen problem, you can work through this on the rest of weekend.

    However, there is one other thing that is very important. Have a well written test plan and then test the app with the test plan. QA team and users should help with this.

    Some additional warnings. Check the content source of search. It should change automatically once you change the AAM. However, please double check this and reset and recrawl the entire content after the URL change. Also check if the search database grew too big because of these changes.

    Another thing to be casreful about are the InfoPath forms if any. The InfoPath form library need to be resynced with the new urls.

    I think quick but good regression testing will be your key.


    Thanks, Soumya | MCITP, SharePoint 2010

    Saturday, May 19, 2012 4:49 PM

All replies

  • Hi,

    "Is it possible to just modify the IIS host headers , update the existing AAMs accordingly and adjust the DNS entries? If so, would this procedure automatically update every SharePoint web app links?"

    Yes.

    Obviously this needs to be done after hours with a very specific well written plan followed by the admin (s). Friday evening is a good time to start so that just in case you encounter any unforeseen problem, you can work through this on the rest of weekend.

    However, there is one other thing that is very important. Have a well written test plan and then test the app with the test plan. QA team and users should help with this.

    Some additional warnings. Check the content source of search. It should change automatically once you change the AAM. However, please double check this and reset and recrawl the entire content after the URL change. Also check if the search database grew too big because of these changes.

    Another thing to be casreful about are the InfoPath forms if any. The InfoPath form library need to be resynced with the new urls.

    I think quick but good regression testing will be your key.


    Thanks, Soumya | MCITP, SharePoint 2010

    Saturday, May 19, 2012 4:49 PM
  • How about this?

    http://technet.microsoft.com/library/cc262366(office.12).aspx

    Do you think it will work?

    Tuesday, July 17, 2012 9:13 PM
  • How many are the users who need to have access to the new farm.

    Usually have the farm ready with same url dont put the DNS entry. access the farm by changing the host header on the user machine and once everything is done.

    Change the ip of the Old to the new one in DNS.

    If the contents are not big create farms as per your suggestion remove and attached the DB from new  to old.


    Regards, Aniket


    Wednesday, July 18, 2012 2:32 AM
  • This is a new Production environment we're talking about. 1200+ users.

    The idea you suggest passed my mind at some point, but I thought it would be confusing when testing and I was afraid I could accidentally deploy something or made a change into the original Production environment. Both environments will be running simultaneously at some point.

    Roberto.

    Wednesday, July 18, 2012 1:14 PM