Hello All
I'd like to run this scenario by you all to see what you think.
I'm in the process of upgrading our SharePoint 2007 Intranet to SharePoint 2013.
I'll need to use a third party tool to migrate the content which is fine.
The current Intranet URL for the SP 2007 environment is intranet.domain.com.
The tricky bit is that I will potentially need to run both environments simultaneously under the same URL - intranet.domain.com. SP 2007 so that users can still access the content (read only) and SP 2013 so that I can test everything is working ok.
So, the plan is:
1. Maintain the SP 2007 environment with the Content Databases set to Read Only, this so users can still access the content.
2. Create a new SP 2013 web application with a host header of intranet.domain.com but not register this in DNS initially.
3. Create an Alternate Access Map in SP 2013 - e.g. newintranet.domain.com and temporarily register this in DNS - this so I can test that everything is working as expected post content migration.
4. Once I'm happy that everything is working then I will remove the AAM and temporary DNS record, update DNS with the new IP for intranet.domain.com and decommission the SP 2007 environment.
I have partially tested this in a SP 2013 environment and it did work but what I found confusing was that even after I'd removed the AAM the URL (e.g. newintranet.domain.com) was still accessible and only clearing the browser cache was the AAM site rendered
inaccessible.
Another completely different type of method would be to just rename the host headers for the new SP 2013 environment as detailed here - http://blogs.msdn.com/b/russmax/archive/2013/02/27/how-to-properly-change-the-host-header-url-of-a-web-application-in-sharepoint-2010.aspx
- but the Intranet isn't extended.
Any input greatly appreciated.
Thanks.
MDM.