SharePoint 2007 vs SharePoint 2010
Everything on this page is contained in Microsoft documentation, on the Microsoft website, on MSDN, on Technet, or in the Microsoft webcasts and presentations. As you can imagine it is placed in multiple pages, across multiple documents, and some of it is contained within specific Microsoft presentations. My goal with this page is to just have all of the comparison information in one place.
Quick Links: Sites | Communities | Content | Search | Insights | Composites | Office 2010 | Architecture | Web Services/OM | Editions | Administration
Legend:
○= Feature Included
●= Improved In Office Sharepoint Server 2010
☻= New In Office Sharepoint Server 2010
Feature Name / Area |
Sharepoint Server 2007 |
Sharepoint Server 2010 |
Office Integration |
○ |
● |
Line-Of-Business Integration |
○ |
● |
|
☻ |
|
Enterprise Management Operations |
○ |
● |
|
○ |
● |
|
☻ |
|
Mobile Connectivity |
○ |
● |
|
☻ |
|
|
☻ |
|
Office Interaction |
○ |
● |
|
○ |
☻ |
Robust User Experience |
○ |
☻ |
|
☻ |
|
|
☻ |
|
Office Web Applications |
☻ |
|
Tagging |
☻ |
|
Audience Targeting |
☻ |
Feature Name / Area |
Sharepoint |
Sharepoint |
My Site: People Profile & Personal Site |
○ |
● |
Photos And Presence |
○ |
● |
Status Updates |
○ |
● |
Ask Me About |
☻ |
|
Note Board |
☻ |
|
Recent Activities |
☻ |
|
Organization Browser |
☻ |
|
Add Colleagues |
○ |
● |
Social Bookmarks |
☻ |
|
Tags |
☻ |
|
Tag Clouds |
☻ |
|
Tag Profiles |
☻ |
|
My Network |
☻ |
|
Blogs |
○ |
● |
Wikis |
○ |
● |
Enterprise Wikis |
☻ |
|
Ratings |
☻ |
|
Colleague Suggestions |
○ |
● |
Keyword Suggestions |
☻ |
Feature Name / Area |
Sharepoint |
Sharepoint |
Compliance Everywhere |
☻ |
|
Flexible Records Management |
☻ |
|
Shared Content Types And Managed Metadata Service |
☻ |
|
Content Organizer |
☻ |
|
Rich Media Management |
☻ |
|
Document Sets |
☻ |
|
Word Automation Services |
☻ |
|
Support For Accessibility |
☻ |
Feature Name / Area |
Sharepoint |
Sharepoint |
People And Expertise Search |
○ |
● |
Search From Windows 7 And Windows Mobile |
○ |
● |
Common Connector Framework For Indexing And Federation |
○ |
● |
Scale And Performance Via Improved Topology Architecture |
○ |
● |
Ability To Build Search-Powered Applications |
○ |
● |
Refinement Panel And Sorting |
☻ |
|
Search In Context |
☻ |
|
Social Behavior Improves Relevance |
☻ |
|
Thumbnails, Previews, And View In Browser |
☻ |
Feature Name / Area |
Sharepoint |
Sharepoint |
KPI Details |
☻ |
|
Dashboard Designer |
○ |
● |
Enhanced Navigation, Including Filtering And Sorting (Top/Bottom 10, Switchable Measures) |
☻ |
|
Publish More Workbooks |
☻ |
|
Javascript Object Model |
☻ |
|
Powershell Scripting |
☻ |
|
Richer Fidelity With Excel Workbooks |
☻ |
|
Support For Analytical Services Formatting |
☻ |
|
Additional Data Sources, Including External Lists And “PowerPivot” Workbooks |
☻ |
|
Improved Strategy Map Connection And Formatting |
☻ |
|
Seamless Management Of Dashboard Content |
○ |
● |
Integrated Filter Framework |
☻ |
|
Calculated KPIs |
☻ |
|
Improved Visualizations |
☻ |
|
Chart Web Parts |
☻ |
|
Business Intelligence Center |
(Report Center) |
☻ |
Feature Name / Area |
Sharepoint |
Sharepoint |
Browser-Based Customizations |
○ |
● |
Business Connectivity Services |
|
☻ |
Sharepoint Designer |
○ |
● |
Human Workflows |
○ |
● |
Forms Services |
○ |
● |
Visio Services |
|
☻ |
Access Services |
☻ |
|
Sandboxed Solutions |
☻ |
Microsoft Office 2010 with Different Versions of SharePoint
Feature Name/Area |
Description |
SharePoint 2010 |
SharePoint 2007 |
Coauthor |
Share |
With |
|
Simultaneously |
Work |
Work |
|
Highlight |
Enable |
Shared
|
|
Broadcast |
Share |
Audiences |
|
Save
|
Automatically |
People
|
|
PowerPivot
|
PowerPivot |
Publish |
|
Publish
|
Share |
Use
|
Use
|
Microsoft
|
Microsoft |
Use
|
|
Automate
|
Provide |
Use
|
Word
|
Use
|
Seamlessly |
By |
By
|
Access |
Access |
People
|
|
Apply
|
Make |
People
|
|
Use
|
Support |
SharePoint
|
|
Visualize
|
Allow |
Workflows |
|
Use
|
Forms-based |
Integrate
|
|
Provide
|
Provide |
When
|
|
View
|
Allow
|
View |
|
Mobile
|
View |
View |
|
Work
|
Edit |
Data
|
|
Collaborate
|
Work |
Work |
|
Fill
|
SharePoint |
SharePoint |
|
Extend
|
Fill |
The
|
|
Publish
|
Securely |
While
|
|
Use
|
Design |
Business |
|
Offline
|
Take |
Synchronize |
|
Enhance
|
Help |
InfoPath |
|
Manage
|
More |
Automate
|
|
Use
|
Provide |
Business |
Use
|
Business
|
Insert |
Expose |
|
Package
|
Move
|
Package |
|
Available with SharePoint 2007:
- Administration
- Alerts
- Authentication
- Data Retrieval
- Permissions
- Sites
- Search
- People and Profiles
- Workflow
New with SharePoint 2010:
- List REST access with ADO.NET Data Services
- Excel Services REST access
- Client Object Model
- WSRP (v1.1) Consumer Web Part
v Enterprise Client Access License
v Standard Client Access License
v SharePoint Server 2010 for Internet Sites, Enterprise
v SharePoint Server 2010 for Internet Sites, Standard
v SharePoint Foundation 2010 (Free)
v SharePoint Designer 2010 (Free)
Microsoft has created a fantastic interactive chart here that goes through each edition.
Available in SharePoint 2010:
IT Pro Productivity |
SharePoint Best Practices Analyzer |
Backup And Restore Configuration Data |
Site Collection Migration |
Content Recovery Down To The Site And List Level |
Content Restore Of Site Or List |
Windows PowerShell™ Snap-Ins And Commands |
Managed Accounts |
Correlation IDs |
Scalable Unified Infrastructure |
Shared Service Applications |
Hosting And Multi-Tenancy Architecture With Site Subscriptions |
Claims-Based Authentication |
Profile Synchronization |
High Availability Automatic Failover |
Content Type Syndication |
Sandbox Solutions |
List Throttling |
Remote Blog Storage |
Flexible Deployment |
Prerequisite Installer |
Visual Upgrade |
Configuration Wizards |
Scriptable Deployment |
On-Premise Or Online |
Diagnostics |
Unified Logging Service (ULS) |
Usage Database |
Developer Dashboard |
Reliability and Monitoring |
SharePoint Maintenance Engine (SPME) Rules |
System Center Operations Manager (SCOM) Monitoring |
Reporting |
Out of the Box Usage Reports |
SCOM Reports |
I will try and update this page from time to time with more relevant material (if you know of any please comment here).
Hope this helped someone,
Richard Harbridge
{ 14 trackbacks }
{ 50 comments… read them below or add one }
Next Comments →
Awesome outline, I will link to you from my BLOG.
Very helpful thank you, been looking for one for ages!
Thanks Richard! So Helpful. would love to find a comparison of SharePoint 2010 with different versions of Office, but as it stands, the information provided here is incredibly helpful!!!
Thanking you.
@jayincalgary
They have that 🙂
http://download.microsoft.com/DOWNLOAD/2/A/A/2AA0D302-86A6-4AA2-A0A4-4F15FA7DBF5C/BUSINESS%20PRODUCTIVITY%20AT%20ITS%20BEST_WHITEPAPER.PDF
Found a bunch more stuff and will hopefully update this page soon. 🙂
Awesome detail! Keep it updated. I’ve never included Project Web Access in my 2007 picture. May I should?
I try and include everything (alot more than I show here) so that they have a good picture of the application landscape.
As an example often an organization has specific needs they think SharePoint is the right fit for, but actually could be better resolved by say another Microsoft product. Say for instance you show on the application landscape Microsoft CRM. This might lead a company to better understand why investing in a platform like SharePoint is a good idea – It means more future integration with other MS products/platforms within that enterprise.
It also helps to understand IT’s overall strategy relating to its own Application Landscape and what technology could replace other technology etc.
I suppose that’s the short answer. Hope it helps,
Richard Harbridge
Very useful resource, thank you.
Hi Richard,
I have been tasked with investigating re-hosting a Sharepoint installation for an in-house group. They will be moving from 2007 to 2010. You have a very nice summary. I would like to use your summaries for a presentation to the IT management here at Fred Hutchinson Cancer Research Center, of course giving you full credit whichever of your stuff I would use. Please let me know if that would be ok.
John S.
Absolutely okay with me. 🙂
I appreciate you asking! If there is anything else I can do to help, or resources im missing let me know.
Richard Harbridge
Thank you! Saves me a load of time.
John
Excellent document.
Very useful, thanks a lot!
Great list – saved me a great deal of time. Thanks a million!
Thanks a ton…saved a lot of time…
Good work, awsome
Hi Ricard,
I’m glad that finally somebody (you) took the time to put such a comparison together. This will help a lot for developers, IT pros, customers and not to forget project managers to understand the differences.
Thanks!!
Alex
You have done an Amazing job!
Awesome Post Man,
See you at SPSNYC
FANTASTIC stuff!!! and I mean that in all caps. this is a great summary I would like to use if possible. Of course all credit will go to you for all your hard work putting this together. Let me know if this is okay or problem.
–Javi
I agree. Really appreciate the hard work you’ve put in here. I’m also going to post on my blog (with all due credit naturally). If this is not OK, please let me know.
Great comparison info all in one place. Very helpful to my organization as we move into SP 2010.
Perhaps you can answer a question I have about web design for SP2010. I’ve read elsewhere that SP Designer 2010 is NOT used to design web pages as SPD2007 had been. The suggested web design program was Expression Web. Do you have any knowledge of this? –many thanks!
Glad to hear it helped.
For SharePoint Designer 2010 it is a SharePoint specific development tool. It is absolutely the tool that should be used for many SharePoint Design activities such as building MasterPages and Page Layouts (combined with Visual Studio to support more effective deployment etc).
However it cannot modify a typical .Net website like SPD 2007 used to be able to. Really the way things have gone is that Expression Web (Part of the Expression Studio) is now the Microsoft application for modifying and designing non SharePoint websites. The downside is that there are licensing considerations. The upside is that the entire expression studio suite is pretty robust and powerful.
You can still use SPD2007 on non SharePoint sites, or other free tools, but if you really want the full powerhouse I would recommend looking at Expression Web. Keep in mind though that SharePoint still very much should use SharePoint Designer. 🙂
Great article. What would make it better if you indicated the versions of SharePoint and Office that are required for each feature. Examples: SharePoint Standard vs Enterprise, Office Standard vs Professional Plus/Enterprise.
Great Article..Very Helpful!
I have got a Question on “Publish
and Share Information Through Excel Services ” feature in Sharepoint 2010.
How Can I hide formula using this service.i cannot find any material in web which explains me how to do it.
Thanks much
What do you mean by hide a formula? Hide the results of a formula in a cell?
I know it’s pretty unlikely you kept them, but in the future it’d be useful if you include references to the papers you got info from =)
Ack! Great point! I am trying to do that with the standards but will definitely do that with any updates to this page as well. 🙂
Richard, really great work it has helped me immensely in my research on differences between SharePoint 2007 and SharePoint 2010.
However, I do have a question regarding how SharePoint 2010, with its all “new” features for social collaboration fares in comparison to other social collaboration tools (Jive, Telligent etc). Did you find any particular feature(s) which is going to be a game changer in SharePoint 2010? How does SharePoint fare in external collaboration scenarios.
Thanks a bunch
The short answer is:
Internally it is good enough.
Externally it’s is a more difficult story. I would say the benefits lie in a powerful development framework, integration framework, and more powerful management features than most other vendors (it’s just such a big platform).
There are a couple major factors we have to take into account: Jive, Box.net, SocialText etc have much shorter development cycles. So no matter what; typically any SharePoint functionality will be dated even on release. That’s the core reason why the external scenario is so challenging.
The positive benefit on that is that things are more carefully vetted, tested, and integrated in the development cycle. From a partner perspective this adds quite a bit of opportunity as they don’t have to constantly re-tool as much and can build quite a bit on top of the SharePoint stack.
From a feature perspective bringing say Live accounts into the mix is actually much easier than it was before and with the claims model of authentication and the new SharePoint Security Store (SSS) it can lead to some pretty powerful ‘easy’ authentication scenarios. I have seen some interesting ones using netflix and other authentication schemes that track and store it for users to create a more seamless feeling when showing other external content within the structures of say a SharePoint external list.
The foundation for ‘game changer’ that is set in SharePoint 2010 is simply that they revamped/improved their authentication, interoperability, and social story. This along with the adjustment in how supportive they will be to the community and easier developer ramp up should mean that the real ‘game changer’ will be how partners leverage the core set of capabilities to challenge the best capabilities of other social technologies. (I can think of many partners who are doing this as we speak.)
There are a number of interesting points in comparison with other WCM platforms and especially other Social WCM platforms. While I am a bit overwhelmed right now with projects and some community launches I do hope to dig further into this and write a nice post on it. If nothing else I will be discussing it in depth at the SharePoint Symposium (WCM panel) in DC in November.
Keep the questions coming and forcing us all to have the conversations! 🙂 Certainly worth having!
Wow after trolling around for days trying to find answers I’m looking for i think i may have found a great resource here. I’m a complete newbie to sharepoint, although i understand the concept and its capabilities but am coming from it at a different angle and would love to hear your thoughts on my problem/concern.
This is a design and marketing agency, we have a considerable amount of business with large organisations, large e-commerce sites and education establishments. Generally we brand, re brand and design documents, ads and brochures for print and websites for online. Currently our websites are created using HTML/ASP pages with PHP on our own CMS and blog platform, however we find many of our (particularly education) clients are talking about sharepoint integration of there sites and documents and we feel like we may be losing some pitches to agencies that have an understanding of it.
I’m actually a back up developer to our main development team my main role is actually SEO, however being the only person in the agency that has used Microsoft products and the fact that I am (was) a Frontpage genius I’m now tasked with getting a grip on this sharepoint thing!
My questions really relate to designing for sharepoint users as the clients are the users of the SP installation we just need to design the online elements of our services for SP.
do we have to design in SPD?
can we design in photoshop/illustrator things like brochures and use the designs in Sharepoint?
if we designed and developed sites in the normal fashion, without the CMS presumably, can they be used with sharepoint or must they be modified in expression web or SPD. – on this point I assume that if we design in SPD within a SP installation we can include the full CMS elements of SP rather than modifying our code to make something that works?
the thoughts of someone who knows something would be extremely useful to us
Thanks
Iain
The short answer (apologize as I would prefer a longer explanation but am stressed on time) is that you CAN Design in SharePoint Designer. You can also design in Visual Studio or to varying degrees in other applications.
The recommendation would be to design and brand in SharePoint Designer. Once you have your design you PROVISION or DEPLOY your brand throughout multiple environments (or site collections) by using WSP’s and packaging it in Visual Studio.
That would be my high level recommendation on how (process wise) you work on SharePoint 2007 or 2010 branding/design.
That being said there are a number of design architecture pieces you need to fully understand. The first is Masterpages and how they work in SharePoint, the second is PageLayouts (if you are using MOSS or SP2010 not WSS or Foundation 2010), and then of course there is Themes and how CSS is used in SharePoint (Alternate, Embedded, Themed, etc) and the order which CSS overrides/loads to the page.
For individual components often you will use DataView Webparts or Content Query Webparts and their XSL transformations to improve component level design and roll ups…
This is actually a pretty big conversation but hopefully this gets you started on the right foot and with further reading/exploration you can wrap your head around SharePoint Branding and Design. If you have more questions feel free to ping me as I have branded many a SharePoint site.
Richard’s short answer is fine as far as it goes – but you have a lot of work to do to get your head around how all this stuff works in SharePoint. What I would recommend as a starting point (and I’m sure Richard would have mentioned it too) is Heather Solomon’s excellent site on branding SharePoint MasterPages and Templates.
http://www.heathersolomon.com/blog/
Personally I’d stay away from Themes – Microsoft might have several strengths, but honestly, graphic design isn’t one of them.
Mr A (SharePoint Monkey)
If your going to write a blog or website about web technologies or pretend to know anything about any kind of web development, DONT PUBLISH YOUR FUCKING PAGES FROM WORD! You’re source is a fucking nightmare! Sort your shit out!
Btw, I forgot to mention, the content is very useful and informative! Well done on that front!
Hahaha I totally understand. The issue I had was one of time. I was going to just code the entire page but literally did the compiliation in the course of an hour or two (and it was all in word). So it just made sense to skip the middle man and hurt my development roots.
And yes. It did hurt me to use word, but the business user/tactician in me knows that sometimes it’s okay to sacrifice certain quality in order to get a message out faster. 🙂
Please don’t mind if I use this link to my blog as reference.
trackback http://www.kbworks.nl/blog/archive/2011/01/08/important-links-about-sharepoint-andor-linkedin.aspx
Really great article !
Would you mind if I use this link in my website ,www.patgiri.com
Thanks!
Nbr
Not at all. Go ahead.
Thanks for the wonderfull insights. Sharepoint has become very big and definately a good reference.
Could you also help to find from architect perspective. Something on the content, db, architecture etc..I mean the low level details.
That could help someone from the big guy Microsoft!!!!
Thanks.
Raja
Hi Richard Harbridge,
You have done a great Job.It is very helpful for me.
Thank you !!!!!
Hi, great article!
My company is looking to migrate from MOSS 2007 to SP2010, and I’ve been trying to find some good looking web sites or companies that have already used SP2010 to design their home pages. Any suggestions that you could provide me? Thanks.
Absolutely.
If you go to http://www.WSSDemo.com/LivePivot you can actually filter down to SharePoint 2010 public facing sites. While this isn’t a perfect representation if you are doing an internal upgrade or migration it certainly can help give you creative design ideas. Just select Platform from the right and SPS2010 + SPF2010.
In regards to getting additional help I actually work for a rocking SharePoint consulting company that performs many SharePoint migrations, upgrades, and branding projects. I will send you a personal follow up with additional details in case you are interested. 🙂
Thank you,
Richard
Excellent post.
thanks dude
Thank you very much.. this is so helpful and well written. It has been a one stop site to answer my Sharepoint 2007 vs 2010 query.
Great article! Thank you for doing so much research and putting it in such a easy-to-reference format. I hope you don’t mind me posting a link to this article from my blog site.
Cheers!
Melonie
Thanks so much for this really helpful round up.
W3C should be ashamed of themselves for using such foul language on your website – they clearly have no idea about how to give constructive feedback and swearing (in capitals) shows their total lack of professionalism. If it had been me I would have removed their post (and to be honest you still could)! Well done to you for your gracious response. Although copying from Word into HTML pages does annoy me too, as you say for getting a message out it can be much quicker and for most people just reading your pages it won’t even matter.
You can Save Documents and Presentations Directly to SharePoint 2007 if you first create a network place for the relevant site or document library in SharePoint 2007. You may like to add this into your table above.
Very helpfull and thanks for the information.