#PowerShell scripts for #ProjectServer #PS2013 #SP2013 #PPM
|
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) |
I haven’t posted for a while due to work commitments and just generally being too busy – I am hoping this will change after the summer!
Anyway, just a quick post today to let you know that I have tested some of the key PowerShell scripts I wrote for Project Server 2010 on Project Server 2013. These also work for Project Server 2013. I have since updated the script gallery and associated blogs posts for these scripts listed below:
Publish All Projects:
http://gallery.technet.microsoft.com/scriptcenter/Server-2010-Publish-all-45ba385b
Publish Specified Projects:
http://gallery.technet.microsoft.com/scriptcenter/Server-2010-Publish-537857d8
High-level Audit example:
http://gallery.technet.microsoft.com/scriptcenter/Server-2010-High-level-e9c6ad09
Updating Project Server Lookup Tables:
http://gallery.technet.microsoft.com/scriptcenter/Update-Server-Lookup-table-bb1ae14f
My other scripts are available for download here:
http://gallery.technet.microsoft.com/scriptcenter/site/search?f%5B0%5D.Type=User&f%5B0%5D.Value=PWMather
Look out for more scripts coming soon.
Enjoy ![]()
#ProjectServer and #SharePoint 2010 / 2013 August 2013 Cumulative Update #PS2010 #SP2010 #PS2013 #SP2013 #MSProject
|
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 August 2013 Cumulative Updates are now available, please see the links below:
http://support.microsoft.com/kb/2873346
Project Server 2013 Server Roll up package August 2013 CU (Recommended):
http://support.microsoft.com/kb/2817615
Project Server 2013 August 2013 CU (Included in the Server Roll up package):
http://support.microsoft.com/kb/2817508
Project 2013 August 2013 CU:
http://support.microsoft.com/kb/2817502
Also worth noting, if you haven’t done so already, install the March 2013 Public update: http://support.microsoft.com/kb/2768001 if installing the August 2013 CU.
The Office 2010 August 2013 Cumulative Updates are now available, please see the links below:
http://support.microsoft.com/kb/2869757
Project Server 2010 Server Roll up package August 2013 CU (Recommended):
http://support.microsoft.com/kb/2817573
Project Server 2010 August 2013 CU (Included in the Server Roll up package):
http://support.microsoft.com/kb/2817580 & http://support.microsoft.com/kb/2817587
Project 2010 August 2013 CU:
http://support.microsoft.com/kb/2817584
Remember SP1 or SP2 is a pre-requisite for the Office 2010 August 2013 CUs.
For more details please see:
As always, test these updates on a replica test environment before deploying to production
#Office365 Two Factor Authentication (Preview) (Phone Factor) #O365
So I am about to embark on a client who is interested in two factor authentication in their existing Office 365 environment.
With the speed Microsoft is going at these days, surely there is a solution to this and speaking to some contacts with Oliver Stickley, Microsoft helped us out.
What is Two Factor Authentication?
Single factor authentication is via a single method such as a Username and Password.
Two Factor Authentication adds an extra measure into the mix to ensure that you are who you say you are. This could be an RSA Security Key or more recently the market is shifting towards using mobile phones as the security key with the use of automated phone calls, text messaging (SMS) or mobile apps.
The Solution
In October 2012, Microsoft acquired a company called PhoneFactor (more info) which has been developing two factor authentication solutions in the cloud for a while now and recently the capabilities have been added to Office 365 in the form of a preview which is free to try for Administrators.
NB: Please be aware that this is currently in preview, so they are still working out the kinks, pricing model, release schedules etc..
Given that we are in preview, not everything will be perfect, but there is still options that you can try out now assuming you have an Enterprise plan.
Three options are available:
- The various pros and cons of each option are described below in the video presentation.
NB: I can confirm that this is not available on the P1/P2 plans but unsure about the small business plans.
How does it work?
As part of my research I came across this excellent presentation from Microsoft Consulting Services which goes into detail about how the solution works.
Ignite Webcast – Understanding Identities and Single Sign On
NB: Please note that some limitations exist with non-ADFS setups and local client software (Outlook, Office etc.). (it is a preview after all)
2nd Factor Authentication Options
So we know what two factor authentication is all about and we have seen how it is likely to work within Office 365, lets explore the options we have available to us:
Phone Call & SMS
Using any mobile phone (smart, non-smart or event an office phone), you can log-in with an automated phone call from Microsoft or an SMS Text Message which provides and authentication code.
Mobile App – Windows Phone 7 & 8
If you don’t have phone signal, then you can use generated no. authentication methods via a mobile app. Microsoft of course support their own platforms
- Release Details: PhoneFactor Extends Comprehensive Line of Authentication Solutions with App for Windows Phone
- App Download Link: http://www.windowsphone.com/en-gb/store/app/multi-factor-auth/0a9691de-c0a1-44ee-ab96-6807f8322bd1
- NB: Apps were originally called PhoneFactor but are now called Active Authentication
- Name Change Details: PhoneFactor Becomes Windows Azure Active Authentication
Mobile App – iOS / Android
The mobile app is also available for iOS and Android as well which pretty much covers most of the mobile market. Search for Active Authentication from the Microsoft Corporation or use the links provided below.
iPhone Screens:
iOS (iPhone / iPad) App Download: https://itunes.apple.com/gb/app/active-authentication/id475844606?mt=8
Android Screens:
Android App Download: https://play.google.com/store/apps/details?id=com.phonefactor.phonefactor&hl=en
That’s great, how do I get started?
Excellent question, it’s available in your Office 365 admin panel right now and is incredibly easy to setup without ADFS…
Login to your Office 365 admin portal, click Users and Groups:
Click the set up link shown above.
Now select the name you want to use two factor authentication with and click enable.
Please keep at least one admin account with single factor authentication whilst you are using this preview version.
NB: Admins are free to use the capability, standard users require a license.
Once you have turned it on against your admin user account. Log out and log back in. You will be asked to initially verify your second type of authentication.
Choose your preferred option from below:
NB: You will find this link useful later as in the preview there doesn’t appear to be a link within the Office 365 interface:
Even though it is Windows Azure based, login with your Office 365 account details.
That is it. You are setup and working.
Preview documentation is available on TechNet here:
- If you would like to use ADFS, take a look at the links above and perhaps contact your favourite Microsoft partner (hint: CPS (http://www.cps.co.uk) to help you out.
- Ok, v.long post today but hopefully you will all find it useful. Till the next time…
#ProjectServer #ProjectOnline highlight report example #PS2013 #SP2013 #Excel #BI #Office
|
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 common requirement for clients is to have a report that highlights key information about each project. This usually includes any key project level fields, up and coming tasks / milestones and any active issues or risks. For previous versions of Project Server, in my opinion, the best reporting technology for this was SQL Server Reporting Services (SSRS). For Project Server 2013 on-premise installations SSRS is probably still the best option for most reports due to the flexibility around formatting, layout etc. For Project Online, unfortunately SSRS is not an option, a nice option for a project highlight type report is Power View. This blog post will walkthrough creating a project highlight report using OData and Power View for Project Online. This example report contains key project level data, key milestones due to complete this month, future key milestones, active issues and active risks. The OData feeds used are:
https://<serverurl>/pwa/_api/ProjectData/Projects()?$filter=ProjectType ne 7&$select=ProjectId,ProjectName,ProjectOwnerName,ProjectStartDate,ProjectFinishDate,ProjectWork,ProjectCost,TotalCost,ProjectQuality,ProjectSchedule,ProjectCost,ProjectResource
https://<serverurl>/pwa/_api/ProjectData/Tasks()?$filter=TaskFinishDate gt datetime’2013-08-01T00:00:00′ and TaskFinishDate lt datetime’2013-09-01T00:00:00′ and KeyMS eq ‘Yes’&$select=ProjectId,TaskIndex,TaskName,TaskStartDate,TaskFinishDate
https://<serverurl>/pwa/_api/ProjectData/Tasks()?$filter=TaskFinishDate gt datetime’2013-09-01T00:00:00′ and KeyMS eq ‘Yes’&$select=ProjectId,TaskIndex,TaskName,TaskStartDate,TaskFinishDate
https://<serverurl>/pwa/_api/ProjectData/Issues()?$filter=Status eq ‘(1) Active’&$select=ProjectId,IssueId,Title,Discussion,Resolution,Owner,DueDate
https://<serverurl>/pwa/_api/ProjectData/Risks()?$filter=Status eq ‘(1) Active’&$select=ProjectId,RiskId,Title,MitigationPlan,ContingencyPlan,Owner,DueDate
These feeds need to be added to Excel 2013 using the “From OData Data Feed” option found on the DATA tab:
Paste the feed URL into the Link or File field:
Click Next
Select the Projects table:
Click Next
Click Finish
Select Only Create Connection and Click OK
Repeat these steps to add the other OData feeds using the same steps.
Once all of the feeds have been added, the table relationships need to be created. On the DATA tab in Excel click Relationships. This can be found in the Data Tools group.
Click New
Set up the relationships required, for this example the relationships are:
Click Close
On the INSERT tab click Power View
Design the report as required, in this example we are using Project Name as a slicer to filter the data on the other tables, this can be seen below:
Once the report layout meets your requirements, save this to Project Online. The report can then be accessed and refreshed in the browser:
Clicking a different project on the slicer will filter the data:
Enjoy ![]()
So… you want to print a List Item (dispform.aspx) in #SP2010 #SharePoint do you? We’ll see about that!
As my project continues to go through UAT, it is always when you let your projects loose onto the world that you find the niggles and the minor issues.
So having worked out the email issues (previous post) and a few other bits and bobs. This issue came along and flumuxed me for a sec.
Scenario:
Browser: IE8, IE9
Environment: Microsoft SharePoint Server 2010 Enterprise SP1
When opening the view item value from a list (dispform.aspx), those with a large body of text in any multiple lines of text fields appeared fine on the screen.
However on print preview / paper the text stopped at the end of the page, then it moves on to the next field.
Frustrat-icon!
I hear you say.
What on earth could that be?
I checked the previous system that I was migrating from (SharePoint 2007) and the issue was not present there. So it had to be something to do with the HTML markup right?
Well I compared the SharePoint 2010 dispform.aspx markup with the SharePoint 2007 output and apart from more divs to encase it in, the output is pretty much the same.
So I tried to override with my own print CSS but to no avail.
After Further Investigation…
It appeared to be the doc type. By default, in SharePoint 2010, this is set to IE8, where as in SharePoint 2007 it is set to IE7. This combined with IE8 or IE9 caused the issue.
Internet Explorer 10 and Chrome however, no issues.
How did we resolve?
At the moment we are potentially going to set the doc type to IE7 for this web application. We are lucky that in this scenario, this may work as a quick fix.
However, as for the full solution, that is still to work out!
Useful Links:
Group Policy reference for IE8: http://www.microsoft.com/en-us/download/details.aspx?id=3648
#ProjectServer #PS2010 / #PS2013 Add a background image to homepage #SP2010 / #SP2013 #ProjectOnline
|
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) |
Quite a nice personal touch for a PWA instance is to add the company logo as the background image. This is very simple to do for both 2010 and 2013, 2013 is even easier than 2010.
Firstly we will look at 2010, the quickest way to add an image to the PWA homepage is to use CSS, an example is below:
Update the image URL to the correct image, save the CSS in notepad or preferred editor, for this example I called the file backimage.inc. Then upload the file to PWA, in this example it was uploaded to the Shared Documents library. Edit the PWA homepage and add a content editor web part, then link to the backimage.inc file:
Apply the change and click OK, then save the page and you will see your image set as the background:
For 2013 you just click Change the Look from the settings cog, click current:
Click Change and browse to the image and add. Click Try it out, if you are happy with the image, click Yes keep it:
This will add the image to all pages in 2013. ![]()
Attachment is missing from an e-mail message #SharePoint #SP2007 #SP2010 #SP2013
At a client recently, we were having the issue of emails being sent to a list but the attachments were not appearing with the email.
In this scenario, it was working if we sent it directly to the list email address, but if we forwarded from Exchange via a contact, no attachments came through.
Anyway, it would appear the following needs to be set:
If attachments are missing from email messages that are sent to a SharePoint document library, it might be because you associated the document library with an email address. When you do this, Directory Management Service may not add the following two attributes to the user associated with the email address:
-
internet Encoding = 1310720
-
mAPIRecipient = false
- Full details are below.
Windows SharePoint Services 3.0 / Microsoft Office SharePoint Server 2007
- http://support.microsoft.com/kb/926891
- http://technet.microsoft.com/en-us/library/cc287879(v=office.12).aspx#section8
SharePoint Foundation 2010 / SharePoint Server 2010
SharePoint Foundation 2013 / SharePoint Server 2013
Timesheet Managers in Project Server 2013
Quick Recap
One of the new features in Project Server 2013 was to do with Timesheet Managers – i.e. those that approve timesheets. In previous versions of Project Server, this was controlled via the “Accept Timesheets” permission, but the functionality has now been split out into a new section under Server Settings (PWA Settings if you haven’t added Server Settings to the Quick Launch).
Here’s the old 2010 group permissions:
And the new 2013 group permissions:
There are a couple of other permissions missing from the group permissions in 2013, but I won’t cover those in this post.
The Technet article about permissions for 2013 appears to be out of date (still listing the ‘Accept Timesheets’ permission), but it works as a good overview of the permissions required:
http://technet.microsoft.com/en-us/library/cc197631(v=office.15).aspx
Setting Permissions
There are two methods for timesheet approval within Project Server 2013 – fixed approval, which will turn timesheets in to the resource’s designated timesheet manager, or non-fixed approval, which allows the resource to choose the next approver for the timesheet. This method allows for the approval chains that were available in Project Server 2010.
To set up fixed approval routing – navigate to Server Settings > Timesheet Settings and Defaults and make sure you have checked the ‘Fixed Approval Routing’ option:
When submitting a timesheet with this mode on, the submission screen will look like this:
Disabling fixed approval routing will cause the timesheet submission screen to prompt for the next approver for the timesheet:
Timesheet Managers
OK, so how do people appear in the list of approvers for timesheets? Well, there’s a new menu option in Project Server 2013 under Server Settings > Timesheet Managers:
Simply add users to this list by clicking “Add Manager:
Setting up Multiple Approvers
If you wanted to set up an approval chain so that you have, in effect, timesheet reviewers who then forward the timesheet on for approval, this is done via permissions. Because this is a category permission, you could control which groups of users’ timesheets can be approved or not. This might be useful if you wanted only a subset of resources to review timesheets for another set of resources. This could be useful for reviewing contractor timesheets, for example.
Against the group that you want to have as timesheet reviewers, make sure that the ‘Approve Timesheets’ permission is NOT set for the relevant category. In my example below, this group could approve timesheets for all current and future resources (from the My Organization category).
The above settings would make this group of users able to review all timesheets in Project Server, assuming they have been selected as the approver if you have not turned on fixed approval routing.
Note: There does appear to be a small bug with the label when using multiple timesheet approvers at the minute. This will manifest as the following:
The text says <% <%$Resources:PWA,ADMIN_ADDMODIFYUSER_BROWSE%>>
Nothing to worry about, just a label bug ![]()
More #SharePoint / #ProjectServer 2010 Service Pack 2 details #SP2010 #PS2010
So I see my fellow bloggers Paul and Khurram posted about Service Pack 2 for SharePoint and Project Server 2010.
Having looked around the blog-o-sphere, I came across some extra information that I believe will be useful to all:
Known issues when you install Office 2010 SP2 and SharePoint 2010 SP2
http://support.microsoft.com/kb/2687520
In particular if you are installing Office 2010 SP2 on Windows Server 2003 (SP2) you will need to install this patch first: http://support.microsoft.com/kb/925336
For SharePoint Server SP2 on Windows Server 2008 R2, you need to be careful of your custom XSL views from SharePoint Designer. Apparently they break but the fix is already available and it is recommended to install the June 2013 CU (or later) on top of the SP2
Links for June 2013 CU for SharePoint 2010:
The Full Server Packages for June 2013 CU are available through the following links:
- Download SharePoint Foundation 2010 June 2013 CU
- Download SharePoint Server 2010 June 2013 CU
- Download SharePoint Server 2010 with Project Server June 2013 CU
After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.
Locations of all the SP2 download packages around SharePoint, Project Server, FAST, Office Web Apps, Office 2010 products etc…
Next up is that we of course need to consider the different products that we have installed in our farms. Do we have FAST or Office Web Apps?
This link will help: http://support.microsoft.com/kb/2687522
Further links are available here, including Office, Project, Visio, SharePoint Designer and the CSOM binaries:
- http://support.microsoft.com/kb/2687521/en-us
- http://blogs.msdn.com/b/joerg_sinemus/archive/2013/07/24/sharepoint-server-2010-sp2.aspx
- I haven’t seen a service pack 2 for the language packs yet, but will update if it comes up soon.
Changes for SharePoint / Office 2010 SP2 that are not in Cumulative / Public Updates
Handily Microsoft have also released a spreadsheet detailing the changes and additions as part of Service Pack 2. Be aware that these are not included in any previous CU / PU.
http://support.microsoft.com/kb/2687453
Ok, hopefully you will all find the above useful. Till the next time…
DATEADD DAY parameters and the float based values #SQL #SSRS #SharePoint #CPSReportLink
Just a quick one. Recently bug fixing an issue with an SSRS report that calculated the date and time an SLA was due and highlighted fields accordingly.
The Setup
A choice field in SharePoint determining the expected SLA with values as follows:
- 0.5 days
- 1 day
- 2 days
- 3 days
- 5 days
- 10 days
- 15 days
- 20 days
- 30 days
- 60 days
- What I am trying to achieve
- The values are inside SQL (thanks to CPS ReportLink) as a string value but I need to work out based on a start SLA date and time, when the target SLA date and time is.
- So I need to strip “day” / “days”, convert to a float and then run a dateadd function to determine my target date.
- In SSRS we will then compare that to today and create a nice RAG indicator in some form or another.
- The Issue
- The DATEADD function doesn’t appear to like a float based number. In fact it rounded 0.5 down to 0 making the start date the same as the target date. This ultimately raised an issue in the UAT process I am going through today at a client.
The Original SQL
DATEADD(day, CONVERT(float, REPLACE(REPLACE(wss_SLA_String, ‘days’, ”), ‘day’, ”)), CONVERT(datetime,[wss_SLA Start Time_DateTime])) as [Target SLA Finish]
The Resolution
So given that I am on-site and the developers who created the SQL are nicely on holiday, I have had to roll up the sleeves and delve in.
So taking my developers original concept, rather than working with days, if we convert it down to hours, we get the desired result without any CASE co-fuffle in the SQL. (Co-fuffle – official word of the day @ SPandPS.com)
Update the stored procedure and bob’s your uncle, we are set and another UAT issue checked off the list.
The Updated SQL
DATEADD(HOUR, CONVERT(float, REPLACE(REPLACE(wss_SLA_String, ‘days’, ”), ‘day’, ”)) * 24, CONVERT(datetime,[wss_SLA Start Time_DateTime])) as [Target SLA Finish]
And lastly, a shameless plug
So how did you get SharePoint list data into a database for reporting without breaking the rules and going directly to the content database, I hear you ask…
Why I used CPS ReportLink of course.
It copies data from a list into a database and keeps everything in sync for easy reporting using the standard Business Intelligence tools provided as part of SharePoint (Excel Services, PerformancePoint etc…) / SQL Server (SSRS, PowerView etc…)![]()
Full details here:
http://www.cps.co.uk/What-We-Do/Documents/ReportLink%20for%20SharePoint%20and%20Project%20Server.pdf
That’s it!, Keep SharePoint’n










You must be logged in to post a comment.