Chapter 6. Setting Up Windows SharePoint Services
Whether you are a user or an administrator, you should understand how Windows SharePoint Services is installed and configured. Microsoft has simplified the installation process, allowing you to choose your installation mode and walk away from the server while the installation progresses. Once SharePoint is installed, you can access many configuration options to fine-tune your installation.
In this chapter, you will learn about the options for installing and configuring Windows SharePoint Services. However, detailed installation instructions are beyond the scope of this book. This chapter does provide a high-level overview of the important aspects of the installation process, including:
Software and hardware requirements
The process of installing Windows SharePoint Services
The process for integrating Windows SharePoint Services with SharePoint Portal Server 2003
Once you have read this chapter, you should understand the choices involved in deploying Windows SharePoint Services and be aware of the various configuration options.
Requirements
To use Windows SharePoint Services, you will need a server that meets the minimum requirements. Table 6-1 outlines the hardware, software, and client requirements to run Windows SharePoint Services. Keep in mind that these are only minimum requirements, and most applications require more processing power, memory, and hard disk space.
|
Component |
Description |
|
Hardware requirements |
|
|
Software requirements |
|
|
Client requirements |
|
Tip
If you have not used or installed Windows 2003 before, it is highly advisable to read up on the technology. Microsoft made many changes to the Windows 2003 installation and configuration process. Most notably, IIS is not installed by default with Windows Server 2003, but it is required for Windows SharePoint Services.
Installing Windows SharePoint Services
Installation of Windows SharePoint Services is done by means of a simple wizard. In most cases, you can follow the defaults, walk away from the server, and the installation will be complete. Instead of going over the installation instructions step by step for Windows SharePoint Services, this chapter looks at the installation from a high-level overview. The topics covered include:
Deployment options
Installation process
Configuring Windows SharePoint Services
Deployment Options
You can install Windows SharePoint Services 2.0 in several different configurations based on the number of servers you wish to use. Each option has different strengths and physical requirements. The option you choose depends on your business requirements and the size of your organization.
Single server
You can deploy an entire SharePoint Services instance to a single server. All SharePoint sites are hosted on this server, as is the database. This option is the quickest and easiest deployment method, but it is also the most limited in terms of scalability and performance.
Although the single-server installation is quick and can simultaneously support many SharePoint sites, it is not recommended for large installations or enterprise organizations. Because both the application server and database server reside within one machine, the server’s performance can quickly degrade as more sites are added and more users access the existing sites.
Single-server deployment is recommended for organizations that:
Expect fewer than 1,000 sites to be hosted.
Expect a limited number of simultaneous users. The exact number is a function of the machine specifications.
Want to set up a test site for SharePoint without the overhead of multiple servers.
Even with the potential for performance issues, there are still good reasons for deploying Windows SharePoint Services in a single-server environment. The benefits to using a single server for deployment are:
The database doesn’t require any special configuration. A default installation of Windows SharePoint Services automatically installs WMSDE, which can support most sites.
You can install Windows SharePoint Services and create and publish a SharePoint web site based on the WMSDE database in minutes.
Several SharePoint web sites can be hosted with minimal overhead.
By modifying the installation, Windows SharePoint Services can use SQL Server 2000 Enterprise or Standard Edition as the database. This allows for more SharePoint web sites.
Figure 6-1 illustrates how a client interacts with a single-server SharePoint installation.
Note that the database, the web server, and the SharePoint sites are all stored on a single server. Multiple clients can access the server via HTTP.
Remote SQL Server
Using Windows SharePoint Services on a single server satisfies most small- to medium-sized businesses. However, if you plan to run Windows SharePoint Services in an enterprise environment, or where more than 1,000 SharePoint sites will be hosted, Microsoft highly advises you to separate SQL Server from SharePoint.
By placing SQL Server on a separate machine, you gain the following benefits:
The server hosting Windows SharePoint Services can devote its processor, disk resources, and memory to providing SharePoint sites and files.
The server hosting SQL Server can devote its processor, disk resources, and memory to database management.
An increase in performance and sites served to clients.
Deploying with a remote SQL Server creates an assembly-line scenario. The client asks the web server for a SharePoint page. The web server requests any necessary data from the database. Upon receipt of the information from the database server, the web server generates and returns the SharePoint page to the client. Each server performs a specialized task and can be optimized for that task. Figure 6-2 illustrates how a remote SQL Server deployment interacts with a client.
Note that the web server hosts IIS, Windows SharePoint Services, and any SharePoint sites. The database server hosts SQL Server. By separating the functionality, you can customize each server for its specific role. You might, for example, use a storage area network for the database server, or tune the connections on the web server to support more clients.
Server farm
Unfortunately, separating the database onto a separate server from the application will not solve all the performance concerns of an organization. Eventually, either your database server or application server (or both) will begin to run low on resources. Once this occurs, performance will begin to degrade. Fortunately, Windows SharePoint Services can also be deployed in a fully scalable server-farm configuration.
A server farm allows you to load balance your Windows SharePoint Services installation to provide maximum efficiency and performance. With a server farm, you can add additional servers (both application and database) to balance the load of the application.
In Windows SharePoint Services, a server farm will have the following characteristics:
Multiple servers are running Windows SharePoint Services and SQL Server.
Sites and subsites are grouped into site collection. Each site collection exists within a virtual server in IIS and uses an ISAPI filter to map incoming URLs to specific sites on each virtual server.
Each virtual server has its own set of databases within SQL Server.
For each additional web server added, a higher throughput of content is achieved and more content can be displayed by the Windows SharePoint Services.
To balance the load that is incurred across all servers, special switching and routing hardware or software can be used for load balancing.
Figure 6-3 demonstrates how a server farm interacts with a client.
The exact details of a server farm depend on your available equipment and needs. For example, the switching and routing functionality may be performed by dedicated hardware or software such as the built-in Windows 2003 clustering and load-balancing systems.
Installation Process
Once you have chosen your deployment configuration, you are ready to install Windows SharePoint Services. The deployment mode you select determines the configuration options you need to choose during the installation process. Fortunately, many of the configurations you select during installation can be modified after the installation through the SharePoint Central Administration site.
Considerations prior to installation
Even though many of the configuration options you select during the installation can be modified, you need to make sure you understand the choices before installing the software. Post-installation changes can severely disrupt the uptime of Windows SharePoint Services, thus affecting the users who are attempting to access it. Further, there are some options that cannot be modified after the installation without a full uninstall and reinstall of Windows SharePoint Services.
The following is a list of configuration options that should be analyzed prior to beginning an installation of Windows SharePoint Services:
User account mode
There are two types of user account modes that can be selected during the installation:
- Domain Account mode
Grants users access to the site by using their existing Microsoft Windows Domain accounts.
- Active Directory Account Creation mode
Grants users access to the site through Active Directory accounts. If you are using this mode, you must create the user accounts in Active Directory and allow those accounts within Active Directory to have access to Windows SharePoint Services.
Once one of the two options has been selected, you cannot change it. Nor can you run both modes at the same time.
For more information on the impact of choosing an account mode, see the Section 4.1 in Chapter 4.
Database type
During the installation, you can choose whether you want to install Windows SharePoint Services using an MSDE version of SQL Server or using a full installation version of SQL Server. Unlike the account mode option, you are not stuck with your choice once it is selected. At any time you can change from MSDE to SQL Server.
Warning
While technically it is possible to move from SQL Server back to MSDE, it is not recommended. MSDE has fewer features than SQL Server, and you will lose functionality if you attempt to move your database from SQL Server to MSDE.
If you choose to install SQL Server, you must also select a database authentication mode:
Windows Integrated authentication
SQL Server authentication
If you have worked with SQL Server previously, you will be familiar with these two options. Windows authentication does not transmit usernames or passwords between servers. Rather, it relies on the IIS application pool to handle domain credential verification. Integrated authentication improves SQL Server security because you are relying on secure transmission of credentials. You can also take advantage of the Windows user management system to create new accounts.
Conversely, SQL Server authentication transmits usernames and passwords between servers in an unencrypted form. This creates a much less secure environment. In addition, the SQL Server administrator must create and maintain all necessary user accounts.
One other important note is that you do not need to install either SQL Server or MSDE if you already have a copy installed on your target server. If this is the case, you can simply attach Windows SharePoint Services to the previously installed copy of SQL Server. You will often use this option when you are deploying to a distributed environment where SQL Server is on a separate computer (or cluster).
IIS application pool
Application pools are an IIS 6.0 feature that permits separate, isolated processes to run your web applications. Because each application pool will have a unique identity, you can identify which web application is executing actions based on the application pool identity.
In previous versions of IIS (before 6.0), all web applications were run inside the IIS process. If IIS crashed, all your web applications also crashed. To mitigate this risk, IIS 6.0 assigns web applications to specific application pools, creating virtual sandboxes. Now, if one application pool crashes, the remaining application pools will continue to function as though nothing happened.
With regards to Windows SharePoint Services, you can configure the application pool during installation by choosing one of four options:
The administrative virtual server uses one application pool, but a separate pool is used for other sites.
All virtual servers share an application pool.
Each virtual server receives its own application pool.
Virtual servers that host the same web sites share an application pool.
If SharePoint is deployed in a server-farm mode, or you expect to create multiple virtual servers, you will probably want to use either the third or fourth option, as these options will prevent SharePoint from stopping completely if one of the application pools crashes.
FrontPage 2002 Server Extensions
If installed, FrontPage 2002 Server Extensions are generally found using port 80. This will cause a conflict with Windows SharePoint Services. If you find that FrontPage 2002 Server Extensions are running on port 80, back up your virtual server and, using Microsoft SharePoint Administrator, unextend the virtual server. After the installation of Windows SharePoint Services, you can restore your FrontPage 2002 Server Extensions to a different virtual server running on another port or to the same virtual server and upgrade the extensions to Windows SharePoint Services.
Installing Windows SharePoint Services
Once you’ve considered your choices and made all the important decisions each choice entails, you can now install Windows SharePoint Services. Installing SharePoint is very similar to any other Microsoft installation. There are two types of installation modes:
- Typical
This will install Windows SharePoint Services and set up the IIS default virtual server to be a SharePoint team site. It will also install WMSDE (MSDE for Windows) as the default database.
- Server farm
This will install only Windows SharePoint Services. The database and IIS configurations must be made after the installation is complete.
There is a third installation method known as a quiet
installation. Under a quiet installation, no user
intervention is required. The user will never be prompted to supply
any information or see any messages. A quiet installation needs to be
run from the command line using the setupsts.exe installer and
specifying the /q command to indicate that you
want to run the installation in quiet mode. A quiet installation can
be configured to perform either a typical or server-farm style
installation.
Extending virtual servers
When you install IIS, a default virtual server running on port 80 (HTTP default) is created for you. This virtual server hosts all your SharePoint sites on your server, and allows others to connect through it to view your sites. A single IIS installation can have multiple virtual severs configured; however, each server typically runs on its own port.
Windows SharePoint Services uses virtual servers to host its sites. Windows SharePoint Services attaches to a virtual server to create this link. The attachment process is referred to as extending a server and is used for other applications such as Microsoft FrontPage Server Extensions.
Before you can create any SharePoint sites, you must extend at least one virtual server. When installing SharePoint in a single-server environment, SharePoint will automatically extend the virtual server on the local computer and create a default site for you. However, if you are installing SharePoint in a complicated environment, such as a server farm, you will have to manually extend each virtual server separately.
Configuring Windows SharePoint Services
After Windows SharePoint Services has been installed, you have multiple configuration options to help you fine-tune your system. You can manage these options using the SharePoint Central Administration site, which is automatically deployed with your installation. Through this site, you can configure the following:
The virtual server
Security for SharePoint
The server
Components that SharePoint uses
With any Windows SharePoint installation, the Central Administration site is accesible through the Administrative Tools section in Windows Server 2003. Figure 6-4 shows the Central Administration site and the administration options available.
The central administration site is divided into several different configuration sections. See the Section 4.4 in Chapter 4.
Virtual server configuration
The virtual server controls access to SharePoint team sites. Configuring the virtual server allows you to manage the following options:
- Extend or upgrade virtual server
This option allows you to manage your virtual servers, create new content databases, and extend your virtual server to map to another virtual server. You will need to access this option if you have not extended a virtual server. For instance, if you selected server farm as your installation option, you will need to extend each of the servers in the farm.
- Create a top-level web site
By default, a top-level web site is created for you when you perform a typical installation. However, if one does not exist, or you need to create another top-level web site, you can use this option. From this screen, you can assign the site owners, select a quota template, and choose the site language.
- Delete site collection
At any time, you can remove a top-level web site. By using this option, you can delete an entire top-level web site, including all subsites that exist within it.
- Configure virtual server settings
SharePoint, when installed through a typical installation, creates three virtual servers:
Administration
Default web site
Microsoft SharePoint Administration
The virtual server configuration allows you to manage the settings for all three virtual servers and any other virtual servers that you may have extended for use with SharePoint. Figure 6-5 shows the Virtual Server Settings page. The majority of your site administration exists within this area.
From the Virtual Server Settings screen, you can:
- Automate web site collection management
Enables users to create top-level web sites on the virtual server. You can also configure site collections to be autodeleted if they are not in use.
- Set security for the virtual server and Web Part pages
Enables you to manage rights and permissions for site groups and users.
- Configure the virtual server
Enables you to change the general settings for the virtual server.
- Manage content databases
Enables you to change the content databases for the virtual server.
- Establish email settings
Enables you to configure the email server and settings.
- Remove Windows SharePoint Services from the virtual server
Enables you to remove Windows SharePoint Services from the virtual server.
- Define managed paths
Enables you to specify the paths in the virtual server that Windows SharePoint Services will manage.
- Create a top-level web site
Enables you to create a new top-level web site.
- Delete a site collection
Enables you to remove a site collection from the virtual server.
- Configure components
Enables you to configure the data-retrieval service settings.
Security configuration
With the use of both Active Directory and Windows NT User Accounts, Windows SharePoint Services has made a strong attempt to lessen the burden on administering user accounts. Configuring security allows you to manage the following options:
- Set SharePoint administration group
By selecting this option, you grant a Windows NT group administrative access. By default, the administrator user account is given administrative access to SharePoint. Similarly, the owner of any team site is automatically granted administrative access over that specific site. However, if you want to grant administrative control to a group of users, you can grant global administrative access to a Windows NT group account.
- Manage site collection owners
Whenever you create a new team site in SharePoint, you must specify a site owner. This option allows you to change who the owner is after the site has been created.
- Manage web site users
You can grant users specific roles to any of the SharePoint team sites. By using this screen, you can add, modify, and delete roles for a user to a specific team site.
- Manage blocked file types
In order to prevent malicious files from being uploaded or to stop users from downloading files that they should not be downloading, you can block file types. This screen allows you to prevent specific file types from being saved or downloaded from SharePoint.
- Configure antivirus settings
Because SharePoint allows users to upload and download files from SharePoint team sites, you will want to protect your servers and users’ machines from receiving a virus. This screen allows you to configure settings to scan documents when users upload documents to or download documents from the virtual server.
Server configuration
After installing Windows SharePoint Services, there are several server-based options that are not turned on or set up by default. To modify these settings, use the following options:
- Manage email server settings
In order to use certain SharePoint functionality (such as alerts), you must configure the email options. From this screen, you can identify an SMTP server and specify the From and Reply-to email addresses to be used when sending email from a SharePoint site.
- Manage the web server list
When you are running a server farm, you will want to control what your servers are doing. From this screen, you can not only manage all the servers in your server farm, but also remove servers from your farm.
- Manage the database server
There are two options that can be performed in this section:
Set default content database server
Set configuration database server
The first option allows you to specify the location of your database server. A default single-server installation shows your local server name. The second option allows you to decide how to connect to the database.
- Configure the HTML Viewer
SharePoint allows you to configure an HTML Viewer service. The HTML Viewer service will automatically translate Microsoft Office document types such as PowerPoint and Word into standard HTML. In other words, by configuring the HTML Viewer, you can allow users to view Microsoft Office documents (e.g., .doc, .xls, .ppt) without the required software. From this screen, you can enable this service and point SharePoint to the location of the translation program(s).
- Configure the virtual server for central administration
As mentioned previously, application pools are used to host SharePoint sites. From this screen, you can connect the SharePoint Central Administration site to an existing application pool, or generate a new application pool to support the administration site. Generally, you will want to have the administration site running under a different application pool than ordinary user sites. That way, if the user sites are malfunctioning, you should still be able to access the administrative site to analyze the problem and make any repairs.
Component configuration
There are some global components that can be configured after the installation. These components are used across all SharePoint sites. To configure components, you can use the following options:
- Manage full-text searching
Full-text searching is a feature that is only available if you are using SQL Server 2000 Standard or Enterprise Edition. If you are using a full version of SQL Server, you can use this option to enable and disable full-text searching.
- Manage the usage analysis processing
Usage analysis allows you to monitor all your SharePoint team sites. This information can provide you with a strong idea of how users are accessing and using SharePoint sites. This option lets you set up the logging and processing of data for usage analysis.
- Manage quotas and locks
In smaller installations, site quotas and locks are not a major concern. However, when dealing with larger implementations of SharePoint, you will want to limit how many resources are allocated to different sites. This section allows you to set limits on data storage and the number of users allowed for a site collection.
- Manage the data-retrieval service settings
Using SOAP and XML, this new type of data-retrieval service allows data to be sent and received from different data sources. This option allows you to enable data-retrieval services, limit the response size of SOAP messages, enable update query support, and set the timeout for the data source.
Integrating with SharePoint Portal Server 2003
Windows SharePoint Services provides a powerful suite of functions for developing portals and working collaboratively. However, Windows SharePoint Services only provides part of the total information portal solution.
SharePoint Portal Server
SharePoint Portal Server 2003 extends Windows SharePoint Services by adding many new features to assist larger and more robust collaborative work environments. In particular, SharePoint Portal Server 2003 provides a solution that enables enterprises to:
Use single sign-on to enable easy access and relieve administrators from having to maintain multiple user data stores
Integrate information from various systems (such as Microsoft BizTalk 2004) into a single coherent portal
Employ a complete end-to-end solution that allows users to search for people, teams, and information through audiences, automatic categorization, site directories, and user profiles
Use new deployment and management tools to meet the ever-changing needs of the corporate enterprises
The Relationship Between Windows SharePoint Services and SharePoint Portal Server 2003
Although SharePoint Portal Server 2003 provides more features than Windows SharePoint Services, it is very important to remember that SharePoint Portal Server 2003 is an extension of Windows SharePoint Services. Whereas Windows SharePoint Services allows you to create sites for team collaboration, SharePoint Portal Server 2003 connects these sites to create a global directory. In other words, SharePoint Portal provides a unified interface into all team sites.
Another thing to keep in mind is that many of the features in SharePoint Portal Server 2003 require Windows SharePoint Services. For instance, user profiles are built by using Web Parts, which is a feature from Windows SharePoint Services. In other words, Windows SharePoint Services and SharePoint Portal Server 2003 work together to provide a single, complete portal solution. Figure 6-6 illustrates the relationship between SharePoint Portal Server and SharePoint Services.
Comparing features of Windows SharePoint Services and SharePoint Portal Server 2003
Table 6-2 provides a feature list of many of the items in SharePoint Portal Server. This table identifies whether the feature is exclusive to SharePoint Portal Server 2003 or if the feature also exists in Windows SharePoint Services. Because SharePoint Portal Server 2003 requires Windows SharePoint Services, none of the features of Windows SharePoint Services are excluded from SharePoint Portal Server.
|
Feature |
Both/SharePoint Portal Server |
|
Both | |
|
Automatic categorization |
SharePoint Portal Server |
|
Audiences |
SharePoint Portal Server |
|
Customization from the browser |
Both |
|
Both | |
|
Document libraries |
Both |
|
Document workspaces |
Both |
|
Integration with Biztalk |
SharePoint Portal Server |
|
Integration with Microsoft FrontPage 2003 |
Both |
|
Integration with Microsoft InfoPath 2003 |
Both |
|
Integration with Microsoft Office 2003 |
Both |
|
Lists |
Both |
|
Meetings |
Both |
|
SharePoint Portal Server | |
|
Personal sites |
SharePoint Portal Server |
|
Shared services |
SharePoint Portal Server |
|
Single sign-on |
SharePoint Portal Server |
|
Site directory |
SharePoint Portal Server |
|
Surveys |
Both |
|
Templates |
Both |
|
Topic areas |
SharePoint Portal Server |
|
User profiles |
SharePoint Portal Server |
|
Web Part pages |
Both |
Choosing SharePoint Portal Server or Windows SharePoint Services
If SharePoint Portal Server 2003 is an extension of Windows SharePoint Services, when should one be chosen over the other? Table 6-3 provides some guidance for common enterprise scenarios.
Keep in mind that Windows SharePoint Services is the simpler solution; however, SharePoint Portal Server provides additional features. If you choose to use SharePoint Portal Server, you gain all of Windows SharePoint Services, plus the additional features.
Integrating Windows SharePoint Services with SharePoint Portal Server
Even though SharePoint Portal Server 2003 extends Windows SharePoint Services, integration between the two applications is not completely seamless. As with any upgrade (or in this case, integration), it is advisable to back up the server prior to beginning the integration.
Prior to installing SharePoint Portal Server 2003, there are two tasks that need to be completed:
Verify the configuration is supported.
Record the SQL Server database names.
Once you have completed these tasks, you can proceed to install and configure SharePoint Portal Server.
Verify configuration
Two Windows SharePoint Services configurations are not supported during an install by SharePoint Portal Server:
Unfortunately, if either of these modes has been installed, you cannot install SharePoint Portal Server 2003 over Windows SharePoint Services. These options are set during the installation of Windows SharePoint Services and cannot be changed.
To find out if you are in Scalable Hosting mode, open the
configuration database for Windows SharePoint Services. Find the
Globals table and open it. Search for the UseHostHeader column. If
the value is 1 in UseHostHeader, you are in
Scalable Hosting mode.
To determine if you are using Active Directory Account Creation mode, open the SharePoint Central Administration site. If the options to create a top-level site, enable Self-Service Site Creation, and adding users are not available, you are in Active Directory account mode.
In either case, you will not be able to integrate your existing Windows SharePoint Service installation with a new installation of SharePoint Portal Server.
Record SQL Server database names
During the installation of SharePoint Portal Server 2003, one of the steps will be to identify your database. If you specify the settings of the current Windows SharePoint Services installation, all of the functionality from your existing virtual servers will be retained. Otherwise, your new SharePoint Portal Server 2003 will be created with no information pertaining to the existing Windows SharePoint Services sites.
You can use the SharePoint Central Administration site to gather the names and settings of your content databases for use in the SharePoint Portal Server installation. Figure 6-7 shows the Set Configuration Database Server screen that allows you to enter the configuration information for your databases.
You should note all of the details for each database in your current installation before beginning the installation of SharePoint Portal Server.
Install and configure SharePoint Portal Server 2003
For the most part, installing and configuring SharePoint Portal Server 2003 over an existing Windows SharePoint Services installation is very straightforward. However, as with all things, there are some important items to note:
All virtual servers and content databases will be stopped and disconnected during the installation. You have to manually reconnect the virtual servers to SharePoint Portal Server 2003 once the installation is complete.
In a server farm, you must install SharePoint Portal Server 2003 on every server that contains an instance of Windows SharePoint Services.
If the virtual servers for both Windows SharePoint Services and SharePoint Portal Server 2003 are located on the same machine and use the same port, you must apply host headers to allow for navigation to the correct sites.
You must create a new virtual server in SharePoint Portal Server 2003 and extend it to map to your existing Windows SharePoint Services virtual servers to access existing SharePoint sites.
Consider the Microsoft SharePoint Migration Tool
As mentioned previously, you need to create a new virtual server once SharePoint Portal Server 2003 has been installed over Windows SharePoint Services. By configuring the new virtual server to extend the existing Windows SharePoint Services virtual servers, you can now access your existing SharePoint team sites. Fortunately, there is another way to map to your existing SharePoint team sites without having to create a new virtual server manually.
The Microsoft SharePoint Migration Tool (smigrate.exe) provides you with a method of moving your existing Windows SharePoint Services sites to SharePoint Portal Server 2003. The Migration Tool:
Backs up all sites to a file
Restores the sites to the new location
If you have many sites, or the site you are trying to migrate is large, this process could take a very long time to complete. In order to increase performance, you should configure the process with:
One server running the Migration Tool
One or more servers acting as the web servers
One or more servers acting as the database servers
Once you have completed migration, you should be able to leverage the full features of SharePoint Portal Server.
Windows SharePoint Services Service Pack 1
Microsoft released the first service pack for Windows SharePoint Services on September 2, 2004. The service pack contains important security enhancements and fixes issues not covered in a Microsoft Knowledge Based article previously released. Service pack 1 fixes the following issues:
A "Bad Request” error message is displayed when entering
//localhostin Internet Explorer.A Web Part not being added to the online Web Part gallery.
Restoring a SQL database causes links at the root of a web site to break.
Relinking a form in SharePoint Services causes formatted text to move.
Oldest items in threaded view in a discussion are listed first.
Backing up SharePoint Services causes a “Write error” error message.
An “Error 403.1” error message is displayed when you create a new SharePoint web site.
Installing a language SharePoint template pack does not add the language to the Select Language list.
A “Form Validation Error” error message is displayed when uploading a large file.
A nonprovisioned web site is provisioned when installing or updating a SharePoint server.
If you update SharePoint, IIS services that were originally stopped may be restarted automatically.
Opening a SharePoint web page causes FrontPage to quit.
Installing an update that contains the Mso.dll file may cause Microsoft Office programs to indicate an incorrect service pack level.
Some SharePoint files have certificate expiration dates that are earlier than expected.
Adding a user through Microsoft Windows groups corrupts the UserInfo field on the home page.
Multiple threads accessing the same document at the same time on SharePoint causes an “Access Violation” error message.
Entering
//localhostin Internet Explorer on a Windows Server 2003 machine causes a “Not authorized” error message to be displayed.Pasting text in a new announcement that contains extended characters fails.
If the file properties contain a nonbreaking space, it will corrupt the XML file in SharePoint.