#ProjectServer and #SharePoint 2013 / 2016 June 2017 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject

June 14, 2017 at 8:15 am | Posted in Administration, Configuration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , , , ,

The Office 2016 June 2017 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4023935

Project 2016 June 2017 update:
https://support.microsoft.com/en-us/kb/3191934

SharePoint Server 2016 / Project Server 2016 June 2017 update: 
https://support.microsoft.com/en-us/kb/3203432 & https://support.microsoft.com/en-us/kb/3203433

The Office 2013 June 2017 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4023935

Project Server 2013 June 2017 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/3203429

Project Server 2013 June 2017 update:
https://support.microsoft.com/en-us/kb/3203399

Project 2013 June 2017 update:
https://support.microsoft.com/en-us/kb/3191941

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the June 2017 CU.

As always, fully test these updates on a replica test environment before deploying to production.

#ProjectServer and #SharePoint 2013 / 2016 May 2017 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject

June 2, 2017 at 5:24 pm | Posted in Administration, Configuration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , , , ,

A little later than my normal posts for updates due to vacation but here are the links for the updates. The Office 2016 May 2017 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4020152

Project 2016 May 2017 update:
https://support.microsoft.com/en-us/kb/3191870

SharePoint Server 2016 / Project Server 2016 May 2017 update: 
https://support.microsoft.com/en-us/kb/3191880 & https://support.microsoft.com/en-us/kb/3191884

The Office 2013 May 2017 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4020152

Project Server 2013 May 2017 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/3191912

Project Server 2013 May 2017 update:
https://support.microsoft.com/en-us/kb/3191890

Project 2013 May 2017 update:
https://support.microsoft.com/en-us/kb/3191878

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the May 2017 CU on 2013.

As always, fully test these updates on a replica test environment before deploying to production.

#ProjectServer and #SharePoint 2013 / 2016 April 2017 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject

April 11, 2017 at 6:44 pm | Posted in Administration, Configuration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , , , ,

The Office 2016 April 2017 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4016803

Project 2016 April 2017 update:
https://support.microsoft.com/en-us/kb/3178708

SharePoint Server 2016 / Project Server 2016 April 2017 update: 
https://support.microsoft.com/en-us/kb/3178721 & https://support.microsoft.com/en-us/kb/3178718

The Office 2013 April 2017 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4016803

Project Server 2013 April 2017 CU Server Roll up package:
***No Server rollup package this month – install other SharePoint 2013 patches as required***

Project Server 2013 April 2017 update:
https://support.microsoft.com/en-us/kb/3191824

Project 2013 April 2017 update:
https://support.microsoft.com/en-us/kb/3178713

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the April 2017 CU on 2013.

As always, fully test these updates on a replica test environment before deploying to production.

#ProjectServer and #SharePoint 2013 / 2016 March 2017 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject

March 15, 2017 at 1:38 pm | Posted in Administration, Configuration, Fixes, Functionality, Information | Leave a comment
Tags: , , , , , , ,

The Office 2016 March 2017 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4013886

Project 2016 March 2017 update:
https://support.microsoft.com/en-us/kb/3178669

SharePoint Server 2016 / Project Server 2016 March 2017 update: 
https://support.microsoft.com/en-us/kb/3178675 & https://support.microsoft.com/en-us/kb/3178672

The Office 2013 March 2017 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4013886

Project Server 2013 March 2017 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/3172462

Project Server 2013 March 2017 update:
https://support.microsoft.com/en-us/kb/3178625

Project 2013 March 2017 update:
https://support.microsoft.com/en-us/kb/3178650

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the March 2017 CU on 2013.

As always, fully test these updates on a replica test environment before deploying to production.

#ProjectServer and #SharePoint 2013 / 2016 February 2017 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject

February 26, 2017 at 8:55 am | Posted in Administration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , , , ,

The Office 2016 February 2017 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4010765

Project 2016 February 2017 update:
https://support.microsoft.com/en-us/kb/3141514

SharePoint Server 2016 / Project Server 2016 February 2017 update: 
https://support.microsoft.com/en-us/kb/3141515 & https://support.microsoft.com/en-us/kb/3141517

The Office 2013 February 2017 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4010765

Project Server 2013 February 2017 CU Server Roll up package:
***No Server rollup package this month – install other SharePoint 2013 patch as required***

Project Server 2013 February 2017 update:
https://support.microsoft.com/en-us/kb/3141525

Project 2013 February 2017 update:
https://support.microsoft.com/en-us/kb/3141499

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the February 2017 CU.

For more details see: https://blogs.technet.microsoft.com/projectsupport/2017/02/24/project-and-project-server-february-2017-updates-released/

As always, fully test these updates on a replica test environment before deploying to production.

#ProjectServer 2016 environment migration / rollover steps #PowerShell #PS2016 #MSProject #SP2016

January 19, 2017 at 3:48 pm | Posted in Administration, Configuration, Functionality, Information, Installation | Leave a comment
Tags: , , ,

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>

Post Provisioning

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 #MSProject

January 12, 2017 at 7:42 pm | Posted in Administration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , , , ,

The Office 2016 January 2017 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/3214449

Project 2016 January 2017 update:
https://support.microsoft.com/en-us/kb/3141459

SharePoint Server 2016 / Project Server 2016 January 201 update: 
https://support.microsoft.com/en-us/kb/3141487 & https://support.microsoft.com/en-us/kb/3141486

The Office 2013 January 2017 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/3214449

Project Server 2013 January 2017 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/3141480

Project Server 2013 January 2017 update:
https://support.microsoft.com/en-us/kb/3141484

Project 2013 January 2017 update:
https://support.microsoft.com/en-us/kb/3141470

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.

Update #ProjectOnline Resource custom field values using #PowerShell with data from #AzureAD user attributes #PPM #Offce365 #ProjectServer #CSOM

November 7, 2016 at 9:40 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, PowerShell, Reporting | Leave a comment
Tags: , , , , , , , ,

This blog post will demonstrate a simple example of how Microsoft’s PPM tool, Project Online, can include / sync metadata from Azure AD user attributes to resource custom fields in Project Online. This example script will update the resource custom field “Job Title” on my test tenant with the data from the Azure AD user “Title” attribute.

This script example can be downloaded here: https://gallery.technet.microsoft.com/Update-Online-Resource-83137b7f

The script does require some additional modules / DLLs to work. Firstly you will need the Azure AD module installed, this can be downloaded here: http://connect.microsoft.com/site1164/Downloads/DownloadDetails.aspx?DownloadID=59185. You will also need the SharePoint Online and Project Online CSOM DLLs. The DLL’s used are from the NuGet package here: https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM/16.1.5521.1200. There are later version available, check here: https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM. Download those as required. These modules can be seen here on line 3,5 and 14 in the example script, the location will need to be updated to reference the correct location for your SP / PS Online CSOM DLLs.

The user setting up the script will need to update the correct location to the DLLs required, the AD username, AD password, CSV file location, PWA instance URL, username, password and the custom field internal name. The PWA account specified will need edit access to all of the resources in PWA and the AD account will need access to read all the users in Azure AD. Ensure the variables have been updated correctly, placeholder values seen below:

image_thumb.png

In this example all users in the Azure AD will be exported, clearly if you have a large organisation it would be efficient the filter for only those users that exist in Project Online. The code matches users and resources based on the AD display name and PWA resource name when updating the resources in PWA.

To get the correct custom field internal ID I use the REST API, <PWA Site URL> + /_api/ProjectServer/CustomFields. Find the resource level custom field and copy the InternalName as seen below:

image_thumb.png

Once the PowerShell script has been updated, save it and it can then be tested on a test / non-production environment. Once executed in PowerShell, each resource found in the CSV file will be outputted as seen in the example below. In this example there are many AD users in the CSV export that do not exist in the PWA instance.

image_thumb.png

Checking in the Resource Center after the script has run you can see for the resources that exist in the CSV file created, the Job Title has been updated with the values found in Azure AD / the export CSV file:

image_thumb.png

The CSV file generated can be seen here:

image_thumb.png

This PowerShell script could be run on a schedule from a server on-prem or even in Azure / webjob. The script would just need access to save / access a CSV file and the DLLs / modules required. Fully test this script on a test / non-production PWA instance before running on a Production PWA instance.

The script is provided “As is” with no warranties etc.

Update #ProjectOnline Project custom field values using #PowerShell with data from a CSV file #PPM #ProjectServer #CSOM

November 6, 2016 at 4:44 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, PowerShell | 1 Comment
Tags: , , , , , , , ,

This blog post will demonstrate a simple example of how Microsoft’s PPM tool, Project Online, can include data from an external system. This is a very simple example using a demo CSV mock up of data that could be from an external system. The CSV part could easily be replaced by a SQL query or a REST API query to the source system etc.

Example CSV data used can be seen below:

image

As you can see, my imagination for example project names has not improved! The code uses the Project Name as the key between the two data sets – the CSV file and PWA so the names will need to match.

This script example can be downloaded here: https://gallery.technet.microsoft.com/Update-Online-Custom-Field-12f034f4

The user setting up the script will need to update the correct location to the DLLs required, the PWA instance URL, username, password, the custom field internal name and the location of the CSV file. The account specified will need edit access to all of the projects in PWA. Ensure the variables have been updated correctly, placeholder values seen below:

image

image

The DLL’s used are from the NuGet package here: https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM/16.1.5521.1200. There are later version available, check here: https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM. Download those as required.

The get the correct custom field internal ID I use the REST API, <PWA Site URL> + /_api/ProjectServer/CustomFields. Find the project level custom field and copy the InternalName as seen below:

image

Once the PowerShell script has been updated, save it and it can then be tested on a test / non-production environment. Once executed in PowerShell, each project found in the CSV file will be outputted as seen in the example below. In this example two projects exist in the CSV data but not in my example Project Online PWA instance (remember for this example, the names need to match in the CSV file and PWA):

image

Checking in the Project Center after the script has run you can see for the projects that exist in the CSV file, the project budget includes the values found in the CSV file:

image

This PowerShell script could be run on a schedule from a server on-prem or even in Azure. The script would just need access to the data to import (CSV file etc.) and the DLLs. Fully test this script on a test / non-production PWA instance before running on a Production PWA instance.

The script is provided "As is" with no warranties etc.

#ProjectServer / #ProjectOnline error opening Enterprise Resource Pool #MSProject #Office365 #PPM

October 10, 2016 at 8:17 am | Posted in Administration, Functionality, Information, Issue, Workarounds | Leave a comment
Tags: , , , , ,

A quick post to highlight an issue and workaround for opening the Enterprise Resource Pool in Project Pro using the Open button on the Resources tab in the Resource Center:

image

If you try and click the Open button with no resources selected in the grid you will get the error below:

“This action couldn’t be performed because Office doesn’t recognize the command it was given” :

image

Select at least one resource in the grid then this command will work fine.

Next Page »

Blog at WordPress.com.
Entries and comments feeds.