On Aivea Server

stsadm -o export -url http://pipeline.mmlegalnetwork.com/ -filename C:\software\client_delivery\pipeline.cab -versions 4 -includesecurity

On Joe's Server

stsadm.exe -o import -url http://pipeline.mmlegalnetwork.com/ -filename C:\software\client_delivery\pipeline.cab –includesecurity

The subsites doesn’t import, you have to individually import them 1 by 1 {better write a script}

On Aivea Server

stsadm -o export -url http://pipeline.mmlegalnetwork.com/subsite1 -filename C:\software\client_delivery\pipeline-subsite1.cab -versions 4 -includesecurity

On Joe's Server

stsadm.exe -o import -url http://pipeline.mmlegalnetwork.com/subsite1 -filename C:\software\client_delivery\ pipeline-subsite1.cab –includesecurity

Sometime, it looks impossible to shrink the Trucated Log file for SharePoint 2007 Configuration database. Following code always shrinks the Trucated Log File to minimum size possible.

USE SharePoint_Config

GO

DBCC SHRINKFILE(SharePoint_Config_log, 1)

BACKUP LOG SharePoint_Config WITH TRUNCATE_ONLY

DBCC SHRINKFILE(SharePoint_Config_log, 1)

Aivea launched dedicated website for SharePoint Training!

Please visit http://www.sharepointrangers.com

http://www.microsoft.com/downloads/details.aspx?FamilyID=BD5C77B0-F556-4136-8730-1D7FEEAE0A42&displaylang=en

You can view user alerts for each site under Site Actions-->Site Settings-->User Alerts. Simple

 

Here is the first incarnation of the a simple SharePoint collaboration site in French, this site was created a site collection after the French language pack was installed.

Multilingual User Experience

Office SharePoint Server 2007 provides capabilities to create, manage, and read content, but it also provides tools to administer sites, site collections, and farms. Multilingual experience can vary depending on the user‘s rights and tasks. This list describes the multilingual experiences supported by Office SharePoint Server 2007:

Activity	Multilingual experience
Read and manage content, site navigation, search	Full multilingual experience out of the box, except for search, where customization is needed
Site administration	Full multilingual experience out of the box
Site collection administration	Single language experience, depending on the language of the top-level Web site
Farm administration	Single language experience, depending on the SharePoint Products and Technologies installation language

 

The following language considerations are applied to an Office SharePoint Server 2007 server farm:

·         Office SharePoint Server 2007 supports one installation language per server farm. The same language version of Office SharePoint Server must be installed on all servers in the server farm.

·         Language packs can be installed on the server farm; however, all servers in the farm must have the same language packs installed for the sites to work properly.

·         Site collections and sites can use different languages, depending on the language packs installed.

·         Site collections can contain subsites in different languages from the parent site and from each other.

Collaboration Team Sites (WSS/MOSS)

In this scenario, users have a place where they can collaborate by creating content and sharing information. This scenario is typically composed of a small number of users who understand a common language. Normally, this scenario doesn’t require content translation and the scope is usually a single site. Those sites can be a single island of information or they can be grouped under a corporate portal. Both Windows SharePoint Services and Office SharePoint Server 2007 can fit in this scenario by using features such as language packs, search, and self-service site creation. Users can create site collections in different languages by themselves, without relying on farm administrators. Moreover, site collection owners can also create subsites in different languages within the same site collection. These concepts can now be applied to both collaboration and Internet portals, where users are able to create subsites in the portal’s hierarchy in different languages.

Corporate Enterprise Collaboration Portals (Publishing/Pages Library Only)

In this scenario, a single company or an enterprise has a portal where information is available in different languages. This portal can be located in a single place or geographically distributed (also called "geo-deployment"). Information needs to be managed and accessible to employees by using their preferred language. Depending on the requirements, all content can be provided in different languages or only a specific subset of content may have this requirement (for example, company news). Employees also need a personal site where they can store information and collaborate with each other in their preferred language. Most features provided out of the box by Office SharePoint Server 2007 can help people implement this scenario. A new Office SharePoint Server 2007 feature named Variations provides the ability to synchronize publishing pages among sites in a site collection. Moreover, the Variations feature can redirect users to the correct site based on their language preferences. Search can be customized to provide users a search experience in their preferred language; doing this, users will be able to submit queries or look for content in a familiar user interface (UI). Finally, in some specific scenarios, by using a new feature in Office SharePoint Server 2007 named Content Deployment, the same portal can be replicated in read-only instances in a different location to provide a fast experience to users across enterprise or geographic boundaries. This paper provides, in the sections below, some generic guidelines for using content deployment for multilingual geo-deployment scenarios. For additional information about the Content Deployment feature and geo-deployment options, visit www.microsoft.com.

Internet Portal (Publishing/Pages Library Only)

In this scenario, companies need to create an Internet portal to publish content on the Internet. Content must be published in many languages so Internet users can read and search for content in their preferred language, or they can switch between various languages for the same content, which gives them a dynamic multilingual user experience. On the other hand, content owners need a tool that provides a way to create and keep content synchronized in these languages. They may also have to provide content to third parties for translation, without letting external users access the staging environment. Content approval workflow features ensure that only approved content is published, only after review or on a certain date. Finally, this portal can be located in a single place or geo-deployed to provide better performance for users. Just as with the above scenario, features provided out of the box by Office SharePoint Server 2007 can help people implement this scenario. By using the Variations feature, content can be synchronized in different languages (on different sites) and users can be redirected to their preferred language. Search can also be customized to provide a search experience to the user in their preferred language. If necessary, by using the Content Deployment feature, the same portal can be replicated to read-only instances in a different location to provide a faster experience to users across enterprise or geographic boundaries.

Enterprise Search Portal

In this scenario, a single company has different portals in different languages where users manage and share content in their preferred language. This is a typical scenario in enterprises where each subsidiary needs a single divisional portal for local content. However, there is often a need to have a single centralized place where users can land to perform a search on all of a company's content. By using enterprise portal search, users are then able to find specific content among all divisional portals by using a friendly UI that provides search options in their preferred languages. Office SharePoint Server 2007 provides features to create a solution for this scenario: by having different site collections in different languages on the same farm, it is now possible to create different divisional portals in different languages by using the same hardware infrastructure. By using the Variations feature, it is also possible to set up an enterprise search portal that provides search options in the user’s preferred language. Topologies and farm configurations in Office SharePoint Server 2007 provide options to share services between site collections in different languages on the same farm or among different farms.

Here is the process to install the language packs for MOSS 2007

I followed the instructions here;

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=2447426b-8689-4768-bff0-cbb511599a45

I downloaded the language pack from the following URL;

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=2447426b-8689-4768-bff0-cbb511599a45

Then I discovered that you have to select the language you want from the drop down and then click change. Then you have to download the language pack from that page. Interesting given that I don't read or speak any of the other languages of course except French

Then I installed those language packs (after extracting them using WINRAR).

Even the installation is in that language :)

and voila!

Finally, Microsoft just released SQL Server 2008 platform. Aivea announced the first ever production ready Hosted SharePoint 2007 on 64 SQL Server 2008 Enterprise Platform - Please see more details at http://www.aivea.com/sharepoint-hosting.htm

Microsoft recently released important updates for SharePoint after SP1. Microsoft strongly recommends that you install the updates

The updates can be downloaded from the links below:

 

Infrastructure Update for Microsoft Office Servers (KB951297) - x86 (MOSS)

 

Infrastructure Update for Microsoft Office Servers (KB951297) - x64 (MOSS)

 

Infrastructure Update for Windows SharePoint Services 3.0 (KB951695) - x86 (WSS)

 

Infrastructure Update for Windows SharePoint Services 3.0 (KB951695) - x64 (WSS)

 

Please see the details at Microsoft SharePoint Team Blog

 

Please don’t do the updates if you running an extranet site using AAM for public URLs – see Joel’s blog http://www.sharepointjoel.com/Lists/Posts/Post.aspx?ID=70