(Managed to hit a key combination in Windows Live Writer that posted this half way through – sorry if this is a duplicate…)
Thanks to everyone who attended the webcast covering details of the Project and Project Server 2007 and 2010 cumulative updates for October 2011 – as well as some brief comments on Project and Project Server 2007 SP3. The recorded webcast can be viewed here – https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032493963&Culture=en-US. Mark your calendars for the next one about the December 2011 CU on 1/10/2012 – https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032493964&culture=en-us.
I’m posting the questions that were asked both during and at the end of the webcast – in some cases I’ve found out more complete answers since the webcast and have included the detail here too.
Q. Adrian mentioned an anti-virus package had slowed down Project Professional – which one?
A. We not going to name names here – and really the same could apply to any of the packages that scan what winproj is doing. It is really up to the customers to decide if they feel they can exclude the project executable from the virus scanner – balancing the virus risk against the performance gain.
Q. Ref fix 30990 (Modifying time-phased work in Project Professional moves actual work; additionally, the “Out of Sync” message does not occur), will this fix work if you are on a server with August 2011CU+SP1, and client with SP1 + October 2011CU? (i.e. out of sync client server CUs)
A. Yes, this is a client side fix and not dependent on the server CU or SP level.
Q. Project Server 2010…Graphical indicators – we have had lots of issues with graphical indicators not displaying correctly. The issue is random (as far as we can tell) and it doesn’t matter whether the custom field references a formula or lookup table. Both can be affected. Sometimes (not always) opening, modifying, saving and publishing the project in PWA resolves the issue, but on next publishing from ProjectPro the indicators disappear again. This problem is well over 18 months old and was supposed to be fixed in the Dec 2010 update, but wasn’t. When will this be fixed ??? Customers (as well as ourselves) are finding this incredibly frustrating.
A. Had some dialog on this after the webcast with a couple of the attendees (Thanks Kelvin and Marc!). Looks like we have specific issues where the first publish does not show the indicator – just the text. We have a fix coming in December that should address the publish from Pro causes the loss of the GI – I’ll keep you posted on other changes…
Q. Is it true that after April there will be no additional CU’s for 2007? Followed by – My understanding is that Primary Support for Project Server 2007 ends in April 2012
A. At the time of the webcast the Microsoft Support site at http://support.microsoft.com/lifecycle/?p1=11381 listed April 2012 as the date for the end of Mainstream Support. This has now been updated to reflect the recent SP3 release – so that makes the end of mainstream support date 10/9/2012. This would tend to indicate that the August 2012 CU might be the last for 2007, though if hotfix requests are accepted right up to the end of mainstream support I could see there also being an October one. As this is the first CU supported version of Project to go out of mainstream support this is new territory. As you will have noticed from this webcast – the number of fixes for 2007 has dropped off quite dramatically.
Q. Project Demo Image–Excel Services problem after SP1 upgrade http://epmsource.com/2011/07/16/project-demo-imageexcel-services-problem-after-sp1-upgrade/ has this been fixed?
A. This is fixed for the latest partner-only demo – see http://blogs.msdn.com/b/jkalis/archive/2011/10/26/project-2010-demo-pack-version-2-now-available-to-partners.aspx
Also we received a suggestion that we should include any SharePoint updates that would have an affect on PWA or project sites. We will see if we can build this in next time.
And finally – the PowerPoint didn’t get loaded up to the Live Meeting – so I am including here.