none
Project Server 2013 RRS feed

  • Question

  • I am migrating  Project Server 2010 to a 2013 Test farm. Production data  from 2010 has been  restored on a separate database for 2013.

    Will the original Production site be affected if I change the site ownership and do other changes to content database for the upgrade, as the production site is still running. What other precaution should I take to not affect the production site?

    Also, the 2010 site has Windows Classic Authentication. If I make a Windows Classic Authentication web application in 2013 and upgrade the 2010 site there, can I convert it to Claims Authentication later on without issue, if it is required to do so?

    Any suggestions regarding above will be highly appreciated!!!


    • Edited by geeam Monday, May 5, 2014 3:53 PM
    Monday, May 5, 2014 3:52 PM

Answers

  • Which content DB are you referring to ? the one associated with Production Site (Project Web App Content DB) ? if answer is yes, then yes the production site will be affected, but if you are talking about content DB copied over for your test farm then it wouldn't impact the production, however on a side note direct modifications to content DB is not recommended you may be breaking other things

    Authentication of web app can be changed from classic to claims using powershell command anytime, note for 2013 claims is the way to go 


    Thanks | Sunil Kr Singh | http://epmxperts.wordpress.com

    Monday, May 5, 2014 3:59 PM
    Moderator
  • Ideally it shouldn't but you never know, let us know in a separate thread if you find any errors or related thing and we will be glad to help 

    Thanks | Sunil Kr Singh | http://epmxperts.wordpress.com

    • Marked as answer by geeam Tuesday, May 6, 2014 12:15 AM
    Monday, May 5, 2014 8:25 PM
    Moderator

All replies

  • Which content DB are you referring to ? the one associated with Production Site (Project Web App Content DB) ? if answer is yes, then yes the production site will be affected, but if you are talking about content DB copied over for your test farm then it wouldn't impact the production, however on a side note direct modifications to content DB is not recommended you may be breaking other things

    Authentication of web app can be changed from classic to claims using powershell command anytime, note for 2013 claims is the way to go 


    Thanks | Sunil Kr Singh | http://epmxperts.wordpress.com

    Monday, May 5, 2014 3:59 PM
    Moderator
  • Thanks a lot Sunil for the reply. Yes, I am referring to the content database restored from 2010 production to the 2013 test database environment. All the 4 Project Server and the content database has been restored on the new server.The two PowerShell commands I will be running it on it through powershell will be like:

    Set–SPSite -Identity http://testserver/pwa -SecondaryOwnerAlias “Test\Admin" and

    Upgrade–SPSite –Identity http://testserver/pwa –versionupgrade.

    I will also be converting the Classic Window Authentication to Claims authentication on upgrade.

    Hope I will not be breaking anything?

    Monday, May 5, 2014 8:12 PM
  • Ideally it shouldn't but you never know, let us know in a separate thread if you find any errors or related thing and we will be glad to help 

    Thanks | Sunil Kr Singh | http://epmxperts.wordpress.com

    • Marked as answer by geeam Tuesday, May 6, 2014 12:15 AM
    Monday, May 5, 2014 8:25 PM
    Moderator