Tuesday, 9 December 2008

If you want to bind an event handler with a simple feature all you need to do is tweak your Feature.xml and add the Assembly Information into that and Create a Simple Event handlerFeature.xml FileFeature Id="ec4b9423-46ff-4a61-9264-8761e7c17145"Title="FeatureWithReceiver1"Description="Description for FeatureWithReceiver1"Version="1.0.0.0"Hidden="FALSE"Scope="Site"DefaultResourceFile="core"ReceiverAssembly="SimpleEventHandlerPro, Version=1.0.0.0, Culture=neutral, PublicKeyToken=$PublicKeyToken$"ReceiverClass="SimpleEventHandlerPro.FeatureWithReceiver1"xmlns="http://schemas.microsoft.com/sharepoint/">Creating a Simple Event Handlerusing System;using System.Collections.Generic;using System.Text;using Microsoft.SharePoint;using Microsoft.SharePoint.WebControls;

The List definition files can be configured in such a way that the event handler configured automatically for the newly created document libraries. Here I provide the details of how to do it.Open the Site definition folder. If you use default Site definition, STS, then open the folder from the following location.“C:\program files\common files\Microsoft Shared\web server extensions\60\template\1033\STSNote: Modifying the default files is not supported by Microsoft. Microsoft recommends using custom Site Definition.Open the List Definition folder. If you use default list definition for document library, then open the “DOCLIB” folder in the LISTS folderOpen the “SCHEMA.XML” file in notepad or visual studioModify the LIST node by adding the EventSingAssembly, EventSinkClass, and EventSinkData

Note:Here I hardcoded the EventSinkAssembly for sample. Could you please change it according to your component.Restart IIS.After configuring the details, if you create new document library based on the list definition, then the document library event handler will be automatically configured.

Tere are two types of Events Synchronous and Asynchronous Events.* Synchronous events can trap an item, document library or site before it is deleted,added or updated.eg, ItemAdding, ItemUpdating,ItemDeleting etc.* Asynchronous events can trap an item, document library or site when it is added,deleted or updated.eg, ItemAdded, ItemUpdated,ItemDeleted etc. We create Event Recivers to handle these events. An event receiver basically, is a piece of managed code that is launched in response to an event that takes place within SharePoint.SharePoint Object Model exposes several event classes inherited from Microsoft.SharePoint assembly. There are three main event classes:

SPItemEventReceiver

SPListEventReceiver

SPWebEventReceiver

Each class includes both synchronous and asynchronous methods to work with Item, List or Web Level.

In most cases you want to create your own list definition with your own event receiver that sould only react on events of your custom list.SharePoint ships with alot of list definitions with unique list type numbers:100: Generic list101: Document library104: Announcements listand many more.You can create event receivers that react on events of these list types.To create a custom list definition you should use the visual studio template "List Definition" shipped with the VSeWSS 1.1. If you create a custom list with base type "document library" its id will also be 101. It's just a copy of the template you selected.

First line of schema.xml after creating the custom list definition project:

Thursday, 20 November 2008

The preferred way to provision your features, web parts and assemblies is by creating a Solution Package (.wsp file). You will add add your assembly, the manifest.xml file and all your other components and resources into the cabinet.You will need to add the following entry into the manifest.xml

DeploymentTarget The depoloyment target is location where the assembly will be copied to and can ether be the bin folder of the WebApplication or it could be the GlobalAssemblyCache (GAC)Location The location of the assembly within the cabinet file. SafeControl A SafeControl element entry as described at the beginning of the post.Using this method, your assembly will be correctly deployed the servers in the farm as well as added to the safe controls of the web application. Again any new server added to the farm will automatically get all the solution packages deployed.

Saturday, 27 September 2008

Security account requirements for the configuration of Sharepoint 2007To install Office SharePoint Server 2007 in a server farm environment, at-least 2 accounts are required:A user account that you can use to install Office SharePoint Server 2007 and run the SharePoint Products and Technologies Configuration Wizard. This account must be: A domain user account.

A member of the Administrators group on each of your front-end servers. A member of the SQL Server Logins, which grants login access to your SQL Server instance. A member of the SQL Server Database Creator server role, which grants permission to create and alter databases. A member of the SQL Server Security Administrators server role, which grants permission to manage server logins.A unique domain user account that you can specify as the Office SharePoint Server 2007 service account. This user account is used to access your SharePoint configuration database. It also acts as the application pool identity for the SharePoint Central Administration application pool and it is the account under which the Windows SharePoint Services Timer service runs. The SharePoint Products and Technologies Configuration Wizard adds this account to the SQL Server Logins, the SQL Server Database Creator server role, and the SQL Server Security Administrators server role. It is recommended that you follow the principle of least privilege and do not make this user account a member of any particular security group on your front-end servers or your back-end servers.

Thursday, 25 September 2008

What is a Shared Service Provider?For those of you who don't know what I am talking about a bit of overview. In MOSS 2007 there is this new concept of Shared Services Providers(SSP). The idea being that there are certain services that really make sense to centrally manage and share. A good example being profiles. With a SSP we can import all of the profile information from AD once and then our various web applications can consume the data. So maybe we have http://marketing/ and http://accounting/ it doesn't make sense for each one to maintain identical profile information, they should share.The major services that are handled by the SSP are:Profiles and AudiencesMy SitesSearchAll of Excel ServicesAll of the BDC (Business Data Catalog)Below is an example screen shot from MOSS 2007 Enterprise:

Sometimes the easiest way to think of Shared Services is the Parent vs. Child relationship. The Parent (your SSP) goes out and does all of the work (pulling BDC data, indexing content, hosting My Sites) and the child (your web applications) come to the parents to ask for $5 (request data from the BDC, or view a calculated Excel sheet). Does that help?Multiple SSPsOne of the most overwhelming things about SSPs for some people planning is how many should I have? It is easy to see from the interface that you are given the opportunity to create more than one. When should you do this?As a general rule of thumb most companies will use one SSP. This is my default answer. So why do they give you the ability to run multiple SSPs? There are cases where you want separate search or profiles. The most common? Extranet/internet scenarios. Maybe your SharePoint farm hosts two primary web applications. http://portal/ for your intranet and http://ourcustomers/ for your extranet. In this scenario you probably want separate search and profiles. And now you have found the reason to have multiple SSPs. You don't want to share information you want unique information for both.Another advantage of SSPsSeparation of roles. In some medium and large environments it is not uncommon to have one group administering the physical server farm while another group needs to just maintain search. Well the SSP concept makes this very easy. Since the SSP is its own SharePoint site collection you can define a users access so they can NOT access central administration but they CAN access the SSP. And once they get into the SSP you can even limit them. Once inside the SSP you can determine if they can:Manage user profilesManage audiencesManage permissionsManage usage analyticsBest I can tell if you give them access to the SSP all of the other SSP functions they will have rights to. Guess it needs more testing.Still this separation of services from the actual administration of the server can be quite useful. Epically in companies where the less access I give a user the better.

You have heard a lot about WSS and SharePoint 2007 ,basically what is WSS ?Windows Share point Services (WSS) is a technology provided as an extension to Microsoft Windows 2003 (and above). WSS provides a platform for collaboration applications, offering a common framework for document management and a common repository for storing documents of all types.

Office SharePoint Server 2007 builds on top of Windows SharePoint Services 3.0, rather its an additional layer to provide capabilities including collaboration, portal, search, enterprise content management, business process and forms, and business intelligence.

Friday, 29 August 2008

At times we would be finding difficulty to add a custom webpart to your own site definition(Custom), Many a times i had seen this Error popping up becuase of any xml format error in the webpart defenition added.

Error :[ Web Part Error: The file you imported is not valid. Verify that the file is a Web Part description file (*.webpart or *.dwp) and that it contains well-formed XML. ]

Inorder to get the correct webpart definition look into sharepoint itselfGo to Site settings -> Webparts (under Galleries) -> Click the Edit button/Image next to the webpart you want to add in the site definition, and then click View XML

The XML you get, is the definition that has to be included in the CData part of your page!So, for example you would get:

Saturday, 16 August 2008

If you want to change the product key of SharePoint MOSS Go to Central administration > Operations > Upgrade and Migration section > Convert license type. Enter the new product key and a timer job will be scheduled and once the job completes, the product key should be updated.

Tuesday, 1 July 2008

To view the site defenition (onet.xml) which was used to create the sharepoint site, you could do by using RPC.Append /_vti_bin/owssvr.dll?Cmd=GetProjSchema to the end of the url of your site to get it.Example: http://myserver/sites/mysites/_vti_bin/owssvr.dll?Cmd=GetProjSchema

Friday, 20 June 2008

Its pretty Simple and Sleek creating a Video on your Home Page in Sharepoint 2007 . All you need to do is this to

1. Add a Content Editor WebPart on your Page.
2. Go to Edit > Modify Shared WebPart , Click on Source Editor add this Code
Notes:
1. CLASSID="CLSID:6BF52A52-394A-11d3-B153-00C04F79FAA6" is the class id for Windows Media player.
2. URL will point to the location of the file. Upload this file to document library and put the URL for that file.
3. autoStart specifies value indicating whether the current media item begins playing automatically.
4. uiMode specifies which controls are shown in the user interface.
Possible values: invisible, none, mini, full.
5. PlayCount specifies the number of times a media item will play. Minimum value of one.

Thursday, 24 April 2008

What's the best way to determine the current user within a custom web part developed for MOSS 2007? I've found four solutions so far, but I'm pretty sure there are more:1. Use System.Web.HttpContext.Current.User.Identity.Name, like in any ASP.Net web application2. Use System.Security.Principal.WindowsIdentity.GetCurrent().Name3. Have the Current User Filter send the current user to your web part, and (of course) make your web part a consumer of that value.4. SPWeb web = SPControl.GetContextWeb(Context); SPUser currentUser = web.CurrentUser;

Thursday, 17 April 2008

Q.Trying to setup a people search. I noticed there was a web-part forthis, I've added it to my main page but when I search for something Igot a 404 not Found on peopleresults.aspx.Sol.In sharepoint 2007 it will throw 404 if by default if you have not created a sitewith Search Center Template. Create a new sitecollection and in the Templateselect Enterprise -> Search Center template (with Tabs or regular).Once you have the site create you will just select People Search WebpartEdit -> Modify Shared WebPart and in the Miscellaneous section change theTarget search results page URL to /sites/SearchCenter/results.aspx.Where i have created "searchcenter" i createde it under "sites", try to search afterthat guess it will work..

Monday, 10 March 2008

Windows SharePoint Services allows teams to create Web sites for information sharing and document collaboration, benefits that help increase individual and team productivity. Windows SharePoint Services is a component of the Windows Server 2003 information worker infrastructure and provides team services and sites to Microsoft Office System and other desktop programs. It also serves as a platform for application development. Including such IT resources as portals, team workspaces, e-mail, presence awareness, and Web-based conferencing, Windows SharePoint Services enables users to locate distributed information quickly and efficiently, as well as connect to and work with others more productively.How Windows SharePoint Services WorksWindows SharePoint Services sites take file storage to a new level, providing communities for team collaboration and making it easy for users to work together on documents, tasks, contacts, events, and other information. In addition, team and site managers can coordinate site content and user activity easily. The Windows SharePoint Services environment is designed for easy and flexible deployment, administration, and application development.SharePoint sites are made up of Web Parts and Windows ASP.NET-based components. Web Parts are designed to be added to pages and configured by site administrators and users, creating complete page-based applications. Windows SharePoint Services ships with a number of ready-to-use Web Parts; more will be available in the future from Microsoft and third-party vendors.Team CommunitySharePoint sites provide places to capture and share ideas, information, communication, and documents. The sites facilitate team participation in discussions, shared document collaboration, and surveys. Site content is accessible from both a Web browser and through clients that support Web Services. The document collaboration features allow for easy check in, check out, and document version control.Individual EmpowermentSharePoint site members can find and communicate with key contacts and experts, both by e-mail and with instant messaging. Site content can be easily searched, and users can also receive alerts to tell them when existing documents and information have been changed, or when new information or documents have been added. Site content and layout can be personalized on a per-user basis, and Web Parts can be used to present targeted information to specific users on precise topics.Microsoft Office System programs use SharePoint site content. All of a site's collaborative content—for example, documents, lists, events, task assignments, and membership rosters—can be read and edited within Microsoft Office Word 2003, Microsoft Office Excel 2003, and Microsoft Office PowerPoint 2003. Picture editing of Web-based photo libraries is also possible. Microsoft Office Outlook 2003 allows SharePoint site event calendars to be viewed side-by-side with personal calendars, and it also creates meeting-specific workspaces to augment group appointments.Management EnablerSharePoint site managers can customize the content and layout of sites to ensure that site members can access and work with important and relevant information. Members' participation can also be monitored and moderated when necessary. Security and task responsibilities are both flexible and easily accessible. Well-designed lists and entire sites can be saved as templates and reused by individuals, teams, or business units across an organization.Administration and DeploymentWindows SharePoint Services can scale to thousands of sites within an organization. It fully supports load-balanced Web farm and clustered database deployments. For site and server managers, quotas can be set and enforced not only on storage, but on sites per-server and users per-site. Site usage can be monitored to detect and retire inactive sites. Detailed security options are available and easily managed. Server managers can delegate to end users the ability to create their own sites. Sites and servers can be managed from a Web browser, command-line tools, or a Web service-accessible object model.Integrated Windows .NET DevelopmentIn addition to the Web Part infrastructure, Windows SharePoint Services servers, sites, and site contents are exposed by a comprehensive Windows .NET–based object model and industry-standard Web services. Site customization and enhance data-driven site content is possible, even to non-programmers, by using Microsoft Office FrontPage 2003.

Monday, 3 March 2008

In this post, I'll demonstrate with words and screen shots how to install and get working a portal using Microsoft Office SharePoint Server 2007. Installing this product is not difficult, but it does require some forethought and planning. You can use this post as a reference for getting your version of MOSS 2007 installed.You need to have downloaded the software from Microsoft's site. For information on how to do that, please go here. Once you have registered and downloaded the software, you're ready to start.First, you'll need Windows 2003 Server, fully patched and ready to go. I believe I've seen blog postings recently that indicate that you can install MOSS07 on a Vista server. I'll leave that discussion for other threads and posts.Once you have the operating system ready to go, you'll want to start by running the setup.exe for MOSS 2007. Figure 1 illustrates that after you start the installation process, you'll need to enter a valid product identification key code. This key code can be found on the download site and should have been a part of what you did to get the software in the first place.

Figure 1: Product Identification Key Code Input ScreenAfter entering the product identification key code, click Continue. The next screen is the licensing agreement screen. Now, I always recommend that you read the licensing agreement since it is a legal document and you are bound by its' terms. But I also recognize that in the 10+ years I've been in this industry, I've never seen an agreement that I didn't agree with.............if you get my drift.

Figure 2: Licensing Agreement Screen.Be sure to select the "I accept the terms of this agreement" check box and then click Continue.The next screen will give you the chance to select which type of installation you wish to commit. The Basic installation is used for those who:· Need to install everything on a single server· Do not need to grow into a multi-server farm· Need a quick, easy deployment during installation with lead administrative effortThe Advanced option is selected by those who wish to install MOSS 2007 selecting some of the customizable features. In this illustration, we'll select the Advanced option and follow that route.

Figure 3: Installation Type Selection ScreenAfter clicking on the Advanced button, you'll find that the selections default to StandAlone (Figure 4). However, we'll choose Complete. The meaning of the three options is as follows:· Complete: Enables all of the options for one server to offer the entire range of MOSS 2007 services and features to the network. You can scale out this deployment, start and stop services on this server and use a SQL server to host your databases.· Web Front End: Enables only those options that allows the server to run as a web front end server. What this means is that server is merely the entry and exit point (or one of them among the other WFE servers) for the farm. The actual servers that users will consume will be hosted on other servers (presumably). This cannot be the first choice of a farm unless you plan on installing other servers in the farm to offer the services and features that users will want to consume.· Stand-Alone: Similar to complete, this option enables all of the services and features for the MOSS 2007 farm, but assumes that there is no SQL server, so the MSDE engine is installed locally on this server. You cannot scale out this server into a larger MOSS 2007 farm.Note that in reality, all of the MOSS 2007 binaries are installed in all three choices. All these choices really do is (pragmatically, not technically) turn on and off the code that is required for the server to fulfill the functions that have been assigned to it. Note also that you can select the location where the binaries should be installed in the File Location tab and then sign up to give feedback directly to Microsoft if you'd like to do this.Make your selections, then click Install Now.

Figure 4: Server Type Selection ScreenDuring the installation, you'll be presented with a status bar that is illustrated in Figure 5.

Figure 5: Installation Status ScreenAfter installation has completed, you'll be given the chance to run through the SharePoint Products and Technologies Configuration Wizard (Figure 6). You'll use this wizard to commit the initial configuration options for your new SharePoint farm.

Figure 6: Entry screen to the SPPT Configuration Wizard. Note that you can come back to this screen using the Administration menus that automatically install with the SharePoint Server binariesOne you start the SPPT wizard, you'll receive a pop-up box (Figure 7) that will inform you that certain services are going to be stopped. Be sure it is a good time to stop these services before moving on with the configuration options for your farm.

Figure 7: Informational Pop-Up BoxThe following set of screens in the SPPT Configuration Wizard are design to help you setup the farm. In Figure 8, you'll be able to create a new farm or join and existing farm. Farm membership, at the server level, is determined by which servers are using the same configuration database in SQL and which servers are not. In my illustration, I want to create a new farm, so I select the "No, I want to create a new server farm" radio button. If I had wanted to connect to an existing farm, I would have selected the other radio button.

Figure 8: Connect to a server farm configuration screen in the SPPT Wizard .After making our selection in Figure 8 and then clicking Next, I'm taken to the next screen illustrated in Figure 9. On this screen, I can enter the following configuration values:· The SQL database server name. I'm not clear if this is the host name or netbios name, but I suspect this is the host name. However, you don't need the FQDN here, but you do need name resolution to this server or SQL Instance.· The farm configuration database name is needed in the next input box. Note that the screen just asks for a name, but you need to understand you're entering the most persistent database name for the entire farm - the farm configuration database name. Be sure this name supports your database naming convention. You should decide the name of this database in advance of getting to this screen· The database access account will need to be a member of the local admins group on each SharePoint server along with having db_creator and db_security permissions in SQL. I would suggest you have an account setup just for this purpose in your Active Directory and that you have a strong password associated with this account.

Figure 9: Configuration Database Settings Screen in the SPPT Wizard in Figure 10, you'll be asked to decide which type of security settings you want to use for your farm. First, you can specify a pre-selected port number for central administration to run on or you can allow the wizard to randomly assign a port number. As you can see, this instance of the wizard randomly selected 17386 as the port number for Central Administration (CA). If you want CA to run on a different port, then select the check box and enter the desired port number.The issue of NTLM vs. Kerberos is one that you may at some point wish to consider. Do you want the CA application to run using NTLM (NT Lan Manager) for security authentication or Kerberos? If the latter, there are some special configurations you'll need to complete for your Active Directory (AD) before Kerberos will work. I'm finding that most administrators are happy with NTLM, though those in a larger and more secure implementations are increasingly using Kerberos. For purposes of my illustration here, I'm selecting NTLM.

Figure 10: Configure SharePoint Web Application configuration screen in SPPT WizardAfter you click Next, you'll be given a status bar that indicates how the SharePoint configuration is going. Depending on the type of server you're installing and the options you're installing, you could have as few as seven tasks or as many as eleven. Figure 11 illustrates the progress screen. Note that the caption below the status bar will inform you about the configuration actions that are being executed during this process.

Figure 11: Configuration status bar screen in the SPPT Wizard After the configurations have been executed and committed to the SQL Server database, we finally get to CA where we can further configure our farm. We can start and stop services (Figure 12) on this server and then create web applications. In order to have portal, you'll first need to start the Office SharePoint Server Search service and then create a Shared Services Provider (SSP). I'll start the search service.

Figure 12: Services configuration screen in CA When the search service is started, you're presented with another web page for search configuration administration that needs to be completed before the search service can start. The configuration options are pretty clear. Out of the shoot, you'll use this server for both indexing and servicing queries from users until you can get enough servers in your farm to quarantine those options in your farm. Select a location that has enough disk space for your indexes. You should plan on a space allotment of 20% relative to the amount of information you wish to index. You'll also need to input an email address, a service account and whether or not there is a dedicated WFE for all crawling activities. For now, in my illustration, since this is the first server in the farm, I'll accept the defaults and click OK.

Figure 13: Search configuration screenAfter starting the search service, the next thing I need to do is create a SSP. In order to do this, I'll navigate to the Application tab in CA, click Create or Extend a Web Application, then click Create a New Web Application, then make the configurations necessary that you see in Figure 14. Most of this is pretty self-explanatory, so I won't go through each input in detail. Suffice to say that I've done two things not illustrated here. First, after creating this web application, I then web back into CA, selected the Create or Configure Core Farm Services, then selected New SSP (Figure 15) and then filled in the configuration information for the new SSP. All of the options on that page are self-explanatory, except that you must select an Index server for the SSP to operate.Backtracking just a bit, you can't have an Index server unless the Search services is started. So, that's why I illustrated starting the search services first, then creating an SSP, then creating a portal.

Figure 14: Configuring the new web application to host the portal

Figure 15: Illustration of the SSP management interface where you can select to create a New SSP.Once the SSP is created and the web application for the portal has been created, you can then create the portal. The way to do this is to navigate to CA and then click Create Site Collection. Be sure the http://portal is selected in the drop down list in the upper right-hand portion of the screen (Figure 16). Note that on this screen, you'll need to ensure that you are creating the site collection at the root by selecting the "Create Site at this URL" where the URL path is "root", not in the Sites managed path. Also, if you scroll down, you'll need to select the Corporate Intranet Site under the Publishing tab. Microsoft has renamed the Portal to Corporate Intranet Site and placed it under the Publishing tab for web content publishing purposes. BTW, even though I don't illustrate it here, be sure to give the site a title.

Figure 16: Create Site Collection ScreenAt this point, you should now have a new portal, ready to aggregate, organize and present content for your enterprise, division or department.

Thursday, 28 February 2008

Microsoft Office SharePoint Server 2007 is a new server program that is part of the 2007 Microsoft Office system. Your organization can use Office SharePoint Server 2007 to facilitate collaboration, provide content management features, implement business processes, and supply access to information that is essential to organizational goals and processes.You can quickly create SharePoint sites that support specific content publishing, content management, records management, or business intelligence needs. You can also conduct effective searches for people, documents, and data, participate in forms-driven business processes, and access and analyze large amounts of business data.Microsoft Office SharePoint Server 2007 CapabilitiesMicrosoft Office SharePoint Server 2007 provides a single, integrated location where employees can efficiently collaborate with team members, find organizational resources, search for experts and corporate information, manage content and workflow, and leverage business insight to make better-informed decisions.•Collaboration Allow teams to work together effectively, collaborate on and publish documents, maintain task lists, implement workflows, and share information through the use of wikis and blogs.•Portals Create a personal MySite portal to share information with others and personalize the user experience and content of an enterprise Web site based on the user’s profile.•Enterprise Search Quickly and easily find people, expertise, and content in business applications.•Enterprise Content Management Create and manage documents, records, and Web content.•Business Process and Forms Create workflows and electronic forms to automate and streamline your business processes.•Business Intelligence Allow information workers to easily access critical business information, analyze and view data, and publish reports to make more informed decisions.Integration with 2007 Microsoft Office SystemOffice SharePoint Server 2007 is designed to work effectively with other programs, servers, and technologies in the 2007 Office release. For example, with Microsoft Office PowerPoint 2007, you can create a slide library on an Office SharePoint Server 2007 site that allows other users to pick specific slides for their own presentation and receive notifications and updated versions when the slides have been modified. Click here for more examples of how specific 2007 Office release programs work with Office SharePoint Server 2007.Microsoft SharePoint Products and TechnologiesSharePoint Products and Technologies provide enterprise-scale capabilities to meet business-critical needs like managing content and business processes, simplifying how people find and share information across boundaries, and enabling better informed decisions. Using the combined collaboration features of Windows SharePoint Services and Office SharePoint Server 2007, plus the design and customization capabilities of Office SharePoint Designer 2007, organizations can enable their users to create, manage, and easily build their own SharePoint sites, and enable these sites to be discovered throughout the organization.How are Microsoft Office SharePoint Server 2007 and Microsoft Windows SharePoint Services related?If you've heard about Microsoft Windows SharePoint Services, you may wonder how it relates to Office SharePoint Server 2007. Windows SharePoint Services is an enabling technology that is included in Microsoft Windows Server 2003. It helps teams stay connected and productive by providing easy access to the people, documents, and information that they need to make well-informed decisions and get work done. Office SharePoint Server 2007 relies on the Windows SharePoint Services 3.0 technology to provide a consistent, familiar framework for lists and libraries, site administration, and site customization. Any features that are available in Windows SharePoint Services 3.0 are also available in Office SharePoint Server 2007.However, Office SharePoint Server 2007 offers enhanced and additional features that are unavailable on a Windows SharePoint Services site. For example, both Office SharePoint Server 2007 and Windows SharePoint Services include site templates for collaborating with colleagues and setting up meetings. However, Office SharePoint Server 2007 includes a number of additional site templates related to enterprise and publishing scenarios.The chart below shows a quick overview of the capabilities available under Windows SharePoint Services 3.0, Office SharePoint Server 2007 Standard edition, and Office SharePoint Server 2007 Enterprise edition. For a complete breakdown of the features of Office SharePoint Server 2007 and Windows SharePoint Services 3.0, please download the product comparison chart (168 KB .xls worksheet). Visit the Windows SharePoint Services 3.0 TechNet site for more information about this versatile technology.CapabilitiesWindows SharePoint Services 3.0Office SharePoint Server 2007 Standard EditionOffice SharePoint Server 2007 Enterprise Edition