From Network Computing Asia
Microsoft sent the SharePoint Portal Server to our business applications lab and I installed it on a single processor Intel white box with 1 GB of memory running Windows 2003. I had to choose to make my machine an application server, which instigated an odd conflict.
When Windows 2003 installs the Application Server components, it turns on SharePoint Windows 2003 Services and Front Page Extensions by default. Unfortunately, SharePoint 2003 will not install until you deactivate them.
Once I got everything configured to SharePoint’s satisfaction, I set up the default portal to use for my fictional corporation. Within the portal are “subareas”—consider them individual sites for divisions such as HR, support, sales and marketing. The divisions start out with nothing much in them—you build them from such choices as generic Excel-like lists, discussions, document libraries, news lists and lists of scheduled events. As admin, you can also decide at this point to allow some or all users to create personal sites.
My primary concern with SharePoint 2003 is its document management. The ability to check in a document in many different places severely limits the usefulness of document management, because edits to the doc in one location are not carried over to the doc in other locations. Therefore, if you choose SharePoint for document management, be prepared to write standards for how and where documents are published and edited, and to develop tools to validate that there is only one copy of a document in the repository.
If you are a Microsoft shop looking for a portal and you can live with the severely limited document management, SharePoint might be the solution you’ve been looking for. I would recommend checking out the competition though, as this is a tight market with excellent competition.
Read the original article