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

February 14, 2018 at 7:39 am | Posted in Administration, CU, Fixes, Functionality, Information, Installation | Leave a comment
Tags: , , , , , , ,

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

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

Project 2016 February 2018 update:
https://support.microsoft.com/en-us/kb/4011672

SharePoint Server 2016 / Project Server 2016 February 2018 update: 
https://support.microsoft.com/en-us/kb/4011680

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

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

Project Server 2013 February 2018 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/4011694

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

Project 2013 February 2018 update:
https://support.microsoft.com/en-us/kb/4011679

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 2018 CU for 2013.

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

Advertisements

#ProjectServer and #SharePoint 2013 / 2016 January 2018 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject

January 13, 2018 at 9:13 am | Posted in Administration, CU, Fixes, Functionality, Information, Installation | Leave a comment
Tags: , , , , , , ,

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

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

Project 2016 January 2018 update:
https://support.microsoft.com/en-us/kb/4011633

SharePoint Server 2016 / Project Server 2016 January 2018 update: 
https://support.microsoft.com/en-us/kb/4011642 & https://support.microsoft.com/en-us/kb/4011645

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

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

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

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

Project 2013 January 2018 update:
https://support.microsoft.com/en-us/kb/4011640

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 2018 CU for 2013.

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

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

November 16, 2017 at 9:20 am | Posted in Administration, CU, Fixes, Functionality, Information, Installation | Comments Off on #ProjectServer and #SharePoint 2013 / 2016 November 2017 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject
Tags: , , , , , , ,

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

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

Project 2016 November 2017 update:
https://support.microsoft.com/en-us/kb/4011227

SharePoint Server 2016 / Project Server 2016 November 2017 update: 
https://support.microsoft.com/en-us/kb/4011243 & https://support.microsoft.com/en-us/kb/4011244

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

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

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

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

Project 2013 November 2017 update:
https://support.microsoft.com/en-us/kb/4011235

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

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

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

October 19, 2017 at 1:32 pm | Posted in Administration, CU, Fixes, Functionality, Information, Installation | Comments Off on #ProjectServer and #SharePoint 2013 / 2016 October 2017 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject
Tags: , , , , , , ,

The Office 2016 October 2017 updates and cumulative updates are now available – post a bit later than normal, please see the links below:

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

Project 2016 October 2017 update:
https://support.microsoft.com/en-us/kb/4011141

SharePoint Server 2016 / Project Server 2016 October 2017 update: 
https://support.microsoft.com/en-us/kb/4011217 & https://support.microsoft.com/en-us/kb/4011161

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

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

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

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

Project 2013 October 2017 update:
https://support.microsoft.com/en-us/kb/4011156

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

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

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

September 13, 2017 at 9:24 pm | Posted in Administration, CU, Fixes, Functionality, Information, Installation | Comments Off on #ProjectServer and #SharePoint 2013 / 2016 September 2017 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject
Tags: , , , , , , ,

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

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

Project 2016 September 2017 update:
https://support.microsoft.com/en-us/kb/4011101

SharePoint Server 2016 / Project Server 2016 September 2017 update: 
https://support.microsoft.com/en-us/kb/4011127 & https://support.microsoft.com/en-us/kb/4011112

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

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

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

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

Project 2013 September 2017 update:
https://support.microsoft.com/en-us/kb/4011109

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

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

#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 | Comments Off on #ProjectServer and #SharePoint 2013 / 2016 August 2017 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject
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.

#ProjectOnline – 1 PWA site collection for all or 1 per department? #O365 #PPM #PMOT #Office365 #MSProject

March 20, 2017 at 6:55 pm | Posted in App, Configuration, Customisation, Functionality, Information, Installation | Comments Off on #ProjectOnline – 1 PWA site collection for all or 1 per department? #O365 #PPM #PMOT #Office365 #MSProject
Tags: , , , , ,

A question I hear a few times from organisations is “We have a new department or business unit coming on-board with Project Online, do we need a new PWA instance for them or can we use the one we already have?” The answer isn’t normally a straightforward yes or no. This post aims to cover most of the questions you need to ask when considering using the existing PWA site collection or creating a new one for a new department / business unit.

The first thing to consider is the Project Online limitations for the data such as number of projects per PWA site, check out the limits here: https://support.office.com/en-us/article/Project-Online-software-boundaries-and-limits-5a09dbce-1e68-4a7b-b099-d5f1b21ba489. Check how many projects you currently have in the PWA site collection and how many more the new business unit expect to add into the PWA site collection – if you are going to be reaching the limits on a PWA site collection then consider a dedicated PWA site collection for the new business unit. The number of PWA site collections in each Office 365 tenant will not be an issue – you can have up to 9,999. Just because you can have lots of PWA site collection doesn’t automatically mean the answer is a new PWA site collection each time!

One PWA site collection will support different PWA configurations for each business unit or department (custom fields , Enterprise Project Types etc.) by making use of the Department functionality to separate those configuration items. So for example, the R&D department only see configuration items relevant to them. So if the new business unit has different custom field / EPT requirements, that shouldn’t be a problem using a single PWA instance.

Whilst talking about configuration items, there are some items that are at the PWA site collection level that can’t be configured / tailored to each business unit or department. These would be some of the Time and Task Management options such as Time Reporting Periods, Timesheet settings and Task settings. Also some settings under the Operational Policies such as Additional Server Settings. If the new business unit has different requirements for time capturing they would need a dedicated PWA instance.

Another important aspect to consider is – will these different business units require access to the same enterprise resources to assign to tasks? Will they need to view the true resource demand / availability for these resources in one place? If this is the case then the easiest option is for the new business unit to use the same PWA site collection.

If there is a requirement to see the data from each business unit together in PWA, for example in a project center view then a single PWA site collection would be required. Similarly, if both business units projects needed to be included in the organisations portfolio strategic analysis for cost and resource requirements, a single PWA site collection will be required.

Reporting is another key factor, if the reports need to show data from all business units / departments then a single PWA instance is easier but it is still possible to generate reports that use data from multiple PWA site collections. With multiple PWA site collections this is something that can be worked around providing there was common metadata between the PWA site collections to enable projects from both PWA site collections to be viewed in the same report.

Then there is the management of the PWA site collection/s. It might be that the organisation has a central PMO function that administers the PWA site collection – adding another PWA site collection will increase their workload.

This is by no means an exhaustive list, here are just a few of the things to consider when deciding on using the existing PWA site collection or a new PWA site collection when a new business unit / department are coming on board.

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

January 19, 2017 at 3:48 pm | Posted in Administration, Configuration, Functionality, Information, Installation | Comments Off on #ProjectServer 2016 environment migration / rollover steps #PowerShell #PS2016 #MSProject #SP2016
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.

CPS’ PS+ solution is an Award Winner at the #Microsoft Partner Awards #WPC16 for #PPM #ProjectOnline / #ProjectServer

May 31, 2016 at 5:24 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, Installation | Comments Off on CPS’ PS+ solution is an Award Winner at the #Microsoft Partner Awards #WPC16 for #PPM #ProjectOnline / #ProjectServer
Tags: , , , ,

I am pleased to announce that CPS’ PS+ solution was an Award Winner in the recent Microsoft Partner of the Year Awards 2016 in the Project and Portfolio Management Competency.

PS+ logo

http://projectserverplus.com/project-and-portfolio-management-award-winner-2016/

http://www.cps.co.uk/blog/cps-named-microsoft-project-portfolio-management-award-winner-2016/

For a full list of winners and finalists see:

https://partner.microsoft.com/en-GB/WPC/awards

Great work to all the partners that received awards.

#ProjectOnline / #ProjectServer #Project site provisioning using #Office365 PnP remote provisioning #SharePoint #PowerShell

May 4, 2016 at 4:20 pm | Posted in .Net, Add-on, Administration, App, Configuration, Customisation, Functionality, Information, Installation | 1 Comment
Tags: , , , , , ,

For many years now Project Server deployments have used Project Sites or known as Project Workspaces before Project Server 2010. Typically most deployments have custom requirements for the sites so custom site templates were created from a site created using the default Project Site template. The updated custom site template was then linked to the Enterprise Project Type so that new projects created used the new site template. The biggest issue with this approach was that if you wanted to update the site template later on down the line all of the existing project sites would either need manually updating or writing code to traverse through all the existing sites and make the changes. With the new online world in Office 365 there are other things to think about too. If you create a new custom site template based on the default Project Site template then Microsoft roll out a new feature in the base Project Site template – your new project sites wont get that change either. This is where the PnP remote provisioning engine is great. For a while now – at least a year or 2 I think, the best practise is to stick with the default site templates Microsoft provide, so the Project Site template for example. The Enterprise Project Types should use the default Project Site template so each new project gets a site created using the default site template. But what about my custom lists, or columns or views I hear you ask – deploy the custom artefacts once the site is created from the default site template. In this post I will give you a very quick introduction to the Office 355 PnP Remote Provisioning engine which is part of the PnP core component. PnP, known as Patterns and Practices – details can be seen here: http://dev.office.com/patterns-and-practices. This will enable you to deploy your custom site artefacts.

For this example we will look at the PowerShell variant: https://github.com/OfficeDev/PnP-PowerShell but is also available with managed code. To get started with the PowerShell version follow the steps in the GitHub link to get the components installed. I have created a project / project site using the default Project Site template and added a new list called Change Requests that is linked to a Site Collection Content type in my root PWA site collection:

image

This list has two views:

image

I have also updated the default Risks list to use custom content type and included one new column:

image

I have added my new column to the All Items view:

image

This is the new site template I want to use. Typically this is where you would save as a template but not for this example.

Once the PnP components are installed on your machine, connect to the source project site using this command – update the Url for your site:

Connect-SPOnline –Url <source site URL> 

image

Enter credentials if prompted to do so.

Now use the following command to extract the site:

Get-SPOProvisioningTemplate -Out C:\Temp\PnP\NewTemplate.xml

image

This process will extract the site definition and create an XML file in the specified location:

image

At this point the XML should be modified to remove unneeded properties. For example, as this project site is linked to a project already the property bag will contain certain properties referenced to the source site – I don’t want to overwrite these settings on my target sites so I removed the property bag entries highlighted below.

image

I have also removed properties for configuration I don’t need to update, other lists etc.  See an example below, I have only left the two lists I have added / updated:

image

I don’t cover this here but I used Visual Studio – really one for the devs out there.

Once you are happy with the source XML file you are ready to deploy this to the existing project site/s. In this example I have a test project site created by the default Project Site template that has not been modified:

image

In PowerShell I now connect to the test target site using the command below – update the Url for your site:

Connect-SPOnline –Url <target site URL> 

image

Then run the following command to apply the changes:

Apply-SPOProvisioningTemplate -Path C:\Temp\PnP\NewTemplate.xml

image

Once completed the test target site should be updated, in this example, with a new list and updated risk list. Once you are happy with the test target project site you could repeat the process on other project sites. I have found some settings are not set correctly and some do generate errors in PowerShell but there are usually monthly updates the PnP code so always ensure you regularly update the modules using the Update-Module command.

This is a very simple example using PowerShell, in production you might have a full script that has a list of Project Sites you want to update and get the script to update them all etc. Or better still, go down the manage code route and create an event driven SharePoint provider hosted add-in to do it. Either way, fully test this process on test project sites / projects first before any production projects / project sites!

Next Page »

Create a free website or blog at WordPress.com.
Entries and comments feeds.