A team of SharePoint authorities addresses the six most essential areas of SharePoint Six-in-One () cover image Excerpt 1: (PDF). 6. Module 2: SharePoint Introduction. Choosing SharePoint has become a no-brainer. .. An example would be Adobe PDF files. phone, SharePoint Server offers an intuitive and familiar user six major areas to explore: Figure 1. Capability areas of SharePoint.
|Language:||English, Spanish, Dutch|
|Genre:||Business & Career|
|Distribution:||Free* [*Register to download]|
of America. 10 9 8 7 6 5 4 3 2 1 Microsoft SharePoint Server is a product that takes advantage of the best of the Documents, such as PDF files. Contents at a Glance. 8. 7. 6. 5. 4. 3. 2. 1. Chapter 1 Exploring SharePoint Microsoft SharePoint QuickSteps is aimed at new or inexperienced. 1. Site and solution governance. (SharePoint Server ). Published: May 12, . 6. Additionally, the set of governance policies your IT and business divisions implement SharePoint Governance Planning (PDF version).
Most of the source code used in this book is available for download at www. Code that is included on the website is highlighted by the following icon: Listings include a description and in some cases the fi lename in the title. Once you download the code, just decompress it with your favorite compression tool. Alternatively, you can go to the main Wrox code download page at www. However, no one is perfect, and mistakes do occur.
If you fi nd an error in one of our books, like a spelling mistake or faulty piece of code, we would be very grateful for your feedback. By sending in errata, you may save another reader hours of frustration, and at the same time, you will be helping us provide even higher quality information. To fi nd the errata page for this book, go to www. Then, on the book details page, click the Book Errata link. On this page, you can view all errata that has been submitted for this book and posted by Wrox editors.
The forums are a Web-based system for you to post messages relating to Wrox books and related technologies and interact with other readers and technology users. The forums offer a subscription feature to e-mail you topics of interest of your choosing when new posts are made to the forums. When your organization uses Office client applications together with SharePoint Server, policies are enforced both on the server and in the client applications.
This is done transparently; policy features that apply to a document are described in a policy statement that is associated with the document, and policy-aware applications prevent users from doing tasks that violate the document's policy. Associate policy features with a Site Collection policy and then associate that policy with a content type or with a list or library. The top-level site of a site collection includes a Site Collection Policies gallery where administrators of the top-level site can create new policies.
After creating a Site Collection policy, you can export it so that administrators of other site collections can import it into their Site Collection Policies galleries. This lets you standardize policies across your organization. When a Site Collection policy is associated with a content type and that content type is associated with a list or library, the owner of the list or library cannot modify the Site Collection policy in the list or library.
This ensures that policies that are assigned to a content type are enforced at each level of the site hierarchy.
Associate a set of policy features directly with a content type, and then add that content type to one or more lists or libraries. To ensure that a policy that is created by using this method will be used in the whole site collection, associate it with a content type in the Site Content Type gallery of the top-level site collection.
Then every item of that content type in the site collection, and every item of a content type that inherits from the original content type, will have the policy. When you use this method of associating a policy with a content type, it is harder to reuse the policy in other site collections, because policies created by using this method cannot be exported.
To more tightly control which policies are being used in a site collection, site collection administrators can disable the ability to set policy features directly on a content type. When setting policy features on a content type is restricted, content type designers can only associate policies from the Site Collection Policies gallery with content types. Associate a set of policy features directly with a list or library. You can only use this method if the list or library does not support multiple content types.
This method of creating a policy is only useful for a narrowly defined policy that applies to a single list or library. To more tightly control which policies are being used in a site collection, site collection administrators can disable the ability to set policy features directly on a library. When setting policy features on a library is restricted, content type designers can only associate policies from the Site Collection Policies gallery with libraries.
SharePoint Server information management policies are exposed in Office client applications. When you configure an information management policy on the server, you can write a policy statement that informs information workers about the policies that are enforced on documents. For example, the policy statement might indicate that a document will be deleted after a certain time or that it contains sensitive information that should not be communicated outside the company.
The statement might even provide a contact name if the information worker needs more information about the policy. The first step is to make notes of all your web app settings.
In most cases, there won't be many, and you'll be familiar with any changes that you made. Then, detach the content databases from your web app. Keep them safe; you're going to need them.
Next, make a copy of the web. Finally, go into Central Administration and delete the web app. Tell SharePoint to delete the extra stuff. The scary part is over.
Now, recreate the web app, but do it right this time. Do your end users a favor, and put the web app on port 80, as Figure 1 shows. You can change those settings later, and you want to make sure that the web app works correctly before you apply fancy security settings.
Doing so helps in any troubleshooting that you might need to do. Under the Application Pool settings, pick an existing application pool. I'll explain why in the next section. Figure 1: Creating a new web app It is important to give your content databases distinct names.
You should be able to look at a content database name and know exactly which web app that database goes with. This is another one of those things that doesn't usually seem important but is priceless in a disaster-recovery situation.
If the content databases that you detached from the web app before you deleted it didn't have such names, then take this opportunity to right that wrong when you recreate the web app.
Give the new content database a good name, then use the PowerShell cmdlet Move-SPSite to move the site collections to that new database. If your content database already has a good name, enter it during the creation of the new web app.
If you had multiple content databases, attach the rest after the web app is created. After the web app is created, you can tweak settings as needed.
Most settings can be changed in Central Administration. If you made any changes to the web. You should now have a well-created web application that you can trust in times of crisis.
Unless you have reason to do otherwise, you should run all SharePoint web apps inside one application pool; the same goes for the service applications.
Running each web app in its own application pool makes inefficient use of the server's memory. Each application pool has a minimum overhead of more than MB, and its memory footprint increases as it caches content that's rendered frequently.
Figure 2 shows multiple W3WP. We've all experienced SharePoint slowing first thing in the morning because the app pools recycle overnight and need to warm up and cache that content again. Well, multiple application pools mean that the same content is cached multiple times. Most users are impatient. I'm sure that studies would show that they spend the time waiting for SharePoint to respond by thinking of ways to punish us for SharePoint's poor performance.
Figure 2: Result of running web apps in separate application pools For service applications, this problem is easy to fix.
First, make sure that you have a good service application pool to use. I recommend calling this pool Default SharePoint Service App Pool so that it floats to the top of all your drop-down lists.
Most service applications allow you to assign them to a new service application pool by modifying their properties in Central Administration. If the option is unavailable there, look for it in PowerShell. Web applications are a tougher matter. There's no easy, out-of-the-box way to change the application pool that a web app is using.