none
Migrating Project Server 2016 configuration without data RRS feed

  • Question

  • Hello,

    We are running Project Server 2016 environment (on-premises). We have 1 single server environment which we use for development and testing. However we need to migrate this to the following:

    1. 1 single server environment but the configuration only without any project i.e. transfer of Enterprise Calendars, Enterprise Custom Fields, Workflow Stages, PDPs, EPTs, Project Server workflows etc. only
    2. 2 server environment i.e. 1 Application and 1 Database. This also needs only configuration to be transferred and not the data.

    How shall we achieve the above mentioned requirements?

    Moreover we also need guidance (steps) to migrate from development to staging and from staging to production clean.

    Regards


    Tanzim Akhtar

    Thursday, October 4, 2018 1:32 PM

Answers

All replies

  • Here is a good starting place for migration

    https://docs.microsoft.com/en-us/project/upgrading-to-project-server-2016

    From DEV to TEST to PROD are basically migrations

    Once PRODUCTION is up and running, you may want to migrate PROD back to DEV and TEST.  

    This is basically backing up and restoring to the difference environments and then rebuilding project server.  Build powershell scripts to automate the process.


    Michael Wharton, Project MVP, MBA, PMP and a Great Guy <br/> Website http://www.WhartonComputer.com <br/> Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Friday, October 5, 2018 1:54 AM
    Moderator
  • Hello,

    For an environment roll over these steps will help: https://pwmather.wordpress.com/2017/01/19/projectserver-2016-environment-migration-rollover-steps-powershell-ps2016-msproject-sp2016/

    This will take the data too but you can delete that after. If you need to only take the config then you will either need to:

    • do the config manually in the blank instance
    • Look at a 3rd party migration tool such as Fluent Pro
    • Or write the code to do it

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS | MVP | Downloads

    Friday, October 5, 2018 7:29 AM
    Moderator
  • I have been through the above mentioned Microsoft Docs article and it is about 2013 version migration to 2016. However we need 2016 to 2016. What we usually do is that we copy and paste content database using powershell and then provision Project Server. This works perfectly but the drawback of this approach is that brings along the orphaned projects and other unwanted data. Hence we are looking for an approach that will transfer only configurations of the Project Server without the data.

    Thank you Michael for your quick response.

    Regards


    Tanzim Akhtar

    Saturday, October 6, 2018 7:42 AM
  • Hi Paul,

    Thank you for your article I have seen that article before and as you have mentioned correctly that it will bring in the data too. What shall we watch out for when deleting the data? For e.g. some of the workflows are started and it doesn't end (even after clicking end this workflow it doesn't end) etc. These will keep the orphaned projects from deleting through the user interface. Although we can write script to delete those orphaned projects but we would like to avoid this approach.

    The third option in your recommendation looks closest to our need.

    I remember that we used to have PlayBook when copying these information but couldn't find one for Project Server 2016. Can you please point out some scripts to copy the configurations like Enterprise Calendars, Enterprise Custom Fields etc.

    Regards


    Tanzim Akhtar

    Saturday, October 6, 2018 7:50 AM
  • Hello,

    There used to be an app in the app stored that did migrate some config (custom fields etc.) but that has been rermoved. You could build your own scripts, here is a link to the CSOM API details: https://msdn.microsoft.com/en-us/office/project/api/index or as you are on-prem you could still use the PSI. We built and use a tool internally that migrates the PWA config.

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS | MVP | Downloads

    • Marked as answer by Tanzim Saturday, October 13, 2018 5:52 AM
    Saturday, October 6, 2018 9:44 AM
    Moderator
  • Moving production data to a test or development environment basically requires the following

    !) Deprovision Project Server

    2) Delete the web application

    3) backup the SharePoint database over from Production and restore on the test/dev SQL server

    4) Create web application using the database restore 

    5) Provision project server again


    Michael Wharton, Project MVP, MBA, PMP and a Great Guy <br/> Website http://www.WhartonComputer.com <br/> Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Saturday, October 13, 2018 2:10 AM
    Moderator
  • Hi,

    We are going on to write the code for this.


    Tanzim Akhtar

    Saturday, October 13, 2018 5:52 AM