Tuesday, 19 May 2015

Enterprise Calendars Use Case

Applies: Project Server 2007+

Here are a few considerations when working with Enterprise Calendars. Enterprise Calendars can be assigned to Projects, Resources and Tasks.


1) Project Calendar

An Enterprise Calendar assigned to a Project impacts all the Tasks within the project schedule. E.g. tasking will NOT take place on weekends etc.

Note: ensure that the project scheduling OPTIONS for task working times match that of the project calendar.

PMO will need to keep this Enterprise Calendar updated for exceptions such as weekends, public holiday etc.


2) Resource Calendar

Resource Calendars are based on a specific Enterprise Calendar, normally the BASE calendar that the project is based on, so that it inherits the exceptions such as weekends, public holiday etc.


Resource Managers/PMO can add further exceptions to the resource calendar for specific resource availability/exceptions e.g. holidays etc.

Note: if a Resource calendar is based on a different BASE calendar to that of the project, then the resource calendar scheduling will take precedence. E.g.  an international Project is based on UK holidays and Resource in Middle East is based on UAE calendar (with Friday/Sat off and Sun working). Any task that has the UAE resource assigned will show as working on Sunday. The scheduling for the assigned task  is governed by the working times of the resource on that task, i.e. based on that resource’s calendar (BASE Calendar + exceptions).


3) Task Calendar

If you want to override the default scheduling behaviour of resource calendar, then you will need to set the scheduling exception against the task and assign a different/specific calendar. See figure below to override the Resource Calendar scheduling.


Note: if you want to update multiple[le task calendars en-mass, inside of a project,  you can insert the following two columns/built in fields. And then Copy/fill-down to all the tasks in the project. Alternatively, you can write a macro and add to Enterprise Global, to do this for programmatically.


Hope this helps.

Wednesday, 6 May 2015

SharePoint Server 2016 update

Today, Microsoft confirmed that SharePoint Server 2016 will become generally available in Q2 2016, with a public beta planned for Q4 2015, and commitment to delivering on-premises releases of SharePoint for the foreseeable future. There will be support for combination of on-premises, cloud and hybrid deployments for many years to come.  Learn More>>

Thursday, 12 March 2015

How to Delete OLD Status Reports to avoid Receiving Alerts and Notifications

Affects: Project Server 2007+

To delete/remove old Status Reports, do the following;

1) Navigate to the the Status Reports Page

2) Select the specific Status Report Request

3) Click Delete Request on the Toolbar


If you delete your REQUEST the associated RESPONSES for that Request will also be deleted by the system automatically. If, however, another PM has sent you a REQUEST that you need to respond to, then please ask them to remove their REQUEST.

Hope this helps.

Wednesday, 4 March 2015

SharePoint & Project Server – Feb 2015 Public Updates Really??

The last update for SharePoint & Project Server 2013 was announced as Public Update available along with Windows Updates! Here is why you should disable this immediately?

SharePoint and Project Server updates need to be applied planned with DUE CARE;

  1. Applied ONLY if you have an issue that is resolved by the update.
  2. Applied after due testing on your dev/test environment with COPY of live data. Testing to include key/normal business processes.

A few key things to remember with SharePoint and Project Server updates/patching;

  1. There is no roll-back for SharePoint and Project Server, as there is for Windows update!! if you have some data related issues or key services running in the background, then patching will not be applied correctly. Remember, key services need to be STOPPED prior to patching on each Web Server. Surely you would want to take precautions, take full backups, ensure you have a bullet proof roll-back/back-out plan in the event of failure.
  2. Patching is a two two step process. If you simply update bits and database schema is not upgraded by running the SharePoint Configuration Wizard on each web server, then your databases will be left in COMPATIBILITY mode, leading to potential issues and unknown data corruption downstream.
  3. Project Pro is recommended to be at the same patch level as the server, so you would have to update/patch ALL the users’ client application at the same time.
  4. Some Patches have dependencies on other Service Packs!

SharePoint/Project Server System Administrators should apply the patches manually as a carefully planned exercise. Take control of your system today!!

I will follow up this post with steps/guidelines to manually patch your SharePoint and Project Server 2013 environment.

Tuesday, 3 March 2015

Amazing? New Microsoft Surface Hub

New Microsoft Surface Hub Announced–Interactive White Board Powered by Windows 10


AIIM’s 2015 SharePoint Survey

AIIM’s 2015 SharePoint Survey Published: Adoption, Executive Commitment and Governance Still Major Challenges


Tuesday, 4 November 2014

SQL Server 2008 SP4 Released

After releasing SQL Server 2008 R2 SP3 earlier in the month, Microsoft followed up with the release of the final service pack for the first revision of SQL Server 2008.

SQL Server 2008 SP4 include s a rollup of all 17 updates released for SQL Server 2008 SP3 (listed here).  According to a Microsoft blog entry, any updates moving forward will not include functional fixes. While this marks the end of cumulative updates, Microsoft will continue to provide security updates as needed and within the guidelines of its mainstream and extended support policies.

For details and download information on SQL Server 2008 R2 SP3, go here. For SQL Server 2008 SP4, go here