The Office Sustained Engineering blog has an announcement that Service Pack 1 for Office 2010 and SharePoint 2010 is on track for release at the end of June.
As you might expect, this will include a roll up all previous patches and cumulative updates, as well some minor feature changes.
Update 28th June 2011: It’s here!
Read all about it and find links to all sorts of information and resources: Office 2010 sp1 available for download
Change to Outlook reminders dialogue
One of the changes declared for Service Pack 1 will be to revert the behaviour of the reminders window in Outlook 2010 back to the way it worked in 2007 thanks to sustained pressure from various contributors on the Microsoft Answers forums.
In Outlook 2007 when you snooze a reminder it remembers how long you snoozed that item for, and next time it comes up that is the default time chosen so you can very easily hit snooze again for the same delay. Each item (calendar entry, task or follow up) remembers it’s own interval so you can snooze a meeting later today maybe 15 minutes at a time, but a reminder about a conference next month a whole day at a time.
Outlook 2010 changed this behaviour so that each time you snooze any item, the time interval chosen is remembered for the next item as well, which means some people found they had to keep changing this back and forth between different values, and might snooze something for too long without realising – possibly ending up being late for that important meeting for example. Service Pack 1 will switch this behaviour back to the 2007 method, and it sounds like this will just happen, rather than providing the user with any option to choose which approach works better for them.
Which way would you prefer this to work? Let us know via the comments.
No news on Outlook 2010 holiday errors
For over a year now people using Outlook 2010 have been able to add public holidays for their country, with the slight problem that many of these holidays have several errors in at least 23 countries around the world . I have actually seen some people report the problem and offer fixes for it which still contain some of the incorrect dates, or “corrections” which introduce different faults.
Hopefully Microsoft will stick to their plan of including fixes in the service pack to finally address this problem, but there is no detail available on this yet, but we’ll update this with any news when it arrives.