There are three storage mechanisms SharePoint Workspace uses to store data on your local computer. Lists, InfoPath forms, schema, and views are stored in SharePoint Workspace itself, BCS data has its own storage mechanism, and your SharePoint documents are stored in a common Office file store called the Office Document Cache (ODC). The diagram below shows the relationships between the three data stores and the content sources for each.
SharePoint Workspace, along with other Office 2010 products, uses the Office Document Cache (ODC) for file storage. Files are downloaded and synchronized using a protocol called File Sync via SOAP over HTTP (FSSHTTP). SharePoint Workspace’s use of the ODC and FSSHTTP has many advantages for XML-based Office documents, including:
· Reduced network load
· Faster saves
· Conflict resolution
· Coauthoring
After initial sync, only document changes are sent between SharePoint and SPW. This reduces bandwidth consumption and server load, while giving the user a more responsive save experience, even when working with very large files.
When you’re offline and working with SharePoint documents, other users may be editing the same document, putting it in conflict when you try to sync your changes. SharePoint Workspace and the ODC handle many of these changes automatically for you, by seamlessly integrating your changes with the updated document on the server. When you get back online, your changes will be merged with the new server copy and any changes on the server will appear highlighted green.
Coauthoring allows multiple users to edit the same document at the same time collaboratively. You will be notified when you open a document someone else is editing, along with easy access to their contact information.
When the other user makes changes to a section of a document, that section will become locked, shown below. Once the user has completed making changes you will be notified and the new changes can be merged into your work.
We’re actively working on increasing capacity limits to optimize throughput, but for now synching a large number of documents can degrade performance. SharePoint Workspace will first warn you when the number that you’re scheduled to synchronize gets high, and then it will actually change its behavior when the number gets higher still.
If you are syncing 500 or more documents, SPW will give you a warning, which also serves as a heads-up to suggest that you should expect gradually slower performance as the number of documents gets larger.
When you’re about to synch 1800 documents or more, SharePoint Workspace will change its behavior to make sure that you get your documents in a timely fashion. It will synchronize only headers (metadata about the document) at this point, and will synchronize actual documents only on demand. When you actually need one or more documents, you can click on them, and SPW will sync them for you on the spot.
There are several ways to reduce the number of documents you have offline, such as deleting unused SharePoint workspaces, disconnecting from unused document libraries, or discarding local copies of documents.
Note that these limitations apply to the ODC only and do not apply to Groove workspaces.
Andrew Harris and Jim McCoy
If you are playing with enterprise features of Sharepoint 2010 you have probably noticed that Site Directory template is missing. Site directory has been intentionally hidden because of compatibility issues with upgrade process between 2007 and 2010.
If you want to "enable it" simply follow these steps.
After that go to your site URL and create new site and you'll see "Site Directory"
This download contains a two Windows Server 2008 R2 Hyper-V Virtual Machine set for evaluating and demonstrating Office 2010, SharePoint 2010 and Project Server 2010.
Virtual machine “a” contains the following pre-configured software:
This paper shows how two products, Microsoft Office and Microsoft SharePoint, contribute to the powerful architectural design of the Microsoft Business Productivity Infrastructure (BPI). The BPI stack approach suggests that only by thinking at a capability level (for example, ¡°What do users want to do?¡¬), and then adding the right aspects of capability in each place (client, server, and services), can we create desktop applications that also deliver rich server and services capabilities to information workers.
When you create or customize SharePoint solutions, it is usually best to develop the solution on a local computer where Microsoft SharePoint Server 2010 or Microsoft SharePoint Foundation 2010 is installed. This article describes how to install a development environment with Microsoft SharePoint 2010 and Microsoft Visual Studio 2010. The development environment that you create by using these instructions will not support SharePoint farm installations, and you should not host active production sites with this configuration. These instructions will enable you to get started with an environment that is specifically suited to developing SharePoint custom solutions.
Quote
Clean Up Those SharePoint Logs! To help keep my SharePoint log files under control I have created a simple PowerShell script that automatically deletes files from a directory and all subdirectories that are over a set number of days old. Once the log files are cleaned up the script will then delete any left over empty subdirectories. You can download this script and use it as is or modify it for your specific needs. I would recommend modifying the $Days and the $TargetFolder variables in the script to match your specific needs and environment. The $Days indicates how many days of logs should be kept. I have this set at 5. I figure that if my SharePoint environment starts having issues I will most likely only care about the most recent days events. The $TargetFolder should be set to the SharePoint log folder. Note: Although I have tested this on several environments I will not be responsible for any damages or loss that you may experience. In other words: Use at your own risk. To run the script you will need to set the execution policy to unrestricted by typing Set-ExecutionPolicy unrestricted at your PowerShell command prompt. Before doing this please take a moment to review the effects of this command and understand any additional security risks it may create.
To help keep my SharePoint log files under control I have created a simple PowerShell script that automatically deletes files from a directory and all subdirectories that are over a set number of days old. Once the log files are cleaned up the script will then delete any left over empty subdirectories.
You can download this script and use it as is or modify it for your specific needs. I would recommend modifying the $Days and the $TargetFolder variables in the script to match your specific needs and environment. The $Days indicates how many days of logs should be kept. I have this set at 5. I figure that if my SharePoint environment starts having issues I will most likely only care about the most recent days events. The $TargetFolder should be set to the SharePoint log folder.
Note: Although I have tested this on several environments I will not be responsible for any damages or loss that you may experience. In other words: Use at your own risk. To run the script you will need to set the execution policy to unrestricted by typing Set-ExecutionPolicy unrestricted at your PowerShell command prompt. Before doing this please take a moment to review the effects of this command and understand any additional security risks it may create.
Published the week of April 12, 2010
Availability configuration (SharePoint Server 2010) The articles in this section describe how to configure availability for Microsoft SharePoint Server 2010. They include descriptions of how to use Microsoft SQL Server clustering and SQL Server database mirroring.
Copy configuration settings from one farm to another (SharePoint Server 2010) This article describes how to copy configuration settings from one SharePoint Server 2010 farm to another SharePoint Server 2010 farm.
Plan for availability (SharePoint Server 2010) This article describes key decisions in choosing availability strategies for a SharePoint Server 2010 environment.
Plan for disaster recovery (SharePoint Server 2010) This article describes key decisions in choosing disaster recovery strategies for a SharePoint Server 2010 environment.
Virtualization planning (SharePoint Server 2010) This section contains the following new articles designed to help you plan and implement a server virtualization solution for SharePoint Server 2010 server farms:
Performance and capacity management This section contains the following new articles related to capacity management for SharePoint Server 2010:
Deploy by using DBA-created databases (SharePoint Server 2010) This article describes the steps that are required to deploy SharePoint Server 2010 in an environment where a DBA has to create all the farm databases. Windows PowerShell commands are also provided as examples.
IP support (SharePoint Server 2010) This article describes SharePoint Server 2010 support for IP version 4 (IPv4) and IP version 6 (IPv6).
Plan to share terminology and content types (SharePoint Server 2010) This article contains procedures for identifying the managed metadata services and connections that your solution requires.
Privacy and security implications of social tagging (SharePoint Server 2010) Social tagging helps people communicate and share information, which by definition can affect privacy (if personal information is shared) and security (if confidential information is shared). This article describes the features of SharePoint Server 2010 that you can use to manage the effects of social tagging on privacy and security.
Plan Web content management (SharePoint Server 2010) This section has been updated with new articles that help IT pros plan publishing sites that use SharePoint Server 2010 features. They include:
Database types and descriptions (SharePoint Server 2010) This article describes the databases that are installed for SharePoint Server 2010. It also includes some sizing and placement information.
Storage and SQL Server capacity planning and configuration (SharePoint Server 2010) This article describes how to plan for and configure the storage and SQL Server database tier in a SharePoint Server 2010 environment.
Monitor health and performance of a virtual environment (SharePoint Server 2010) This article describes the monitoring required for Hyper-V virtualization servers and SharePoint Server 2010 virtual machines in a virtual environment.
Configure proxy server settings for search (SharePoint Server 2010) This article describes how to configure proxy settings for use with SharePoint Server 2010 search.
Deploy customizations - overview (SharePoint Server 2010) The articles in this section describe how to deploy site elements that have been customized by developers or Web designers in a SharePoint Server 2010 environment.
Upgrading to SharePoint Server 2010 This section contains new and updated articles to match the release version of the software.
Virtual machine guidance (SharePoint Server 2010) This article describes the available configuration options for virtual machines and guidance for specific configurations when a virtual machine is used in a SharePoint Server 2010 farm.
Add a Web or application server to the farm (SharePoint Server 2010) This article describes the steps required to add a new Web server or application server to an existing farm by using the user interface (UI) or the command line.
Add a database server to an existing farm (SharePoint Server 2010) This article describes the steps required to add a new database server to an existing farm by using the UI or the command line.
Plan for multilingual sites (SharePoint Server 2010) This article describes how to plan multilingual sites for SharePoint Server 2010.
Languages for word breakers and stemmers (SharePoint Server 2010) This article lists the languages for which SharePoint Server 2010 provides word breakers and stemmers.
Use the variationsfixuptool operation (SharePoint Server 2010) This article explains how to use the Stsadm variationsfixuptool operation for SharePoint Server 2010.
Database management (SharePoint Server 2010) This section describes techniques for managing the databases that are associated with SharePoint Server 2010.
Attach or detach content databases (SharePoint Server 2010) This article describes how to attach or detach SharePoint Server 2010 content databases by using Central Administration or Windows PowerShell.
Remove a server from the farm (SharePoint Server 2010) This article describes how to remove a database server, a Web server, or an application server from a SharePoint Server 2010 server farm.
Share service applications across farms (SharePoint Server 2010) In SharePoint Server 2010, some service applications can be shared across server farms. This article describes the process and caveats that are involved in sharing service applications.
Rename a stand-alone server (SharePoint Server 2010) This article describes how to rename a stand-alone server in SharePoint Server 2010.
Configure settings for a Web application (SharePoint Server 2010) This article describes the general settings that you can configure for a Web application and introduces other articles that describe additional Web application settings.
Define managed paths (SharePoint Server 2010) By defining managed paths, you can specify which paths in the URL namespace of a Web application are used for site collections. This article describes how to define managed paths.
Turn on or turn off self-service site creation (SharePoint Server 2010) The self-service site creation feature in SharePoint Server 2010 allows users who have the Use Self-Service Site Creation permission to create sites in defined URL namespaces. This article describes how to turn on or turn off this feature.
Deployment scenarios (SharePoint Server 2010) This section describes how to deploy SharePoint Server 2010 on one or more servers to create different topologies that you can use for testing and implementing SharePoint Server 2010 solutions at different stages of the deployment life cycle. This section includes the following updated articles:
Hardware and software requirements (SharePoint Server 2010) This article describes the hardware and software requirements that you must meet to successfully install SharePoint Server 2010.
Plan browser support (SharePoint Server 2010) This article describes levels of support for Web browsers to use with SharePoint Server 2010.
Configure a mobile account (SharePoint Server 2010) This article discusses how to configure and manage a mobile account for SharePoint Server 2010 to enable users to subscribe to alerts that are sent by using SMS.
How to Create a Document Set in SharePoint 2010 (Beta) With all this talk about the new ECM and Document Management features in SharePoint 2010 I thought I would start with one and dig a little deeper into it. One thing I always thought SharePoint Server 2007 lacked was the ability to have a set of documents with the same metadata and the ability to treat them as one document especially for workflow. Of course you could always zip up documents and call them “Sets”, but this meant you had to download the zipped file and see what was in it. It really lacked and having to work with all or none was what you have in zip files. With Document Sets you can take action against the entire set or individual files while keeping them part of the set. You may have some new hire documents that can all be part of the same set with the same metadata and yet treat each document separately so you can have a workflow run on each file after filling it out for example. The ideas are endless when it comes to Document Sets. So, I decided to put this post together because for something as easy as creating a Document Set in SharePoint 2010 it was actually pretty annoying to get going and really play with. Here are the steps to create a Document Set in 2010. This is done with the beta so this can always be different when the RTM comes out. i doubt it, but I thought I would warn you. 1. You need to enable the Document Sets feature at the Site Collection level. Now that we have this figured out we can easily go create a document set. A Document Set is actually just a content type. This is important to know when planning out site collections because, as we know, we can add a content type to any library in the site collection now. So, what that means, is a Document Sets can only be created within a document library that is using this content type. We may have enabled Document Sets across the site collection, but really all we did is allow the use of the content type and pages that go with the set. 2. Just like in SharePoint Server 2007, we need to allow the management of content types. Choose the document library you would like to be able to create document sets in and click library settings on the ribbon Then click Advanced Settings and allow the management of content types. Then click save 3. Create a Document Set just as you would use a content type. Go to New and choose Document Set. For whatever reason the icon seems to be missing in the beta. 4. Create a name and description for your Document Set. You might get an error if you try to add any managed metadata and this is not active in your site 5. You add documents to your document set by choosing the Library Tools > Documents and upload multiple documents. Yes you can have only one document in a set if you need to add more later. 6. Drag your files you want uploaded. 7. That is it. You now can manage your documents in a set. You can see your set within your library even when you have other documents in that library that are not in a set. Now we can treat this Document Set as a single file or multiple files. We can delete the set and thus delete all the documents. Really we can act like it is a zip file with the ability to manage the documents within it. The documents that are part of a set are indexed individually unlike zip files so search is much better when it comes to Document Sets. Everyone will have their own reasons for creating Document Sets and I am sure you can think of a few now. My favorite part of sets is being able to run workflow on a set of documents. Now an approval workflow can be based on an entire set of documents rather than one document.
With all this talk about the new ECM and Document Management features in SharePoint 2010 I thought I would start with one and dig a little deeper into it. One thing I always thought SharePoint Server 2007 lacked was the ability to have a set of documents with the same metadata and the ability to treat them as one document especially for workflow. Of course you could always zip up documents and call them “Sets”, but this meant you had to download the zipped file and see what was in it. It really lacked and having to work with all or none was what you have in zip files. With Document Sets you can take action against the entire set or individual files while keeping them part of the set. You may have some new hire documents that can all be part of the same set with the same metadata and yet treat each document separately so you can have a workflow run on each file after filling it out for example. The ideas are endless when it comes to Document Sets.
So, I decided to put this post together because for something as easy as creating a Document Set in SharePoint 2010 it was actually pretty annoying to get going and really play with.
Here are the steps to create a Document Set in 2010. This is done with the beta so this can always be different when the RTM comes out. i doubt it, but I thought I would warn you.
1. You need to enable the Document Sets feature at the Site Collection level.
Now that we have this figured out we can easily go create a document set.
A Document Set is actually just a content type. This is important to know when planning out site collections because, as we know, we can add a content type to any library in the site collection now. So, what that means, is a Document Sets can only be created within a document library that is using this content type. We may have enabled Document Sets across the site collection, but really all we did is allow the use of the content type and pages that go with the set.
2. Just like in SharePoint Server 2007, we need to allow the management of content types.
Choose the document library you would like to be able to create document sets in and click library settings on the ribbon
Then click Advanced Settings and allow the management of content types. Then click save
3. Create a Document Set just as you would use a content type. Go to New and choose Document Set. For whatever reason the icon seems to be missing in the beta.
4. Create a name and description for your Document Set. You might get an error if you try to add any managed metadata and this is not active in your site
5. You add documents to your document set by choosing the Library Tools > Documents and upload multiple documents. Yes you can have only one document in a set if you need to add more later.
6. Drag your files you want uploaded.
7. That is it. You now can manage your documents in a set. You can see your set within your library even when you have other documents in that library that are not in a set.
Now we can treat this Document Set as a single file or multiple files. We can delete the set and thus delete all the documents. Really we can act like it is a zip file with the ability to manage the documents within it. The documents that are part of a set are indexed individually unlike zip files so search is much better when it comes to Document Sets. Everyone will have their own reasons for creating Document Sets and I am sure you can think of a few now.
My favorite part of sets is being able to run workflow on a set of documents. Now an approval workflow can be based on an entire set of documents rather than one document.
Today we reached an exciting engineering milestone- the release-to-manufacturing (RTM) for Office 2010, SharePoint 2010, Visio 2010 and Project 2010!
RTM is the final engineering milestone and a major achievement for all of the internal teams who worked so hard to get to this point. As tirelessly as our engineering teams worked, we would never have reached this milestone without incredibly active participation from our customers and partners. More than 5,000 organizations and partners have worked with us on rapid deployment and testing of the products, and the feedback that we’ve received from all these programs has shaped a fantastic set of products that I’m sure our customers will love.
Our Volume License customers with active Software Assurance (SA) on these products will be one of the first to receive the 2010 set of products. They will be able to download the product in English, French, Spanish, German, Russian, and Dutch via the Volume Licensing Service Center starting April 27. Other languages will be available on a rolling timeline. Customers without SA will be able to purchase the new products through Volume Licensing from Microsoft partners starting May 1.
Earlier this year we announced that we will officially launch SharePoint 2010 to our business customers on May 12 with a virtual launch. Our virtual launch will allow people from around the globe to participate in our launch by going to http://www.the2010event.com. Stephen Elop, President of Microsoft’s Business Division, will deliver a keynote as part of the virtual launch, and the virtual launch site will showcase product demos, customer and partner testimonials, and interviews with product managers and executives, and we hope this will give you another great way to explore, learn, and get excited about the 2010 releases.
On behalf of the SharePoint team, I want to thank all of the customers and partners who have helped us reach this milestone. We look forward to continue learning from you and all the great things you will do with our products!
-Jeff Teper
Corporate Vice President, SharePoint Server, Microsoft
How will SharePoint 2010 impact your job as a SharePoint administrator? In this new Quest white paper, learn about nine key features that will make your life easier! Read it today.