Microsoft Office Tutorials and References
In Depth Information
SharePoint installed on the same server, and want to use Report Builder (or another tool) to
make reports that can be stored in (and read from) a SharePoint library.
Of course, from the client side, users will need a browser to access the SharePoint sites.
Browser support comes in two levels. Level 1 describes browsers that are fully supported,
and SharePoint is considered optimized for their access. Not surprisingly, the only browser that
supports all of SharePoint’s advanced features is Internet Explorer 7 or higher, 32-bit (yes, 64-bit
IE is not entirely compatible with all SharePoint features). This is largely because of SharePoint’s
use of proprietary ActiveX controls. Mozilla’s Firefox 3.5 or higher is a quasi level 1 browser, but
some ActiveX features, such as Datasheet view, do not function.
Level 2 browsers are mostly supported, but they are intended to be used to do rudimentary
things with SharePoint, such as reading and writing in the SharePoint sites, and to do basic
SharePoint administration. Anything that truly requires ActiveX will not work for level 2 browsers.
So, what browsers are considered level 2? Any browser that isn’t IE 7, 8, or higher, or isn’t
Firefox 3.6. That means any IE version older than 7 (or IE for Mac), Safari 4.04, Opera, and so on.
IE version 6 and lower are definitely not supported.
The bottom line is that Microsoft wants you to use the most recent versions of Microsoft IE to
use SharePoint—that and Office 2010, of course.
Office 2010 is really integrated with SharePoint; half the things you can do with SharePoint you
can do better with Office 2010. Don’t get me wrong, though; Office 2007 can integrate too, but not as
completely as Office 2010. Keep in mind that SharePoint prefers you use the 32-bit version of Office
2010 to integrate; not all features are supported with 64-bit Office at this point (sadly enough).
There you have it. That’s SharePoint Foundation under the hood—a Windows Server
operating system, IIS 7.0 or higher with 6.0 support, PowerShell, .NET Framework 3.5, a handful of
additional components that extend .NET 3.5, filtering, and SharePoint’s use of SQL, specifically
64-bit SQL Server 2005 SP3 CU3 or higher (or you can let SharePoint install SQL Server 2008
Express). These roles and technologies, working in tandem, power SharePoint. The strengths
and weaknesses of this underlying infrastructure lend their particular traits to SharePoint.
Knowing about them teaches you both how SharePoint works and how to manage it, especially
when it comes to troubleshooting.
I N S T A L L I N G S H A R E P O I N T : S I N G L E S E R V E R O R S E R V E R F A R M
Now that you know what you need to have on the server before you even consider installing
SharePoint, let’s take a look at what you need to know about the installation process itself, which
I’ll take you through in Chapters 2 and 3.
There are essentially two ways to install SharePoint. Either you don’t have a copy of SQL
running on your network (or even on the same server) that you can use to host SharePoint’s
databases or you do.
SharePoint may come in two sizes (Standalone and Server Farm; see Figure 1.2), but it can
actually be installed three different ways: Standalone, Standalone Server, and Complete. The
last two options are under the heading Server Farm (see Figure 1.3) and indicate that the SQL
Server 2008 Express database won’t be installed locally; instead, the installation process will
prompt for SQL server and database information.
Standalone The Standalone install assumes that you are going to use only one server
ever to run SharePoint and that you don’t have a copy of SQL handy to use for its
databases. What it does in that case is install SharePoint assuming all necessary services are
going to run locally and that you need it to install the free SQL Server 2008 Express
version of SQL on the same server.