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

August 10, 2017 at 7:46 am | Posted in Administration, CU, Fixes, Functionality, Information, Installation | Leave a comment
Tags: , , , , , , ,

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

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

Project 2016 August 2017 update:
https://support.microsoft.com/en-us/kb/4011034

SharePoint Server 2016 / Project Server 2016 August 2017 update: 
https://support.microsoft.com/en-us/kb/4011049 & https://support.microsoft.com/en-us/kb/4011053

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

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

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

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

Project 2013 August 2017 update:
https://support.microsoft.com/en-us/kb/4011084

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

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

Running #ProjectOnline #PowerShell in #Azure using #AzureFunctions #PPM #Cloud #Flow #LogicApp Part1

July 28, 2017 at 4:50 pm | Posted in Add-on, Administration, App, Configuration, Customisation, Fixes, Functionality, Information, PowerShell, Workflow | 4 Comments
Tags: , , , , , ,

Following on from my last post where I published an example solution starter PowerShell script for adding project team users to the Project Site, here I mentioned about running the script in an Azure Function and even running this sync from a Project Online event. The blog post can be seen below if you missed that:

https://pwmather.wordpress.com/2017/07/07/projectonline-project-user-sync-to-project-sites-ppm-o365-powershell-sharepoint/

Whilst I will use that example PowerShell script from my last blog post as an example, the concept will work for any PowerShell script.

I wont cover the details in setting up the Azure Function in part 1 as there is plenty of support out there for this – for this example I created an Http Trigger – PowerShell function.

image

I then uploaded the SharePoint DLLs and copied in the PowerShell script into the editor:

image

The project site user sync script didn’t work as is as I had to make some minor changes to get this to run from the Azure Function. This included change the way the SharePoint CSOM DLLs where loaded in. In the example script I used Add-Type to load the DLLs but in the Azure Function I had to switch this out to use Import-Module:

image

The next change I had to make was to comment out all of the feedback to the console, so all of the write-hosts. I also had to remove the functions within the script so that is was one block. After these changes I could execute the PowerShell script to add the project team members from my example project into the associated project site from the Azure Function. As this was an HTTP Trigger Azure Function, you can get the URL to the function and access that URL to execute the function.

This opens up lots of possibilities to easily execute this Azure Function from other applications that can make the HTTP call. For example you build easily execute this script once the project has been published either using a remote event receiver (RER) or a Microsoft Flow / Azure Logic App. The example script would need to be made generic and pass in a variable into the Azure Function for it to be a workable solution.

In part 2 of this blog post we will look at make a full event driven solution that is fired on project publish then executing the Azure Function and passing in a variable.

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

July 16, 2017 at 2:25 pm | Posted in Administration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , , , ,

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

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

Project 2016 July 2017 update:
https://support.microsoft.com/en-us/kb/3203476

SharePoint Server 2016 / Project Server 2016 July 2017 update: 
https://support.microsoft.com/en-us/kb/3213544 & https://support.microsoft.com/en-us/kb/3213543

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

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

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

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

Project 2013 July 2017 update:
https://support.microsoft.com/en-us/kb/3213538

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

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

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

Update for script to report across #ProjectOnline Project Sites for #SharePoint list data #PPM #JavaScript #Office365 #REST #OData

June 3, 2017 at 8:58 pm | Posted in Configuration, Customisation, Fixes, Functionality, Information, Reporting | Leave a comment
Tags: , , , ,

I have made a quick change to the example solution starter script to fix a common encoding issue with the EPT names. For example, if your EPT name is “R & D”, the original example solution starter script wouldn’t handle this when querying the Project OData API. It would pass in R & D when querying the OData API but the OData API call fails as it should use R %26 D. I have updated the solution starter code to handle this and encode the EPT name before querying the Project OData API. The solution starter code can be downloaded here:

https://gallery.technet.microsoft.com/Report-on-Online-list-data-f5cbf73f

If you didn’t seen the original post or solution start script before, see the post below:

https://pwmather.wordpress.com/2017/05/05/want-to-report-across-projectonline-project-sites-for-sharepoint-list-data-ppm-javascript-office365-rest-odata/

This script is still a solution starter and should be updated for production use to include the correct data you want, improve error handling, support the REST API pagination, split out HTML, CSS and JavaScript etc.

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

#ProjectOnline issue with #PowerBI and the #OData URL with [] now fixed #PPM #BI #PMOT

April 11, 2017 at 11:59 am | Posted in Administration, Configuration, Customisation, Fixes, Functionality, Information, Reporting | Leave a comment
Tags: , , , ,

Just a quick post to highlight that the issue with setting the credentials for a Project Online OData connection that contained the [] for localisation is now fixed in the Power BI Service. If your OData URL contained the [] to specify the OData localisation you couldn’t set the credentials in the Power BI Service for the data refresh, you would see the error below.

For the details on the error see a previous post of mine, see the Note halfway down the post: https://pwmather.wordpress.com/2017/02/10/projectonline-ppm-powerbi-report-pack-publish-bi-reporting-powerquery-dax-office365/

It’s good to finally have this issue fixed in Power BI. The Project Online Power BI report pack I created will now refresh / work as expected in the Power BI Service: https://pwmather.wordpress.com/2017/01/03/projectonline-ppm-powerbi-report-pack-bi-reporting-powerquery-dax-office365/

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

Next Page »

Blog at WordPress.com.
Entries and comments feeds.