locked
Migration of SharePoint from VM to host machine RRS feed

  • Question

  • would like to get your advice in the below:

    Existing Setup : SharePoint 2010 + SQL database on the same server installed on the host.

    Created a new virtual machine and installed SharePoint 2013 on virtual machine, but the database is made to point to the same old in the host machine.

    Advice me the best practice to achieve the below:

    We are not using SharePoint 2010 anymore and I would like to get the SharePoint 2013 from the VM to the host. The database is already in the host.

    Thanks and Regards,

    Alex

    Sunday, November 2, 2014 12:18 PM

Answers

  • Hi Alex,

    if you are having classic based  web application you will need to do the following if it is not so just create claims based web app on 2013 and proceed with rest of instruction, you will mount DB and Install SharePoint then will apply the following steps:

    1-Create in 2013 classic mode web application (if the 2010 web app is classic)

    New-SPWebApplication -Name <Name of WebApp> -ApplicationPool <AppPool Name> -AuthenticationMethod NTLM  -DatabaseName <Name old Database> -Databaseserver <ServerName> -HostHeader <Host Header for web app> -Port 80 -URL <URL for site>

    2-Deploy any custom code to 2013 farm (if any)

    3-mount DB 

    Mount-SPContentDatabase Name ContentDbName -DatabaseServer " <DbServer>" -WebApplication http://SiteName

    4- Do IIS reset

     Open IE and browse the site created , if you get file not found error, go to settings page by adding _layouts/settings.aspx after the site url e.g. http://siteurl/_layouts/settings.aspx

    Click on master page and change master page to V4 in “Site Master Page” section and click ok

    5-

       Click on Site Action > Site Settings>Upgrade Site Collection under Site Collection Administration section and click on Upgrade site collection on the next page. 

    6-convert web app to claims (if it is classic)

    Conver-SPWebApplication –Identity <url of webapp> -To Claims –Retainpermissions –Force


    Kind Regards, John Naguib Technical Consultant/Architect MCITP, MCPD, MCTS, MCT, TOGAF 9 Foundation

    • Marked as answer by Alex Varghese Monday, November 3, 2014 8:15 AM
    Sunday, November 2, 2014 12:32 PM

All replies

  • Hi Alex,

    if you are having classic based  web application you will need to do the following if it is not so just create claims based web app on 2013 and proceed with rest of instruction, you will mount DB and Install SharePoint then will apply the following steps:

    1-Create in 2013 classic mode web application (if the 2010 web app is classic)

    New-SPWebApplication -Name <Name of WebApp> -ApplicationPool <AppPool Name> -AuthenticationMethod NTLM  -DatabaseName <Name old Database> -Databaseserver <ServerName> -HostHeader <Host Header for web app> -Port 80 -URL <URL for site>

    2-Deploy any custom code to 2013 farm (if any)

    3-mount DB 

    Mount-SPContentDatabase Name ContentDbName -DatabaseServer " <DbServer>" -WebApplication http://SiteName

    4- Do IIS reset

     Open IE and browse the site created , if you get file not found error, go to settings page by adding _layouts/settings.aspx after the site url e.g. http://siteurl/_layouts/settings.aspx

    Click on master page and change master page to V4 in “Site Master Page” section and click ok

    5-

       Click on Site Action > Site Settings>Upgrade Site Collection under Site Collection Administration section and click on Upgrade site collection on the next page. 

    6-convert web app to claims (if it is classic)

    Conver-SPWebApplication –Identity <url of webapp> -To Claims –Retainpermissions –Force


    Kind Regards, John Naguib Technical Consultant/Architect MCITP, MCPD, MCTS, MCT, TOGAF 9 Foundation

    • Marked as answer by Alex Varghese Monday, November 3, 2014 8:15 AM
    Sunday, November 2, 2014 12:32 PM
  • Thank you John, It would be helpful if you could provide me a little more insight on the below on how to uninstall the SP 2010 and install 2013 without modifying the database. Please see the elaborated issue below:

    I am new to SharePoint and I would like to elaborate on the issue a little more.

    Physical machine:

    1. Installed SharePoint 2010

    2. Installed SQL with the instance : MSSQLSERVER

    Virtual Machine:

    1. Only SharePoint 2013

    We tried upgrading from SharePoint 2010 to 2013, due to some issue we had installed SP2013 in a virtual and when prompted to enter the database, we navigated to the same database in physical with a new instance name : MSSQLSERVER\SP2013

    The virtual in the VM seems to be slow and has less configuration, we would like to remove the existing 2010 from physical and configure the 2013. Please note that the database is still in physical and needs to be unchanged.

    Monday, November 3, 2014 8:15 AM