SharePoint 2010/2013 Installation and Configuration
The logical result of SharePoint 2013's flexibility and richness can be a high degree of complexity around installing and configuring SharePoint 2013 correctly. A fundamental understanding of the following key structural elements in a SharePoint 2013 environment is required in order to correctly deploy and support SharePoint 2013:
Server farm: The top-level element of a logical architecture design for SharePoint 2013.
Web application: An IIS Web site that is created and used by SharePoint 2013.
Content database: Provides storage Web application content. You can separate content into multiple content databases at the site collection level.
Site collection: A set of Web sites that have the same owner and share administration settings.
Site: One or more related Web pages and other items (such as lists, libraries, and documents) that are hosted inside a site collection.
The physical architecture, which consists of one or more servers and the network infrastructure, enables you to implement the logical architecture for a SharePoint 2013 solution. The physical architecture is typically described in two ways: by its size and by its topology. Size, which can be measured in several ways, such as the number of users or the number of documents, is used to categorize a farm as small, medium, or large. Topology uses the idea of tiers or server groups to define a logical arrangement of farm servers.
Configure different types of service application
In SharePoint 2013, individual services can be configured independently and third-party companies can add services. The services infrastructure gives you control over which services are deployed and how services are shared.
Services that are deployed are named service applications. A service application provides a resource that can be shared across sites throughout a farm, and can be accessed by users through a hosting web application. Service applications are associated to web applications by service application connections. Some services can be shared across farms.
SharePoint 2013 includes a set of service applications that you can use to share services across web applications. In some cases, you can also share service applications across farms. You can manage service applications by using Central Administration or by using Windows PowerShell 3.0.
In SharePoint you can have following Service Application:
Visio Graphics Service
User Profile Service
SharePoint upgrade and migration
Upgrades and migrations are major milestones for companies providing benefits but a source of concerns due to the nature of business critical applications. The SharePoint 2013 Migration Kit was built and tested based on work performed in the enterprise and allows you to leverage our expertise in Microsoft SharePoint 2013 to understand where, when and how to introduce the latest Microsoft collaboration platform within your organization.
SharePoint multi tenant
The traditional and most accurate definition of multi-tenancy remains as a single instance of software that services multiple organizations or clients virtually partitioning its data and configuration allowing those clients to work within a customized application instance. SharePoint Server 2010 delivers new features and capabilities that contribute to supporting true multitenant architectures that are useful not only to hosting providers, but the Enterprise equally.
Office Online (previously Office Web Apps) is an online office suite offered by Microsoft, which allows users to create and edit files using lightweight, web browser-based versions of Microsoft Office applications: Word, Excel, PowerPoint and OneNote. The offering also includes Outlook.com, People, Calendar and OneDrive, all of which are accessible from a unified app switcher. The on-premise version of this service called Office Web Apps Server can be installed in private clouds in conjunction with Microsoft SharePoint, Microsoft Exchange Server and Microsoft Lync Server.
Office Online can open and edit documents, spreadsheets and presentations in Office Open XML formats on the web. Starting on July 2013, they can render PDF documents or convert them to Microsoft Word documents, although the formatting of the document may deviate from the original. Starting on November 2013, the apps support real-time co-authoring and autosave Word files.
SharePoint Backup and Restore
Office SharePoint Server 2007 provides a default backup and restore operation user interface (UI) and command line (stsadm) access for central administrators. SharePoint Backup and Restore provides full server farm backup and restore functionality at the database level and is the recommended recovery solution for small and medium deployments.
SharePoint backup and restore supports full and differential backup and hooks up databases and search index at recovery.
You can back up the following components:
Farm. The entire server farm, including the Configuration database, which contains the collection of Web applications and databases that make up Central Administration.
Windows SharePoint Services Web Application. All Web applications in the farm.
Individual SharePoint Web applications.
Individual content databases for SharePoint Web applications.
Individual Shared Services Providers (SSPs). All the components that are part of the SSP, such as databases and the search application.
SharePoint Search. The Windows SharePoint Search Service, the search application, and the Search database.
SharePoint integration with Exchange Server
The three main Office servers—SharePoint, Exchange, and Lync—deliver terrific value to businesses. On their own, they help you communicate, collaborate, publish, share and manage content. By integrating these three server products, you can solve bigger business problems than any of them solve on their own.
The Office Content Group is now introducing a new type of content guidance, one that directly addresses Office Servers (SharePoint, Exchange and Lync) integration to solve larger business problems.
Exchange Server upgrade and migration
Exchange Server migration can be best described as the process of migrating the user mailboxes from an Exchange based system to another Exchange based system. This process simply moves the mailboxes from the source computer to the target computer while maintaining a copy of the data that is being transferred at the original location as well. Migration can be performed between the Exchange Server mailboxes of same organizations or between different organizations also.
In the present highly competitive world technologies, processes and everyday concepts in different fields are changing at a fast pace. As a result, an organisation has to migrate from an established system if it has to keep on getting desired results. In a way it has become an integral part of growth of any organisation. In many cases the process of migration becomes an ordeal.
Exchange integration with Microsoft Lync
When someone is not available to communicate in real-time, we still have a need to store and forward communications methodology. The real-time communication technologies do not lend themselves to long-term storage and retrieval. By integrating real-time solutions, like Lync Server 2013, and store and forward solutions like Exchange Server 2013 together, it is possible to have the best of both worlds. While Lync Server 2013 provides audio, video, data, application sharing, and desktop sharing for peer-to-peer and multi-party conferences, it lacks some of the features necessary to preserve conversations across all communication modalities. Exchange Server 2013 has an outstanding architecture for the storage and retrieval of information long-term. It also has a highly evolved compliance feature set that can be utilized for compliance policy enforcement and eDiscovery.