Showing posts with label Office SharePoint Server 2007 Deployment. Show all posts
Showing posts with label Office SharePoint Server 2007 Deployment. Show all posts

2009-03-04

SharePoint 2007 - Move Content and Configuration Databases

If you’ve ever wanted to relocate your WSS 3.0 or MOSS 2007 content databases or configuration database from one SQL server to another, you’ve probably found very little documentation and very little written on this topic. Below is my attempt to provide some guidance for these tasks. The steps are fairly simple, but please remember to try all operations of this magnitude on a development or test environment before trying this on your production SharePoint environment.

http://sharepointsherpa.com/2008/04/18/sharepoint-2007-move-content-and-configuration-databases/

2009-03-03

Plan for administrative and service accounts (Office SharePoint Server)

This article describes the accounts that that you must plan for and describes the deployment scenarios that affect account requirements.

http://technet.microsoft.com/en-us/library/cc263445.aspx

2009-02-25

Scaling MySites; How Many MySites per Content DB?

Scale-out
The primary scale-out strategy is to use multiple content databases in the MySite web application. To meet the guideline of 50,000 site collections per DB, you should plan a minimum of 2 content databases to handle 100,000 MySites.

Scale-up
To further ensure the overall performance of SharePoint when using multiple content databases, configure SQL Server so that the databases are hosted on different physical drives (spindles). This is usually possible with SAN storage solutions also. My instinct is that you'd want to balance this with the scale-out strategies and usage patterns. If you had 200,000 users with MySites and a large portion really began to use MySites heavily, then you might want to use 20 content databases distributed across 5 or 10 physical drives.

Scaling MySites; How Many MySites per Content DB?

2009-02-24

Best practices for My Sites

This article is one of a series of Best Practices articles for Microsoft Office SharePoint Server 2007. This article describes the typical characteristics and best practices for My Sites based on Office SharePoint Server 2007.

Best practices for My Sites

2009-01-20

Downloadable book: Planning and deploying Service Pack 1 for Office SharePoint Server 2007 in a multi-server environment

Learn how to plan for and deploy Microsoft Office SharePoint Server 2007 Service Pack 1. In this document, we present our most up-to-date capacity planning and performance guidance for planning, operations, and monitoring along with deployment information for SP1, so that you can tune and address system performance as you upgrade to SP1.

http://technet.microsoft.com/en-us/library/cc262996.aspx

2008-12-07

What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

SharePoint is compatible with a variety of reverse proxy servers, but for this example we'll take a look at a publishing rule from Microsoft's reverse proxy software - Internet Security and Acceleration Server 2006. ISA Server 2006 includes a SharePoint publishing wizard that walks you through creating a publishing rule for SharePoint. Once the rule is created, you can modify it at any time. (The following images show a slightly modified publishing rule where the "Forward the original host header" option is turned off to help demonstrate the flexibility of AAM. If we left the "Forward the original host header" option turned on, the public hostname would also serve as the internal hostname when configuring AAM.) The first two dialogs show the "listener" and "public name" properties of the rule, which define what URL users will use to access your SharePoint site. Remember that this URL is really the URL of your reverse proxy server, which will forward the request to your SharePoint server.

http://blogs.msdn.com/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx#9163002

2008-11-05

Add a trusted data connection library

In this article:

- About trusted data connection libraries
- Add a trusted data connection library

About trusted data connection libraries

In Microsoft Office SharePoint Server 2007, a trusted data connection library is a data connection library from which you have determined that it is safe to access Office data connection (.odc) files. The .odc files are used to centrally manage connections to external data sources.

Instead of allowing embedded connections to external data sources, Excel Calculation Services can be configured to require the use of .odc files for all data connections. The .odc files are stored in data connection libraries, and the data connection libraries have to be explicitly trusted before Excel Calculation Services will allow workbooks to access them.

If a data connection is linked from a workbook that is accessed by a server running Excel Calculation Services, the server checks the connection information and the list of trusted data connection libraries. If the data connection library is on the list, a connection is attempted by using the .odc file from the data connection library; otherwise, the connection request is ignored.

Before you can configure a data connection library as a trusted data connection for Excel Services in Microsoft Office SharePoint Server 2007, you must create a data connection library on a SharePoint site. To create a data connection library, click the Site Actions menu, select Create, and then click Data Connection Library. On the New page, type a name for the new data connection library and click Create.

http://technet.microsoft.com/en-us/library/cc262739.aspx

2008-10-12

2007 Office System Converter: Microsoft Filter Pack

This download will install and register IFilters with the Windows Indexing Service. These IFilters are used by Microsoft Search products to index the contents of specific document formats. This Filter Pack includes IFilters for the following formats: .docx, .docm, .pptx, .pptm, .xlsx, .xlsm, .xlsb, .zip, .one, .vdx, .vsd, .vss, .vst, .vdx, .vsx, and .vtx.

To register these IFilters with a specific Search product, please see the associated KB article below:

- Office SharePoint Server 2007 - Office SharePoint Server 2007 registration steps
- Search Server 2008 - Search Server 2008 registration steps
- SharePoint Portal Server 2003 - SharePoint Portal Server 2003 registration steps
- Windows SharePoint Services v3.0 - Windows SharePoint Services v3.0 registration steps
- Exchange Server 2007 - Exchange Server 2007 registration steps
- SQL Server 2005 - SQL Server 2005 registration steps
- SQL Server 2008 - SQL Server 2008 registration steps

http://www.microsoft.com/downloads/details.aspx?FamilyID=60c92a37-719c-4077-b5c6-cac34f4227cc&DisplayLang=en

2008-08-23

SQL Server 2008 Unterstützung für Office SharePoint Server 2007

Microsoft SharePoint Team hat in ihrem Blog die SQL Server 2008 Unterstützung für Office SharePoint Server 2007 und Windows SharePoint Services 3.0 bekannt gegeben.

SQL Server 2008 Support for SharePoint Products and Technologies

Windows SharePoint Service 3.0

Office SharePoint Server 2007