Round Robin - Round robin is a local balancing mechanism used by DNS servers to share and distribute network resource loads. You can use it to rotate all resource record (RR) types contained in a query answer if multiple RRs are found. By default, DNS uses round robin to rotate the order of RR data returned in query answers where multiple RRs of the same type exist for a queried DNS domain name. This feature provides a simple method for load balancing client use of Web servers and other frequently queried multihomed computers. If round robin is disabled for a DNS server, the order of the response for these queries is based on a static ordering of RRs in the answer list as they are stored in the zone (either its zone file or Active Directory).
Business Connectivity Services - Microsoft SharePoint Server 2010 and the Microsoft Office 2010 suites include Microsoft Business Connectivity Services, which are a set of services and features that provide a way to connect SharePoint solutions to sources of external data and to define external content types that are based on that external data. External content types resemble content types and allow the presentation of and interaction with external data in SharePoint lists (known as external lists), Web Parts, Microsoft Outlook 2010, Microsoft SharePoint Workspace 2010, and Microsoft Word 2010 clients. External systems that Microsoft Business Connectivity Services can connect to include SQL Server databases, SAP applications, Web services (including Windows Communication Foundation Web services), custom applications, and Web sites based on SharePoint. By using Microsoft Business Connectivity Services, you can design and build solutions that extend SharePoint collaboration capabilities and the Office user experience to include external business data and the processes that are associated with that data.
Microsoft Business Connectivity Services solutions use a set of standardized interfaces to provide access to business data. As a result, developers of solutions do not have to learn programming practices that apply to a specific system or adapter for each external data source. Microsoft Business Connectivity Services also provide the run-time environment in which solutions that include external data are loaded, integrated, and executed in supported Office client applications and on the Web server.
//--------embeded video --------------//
Word Automation Services - http://technet.microsoft.com/en-us/library/ff742315.aspx
Summary: Learn to use Word Automation Services to do server-side document conversions to and from a variety of document formats. By using the Open XML SDK, you can accomplish tasks that are difficult such as updating the table of contents or repaginating documents.
Configure Recycle Bins -
Recycle Bins are used to help users protect and recover data.Microsoft SharePoint Foundation 2010 supports two stages of Recycle Bins: the first-stage Recycle Bin and second-stage Recycle Bin. When a user deletes an item, the item is automatically sent to the first-stage Recycle Bin. By default, when an item is deleted from the first-stage Recycle Bin, the item is sent to the second-stage Recycle Bin. A site collection administrator can restore items from the second-stage Recycle Bin. You turn on and configure Recycle Bins at the Web application level. By default, Recycle Bins are turned on in all the site collections in a Web application. This article describes how to configure Recycle Bin settings for a Web application.
Performance Point Services - http://technet.microsoft.com/en-us/library/ee661741.aspx PerformancePoint Services in Microsoft SharePoint Server 2010 is a performance management service that you can use to monitor and analyze your business. By providing flexible, easy-to-use tools for building dashboards, scorecards, reports, and key performance indicators (KPIs), PerformancePoint Services can help everyone across an organization make informed business decisions that align with companywide objectives and strategy. Scorecards, dashboards, and KPIs help drive accountability. Integrated analytics help employees move quickly from monitoring information to analyzing it and, when appropriate, sharing it throughout the organization.
Prior to the addition of PerformancePoint Services to SharePoint Server 2010, Microsoft Office PerformancePoint Server 2007 functioned as a standalone server. Now PerformancePoint functionality is available as an integrated part of the SharePoint Server Enterprise license, as is the case with Excel Services in Microsoft SharePoint Server 2010. The popular features of earlier versions of PerformancePoint Services are preserved along with numerous enhancements and additional functionality.
Database mirroring is a primarily software solution for increasing database availability. Mirroring is implemented on a per-database basis and works only with databases that use the full recovery model. The simple and bulk-logged recovery models do not support database mirroring. Therefore, all bulk operations are always fully logged. Database mirroring works with any supported database compatibility level.
.gif) Note |
|---|
You cannot mirror the master, msdb, tempdb, or model databases. |
Database mirroring maintains two copies of a single database that must reside on different server instances of SQL Server Database Engine. Typically, these server instances reside on computers in different locations. One server instance serves the database to clients (the principal server). The other instance acts as a hot or warm standby server (the mirror server), depending on the configuration and state of the mirroring session. When a database mirroring session is synchronized, database mirroring provides a hot standby server that supports rapid failover without a loss of data from committed transactions. When the session is not synchronized, the mirror server is typically available as a warm standby server (with possible data loss).
Before you run any process to upgrade from Microsoft Office SharePoint Server 2007 to Microsoft SharePoint Server 2010, you have to determine which upgrade approach to take. Use the information in this article to help compare the pros and cons for each approach and to review information about special cases that might influence your approach. In addition to the information in this article, be sure to read
Review supported and unsupported upgrade paths (SharePoint Server 2010) to understand exactly which upgrade situations are valid and lead to successful upgrades.
Manage Quick Deploy jobs - http://technet.microsoft.com/en-us/library/cc262560.aspx To be able to immediately deploy content (thus not having to wait for the scheduled deployment) you must use a Quick Deploy job.
A Quick Deploy job enables users such as authors and editors to quickly deploy Web pages. For users to use the Quick Deploy feature, the Publishing feature must be enabled for the site collection, and the user must be a member of the Quick Deploy users group.
Before you can run a Quick Deploy job, you must first create a new content deployment path. Content deployment paths specify a source and destination for content deployment and specify other related settings such as authentication information. For information about creating a new content deployment path, see
Manage content deployment paths and jobs.
Site Definitions and Configuration - http://technet.microsoft.com/en-us/library/aa978512.aspx
A site definition defines a unique type of Microsoft SharePoint Foundation website. Several site definitions are built into SharePoint Foundation. A site definition can include more than one site definition configuration. A SharePoint Foundation website is based on particular site definition configuration. For this reason, you can think of a site definition as a family of configurations, although some families contain only one configuration.
The following are the four site definitions whose configurations can be used to create new websites.
STS includes the site definition configurations for, Blank Site, Team Site, and Document Workspace.
MPS includes the site definition configurations for Basic Meeting Workspace, Blank Meeting Workspace, Decision Meeting Workspace, Social Meeting Workspace, and Multipage Meeting Workspace.
BLOG provides a site definition configuration for blogs.
SGS provides a site definition configuration for Group Work Site.
The following site definitions are also built into SharePoint Foundation, but they cannot be used as the basis for new sites.
CENTRALADMIN provides a site definition configuration for central administration websites.
TENANTADMIN provides a site definition configuration to support SharePoint Foundation site hosting features.
WIKI provides a site definition configuration for legacy wiki sites that were originally created in an earlier version of SharePoint Foundation. Because standard site pages on SGS sites are wiki-enabled pages, users do not have to create sites that are specifically for wikis.
GLOBAL provides a basic configuration used for initializing all other site configurations.
Each site definition consists of a combination of files that are placed in the %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\SiteTemplates subfolders of SharePoint Foundation servers during installation of SharePoint Foundation. The XML markup in the site definition files may include references to files in other subfolders of %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE, including .xml, .aspx, .ascx, and .master page files, in addition to document template files (.dot, .htm, and so on), and content files (.gif, .doc, and so on).
Authoritative Web Pages - http://technet.microsoft.com/en-us/library/cc262796.aspx
An administrator of a Search service application can designate a Web page as most authoritative, second-level authoritative, third-level authoritative, or non-authoritative. This setting affects relevance rankings for search results. Therefore, it affects the order in which search results appear in a search results list.
The relevance ranking for a search result is determined in part by how far (in clicks) the result is from a URL that is designated as most authoritative, second-level authoritative, or third-level authoritative. A most-authoritative page contains or links to the most relevant information. A second-level authoritative page receives a penalty click of one. A third-level authoritative URL receives a penalty click of two. URLs designated as non-authoritative are ranked lower than other sites.
Configure the Secure Store - http://technet.microsoft.com/en-us/library/ee806866.aspx
This article describes the Microsoft SharePoint Server 2010 Secure Store Service operations that enable solution designers to create target applications that map user and group credentials to the credentials of external data sources. By using these target applications, external content types in the Business Data Connectivity service will be able to interact with their external data sources to read, write, create, and edit data stored in external data sources. For an overview of the Secure Store Service, see Plan the Secure Store Service (SharePoint Server 2010).
Before using the Secure Store Service to create target applications, you must provide it with a pass phrase. The pass phrase is used to generate a key that is used to encrypt and decrypt the credentials that are stored in the Secure Store Service database. If you have to supply the initial pass phrase, you will see the following message when you open a Secure Store Service application instance: "Please generate a new key for this Secure Store Service application."
Secure Store Service Planning - http://technet.microsoft.com/en-us/library/ee806889.aspx
In Microsoft SharePoint Server 2010, the Secure Store Service replaces the single sign-on (SSO) feature. The Secure Store Service is a claims-aware authorization service that includes a secure database for storing credentials that are associated with application IDs. These application IDs can be used to authorize access to external data sources.
The Secure Store Service is an authorization service that runs on an application server. The Secure Store Service provides a database that is used to store credentials (consisting of a user identity and password) for application IDs that can be used by applications to authorize access to shared resources. For example, SharePoint Server 2010 can use the secure store database to store and retrieve credentials for access to external data sources. The Secure Store Service provides support for storing the credentials of multiple back-end systems using multiple application IDs.
Kerberos - http://technet.microsoft.com/en-us/library/cc263449(office.12).aspx
Kerberos is a secure protocol that supports ticketing authentication. A Kerberos authentication server grants a ticket in response to a client computer authentication request, if the request contains valid user credentials and a valid Service Principal Name (SPN). The client computer then uses the ticket to access network resources. To enable Kerberos authentication, the client and server computers must have a trusted connection to the domain Key Distribution Center (KDC). The KDC distributes shared secret keys to enable encryption. The client and server computers must also be able to access Active Directory directory services. For Active Directory, the forest root domain is the center of Kerberos authentication referrals.
Database Layers - http://blogs.technet.com/b/wbaer/archive/2009/11/30/introduction-to-the-microsoft-sharepoint-sharepoint-2010-database-layer.aspx
Microsoft SharePoint Server 2010 introduces both new databases and databases whose distribution and purpose differs over previous versions of Microsoft SharePoint Products and Technologies. This post details the changes in the Microsoft SharePoint Server 2010 database layer. This section provides information about Shared Service Applications that have a database dependency and is not an exhaustive list of all Shared Service Applications available in Microsoft SharePoint Server 2010. At the time of publication this is not 100% complete.
The Usage and Health Data Collection Service collects and logs SharePoint health indicators and usage metrics for analysis and reporting purposes.
Logging Database
The logging database is the Microsoft SQL Server, MSDE, or WMSDE database that stores health monitoring and usage data temporarily, and can be used for reporting and diagnostics.
Search Service
Administration Database
The Administration Database is what the Shared Services Provider database was in Microsoft Office SharePoint Server 2007 and is instantiated once per Search application aligning with the Administration Component. The Administration Database hosts the Search application configuration and access control list (ACL) for the content crawl.
Property Database
The Property Database stores crawled properties associated with the crawled data to include properties, history data, crawl queues, etc.
Crawl Database
The Crawl Databases host the crawled data and drives crawl - the Crawl Database is what the Search database was in Microsoft Office SharePoint Server 2007.
Web Analytics Service
The Web Analytics Service provides rich analytics giving you insights into your web traffic, search, and SharePoint assets enabling you to better understand your user and deployments. With SharePoint Web Analytics, you’ll be able to tailor the system to meet the needs of your users, optimize how they use and discover information, and create targeted content for your sites.
Staging Database
The Web Analytics Staging database is the working database that stores un-aggregated Fact Data, asset metadata, queued batch data, and provides short term retention of this content.
Reporting Database
The Web Analytics Reporting database stores aggregated standard report tables, Fact Data aggregated by Site Group, date, and asset metadata in addition to diagnostics information.
Configuration Database
The configuration database handles all administration of the deployment, directing requests to the appropriate database, and managing load-balancing for the back-end databases. When a front-end Web server receives a request for a page in a particular site, it checks the configuration database to determine which content database holds the site's data. You can run the configuration database on the same computer as a Web server or on a remote computer running Microsoft SQL Server. The configuration database concepts are relatively unchanged in Microsoft SharePoint Server 2010. In Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 the SiteMap table was stored in the configuration database which provided information about which content database contains data for a given site. When Windows SharePoint Services or Microsoft Office SharePoint Server 2007 received the URL of a request, settings in this database determine which content database contains data for the site. In Microsoft SharePoint Server 2010 and Windows SharePoint Services 4.0 the SiteMap is serialized to disk to improve performance and reduce database callback operations that could result in contention when serving requests on large server farm deployments.
Content Database
The back-end content database stores all site content, including site documents or files in document libraries, list data, and Web Part properties, as well as user names and rights. All the data for a specific site resides in one content database on only one computer.
Central Administration Content Database
See also Content Database.
Shared Services Provider (SSP)
The Shared Services Provider layer is obsolete in Microsoft SharePoint Server 2010 replaced with Shared Services Applications, to understand changes in database design associated with the Shared Services Provider database, see also Search and People in this section.
NOTE
A Microsoft Office SharePoint Server 2007 Shared Services Provider when upgraded will result in a new Search, User Profile, Excel Services, Application Registry Backwards Compatability, and Managed Metadata Service shared services applications. New databases will be created as required to support the upgrade and Web application settings are preserved through establishing a proxy for each service application.
User Profile Service
Profile Database
The user profile database is a flexible database that stores and manages user and associated information. The database allows for a flexible schema that supports multiple data types. It can be queried and it can be updated. For example, a company can define the attributes of an employee record in the profile database. Then for each record, an employee object will be created and saved. This information is now usable in a number of ways, such as in WebParts, in the Web service, or to create rule based groups or roles.
- Properties
- Profiles
- Multiple values
- Vocabularies
- Colleagues
- Memberships
- Change Log
Synchronization Database
The synchronization database is used to store configuration and staging data for synchronization of profile data from external sources such as Active Directory.
Social Tagging Database
The social tagging database stores social tagging records and their respective Url which are coupled with information from the profile and taxonomy databases at the front-end layer at execution/request. This database is used to store social tags and notes created by users.
Managed Metadata Service
The Managed Metadata Service publishes a term store and, optionally, a set of content types.
Term Store Database
A database in which managed metadata is stored. The Web front end public APIs interact with the data layer to get or set data. The data layer talks to the term store directly if the shared service is local to the farm, or it talks to a backend Web service on an application server if the shared service is not local. The backend Web service then interacts with the data layer on the application server to get to the term store.
State Service
The State Service maintains temporary state information for InfoPath Forms Services.
State Database
The state database maintains temporary state information for InfoPath Forms Services.
Business Data Connectivity Service
The Business Database Connectivity Service provides a means for storing, securing, and administering external content types and related objects.
Database
Stores external content types and related objects.
Secure Store Service
The Secure Store Service replaces the Single Sign On Service in previous versions of the product.
This service provides storage and mapping of credentials such as account names and passwords. Portal site–based applications can retrieve information from third-party applications and back-end systems such as Enterprise Resource Planning (ERP) and Customer Relations Management (CRM) systems.
The use of Secure Store functionality enables users to authenticate without asking the user multiple times for the credentials needed to authenticate in that system.
Store Database
Provides storage and mapping of credentials such as account names and passwords.
Crawl Components - http://technet.microsoft.com/en-us/library/ee805950.aspx
In Microsoft SharePoint Server 2010 Search, crawl components process crawls of content sources, propagate the resulting index files to query components, and add information about the location and crawl schedule of content sources to their associated crawl databases. Crawl components are associated with a single Search Service Application. You can distribute the crawl load by adding crawl components to different farm servers.
You can decide which servers in a farm will participate in crawling by creating a crawl component on that server. If you want to balance the load of servicing crawls across multiple farm servers, add crawl components to the farm and associate them with the servers you want to crawl content sources.
Managed metadata service applicaton overview - http://technet.microsoft.com/en-us/library/ee424403.aspx
The managed metadata service application makes it possible to:
- Use managed metadata.
- Share content types across site collections and Web applications.
Managed metadata services
When you enable managed metadata in your SharePoint Server 2010 application, a managed metadata service and connection are created automatically. The service identifies the database to be used as the term store, and the connection provides access to the service. When you create new managed terms, or when users add enterprise keywords, these terms are stored in the database that is specified in the managed metadata service. When you publish a managed metadata service, a URL to the service is created. Before an administrator can create a connection to the service from another Web application, the administrator must know the URL of the service.
In addition to sharing managed metadata, you can also use the managed metadata service to share content types. By creating a new managed metadata service and specifying a site collection as the content type hub, you can share all content types in the site collection’s content type gallery.
You can create multiple managed metadata services, and share multiple term stores and content types from multiple site collections. However, each managed metadata service must specify a different term store. When you specify a nonexistent database for the term store, a new database is created.
TCP Port 443 = default port for SSL (Secured Sockets Layer)
By Default, SQL Server uses port 1433 for database access
Developer Dashborad - PowerShell script - see blog.
Configure incoming email - http://technet.microsoft.com/en-us/library/cc262947.aspx & http://technet.microsoft.com/en-us/library/cc263260.aspx
See: This article describes how to configure incoming e-mail for a server farm for Microsoft SharePoint Server 2010. This article also describes how to install and configure the SMTP service that you must use to enable incoming e-mail.
Enable and congiure email for lists and libraries -
http://office.microsoft.com/en-us/sharepoint-server-help/enable-and-configure-e-mail-support-for-a-list-or-library-HA010082307.aspx
Import Wizard for Performance Point Server 2007 to 2010 - http://technet.microsoft.com/en-us/library/ee681485.aspx
To import dashboard content from Microsoft Office PerformancePoint Server 2007 into PerformancePoint Services in Microsoft SharePoint Server 2010, an import wizard has been provided to facilitate and simplify the process. There are subtle yet significant changes in working with PerformancePoint Services over PerformancePoint Server 2007. In Microsoft SharePoint Server 2010, the PerformancePoint content is stored in SharePoint lists and document libraries. For additional information on planning your import, see Plan for importing PerformancePoint Server 2007 dashboard content to SharePoint Server 2010 (SharePoint Server 2010).
Manage Crawl Rules - http://technet.microsoft.com/en-us/library/ee792871.aspx
You can add a crawl rule to include or exclude specific paths when you crawl content. When you include a path, you can optionally provide alternative account credentials to crawl it. In addition to creating or edit crawl rules, you can test, delete, or reorder existing crawl rules.
Determine upgrade approach - http://technet.microsoft.com/en-us/library/cc263447.aspx
Before you run any process to upgrade from Microsoft Office SharePoint Server 2007 to Microsoft SharePoint Server 2010, you have to determine which upgrade approach to take. Use the information in this article to help compare the pros and cons for each approach and to review information about special cases that might influence your approach. In addition to the information in this article, be sure to read Review supported and unsupported upgrade paths (SharePoint Server 2010) to understand exactly which upgrade situations are valid and lead to successful upgrades.
Attach Database and upgrade to SharePoint Server 2010 - http://technet.microsoft.com/en-us/library/cc263299.aspx
When you upgrade from Microsoft Office SharePoint Server 2007 to Microsoft SharePoint Server 2010 by using the database attach upgrade approach, you upgrade only the content for your environment and not the configuration settings. Using a database attach upgrade approach is useful when you are changing hardware or want to reconfigure your server farm topology as part of the upgrade process. For more information about how to choose an upgrade approach, see Determine upgrade approach (SharePoint Server 2010).
After you set up the new environment, you can use the procedures in this article to detach and then reconnect the databases to perform the actual upgrade. This article contains the steps required to perform a standard database attach upgrade and a database attach upgrade with read-only databases.
SharePoint sites exposed on the Internet should be secured of SSL, Active Directory Certificate Services (AD CS) should be used.
System Center Operations Manager -
What is a extranet? - An "intranet" is the generic term for a collection of private computer networks within an organization. An "extranet" is a computer network that allows controlled access from the outside for specific business or educational purposes. Intranets and extranets are communication tools designed to enable easy information sharing within workgroups.
All about SharePoint Site Collections - http://technet.microsoft.com/en-us/library/cc742548.aspx
A SharePoint site collection is a hierarchical set of sites that can be managed together. Sites within a site collection have common features, such as shared permissions, galleries for templates, content types, and Web Parts, and they often share a common navigation. A site collection contains a single top-level site, and any number of subsites organized in a hierarchy. A subsite is a single SharePoint site within a site collection. A subsite can inherit permissions and navigation structure from its parent site, or these can be specified and managed independently. Creation of subsites can be delegated to users of a site collection, but creation of site collections must be performed by a service administrator.
There are times when it is appropriate to create an entire site collection, and there are times when it makes more sense to create a single subsite. For instance, if you have many projects that fit within a larger context, it makes sense to create a single site collection for that context, and create subsites to manage each project. For example, an engineering department might have one site collection and use that site collection to house multiple subsites, one per engineering project. If you have projects that need to be isolated from each other, you should create separate site collections for them. For example, it might make sense for the engineering department to have a separate site collection from the legal department.
The information in the following table can help you decide whether to create a site collection or a single subsite.
Table: Site Collections vs. Subsites
| Create a site collection to support |
Create a subsite to support |
|---|
A security boundary (significantly different permissions and roles) between your sites and other sites |
Shared navigation between sites |
Delegation of site administration to someone different from the administrator of existing site collections |
Inherited permissions from parent sites (parent sites are the higher-level sites that subsites are created within) |
Search features or workflows that are scoped differently from existing site collections |
Shared lists between sites |
A size quota different from that of existing site collections |
Shared design elements, such as themes or styles, between sites |
Site collection features that are not active on other site collections (for example, the Publishing Infrastructure feature) |
Backup and revovery planning - http://technet.microsoft.com/en-us/library/cc261687.aspx
This article describes the stages involved in planning for backup and recovery, which include determining backup and recovery strategies for a Microsoft SharePoint Server environment and deciding which tools to use. The stages do not need to be done in the order listed, and the process may be iterative.
When you plan for how you will use backup and recovery for disaster recovery, consider common events, failures, and errors; local emergencies; and regional emergencies.
Sandbox Solutions Administration - http://technet.microsoft.com/en-us/library/ee704542.aspx
A sandbox is a restricted execution environment that enables programs to access only certain resources and that keeps problems that occur in the sandbox from affecting the rest of the server environment. Solutions that you deploy into a sandbox, which are known as sandboxed solutions, cannot use certain computer and network resources and cannot access content outside the site collection they are deployed in.
Hardware and software requirements - http://technet.microsoft.com/en-us/library/cc262485.aspx
This article lists the minimum hardware and software requirements to install and run Microsoft SharePoint Server 2010.
Microsoft SharePoint Server 2010 provides for a number of installation scenarios. Currently, these installations include single server with built-in database installations and single-server or multiple-server farm installations.