Talk:Microsoft Office SharePoint Portal Server

This page is specifically to cover SharePoint Portal Server - thus, I'm thinking that external links, &c., covering Windows SharePoint Services should go on that page, not here. I've made edits in accordance with that - any issues? - SiliconCerebrate 08:20, 10 August 2005 (UTC)[reply]

I know it's premature, but... Can someone explain the difference/strategy behind Groove Server 2007 and Sharepoint Server 2007? For the non-insider, the Microsoft literature is very confusing. If a company buys Groove Server 2007 -- to get a secure Wiki like experience, do they need to bother with Sharepoint? Thanks. Louisducnguyen 22:45, 31 March 2006 (UTC)[reply]

They address different needs (and different markets). I don't know much about what they're doing with Groove 2007, but the previous version was all about being able to build a so-called "virtual workspace"; you'd typically have a team of people (inside the company or out) working on a project of some sort, and the Groove UI would let you see who's online, what they're working on, what files/meetings/events etc. are associated with a project, and you get informed in real-time if those items are updated. Groove also does stuff like automatic synchronization of a set of related files to everyone's machines, so it's especially useful for road-warriors who aren't always on the Internet but need access to files. It plugs into Windows Explorer, too.

Headline text

Office SharePoint Portal Server, on the other hand, is a web application for building Intranets and Extranets. You use it to build out internal sites with information of use to people around the company. It does have a lot of project management capabilities, but it leans more towards the "strategic" side of things, as opposed to Groove which is more "tactical". One nice thing about SharePoint is that people (management, etc.) can peer in on the status of a project without needing any software other than a web browser... permissions control is pretty flexible, too, and it has some workflow features like document approval and versioning that bigger businesses dealing with important documents will probably want.

Microsoft definitely doesn't have their product literature sorted out with this stuff yet, so yeah, it's a bit confusing. Groove is some pretty cool software though, much nicer than anything Microsoft has produced for team-based file sharing, synchronization, and project management. Warrens 00:20, 1 April 2006 (UTC)[reply]

Summary of Differences

Groove is for near-real-time (seconds) ad-hoc (no setup) focused (small set) but light-weight (low storage) and short-term (weeks) collaboration between a limited number of users with disconnected capabilities. This is realized by a very fat client app. Security is not very granular or flexible, nor centrally administered. Think of it as an extended IM conversation. SharePoint is for centralized, organized, broad, long-running, heavy collaboration between many users. SharePoint, esp. MOSS 2007, is typically zero-client-footprint. Security is very granular and flexible at the expense of administration. I suppose one could liken it to a scientific publisher; structured, organized, secured(review process).

Rewrite?

This disambiguation page contains only 4 pertainent links. 1 of these links to a nonexistant page, and 2 of them appear to have been merged. Sorting things by date does not appear particularly nessisary. So long as there are no objections, I plan to rewrite this page.--Verdatum 13:53, 28 September 2006 (UTC)[reply]

MOSS vs Wiki vs CMS

I came here to try and discover information about whether MOSS will meet my need for a combined Wiki/CMS to host process and procedure documentation. I'd welcome some information about whether MOSS addresses these functions. Hubris67 05:29, 6 February 2007 (UTC)[reply]

Made my way to the MS Technet site and can now understand why this information is so sparse. There's buckets of information there. hubris 03:26, 7 February 2007 (UTC)[reply]

Blogs

I thought I would list a few blog links here for the article to link to - Matthew Cosier

That's really not necessary, thanks. Wikipedia is not a directory of links. Kuru ^talk 00:32, 21 March 2007 (UTC)[reply]

External references

Removed a thinly disguised link to a site selling info on portal services. Does not provide any useful information on this topic. —The preceding unsigned comment was added by 209.115.26.19 (talk) 18:54, 16 May 2007 (UTC).[reply]

But what is it?

I came here looking for a one-sentence description of what "SharePoint" typically means. I'm more confused now than when I came here. Some of that may be due to the word being used for many different things, but other product families that share one name do a better job of describing what, overall, the product family does (like the "Microsoft Windows" page).

Also, I started on the Wikipedia page called "SharePoint", hit "discussion", which took me to "Talk:Microsoft Office SharePoint Portal Server". From there, hitting "article" goes to "Microsoft Office SharePoint Portal Server", which is a completely different page from "SharePoint". It's also a lot clearer than the "SharePoint" page -- remove/redirect?

ebook licensing

Is that ebook legally ok to be downloaded by anyone who comes to this article? It looks like one of those microsoft press books, though it does say 'Not For ReSale' on the cover...

Bhavana Batwal

Features of SharePoint In general, SharePoint contains all of the features you would expect from a portal or collaboration tool: • Browser-based customization of page • Browser-based content administration • Aggregation capabilities • Document Repository • Message board • Ad-hoc data storage • E-mail notifications • Announcements, event calendar and contact list. —Preceding unsigned comment added by 220.225.35.3 (talk) 10:17, 21 September 2007 (UTC)[reply]

Wikiproject Computing

I have removed the WikiProject tag, as this article is either a redirect or deleted. If you oppose, please restore the tag. Thank you, fahadsadah (talk,contribs) 15:55, 30 March 2009 (UTC)[reply]