Check this out! http://www.microsoft.com/presspass/press/2006/feb06/02-15OfficeMoreOptionsPR.mspx
New: Microsoft Office SharePoint Server 2007.
Yes, this used to be called Sharepoint Portal Server
So what is going on?
Microsoft is changing Portal frameworks (http://msdn.microsoft.com/msdnmag/issues/05/09/WebParts/). So it's possible that customers may have to rebuild all of their Sharepoint Web Parts to take advantage of the new features.
Did you know that Sharepoint Portal Server 2003 cannot run on .Net 2.0 (http://support.microsoft.com/kb/907763)
So it's not possible for it to work with the new portal framework included in Net 2.0.
Guess what then? Sharepoint Portal Server 2003 users cannot move to Visual Studio 2005 and .Net 2.0
Here are some reasons why at least one customer has shied away from Sharepoint Portal Server 2003:
- Supports only one language per server or cluster
- Limited development tools for remote deployment
- Active Directory/ADAM (Active Directory Application Mode, LDAP service) does not work together
- Limited out of the box web parts, Poor integration with Domino applications, Limiting Peoplesoft integration
-beyond use as an Office 2003 document sharing server, most everything else for customer portal services would have to be coded, designed and installed or integrated in SharePoint Server... building a server farm for scalability, using Windows load balancing (NLB) for basic data caching, designing roles in Active Directory, doubling performance with SQL Server, adding process management with BizTalk, presence with LCS, and coding or adding capabilities for data abstraction, membership management, localization, mobile transcoding, fuzzy or parametric search, discovery, automated portlet services, portal application integration assembly tools, virtualization, analytics, hot failover, business logic caching...
So, many customers end up federating Sharepoint Server 2003 under WebSphere Portal.