Archive

Posts Tagged ‘Office 2010’

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:

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:

    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…

Office 2010 / #MSProject 2010 SP1 + June 2011 Cumulative Update links #ProjectServer #SharePoint #SP2010 #PS2010

August 8, 2011 Leave a comment

As ever, now that my server environment is starting to stabilise after installing SP1 + June 2011 CU (Security Validation issues aside of course), we are now looking at updating the clients to reflect the update.

This is especially important in a Project Server / Microsoft Project 2010 environment.

As a result, here are some useful links that took me a while to dig out for the Office / Project 2010 client updates:

Project 2010

Project 2010 Service Pack 1 x86:

http://www.microsoft.com/downloads/details.aspx?FamilyId=C72141FE-D264-4F6E-AE09-D0FBD32DE5D5

Project 2010 Service Pack 1 x64:

http://www.microsoft.com/downloads/details.aspx?FamilyId=CE1FD136-A1F4-4FF5-909B-50808D6F39CB

Project 2010 – June Cumulative Update 2011 x86 & x64:

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2536590&kbln=en-us

NB: only update binary available for Project 2010 in the June 2011 CU

Office 2010

Office 2010 Service Pack 1 x86:

http://www.microsoft.com/downloads/details.aspx?FamilyId=9D2E1282-8B69-418B-AFA0-9F61239EC8BE

Office 2010 Service Pack 1 x64:

http://www.microsoft.com/downloads/details.aspx?FamilyId=E9F3C2D0-C321-4910-A4CE-B2F294B42D65

Office 2010 – June Cumulative Update 2011 x86 & x64:

http://support.microsoft.com/kb/2553023
NB: no single update binary available, update client applications as required.

Other Useful Links:

On my travels I also found this other link which lists all the updates for the SharePoint and Office Systems:

http://technet.microsoft.com/en-us/sharepoint/ee748587.aspx

Microsoft Office 2010 Service Pack 1 released #in #SharePoint #SP2010 #MSProject #MSOffice #ProjectServer #PS2010

Quite a day for Microsoft today.  Office 365 has been released!!! (This blog may be moving to Office 365 soon – you can see a preview here: http://ghamson.sharepoint.com)

It is expected that the SharePoint and Project Server 2010 updates will be released in a matter of minutes / hours.

And of course the Microsoft Office 2010 client suite service pack has just been released!

Download Links:

32-bit: http://www.microsoft.com/download/en/details.aspx?id=26622

64-bit: http://www.microsoft.com/download/en/details.aspx?id=26617 

I will post again with SharePoint 2010 / Project Server 2010 Service Pack details as soon as possible.

Useful details and links when rolling out Microsoft Project 2010 #PS2010 #ProjectServer #SharePoint #SP2010 #MSProject #in

February 15, 2011 2 comments

In my current project where we are integrating SharePoint Server 2010 and Project Server 2010, we are starting to go into the details of rolling out the Microsoft Project 2010 client globally.

Some of the features we are implementing require VBA macros in MS Project 2010 which are brought down to the client application via the Enterprise Global Template from Project Server.

The following details and links have been useful during my investigations:

ADM Templates for Office 2010 – AD Policy Templates:

How to Digitally Sign a VBA Macro in Microsoft Project:

Registry Key to change:

  • \\HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\MS Project\Security\VBAWarnings

Registry Option Values:

  • 1 = Enable all macros (not recommended; potentially dangerous code can run)
  • 2 = Disable all macros except digitally signed macros
  • 3 = Disable all macros with notification
  • 4 = Disable all macros without notification
    NB: The text in the options match those available in the Trust Center in File > Options of the Microsoft Project 2010 Client.

Showing the Version column in Office as a Quick Part (Office 2007 & 2010 / Document Field (Office 2003)

October 17, 2010 5 comments

Recently in a project I have had the requirement to show the Version column within the Word document to aid document management at the company.

Why this isn’t standard functionality is anyone’s guess but this has been a “feature” of SharePoint since the beginning.

This post is going to concentrate on the various different methods available to solve this issue:

1. Use SharePoint Designer to copy the Version to a separate column

Although this works, when you open the document, the list data and the document version will be out of sync by one iteration.  This is fine if you are opening the document in read-only, but will give the impression that you are overwriting the current version in editing mode.

Issues with this approach:

  • The version will increase as the metadata gets updated via SharePoint Designer
  • Unless you have “require checkout for editing turned off” you will run into problems in the logic around check in and check out.  Ultimately it will also artificially increase the version of the document and if document approval is turned on you will never be able to publish the document.  (Constant Draft state)

2. Using the Labels feature of SharePoint.

A blog post I have found suggests using the labels feature of SharePoint.  This works but have limited formatting capabilities within the document template.

In particular, formatting must be set at the creation of the label on the server.  This results in no formatting capabilities in the Word client apart from location of the label.  It essentially creates an image on the fly when a user opens the document.

Unlike option 1 in this post, this does however work and doesn’t have adverse affects on the Version or Approval states.

Issues with this approach:

  • Word 2007 or 2010 only (Office 2003 is not supported)
    How to achieve this result (taken from the blog post linked above:
    • Enable versioning and content types on your document library.
    • Go into document library settings and select the content types you want the version to appear in.
    • Select Information management policies settings from the content type menu.
    • Select define a policy and click .
    • Click on the ‘Enable Label’ Check box
    • Do not Check the other two boxes in the Labels section.
    • In the Label Format field, enter the metadata fields in the following format:
       Version : {Version} \n
    • Set the label appearance and click on preview.
    • Click at the bottom of the page.
    • Go back to the library and create a new document using the content type you have modified.
    • Save the file as a Word 2007 format.
    • Select the insert tab
    • Select Quick Parts from the Ribbon menu and hover over document property
    • Select Label from the properties list
    • This should display the metadata defined in your label as a field in your word document. The field will update automatically when you next open the document.
    • Save.

3. Event handler to copy the version to a separate field

Using the object model, to copy the version value on Check Out of the document and upon Check In of the document.

The object model allows you to check in using the existing version number, thus getting over the artificial creation of new versions, but you will need to take into account the end users version comments when you do this. as well as the approval process.

Luckily for use someone has created a solution for us and has made it open source.  The solution is available for WSS 3.0, MOSS 2007 as well as SharePoint 2010 (Foundation and Server).

Compatibility is also available within all likely versions of Microsoft Office (2003, 2007 and 2010).

  • Quick Parts (Office 2007, 2010)
  • Fields (Office 2003)
    The solution handles Major and Minor Versioning as well as Content Approval within Document Libraries by adding the fields Current Version, Approval Version, Approval Date & Approval User.
    The only downside to this solution is that the above columns cannot be set to hidden within the content type as they will not appear in the Quick Part / Field options if this property is set.
    This results in extra fields in the Document Information Panel that end users can fill in if they desire.  However this does not affect operation since the event handler overwrites the values when they fire on Check Out and Check In.
    So basically this solution is 99% perfect and I am not sure the only downside can be fixed without client side development (in Microsoft Word).  This would cause its own headaches anyway.

As a result, this appears to be the best solution available and definitely recommend it to clients.

Follow

Get every new post delivered to your Inbox.

Join 571 other followers

%d bloggers like this: