#sp2013 Site Collection Audit Reports for Business Users

July 26, 2015 Leave a comment

While working on recent 2013 project we had a requirement to allow business users to view site collection audit reports but not be site collection administrators.

Looking into this we could see that there was no way simple way to do this via permissions, but it was actually a very simple request to fulfil.

Firstly we setup site collection auditing for the opening of items (this was the only requirement) and set daily log trimming to a location that the end users can get to.

 

image

The next step was to configure the audit log trimming job from being monthly to daily to force the log generation.

 

image

Now we have a library with daily audit reports that business users can access.

image

 

 

Categories: SharePoint 2013 Tags:

#Project2016 – A Short Review

Few weeks ago Office products of 2016 preview version were released, that includes Office 2016 suite products, plus Project and Visio. 
All of these products are available in desktop and office 365 formats for trials.
I have shared the links to download/install preview of Office and Project 2016 in this posta while ago.
Since then I wanted to write my first hand review of Project 2016.
And here it goes:
Installation of Project 2016
First thing first, installation challenges.
Prior to installing Project 2016, same goes for Office 2016, you need to uninstall 2013 version of the same product as they both can’t stay together.
Anyone can uninstall, and then install the new version, right? Not really.
This wouldn’t be as simple as it sounds like if you also ever have installed Project 2013 office 365 version on your machine along with Project 2013 desktop version.
At least in my case, I have tried every possible way of removing 2013 version, but Project 2016 was kept crashing soon after it starts. Here, and may be few other places, have described a solution to an issue but it never worked for me and eventually I end up installing to a fresh VM that has no traces of prior version.
How it looks like
Exactly the same as its predecessor:

Compatibility with Project Server 2013

It works with Project Server 2013.
You can configure account to connect with PWA instance in a usual way.
The Ribbon
No changes in terms of design, or layout of tabs or options within those tabs. So no learning curve.
The first thing you will notice is: Tell me what you want to do  option on ribbon.
This is not just an online/local search option which can bring you list of URLs or commands to match you search, its much more than that and quite intuitive to use.
For instance I wanted to create/insert a milestone task in my project, I did:
Considering the first option most relevant to my requirement, I clicked on the first one Insert Milestone, and result is below:
Not only this helps you list down all the commands close to your requirement, it also performs action.
In past I have seen requirement of having interactive tutorial or guide which can help user with Project options while schedules. 
This option can fill that gap to some extent.

Multiple Timelines
Timelines were introduced in Project 2013, another way of presenting attractive summary of your schedules.
In Project 2016, it goes one step forward.
You can now create more than 1 timelines within same schedule.
Created one below to depict Project and Project summary tasks:
To create 2ndor more, click on timeline bar to insert another timeline:
And here goes 2nd timeline bar to present milestones of project:
The much awaited option, though not visible yet but would be either in a final version or once you will connect Project with Project Server 2016: Resource Engagement
Image taken from MS blog
Detailed description of Resource Engagement can be found here.
Enjoy Projecting 2016 J

via All about Enterprise Project Management (EPM) http://bit.ly/1KrO0kg

Khurram Jamshed
The author of the blog has an extensive experience of working as an EPM Consultant. Currently he is located in Dubai, UAE and working for Microsoft partner organization as Project Server specialist. He has a thorough experience of providing Project Management technical/functional consultancy to all sort of organizations. He is a certified PMP, a Project Server MCITP, and also received a MS community contributor award 2011.

This article has been cross posted from khurramjamshed.blogspot.com/ (original article)

Different approach to #Project team collaboration, what about #Office365 Groups? #ProjectOnline #PPM #PMO

Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

Inspired by my colleague Alan Eardley’s recent webinar on Office 365 groups, I thought it might be good to blog about this from a project perspective.

For many types of projects, team collaboration is very important. There are many different options currently to support team collaboration. The default one being the project site in a Microsoft PPM environment. Other options include email distribution groups, shared mailboxes, Yammer etc. The latest option to consider is Office 365 groups, this feature was released towards the end of last year in Office 365. A good intro video on Office 365 groups can be found here: http://www.youtube.com/watch?v=t3OLvYXepvE

Groups are managed via the Outlook Web App on your Office 365 tenant, you will see the Groups section below the folders in the left pane:

image

Clicking the blue + symbol next to the Groups heading or the “Create group” link will load a pane of the right hand side:

image

Give the group and a description. The Group ID will be generated automatically from the name you enter but can be modified if required.

image

Then choose the privacy level, typically you would probably only want the project team members or a subset of the project team to have access so in this example it will be set to Private.

image

I have also enabled the subscribe option so that members receive group conversations and calendar events in their inboxes.

Then click the Create button at the top of the pane and the group will be created:

image

Next I need to add the members to the group:

image

For this example I have only added a generic CPS user account, once all the users have been selected click the Add button at the top of the pane and you will see an adding members message:

image

Your group is then created:

image

The group name, description and image can easily be edited by clicking the edit icon on the group image or the edit group option on the ellipsis menu.

image

You can also let people outside of the organisation email the group too – these appear as normal conversations in the group. Once the changes are made click save. In this example I clicked discard then you can view the group / updates to the group.

From here members can easily start new conversations:

image

Easily reply or like a message:

image

Members can navigate to the group calendar, notebook or file share:

image

Easily create meetings in the group calendar and invite the group members:

image

image

Each group has a dedicated OneDrive site to share documents:

image

Keep in mind that if the group is deleted the documents will be lost so key documents probably want to be stored in the project site / document management portal.

You can then add a link on the Project Site to the Office 365 group if needed:

image

Take a look and see what you think.

Categories: Paul Mather, Work Tags:

#ProjectServer and #SharePoint 2010 / 2013 July 2015 Cumulative Update #PS2010 #SP2010 #PS2013 #SP2013 #MSProject

Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

The Office 2013 July 2015 Cumulative Updates are now available, please see the links below:

http://bit.ly/1I3wfqU

Project Server 2013 July 2015 Server Roll up package:
http://bit.ly/1SnR8N8

Project Server 2013 July 2015 CU:
http://bit.ly/1I3wfqV

Project 2013 July 2015 CU:
http://bit.ly/1SnRaEz

Also worth noting, if you haven’t done so already, install Service Pack 1 http://bit.ly/1uorn2C first if installing the July 2015 CU.

The Office 2010 July 2015 Cumulative Updates are now available, please see the links below:

http://bit.ly/1I3wfqU

Project Server 2010 July 2015 Server Roll up package:
http://bit.ly/1SnRaEA

Project Server 2010 July 2015 CU:
http://bit.ly/1I3wfr0

Project 2010 July 2015 CU:
http://bit.ly/1SnR8N9

SP2 is a pre-requisite for the Office 2010 July 2015 CUs.

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

Categories: Paul Mather, Work Tags:

#ProjectServer #PS2010 / #PS2013 delete #Project site using #PowerShell #SP2013 #SP2010

Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

Following on from a post / script I created a year or so ago to bulk create project sites, there have been requests to be able to bulk delete projects sites. I have been reluctant to do that as i am always cautious when “bulk” deleting! The script i have created reads the list of projects from a text file so that the user running the script knows exactly what project sites they are going to be delete. The script can be downloaded from the Microsoft Script gallery below:

http://bit.ly/1QSXuZb

The text file will need to be created with a list of projects names from your PWA instance – ONLY INCLUDE project names for the project sites you want to delete – all site data (lists, documents etc.) will be deleted as the site will be deleted! The only scenario I would really use a script like this is if I wanted to delete all of my project sites, if I only needed to remove a handful I would do it manually via the UI. The example text file can be seen below:

image

Update the location of the text file and text file name for the Get-Content command.

The web service proxy URLs will need to be updated for your PWA instance, replace the http://vm753/pwa with the correct URL.

image

The script can be seen running and deleting sites below:

From the PowerShell ISE:

image

All data from the project sites will be lost so please use this with care and only enter project names in the text file for projects sites and project site data you no longer need.

Run the script with a PWA administrator account.

Fully test this script on a test / non-production PWA instance before running on any production environment. As a precaution, take full database backups (PWA and SharePoint Content) before running the script on the production environment so that you can roll back if needed.

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

Categories: Paul Mather, Work Tags:

#Project virtual conference: call for speakers now open #ProjectOnline #ProjectServer #PPM #ProjectVConf

Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

Following on from my post the other week regarding the announcment of the Project Virtual Conference, post here: http://bit.ly/1FEnY67, the call for speakers is now open:

http://bit.ly/1e3krHx

If you are interested in speaking at this event, please do submit your sessions before 24th July.

Categories: Paul Mather, Work Tags:

#ProjectOnline / #ProjectServer 2013 update Owner label on PDP #JavaScript #jQuery

Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

A quick post to support a very simple script to change the Owner display label on a Project Detail Page page. Quite often clients request to change the Owner to something else such as Project Manager. The script can be downloaded from the script gallery below:

http://bit.ly/1FOXor1

This code will replace “Owner” with “Project Manager” but can easily be updated.

To get the script to work you will need to download the following jQuery library: jquery-2.1.1.min.js – jQuery download Another version of this library may work but this was the one I used / tested with. Upload this library to your PWA site collection then update the script file with the correct location. I uploaded this file to the style library as you can see in the code below:

image

Alternatively you can reference a CDN if preferred.

Once the script is downloaded, upload this to the PWA site collection, in this example it was uploaded to the shared documents library. Select the PDP that has the Owner field displayed, then reference the uploaded script using the content editor web part:

image

In this example it is the Project Information PDP.

Once loaded, Owner will display as Project Manager:

image

One thing this script doesn’t handle is if you have another custom field on the page that contains “Owner” in the string, that will also get replaced :)

This is a very simple script but do test this before rolling out to production etc.

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

Categories: Paul Mather, Work Tags:
Follow

Get every new post delivered to your Inbox.

Join 1,787 other followers

%d bloggers like this: