With the release of Exchange Server 2007 Microsoft deemphasized public folders within Exchange Server and promoted SharePoint as an alternate solution. This article will support you in choosing the correct release of SharePoint and give you a short overview of the installation procedure. Furthermore, it will discuss the configuration of SharePoint to provide you with public folder functionality within SharePoint and how to integrate it with Outlook.
SharePoint Server 2010 is available in three different versions:
SharePoint Foundations is the in line fellow of Windows SharePoint Services 3.0 and is a cost free version of SharePoint which can be run with:
SharePoint Server 2010 Standard and Enterprise Edition provide the full functionality of SharePoint. The only difference between these editions is what functionalities they provide in detail.
A full description of these releases and which functions in detail are provided by which edition can be found at here.
Installing SharePoint is quite easy and straight forward. In general the setup consists of three parts:
After providing a SharePoint Installation Account that has the “DBCreator” SQL permission, we may start with the installation steps.
1. Installation of Prerequisites
At first we need to make sure that all software system requirements are met and that all features and roles of Windows Server are set up properly. This is quite easy because the SharePoint 2010 setup procedure provides a Prerequisites Configuration module called “Install Software Prerequisites” which does the following in detail:
2. Installation of SharePoint to the server’s hard disk
As a next step we need to start the corresponding SharePoint Setup tool which installs the binaries to the hard disk. At this point of the setup procedure we need to choose whether to install SharePoint in a Standalone or Farm installation. Standalone means a single server configuration with SQL Server Express Edition as the underlying database; a farm installation means that you can choose which SQL Server instance you would like to install (e.g. dedicated server instance).
If you would like to choose a “best performance” and “best practice” setup, you should use a dedicated SQL instance on SAN LUNs different than the SharePoint Server itself because of performance optimization.
3. Running the Setup & Configuration Wizard
Finally we come to the third and last part of the SharePoint Setup which is running the “Setup and Configuration Wizard”:
This wizard consists of 10 steps to finish the configuration.
To finish the setup of SharePoint you will need to use a final wizard which:
A final installation of (Office Server) SharePoint SP1 would finalize bug fixing and availability.
If needed you may now start over with:
As a next step we need to make sure that all users gain access to the newly created portal. This is quite easy and can be done with the “Website Actions” item that you will find on the left top edge when running the website itself. This Option allows you to:
A detailed documentation on SharePoint permissions can be found here.
To make sure that administration of the SharePoint portal follows the best practice, Active Directory based groups and their appropriate permissions on SharePoint are configured in a way that user and group nesting will mitigate administrative overhead.
If you need to modify the design and overall look of your SharePoint portal, you will need to use:
Or finally create your own “master template” to meet your “corporate identity” or “look & feel”.
Now that we have the new location of content which in the past used to reside within public folders, we can now migrate it to SharePoint.
This can be done using:
After having migrated all content from Exchange Public Folders to your SharePoint document libraries you may want to dismount and completely disable public folders in Exchange. This is a simple and straight forward procedure which is described here.
As you have seen above, moving from Exchange Public Folders to SharePoint Document Libraries is a straight forward procedure but is a concept and process change. One needs to make sure that all users understand what is happening and how to work using Exchange and SharePoint in combination. But once you are done, then life is easier!
If you have any further questions regarding this issue, please don't hesitate to contact me.
Not being able to find project documentation is way too common. Use Azure DevOps’ built-in…
Samsung is again the first major company to roll out new smartphones in the new…
PhotoSquared has experienced a data leak, mainly because the popular U.S.-based photo app failed to…
Here’s an elegant and modern way to move data from your Azure virtual machine to…
The effects of the recent Facebook data breach are still being felt. In this new…
Are you finally ready to take the plunge into Exchange 2019? If you are building…