View Only

Members of this group can view pages, list items, and documents. If the document has a server-side file handler available, they can only view the document by using that file handler.

• Limited Access permissions

• View Item

• View Versions

• Create Alerts

• View Page

Read

Allows read-only access to the Web site.

• View Only permissions

• Open Item

see User permissions and permission levels (Office SharePoint Server) (http://technet.microsoft.com/en-us/library/cc721640.aspx) for more information.

As we can see the only difference between View Only and Read is *Open Item: View the source of documents by using server-side file handlers* which is very confused.

The server-side file handlers is hard to understand, the following words may be helpful.

Server Side File Handler
In several business activities the output is a file. The contents of this file is generated on the server, but has to be written to disk on the client side. We proposes a serializable class, that will have the same interface like a file on the server just without any writing to disk. Once on the client side it can be stored. It should be aligned with the file features of ASCII IO in Axapta today. Today most of the implementations requiring this feature are writing to the client file directly from the server. Causing a lot of C/S traffic and poor performance. This approach won't work for Green. (the server is stateless and cannot call the client).

the literally difference is the file will not be downloaded to their local computer if you have View Only permission only. While for users who have Read permission, they can open such the document locally.

In most case, there are no significantly different between them, because Office documents can be opened in server side.

If you used stsadm -o createsite or createweb operations, you would complain about the -sitetemplate parameter.

It actually took me lots of time to check the value in the 12Hive.

I am asked by a customer today, so I lists all shown templates in the UI.

The sitetemplate codes (actually site definition codes) are in the webtemp*.xml files located in %Program Files%\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\[Lcid]\XML.

Site Templates shown in the SharePoint Server 2007 site creation UI:

Server Admin Templates

Site Admin Templates

If you add the template using the Addtemplate operation to the central template gallery, you must specify the template name as _GLOBAL_#number, where number refers to the template ID.

For more templates detailed information, please refer to the XML files located in %Program Files%\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\[Lcid]\XML.

There have been a workaround that make the content web application pool use the same account as the central administration web application pool account.

In the August Cumulative Update, we fixed the permission issue related with DMS.

Now, the processes of configuring incoming mail with Microsoft SharePoint Directory Management Service (DMS) enabled are as follows:

1. Apply the August Cumulative Update or later update.

Visit Updates Resource Center for SharePoint Products and Technologies (http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx) to get latest updates.

2. Grant content application pool account with Design permission to Distribution Groups list in Central Administration > Operations > Approve/reject distribution groups.

3. Install Exchange Server 2003 / 2007.

If you do not want to install Exchange Server 2003 / 2007, you need to extend the AD schema by the following command at least.

l For exchange 2003, run setup /PrepareForest from the exchange 2003 installation disk.

l For exchange 2007, run setup /PrepareSchema from the exchange 2007 installation disk.

4. Follow the step by step guidance to configure the incoming mail:

Configure incoming e-mail settings (Office SharePoint Server) (http://technet.microsoft.com/en-us/library/cc262947.aspx)

Windows Internal Database is shipped with WSS 3.0. It is a relational data store used by Windows components and services.

The Windows Internal Database is not listed in the Add or Remove Programs tool and is not removed when you remove Windows SharePoint Services 3.0 from the computer. If you want to remove it from the server, please refer to the commands in the KB 920277 (http://support.microsoft.com/kb/920277)

Because the Windows Internal Database installs to your system drive by default, the disk space of the system drive may run out at some time. You can refer to the article to move it other drives: Move Windows Internal Databases to a different drive (Windows SharePoint Services 3.0) (http://technet.microsoft.com/en-us/library/dd277864.aspx)

If you are not familiar with command line, you could download the Microsoft SQL Server Management Studio Express Service Pack 2 which is a free, easy-to-use graphical management tool for managing SQL Server 2005 Express Edition, and then perform GUI operations by connecting the Windows Internal Database using “\\.\pipe\mssql$microsoft##ssee\sql\query” as Server Name.

SQL Server 2005 Express Edition is a free desktop database engine and shipped with MOSS 2007. It is limited to store a maximum of 4 GB of data and work on single processor systems.

For guidance about moving Windows SharePoint Services 3.0 content databases from Windows Internal Database to an instance of Microsoft SQL Server 2005, please refer to:

Move content databases from Windows Internal Database to an instance of SQL Server (Windows SharePoint Services 3.0) (http://technet.microsoft.com/en-us/library/cc287738.aspx)

Move content databases from Windows Internal Database or SQL Server Express Edition to an instance of SQL Server (Office SharePoint Server 2007) (http://technet.microsoft.com/en-us/library/cc262018.aspx)