Tags: Project 2016, Project Server 2016, SharePoint 2016, SP2016
This blog post will detail the PowerShell commands required to carry out an environment rollover / migration using Windows PowerShell where possible. The steps below use the database approach to rollover the Production environment to the Test / Development environment.
As a prerequisite I would recommend taking full backups of the Test / Dev farm to enable the environment to be rolled back if required. Use your usual farm backup procedures.
Test / Dev environment Prep
Firstly connect to the Test / Dev Application server and launch the SharePoint 2016 Management shell.
Type the following:
Remove-SPSite -Identity ‘<TEST/DEV PWA Site URL>’
You can check in Central admin in the Project Server Service Application to check that the PWA site has been removed.
Using the SharePoint 2016 Management Shell, remove the existing content database from the web application that hosted the PWA site collection that was removed in the previous step.
Type the following:
Dismount-SPContentDatabase ‘<Content database name>’
Test / Dev environment SQL Prep
Take a backup of the PWA Content database from the Production environment and copy this over to the Test / Dev SQL server and restore the database. The database required is:
- Content database that contains the Production PWA site and Project Sites
Make a note of the database name used when this database is restored as it will be required later.
Test / Dev environment configuration
Using the SharePoint Management Shell, mount the restored content database to the web application that will host the PWA site collection.
Type the following:
Mount-SPContentDatabase ‘<content database name restored in previous step>’ -DatabaseServer ‘<Test / DEV SQL Server>’ –WebApplication <web application URL>
The Project Server Cube settings will need to be updated – update the SQL AS server / cube name.
Any Excel based reports in PWA will need to be updated to use the ODC files / connection strings from the Test / Dev environment as they will currently point to the Production ODC files / connection strings. This is done by opening the Excel reports in Excel, changing the ODC file / connection strings then saving the file back to the library.
All projects will need to be republished on the test / dev instance so that the project site features such as the issues and risks sync works as expected. There are other ways to fix that but republishing the projects is the easiest / safest option from what i have found.
#ProjectServer and #SharePoint 2013 / 2016 January 2017 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProjectJanuary 12, 2017 at 7:42 pm | Posted in Administration, CU, Fixes, Functionality, Information | Leave a comment
Tags: Office 2013, Office 2016, Project 2013, Project 2016, Project Server 2013, Project Server 2016, PS2013, PS2016
The Office 2016 January 2017 updates and cumulative updates are now available, please see the links below:
Project 2016 January 2017 update:
The Office 2013 January 2017 updates and cumulative updates are now available, please see the links below:
Project Server 2013 January 2017 CU Server Roll up package:
Project Server 2013 January 2017 update:
Project 2013 January 2017 update:
Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the January 2017 CU.
As always, fully test these updates on a replica test environment before deploying to production.
Tags: Office365, Power Query, PowerBI, PPM, Project Online
Over the holiday period I started to build a Power BI Report Pack for Microsoft’s Office 365 PPM tool Project Online. I have made this publically available to download using the link below:
This Report Pack currently consists of 5 reports but will be extended in the near future with additional reports and / or changes to existing reports. In this release there are 5 reports, these can be seen below:
Resource Demand Report:
These reports only use default intrinsic fields so it should work for all Project Online deployments.
Once downloaded, the report pack data sources will need to be updated to point to your target Project Online PWA instance. To do this you will need the Power BI desktop tool which is a free download here: https://powerbi.microsoft.com/en-us/desktop/
Open the downloaded PWMatherProjectOnlinePowerBIReportPack.pbix file in Power BI Desktop and follow the steps below to point the data sources to your Project Online PWA instance:
- Home > Edit Queries > Edit Parameters
- On the “Enter Parameters” window update the PWAURLParameter value with the correct PWA URL and click OK.
- Click Apply Changes on the yellow status bar . You might be prompted to sign in if you haven’t before, if so, see the details below
- If prompt with the authentication options. Select Organizational account then click Sign In.
- Enter credentials for an account that has access to the OData Reporting API on the target PWA instance
- Then click Connect
- A Privacy levels window may appear, select Organisational then click Save.
- The Apply Query Changes window will appear as the data is refreshed.
- Once the refresh window disappears the reports will update to show the data from the target PWA instance. Click the Project Report tab and change the project filter from Project 1 to a project from your PWA instance. Save the file.
This file can either be emailed around to colleagues with details on how to update the credentials to their own or what would be better is to publish the report to your Power BI workspace can create an organisational content pack that others can add to their Power BI workspace. If the Power BI organisational content pack is the chosen option, you might want to create a Dashboard first.
In a follow up blog post to this one, I will touch on creating a dashboard once the report is published to my Power BI workspace then create an organisation content pack.
Enjoy, I hope you like it