Category: Uncategorized

Internet Explorer 10 Guide for Developers

Posted on by escapebusinesssolutions in Uncategorized

Purpose

The Internet Explorer 10 Guide for Developers provides a look at the developer features included in Internet Explorer 10, as well as the latest HTML5, JavaScript, and Cascading Style Sheets, Level 3 (CSS3) features available to developers of Windows Store apps using JavaScript for Windows 8. By using the documentation and samples in this guide, developers and designers can take full advantage of these new features.

Important   The contents of this guide apply to both Internet Explorer 10 and Windows Store apps using JavaScript for Windows 8, except where noted.

Internet Explorer 10 is available for Windows 8 and Windows Server 2012. Internet Explorer 10 is available as a Release Preview for Windows 7 and Windows Server 2008 R2. For more information about the differences between Internet Explorer 10 for Windows 7 and Internet Explorer 10 for Windows 8, see Internet Explorer 10 on Windows 7.

Listed here are new developer features for Internet Explorer 10. In addition to reading the guide, be sure to see the Release Notes for installation information and known issues, as well as the Internet Explorer Test Drive site for new demos and examples. Download samples and documentation from the Internet Explorer Developer Samples Gallery. You can also obtain detailed technical information about developer features by visiting the Internet Explorer Developer Center and the MSDN Library.

Internet Explorer 10—as well as Windows Store apps using JavaScript—contains support for the following developer features. Except where noted, these features work identically in Internet Explorer 10 and Windows Store apps using JavaScript.

Developer audience

Internet Explorer 10 Guide for Developers is written for use by Web developers and designers, plus those interested in developing for Windows Store apps using JavaScript in Windows 8, to learn about the developer features in Internet Explorer 10.

 
 

 
 

Build date: 11/30/2012

Managing Windows Phones for Hosted Exchange

Posted on by escapebusinesssolutions in Uncategorized

 

 

Connectivity and synchronization may require separately purchased equipment and/or wireless products (for example, Wi-Fi card, network software, server hardware, and/or redirector software). Service plans are required for Internet, Wi-Fi and phone access. Features and performance may vary by service provider and are subject to network limitations. See device manufacturer, service provider and/or corporate IT department for details.

Available programs, features and functionality vary by device and Windows Mobile operating system version. PowerPoint Mobile available with Windows Mobile 5.0.

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This white paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in, or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2009 Microsoft Corporation. All rights reserved.

The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred.

Microsoft, ActiveSync, Internet Explorer, Outlook, SharePoint, Visual Studio, Windows, Windows Mobile, Windows PowerShell, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Table of Contents

Introduction to Windows Mobile Policy Management in the Hosted Exchange Environment .. 1

Management Summary ………………………………………………………………………………………… 1

Overview ……………………………………………………………………………………………………………. 2

Objectives ………………………………………………………………………………………………………….. 2

Target Audience ………………………………………………………………………………………………….. 2

Using Exchange Server to Manage ActiveSync Policies ……………………………………………….. 3

Exchange Server 2007 ActiveSync Policies …………………………………………………………….. 3

Provisioning the Policies at Exchange Server 2007 ………………………………………………….. 5

Windows Phone Provisioning …………………………………………………………………………………… 14

Phone Provisioning Options ………………………………………………………………………………… 14

CAB/CPF File ……………………………………………………………………………………………….. 14

Exchange ActiveSync …………………………………………………………………………………….. 15

Cold Boot Initialization ……………………………………………………………………………………. 15

Web-based Using HTTP over IP ……………………………………………………………………… 15

SMS Initiated ………………………………………………………………………………………………… 15

USB/Bluetooth ………………………………………………………………………………………………. 15

OMA/DM ………………………………………………………………………………………………………. 15

Configuration Service Providers …………………………………………………………………………… 15

Provisioning Exchange ActiveSync Settings ………………………………………………………….. 17

Auto Discover Feature ……………………………………………………………………………………. 17

XML Provisioning File …………………………………………………………………………………….. 23

Windows Phone Provisioning Web Site …………………………………………………………………….. 24

Overview ………………………………………………………………………………………………………….. 24

Setting Up the Provisioning Web Site …………………………………………………………………… 24

Using the Provisioning Web Site ………………………………………………………………………….. 25

Scenarios ……………………………………………………………………………………………………………… 27

Provisioning a Single User ………………………………………………………………………………….. 27

Provisioning Multiple Users in Bulk ………………………………………………………………………. 27

Appendices …………………………………………………………………………………………………………… 28

Appendix A: How to Create CAB Files for Configuration Settings………………………………….. 29

Appendix B: How to Create Signing Certificates …………………………………………………………. 30

Appendix C: How to Distribute Signing Certificates …………………………………………………….. 32

Appendix D: How to Digitally Sign CAB Files and Contents………………………………………….. 33

Appendix E: Sync CSP for Provisioning EAS……………………………………………………………… 34

Appendix F: How to Enroll for Sending Out Text SMS Messages ………………………………….. 35

Appendix G: Windows Mobile Security Model…………………………………………………………….. 36

Appendix H: Frequently Asked Questions …………………………………………………………………. 39 1

Introduction to Windows Mobile Policy Management in the Hosted Exchange Environment

Management Summary

The current version of the Microsoft® Windows® phone has numerous IT security policies that may be applied and enforced. The policies can be easily managed in the hosted Microsoft Exchange environment.

An additional security requirement is that the initial provisioning of Windows phones in the field must allow the phone to connect seamlessly to the hosted Exchange server. Windows phones have several options for customization of various settings. For example, settings are required for connection to an Exchange server in order to synchronize e-mail messages to the device. The settings may be set locally at the device or remotely Over the Air (OTA).

There is a business need for providing information and tools to facilitate the following objectives:

 Enabling the Hosted Messaging and Collaboration (HMC) or the hosted Exchange environment to manage IT security policies.

 Enabling users to provision Windows phones to connect to Exchange.

 

This white paper provides the information on the process and tools to meet the preceding objectives.

A sample Web site is created as a tool to provision the device for Microsoft Exchange ActiveSync® settings Over the Air (OTA). Sample code is provided for a fully functional Web site. Instructions are provided for installing and operating the Web site. 2

Overview

This document is divided into the following sections:

 Introduction—General overview of Managing Windows Phones for Hosted Exchange.

 Using Exchange server to manage ActiveSync policies—Understanding options for managing IT security policies on Windows phones.

 Windows phones provisioning—Options for phone provisioning.

 Windows phone provisioning Web site—Fully functional examples.

 Scenarios—Explanation of multiple scenarios.

 Appendices—Details for completing tasks, and some additional information.

 

Objectives

 To understand how Windows phone IT policy is managed with Exchange Server.

 To understand available device provisioning options with an emphasis on Exchange Active Sync (EAS) provisioning Over the Air (OTA).

 To learn how to install and use the sample Web site for provisioning EAS settings.

 To obtain the knowledge necessary for basic Windows phone management tasks.

 

Target Audience

This document is designed primarily for Information Technology (IT) professionals who are responsible for planning, deploying, and implementing Hosted Messaging and Collaboration solutions. This white paper may also be useful to Planners, Architects, and independent software vendors. 3

Using Exchange Server to Manage ActiveSync Policies

This section provides an overview of ActiveSync-based policies that can be configured from the hosted Exchange server.

Exchange Server 2007 ActiveSync Policies

Exchange Server 2007 SP1 ActiveSync Policies are divided according to the Client Access Licenses (CAL).

The two CALs are:

 Standard CAL

 Enterprise CAL

 

Following are the policies that are available on Exchange Server 2007 SP1 Standard CAL: Sync

Authentication

Encryption

Configure message formats (HTML or plain text)  

Minimum number of complex characters  

Require signed (Secure/Multipurpose Internet Mail Extensions) S/MIME messages  

Include past e-mail items  

Enable password recovery  

Require encrypted S/MIME messages

E-mail body truncation size  

Allow simple password  

Require signed S/MIME algorithm  

HTML e-mail body truncation size  

Password expiration (days)  

Require encrypted S/MIME algorithm  

Include past calendar items (duration)  

Windows file share access  

Allow S/MIME-encrypted algorithm negotiation  

Require manual sync while roaming  

Microsoft Windows SharePoint® access

Allow S/MIME SoftCerts  

Allow attachment download  

Minimum password length  

Device encryption  

Maximum attachment size  

Timeout without user input  

Encrypt storage card  

Require password  

Require alphanumeric password  

Number of failed attempts  

Policy refresh interval  

Allow non-provisionable devices  

Overview of apps for Office

Posted on by escapebusinesssolutions in Uncategorized

Overview of apps for Office


Learn how to use apps for Office to extend your Office 2013 applications. You can build this new Office solution type with web technologies like HTML, CSS, JavaScript, REST, OData, and OAuth. The Apps for Office development platform provides new experiences in Office applications by surfacing web technologies and cloud services right within Office documents, email messages, meeting requests, and appointments.

Applies to:  apps for Office | Office 2013 | Office 365 | Excel Web App | Exchange 2013 | Outlook 2013 | Outlook Web App | Project Professional 2013 | Word 2013 | Excel 2013 | PowerPoint 2013 

What is an app for Office?


The apps for Office platform lets you create engaging new consumer and enterprise experiences running within supported Office 2013 applications by using the power of the web and standard web technologies like HTML5, XML, CSS3, JavaScript, and REST APIs. You can use your existing knowledge of these web technologies to quickly build your apps.

An app for Office is basically a webpage that is hosted inside an Office client application. You can use apps to extend the functionality of a document, email message, meeting request, or appointment. Apps can run in multiple environments and clients, including rich Office desktop clients, Office Web Apps, mobile browsers, and also on-premises and in the cloud. After you develop and publish your apps to the Office Store or to an onsite catalog, they will be available to consumers from their Office 2013 applications.

To try out some apps for Word, Excel, Outlook, and Project, see Download and try out some apps in Word, Excel, Outlook, PowerPoint, and Project.

This document provides a quick overview of the apps for Office platform, how an app works inside of an Office application, and how you publish an app to the Office Store or to an onsite catalog for consumers to use. Once you have read this overview, see the section Create your first app for Office .

Anatomy of an app for Office


The basic components of an app for Office are an XML manifest file and a webpage. The manifest defines various settings and points to the webpage that implements the app UI and custom logic, as shown in Figure 1.

Figure 1. Manifest + webpage = an app for Office



The manifest specifies settings and capabilities of the app, such as the following:

  • The URL of the webpage that implements the app UI and programming logic.
  • The app display name, description, ID, version, and default locale.
  • Whether the app can be shown as a task pane, in line with document content, or activated contextually in an email message, meeting request, or appointment.
  • The kinds of client applications (including rich and Web App clients) that an app supports.
  • The permission level and data access requirements for the app.

For more information about the apps for Office manifest, see Apps for Office XML manifest overview and Creating a manifest for a mail app for Outlook

Types of apps for Office


This section provides a quick look at the three basic types of apps for Office: task pane, content, and mail.

Task pane apps

Task pane apps work side-by-side with an Office document, and let you supply contextual information and functionality to enhance the document viewing and authoring experience. For example, a task pane app can look up and retrieve product information from a web service based on the product name or part number the user selects in the document. Figure 2 shows an example of a task pane app.

Figure 2. Task pane app



Content apps

Content apps integrate web-based features as content that can be shown in line with the document. Content apps let you integrate rich, web-based data visualizations, embedded media (such as a YouTube video player or a picture gallery), as well as other external content. Figure 3 shows an example of a content app.

Figure 3. Content app



Mail apps

Mail apps display next to the currently viewed Outlook items: email message, meeting request, meeting response, meeting cancellation, or appointment. They can access contextual information from the item, and then use that data to access additional information on the server and from web services to create compelling user experiences. In most cases, a mail app runs without modification on the Outlook 2013 rich client and Outlook Web App for Exchange 2013 to provide a seamless experience on the desktop, web, and tablet and mobile devices. Figure 4 shows an example of a mail app.

Note

Mail apps require Exchange 2013. POP and IMAP email accounts are not supported.

Figure 4. Mail app



Supported applications

One big benefit of apps for Office is that they can be supported both on Office 2013 rich clients and some corresponding Web Apps. To the developer, this means in many scenarios there is no need to create separate apps for the two different environments or applications. To the end user, it means a consistent user experience across the desktop and web browser.

For task pane apps, this means the same app can run on Excel, Word, and Project. For mail apps, this means the same app can work for Outlook on the desktop, tablet, and mobile devices.

Table 1 shows the Office client applications (including rich and Web App clients) that support apps for Office, and which types of apps are supported by each Office client.

Table 1. Supported app types

Application

Supported types

Excel 2013
  • Task pane
  • Content

Excel Web App
  • Content

Word 2013
  • Task pane

Outlook 2013
  • Mail

Outlook Web App
  • Mail

Project Professional 2013
  • Task pane

What can an app for Office do?


An app for Office can do pretty much anything a webpage can do inside the browser, such as the following:

  • Provide an interactive UI and custom logic through JavaScript.
  • Use JavaScript frameworks such as jQuery.
  • Connect to REST endpoints and web services via HTTP and AJAX.
  • Run server-side code or logic, if the page is implemented using a server-side scripting language such as ASP or PHP.

And, like webpages, apps for Office are subject to the same restrictions imposed by browsers, such as the same-origin policy for domain isolation, and security zones.

In addition to the regular capabilities of a webpage, apps for Office can interact with the Office application and the user’s content through a JavaScript library that the apps for Office infrastructure provides. The specifics of this interaction depend on the type of app, as follows:

  • For task pane and content apps, the API lets your app read and write to documents, as well as handle key application and user events, such as when the active selection changes.
  • For mail apps, the API lets your app access email message, meeting request, and appointment item properties, and user profile information. The API also provides access to some Exchange Web Services operations. For a summary of top features of mail apps, see Fundamentals for developing mail apps in Outlook.

Understanding the runtime


Apps for Office are secured by an app runtime environment, a multiple-tier permissions model, and performance governors. This framework protects the user’s experience in the following ways:

  • Access to the host application’s UI frame is managed.
  • Only indirect access to the host application’s UI thread is allowed.
  • Modal interactions are not allowed.

Further, the runtime framework provides the following benefits to ensure that an app for Office can’t damage the user’s environment:

  • Isolates the process the app runs in.
  • Doesn’t require .dll or .exe replacement or ActiveX components.
  • Makes apps easy to install and uninstall.

Also, the use of memory, CPU, and network resources by apps for Office is governable to ensure that good performance and reliability are maintained.

For more information about the apps for Office privacy and security model, see Privacy and security for apps for Office.

The following sections briefly describe how the runtime architecture supports running apps in Office rich client applications versus Office Web Apps.

Rich clients

In supported rich clients, such as Word, Excel, and Outlook, apps for Office are supported by integrating an in-process component, the apps for Office runtime, which manages the app lifecycle and enables interoperability between the app and the client application. The app webpage itself is hosted out-of-process inside a web browser control which, in turn, is hosted inside an app runtime process that provides security and performance isolation. The apps for Office runtime manages interprocess communication, the translation of JavaScript API calls and events into native ones, as well as UI remoting support to enable the app to be rendered inside the document, in a task pane, or adjacent to an email message, meeting request, or appointment.

Figure 5 illustrates the components (Apps for Office runtime, host process, and JavaScript API) that are provided to support apps for Office running in Office rich client applications.

Figure 5. Apps for Office rich client runtime environment



Web Apps

In supported Web Apps, such as Excel Web App and Outlook Web App, apps for Office are hosted in an iframe that runs using the HTML5 sandbox attribute. ActiveX components or navigating the main page of the Web App are not allowed. Apps for Office support is enabled in the Web Apps by the integration of the JavaScript API for Office. In a similar way to the rich client applications, the JavaScript API manages the app lifecycle and interoperability between the app and the Web App. This interoperability is implemented by using a special cross-frame post message communication infrastructure. The same JavaScript library (Office.js) that is used on rich clients is available to interact with the Web App. Figure 6 illustrates the infrastructure that supports apps for Office in the Office Web Apps (running in the browser), and the relevant components (the Web App, iframe, apps for Office runtime, and JavaScript API for Office) that are required to support them.

Figure 6. Infrastructure that supports apps for Office in Office Web Apps Preview



Development basics


To create apps for Office, you can use any application that can save a file as text. But, you can create an app for Office more easily in the “Napa” Office 365 Development Tools web-based development environment or in Visual Studio 2012 by using its project templates, development environment, and debugging tools.

Basic components of an app for Office

To create an app for Office, at minimum, a developer must create an HTML webpage and a manifest file. The HTML page can be published to any web server. The manifest file must point to the location of the webpage and be published to any of the following locations: the public Office Store, an internal SharePoint list, or a shared network location.

The most basic app for Office consists of a static HTML page that is hosted inside the task pane of an Office application, but does not interact with either the Office document or any other Internet resource. Figure 7 shows the components of a basic “Hello World” app for Office.

Figure 7. Components of a Hello World app for Office



Creating an app for Office by using “Napa” Office 365 Development Tools

Perhaps the quickest way to build an app for Office is directly out of a browser. You can do this by using “Napa” Office 365 Development Tools. “Napa” Office 365 Development Tools is web-based development environment that lets you create projects, write code, and run your apps all within the browser. There is no need to install any other tools such as Visual Studio. To learn more, see Create apps for Office and SharePoint by using “Napa” Office 365 Development Tools.

You can begin developing apps for Office by using “Napa” Office 365 Development Tools and then open these projects in Visual Studio 2012 if you decide that you want to leverage features such as advanced debugging or the ability to use a web project as part of your app for Office.

Creating an app for Office by using Visual Studio

The most powerful way to build an app for Office is to use the App for Office project template in Visual Studio 2012. Just make a few selections in a wizard. Visual Studio creates a complete solution that contains all of the files that you need to begin testing your app in Office immediately. Visual Studio provides a full range of features to make it easy for you to develop and test apps for Office.

The figure 8 below shows you some of the features that help you develop app for Office.

Figure 8. Visual Studio environment



  • Get started quickly with a complete Visual Studio solution.

    Your solution contains a prepopulated XML manifest file, script libraries, styles sheets, starter HTML and JavaScript files that you can use to get started quickly. The starter HTML file contains a reference to style sheets that enable you to develop a page that has the look and feel of Office. This page also refers to other important files such as a default JavaScript file that you can use to add your JavaScript code. The default JavaScript file contains sample code to help you get started with the JavaScript API for Office.

  • Edit the XML manifest file by using an editor.

    Modify the most common settings of your app by using a convenient property page-like editor. As you interact with the editor, Visual Studio updates the XML manifest file in your app project for you. You can also edit the XML manifest file directly. The editor and the XML manifest file remain in sync.

  • Quickly uncover validation errors.

    Validation errors appear in the code editor as well as in the ERRORLIST window. In the code editor, you can point to a validation error to view a tooltip that describes the error.

  • Discover objects in the JavaScript API for Office by using IntelliSense.

    When you type the name of an object in the JavaScript API for Office, lists of all valid objects or members appear in a drop-down list. You can scroll through the list or type the first few letters of a member to move to that member in the list. As you highlight items in the drop-down list, IntelliSense displays information about the object or parameters.

  • Find and fix issues quickly by using the Visual Studio debugger.

    When you start the solution, Visual Studio opens the Office application for you. Depending on the type of app for Office you create, Visual Studio automatically shows the app in the Office application. To find and fix issues in your app, set breakpoints, interact with the app, and then step through your code.

  • Package your app for publishing by using the publish wizard.

    When you are ready to publish your app for Office, just make a few selections in the publish wizard. Visual Studio generates all of the files that you need to publish the app to the SharePoint corporate catalog, the Office store, file catalog share, or Exchange catalog.

JavaScript API for Office

The JavaScript API for Office consists of members of the Microsoft.Office.WebExtension namespace (which by default is accessed by using the Office object in code) contains objects and members for working with apps and the content they can interact with programmatically. For more information about the JavaScript API for Office, see Understanding the JavaScript API for Office and the JavaScript API for Office reference.

Create your first app for Office


The following topics show you how to create “Hello World” and other simple apps for Office by using either Visual Studio or a text editor:

Publishing basics


You can publish apps for Office to four distribution end-points:

  • Office Store—This is a public marketplace that Microsoft will host and regulate on Office.com. In the Office Store, developers around the world can publish and sell their custom Office solutions, and then end users and IT professionals can download them for personal or corporate use.

    When a developer uploads an app to the Office Store, Microsoft validates the code. For example, it verifies that the app manifest markup is valid and complete. If the code is valid, Microsoft digitally signs the app package. The Office Store then takes care of the consumer download experience from discovery to purchase, upgrades, and updates.

  • Apps for Office catalog on SharePoint—For task pane and content apps, IT departments can deploy private app catalogs to provide the same app acquisition experience that the Office Store provides. This new catalog and development platform enables IT departments to use a streamlined method to distribute apps for Office and SharePoint to managed users from a central location.

    App catalogs are available to all SharePoint 2013 customers (including Office 365 and SharePoint on-premise). An app catalog enables publishing and management of both internally created apps as well as apps that are available in the Office Store and licensed for corporate use.

  • Exchange catalog—This is a private catalog for mail apps that is available to users of the Exchange server on which it resides. It enables publishing and management of corporate mail apps, including internally created apps as well as apps that are available in the Office Store and licensed for corporate use.
  • Network shared folder app catalog—IT departments and developers can also deploy task pane and content apps to a central network shared folder, where the manifest files will be stored and managed. Users can then acquire apps by specifying this shared folder as a trusted catalog, or IT departments can configure this shared folder as a trusted catalog by using a registry setting.

For more information, see Publish apps for Office.

Scenarios


The following scenarios show that apps for Office are targeted, quick-hit apps that can be used to solve complex, time-consuming problems.

These scenarios suggest ways in which you can, for example, surface line-of-business data and drive adoption of structured business processes in the familiar Office UI across multiple devices. They suggest how you could use an expense-managing app that connects Office, SharePoint, and SAP, or create an app that combines sales data with maps from the Bing Maps web service to create more effective sales reports. They show how you can unlock the return on your existing investments, such as enterprise resource planning (ERP) and customer relationship management (CRM) applications, by spending less time navigating to and from these applications from an Office client.

Scenarios include:

  • Translation wizard—A Word task pane app that automatically translates selected text from the document language to another language selected from a drop-down list.
  • Chart creation—An Excel content app that builds a chart automatically from selected data.
  • Third-party service integration—A Word or Excel task pane app that automatically displays the Wikipedia page that corresponds to selected text.
  • Rich mash-ups—A Bing map content app in Excel that plots the offshore equipment and resource locations for a petroleum company, including getting this information in real time from the company resource-management system.
  • Spec validation—A section or paragraph of a design specification for an aircraft component is flagged as outdated, because a Word task pane app that communicates with a business system to validate the contents against the latest spec.
  • Order details surfaced in context—A mail app that detects a purchase order number or customer number embedded in an email message and presents details of the order or customer in the message. This could include an action to take, such as approval.

Components of an app for Office solution


A typical app for Office solution involves the following components:

  • A client device—which can be a desktop, laptop, tablet PC, or mobile phone (Outlook only)—on which the supported Office rich client or Web App runs.
  • For Excel, Project, or Word:
    • A document, workbook, or project.
    • A task pane or content app that the user installed from the public Office Store or from a private SharePoint or file-based app catalog.
  • For Outlook:
    • The user’s email account and mailbox, which resides on an Exchange Server.
    • A mail app that the user or Exchange Server administrator installed through the Exchange Admin Center (EAC).

Note

The user’s installation of an app for Office consists of a pointer to an XML manifest file, which specifies the URL from which to load the app webpage and script at run time.

For all supported Office applications, the implementation of the app for Office itself consists of the following server-based components:

  • An XML manifest file which resides on a public or private app catalog.
  • The app HTML, CSS, and JavaScript files, which the developer creates and which reside on a web server.
  • The JavaScript library files, such as JavaScript API for Office (Office.js) and the Microsoft AJAX Library (MicrosoftAjax.js), which Microsoft provides. The app accesses the JavaScript library files from content delivery network (CDN) URLs, as specified in its HTML file.

When a user starts an app for Office in a supported Office rich client or Web App, the following events occur:

  1. When a supported Office application starts, it reads the XML manifests for the apps that have been installed for or by the user.
  2. For Excel, Project, or Word: When a user inserts or opens a document that contains an app, the Office application loads the app, making its UI visible in the user interface.

    For Outlook: Whenever the current Outlook context satisfies the activation conditions of an app, Outlook activates the app, making its UI visible in the user interface.

  3. The Office application opens the HTML page in a web browser control (rich client) or an iframe (Web App). The web browser control uses Internet Explorer 9 or later components and provides security and performance isolation.
  4. The browser control or iframe loads the HTML body, and calls the event handler for the onload event.
  5. The apps for Office framework calls the event handler for the initialize event of the Office object.
  6. When the HTML body finishes loading and the app finishes initializing, the main function of the app can proceed.

Software requirements


Server

To test and run any kind of app for Office, you need the a web server, such as Internet Information Services (IIS) 7.5 in Microsoft Windows Server 2008 R2, to host the webpage files for the UI of the app. To test and run task pane and content apps for Word, Excel, or Project, you also need a network file share or an app catalog on SharePoint Server 2013 to host the XML manifest files.

Note

When you develop and debug an app in Visual Studio 2012 by using the Office Developer Tools, Visual Studio runs the webpage files for the UI of an app locally, and doesn’t require an additional web server.

To test and run mail apps for the Outlook rich client or Outlook Web App, you also need Exchange 2013, which is available through Exchange Online or on premises. The user’s Outlook email account must reside on an Exchange 2013 server, and you install manifest files for mail apps on that server.

Note

POP and IMAP email accounts in Outlook do not support apps for Office.

Client: desktop and Windows tablet form factors

The following software is required for developing an app for Office for the supported Office rich clients or Web Apps that run on desktop, laptop, or Windows tablet devices:

  • Microsoft Windows 7, or designated pre-release builds of Microsoft Windows 8 that support Office 2013. If you are using Windows 8, be sure to use the 32-bit version of Office 2013 (build 3612.1001 or later) on either the 32-bit or 64-bit version of Windows 8 (build 8158.7.111205-1900).
  • Microsoft Internet Explorer 9 or later, which must be installed but doesn’t have to be the default browser. To support apps for Office, Office 2013 uses browser components that are part of Internet Explorer 9 or later.
  • One of the following as the default browser: Internet Explorer 9, Safari 5.0.6, Firefox 5, Chrome 13, or a later version of one of these browsers.
  • An HTML and JavaScript editor such as Notepad, Microsoft Visual Studio, or a third-party web development tool.
  • Excel 2013, Outlook 2013, Project 2013, or Word 2013 if you are testing or running an app for Office specifically for one of these Office rich clients. Office rich clients can be installed on premises or via Click-to-Run on the client computer.

Client: mobile and non-Windows tablet form factors

Specifically for Outlook Web App running in a browser on mobile and non-Windows tablet devices, the following software is required for testing and running mail apps.

Mobile or tablet device

Operating system

Mobile browser

iPhone 4, iPad 2, iPod 4, or iPod Touch

iOS 5

Safari

Mobile and tablet devices that support the specified versions of Android

Android 2.3 and above

  

How Technology is ChangingSocial Media Marketing

Posted on by escapebusinesssolutions in Uncategorized

How Technology is Changing

Social Media Marketing

Three ways social software harnesses the power of scale

Contents

executive summary………………………………………………………………………………………………………………………… 1

INTRODUCTION…………………………………………………………………………………………………………………………………. 2

STRATEGIC PLANNING……………………………………………………………………………………………………………………….. 2

A pricey proposition………………………………………………………………………………………………………………..2

A n eye to the future………………………………………………………………………………………………………………..2

St rategic advantages built right in……………………………………………………………………………………..3

ORGANIZATIONAL EFFICIENCY……………………………………………………………………………………………………………..4

Mountain Dew…………………………………………………………………………………………………………………… 4

Harness the full power of scale……………………………………………………………………………………………5

Annie’s Homegrown…………………………………………………………………………………………………………..5

St retch your editorial resources………………………………………………………………………………………….6

The Washington Redskins…………………………………………………………………………………………………….. 6

SOCIAL MEDIA RESULTS……………………………………………………………………………………………………………………… 7

G et optimal results with optimized technology.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Y ou can’t fix what you can’t measure…………………………………………………………………………………….8

S ix methods for measuring social.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Measure, monitor and analyze……………………………………………………………………………………………….9

Esurance……………………………………………………………………………………………………………………………. 9

CONCLUSION……………………………………………………………………………………………………………………………………. 9

executive summary

A healthy and growing fanbase is a social marketer’s dream come true. But, keeping all your fans

happy can quickly become a nightmare. Attention spans in the social space are short, and the

impact of any single interaction is fleeting at best. There’s simply no way around it, ongoing social

success demands a constant churn of unique and engaging content. How do leading social brands

keep it up day after day?

The solution is technology. And in the world of social marketing, technology is all about

the power of scale.

Marketing automation is finally catching up to the business technology curve, and some of the

most exciting and valuable advances are in social marketing software. As a marketer, it’s critical

for you to sit up and take notice, not only because technology can make your job easier and more

productive, but also because your influence over the technology you use is growing dramatically.

According to Gartner, 2011 B2B and B2C marketing budgets as a percentage of revenue were

almost three times as high as IT budgets, and the gap was expected to grow in 2012. Marketing

already makes 30% of its own technology purchases and influences almost 50% overall. What’s

more, by 2017 Gartner expects that CMOs will be spending more on IT than CIOs do.1

Because your role as a technology influencer and decision maker is growing, it’s more important

than ever that you understand exactly how different technology choices can affect your resources

and your results. To that end, this paper explains how social marketing technology allows you to

do more faster, at a lower cost, with better results, and greater insight. We explore the top three

ways you can use technology to empower social marketing managers and bolster a growing brand.

And we look at specific examples of how four leading brands use technology to help their social

marketing fly.

1 G artner, “By 2017 the CMO will Spend More on IT Than the CIO,” January 2012

By 2017 CMOs will spend more on IT than CIOs do.

1

Whitepaper | How Technology Can Take Your Social Where It’s Never Been Before

2

them? How can you use your planning tools most effectively?

How do you measure your results and benefit from what

you’ve learned?

A pricey proposition

If you turn to third-party consultants for their expertise, all

that strategizing becomes a pricey proposition. Social media

consulting fees can run up to $500 per hour, and monthly reports

and advisement can result in an annual fee upwards of $90,000.2

And keep in mind; those expenses are in addition to any

development and on-going management fees for social channels.

The right social marketing software will include the same or

better strategic consulting services at little or no extra cost.

Remember, a third-party consultant is happiest when you’re

paying for their help on a repeat basis. Having customers who

are satisfied all the time, on the other hand, motivates a good

social software-as-a-service business. When you’re using a social

technology to its full potential and growing your business as

a result, you’re more likely to expand your use of the product

and recommend it to others. Your success is a win/win for you

and the software vendor, so it’s in the vendor’s best interest to

provide efficient, high-quality strategic resources and advice.

An eye to the future

When choosing your social technology keep in mind that the

social media landscape is changing daily. That means your social

software should be forward-looking and strategic by its very

nature. Your vendor should have more than a great product

right now; it should also have a compelling vision of where

social marketing is headed and a plan to get you there. The best

social software:

• Quickly adapts to incorporate important new social networks

• Always complies with current social network formats and

requirements

INTRODUCTION

A post, a tweet, a pin, or an update are all simple and speedy

enough tasks to complete. But the social audience is a hungry

beast, and once you start feeding it you can’t afford to stop.

When you’re just getting started with social marketing, it may be

simple enough to log onto the separate social networks and create

every interaction by hand. But, if you’re doing social right, your

brand will soon gain traction, your fans will multiply, engagement

will increase, and the demand for content will take off.

Active social brands quickly learn that content demand always

outpaces content resources, which means you need to make

your processes more efficient and enable your team to work

faster. You need systems in place that seamlessly expand your

brand into new networks, regions and markets. You want to be

able to work quickly and efficiently with other departments or

sub-brands and with outside partners. And when employees are

busy with other projects, take a vacation, or move on to other

positions, you have to be sure new people can step in without

skipping a beat.

There are an incredible number of moving parts in almost any

social marketing initiative. But, to successfully grow a brand,

social media managers must be able to focus most of their

energy on the bigger social strategy instead of on the processes

and logistics of individual executions. This paper is organized

around the three key areas where technology can make that

happen: strategic planning, organizational efficiency and

social media results.

STRATEGIC PLANNING

With time and resources at a premium, every significant

social marketing effort should be planned carefully. Not just

to maximize its own results, but also to further the brand’s

overarching social strategy.

The questions you should ask are many, and the answers

are constantly changing: What campaign concepts are most

compelling? What best practices should you use to implement

2 Mack Collier, “Cost of Social Media in 2012,” January 2012

Escape supports all leading social networks,

including Facebook, Twitter, Google+,

LinkedIn, YouTube and Pinterest.

Escape clients get:

• A Escape strategist as part of your contract

• A quarterly review

• 3–6 white papers per quarter

• 3–6 webinars per quarter

3

Localizing a single campaign by hand is essentially the

same as launching multiple campaigns at once, which is a

time-consuming and tedious task. But localization is easily

manageable with the proper technology. Instead of launching

five campaigns in five different languages, you can launch one

campaign, with all of the relevant creative assets stored, that

automatically and dynamically adjusts itself to the relevant

language. Automated scheduling also allows you to post content

at the most ideal time anywhere in the world.

Compliance and regulation

If you’re like most people, you’ve signed up for so many online

accounts that you click right through the terms of agreement

without even realizing they’re there. When it comes to your

brand’s social properties, though, you need to pay attention.

Facebook’s terms provide a prime example of what’s at stake

and how complex the rules can be. To protect the reputation

and integrity of its social network, Facebook’s regulations

consist of thousands of words of legalese, all of which have

direct impact on the governance of your page and its social

activities. Items covered include everything from who may

access your pages to page naming conventions to how you

design your cover photos.

Every social network that your brand uses has its own set of

rules and regulations, and they all change constantly to keep

up with government requirements, product updates and other

developments. If you fall out of compliance, the pages that you’ve

labored on building up for months (and longer) can be removed

• Gives you timely social best practices resources like webinars

and white papers

• Provides strategists who are well versed in developing social

trends and how you can capitalize on them

Strategic advantages built right in

Some aspects of strategy are more technical than analytical, and

the best social technologies handle such issues automatically.

Two areas in particular where strategic functionality should be

built right into your technology are localization and compliance.

Localization

Every social marketer should be thinking about the future,

about expanding their brand into new markets or regions on

the way to becoming a 24/7 global brand.

You never know where you might find your next great customer

or market, and social media can give you efficient low-cost access

to people you might not be able to reach any other way. For

example, Argentina, Brazil and India may be beyond your physical

reach, but they also have the highest penetration of social

network usage plus the highest usage frequency and intensity. 3

But, to go global you need to localize your content. For starters,

you should speak your audience’s language—in Europe, for

instance, nine out of ten Internet users prefer browsing in their

own language.4 For maximum relevancy, you also want to be

sure you’re targeting the right audience at the right time with

the right message.

3 I nSites Consulting, “Social Media Around the World 2012,” September 2012

4 E uroBarometer, “User Language Preferences Online,” May 2011

Qatar ran a global social media campaign with Escape in five languages and

grew its community by 150,000 new fans in 30 days.

Social marketing software ensures that pages and applications stay in

compliance with constantly changing social network requirements.

Whitepaper | How Technology Can Take Your Social Where It’s Never Been Before

4

You could tackle your campaigns one at a time using an agency

or in-house resources, but that’s an extremely time-consuming

and expensive approach. One Industry survey showed that the

typical agency cost of a short-term (1-3 month) social media

campaign in 2012 was between $1,500 and $20,000. A long-term

(3–6 month) campaign averaged between $25,000 and $75,000.6

The right technology not only makes it incredibly faster and

easier to create a campaign, it also allows you to run as many

campaigns as you want at a lower cost. Better still, the value you

receive goes far beyond just the value of the digital assets that

are created for a given campaign. The best social software helps

minimize or eliminate development costs, agency fees, strategy

consultation fees, and maintenance and management fees. And

it allows you to simplify processes, replicate procedures, and

easily create workflows.

With full functionality software, you can efficiently create

integrated campaigns across social networks by building pages,

scheduling and sending messages, running ads and viewing

results from a single interface. You’ll be able to deploy the same

content across multiple networks or create custom content

targeted to individual networks. And you can create custom

workflows that automatically notify team members when their

input and approval is needed to keep a project moving.

Mountain Dew

Mountain Dew, the popular soft drink brand owned by PepsiCo,

learned about the power of scalability when it wanted to launch

what it expected to be a simple promotion. Mountain Dew

had 80 Diet Dew bean bag chairs it wanted to give away to

customers, but was surprised to find out it was going to cost

tens of thousands of dollars to run a single contest.

Then Mountain Dew discovered that Escape’s technology

could help its social team do far more while spending less.

Escape gave them unlimited access to create multiple pages

in an instant, and the communities you’ve grown around them

can disappear. The best way to avoid this disastrous scenario is

to use social software that stays on top of the latest requirements

for you and has compliance built right in.

The best social software vendors constantly monitor social

network requirements and update their products accordingly.

To the extent that it’s possible, they prevent you from making

mistakes that put your social campaigns and communities at

risk. On the other end of the spectrum, they optimize templates

and functionality so you can quickly and easily exploit any

activities that are permitted.

ORGANIZATIONAL EFFICIENCY

Any marketer who tests the social waters realizes quickly

that there’s much more to social marketing than posting a

pithy comment whenever inspiration strikes. In fact, 59% of

marketers work on social more than 6 hours every week,

33% spend over 11 hours weekly, and 15% dedicate a full

20 hours or more to social efforts every week.5

Even if you’re part of the 59% right now, you’ll need to commit

more attention to your social initiatives to keep them healthy

and on track as they begin to gain traction. And the more

successful your efforts, the more complex the challenges you’ll

face. For example:

• What content will be most effective and where will you get it?

• How should you schedule your messaging?

• Who’s going to have editorial oversight?

• How long is it going to take to get everything created,

approved and ready to go?

5 S ocial Media Examiner, “2012 Social Media Marketing Industry Report,” April 2012

6 Mack Collier, “Cost of Social Media in 2012” January 2012

59% of marketers work on social for 6 hours or more every week.

Cost of social campaigns without the

scale of social software:

Short-term campaign: $1,500 to $20,000

Long-term campaign: $25,000 to $75,000

5

and promotions across all the most popular social networks.

Plus, Escape’s technology came with unlimited user accounts

and built-in creative and technical services. Mountain Dew

also gained powerful analytics and the ability to free up brand

managers by letting them schedule posts ahead of time.

Harness the full power of scale

When it comes to organizational efficiency, social software adds

value in more ways than we can list here. To identify the greatest

benefits in simplest terms, though, we say that technology helps

you scale your content and scale your resources.

The one thing that can’t be stressed enough is this: The key to

social success is a constant churn of fresh and original content.

To maximize engagement, you need to create, launch and

maintain lots of great content all the time.

Basic communications like posts and tweets are an important

part of any ongoing social conversation. But, if you’re going to

grow and engage fans and followers and encourage sharing,

it’s essential to up the ante with a regular stream of fun and

rewarding interactive experiences such as polls, surveys,

contests and giveaways.

Creating a rich interactive experience from scratch is extremely

time and resource intensive, but social software makes it easy to:

• Launch a variety of campaigns on a variety of channels

• Keep the content visually appealing and on brand

• Create unique and memorable experiences

• Capture user data

Social software provides all the templates you need to create

customized tabs and applications for your social properties.

And these templates are already fine-tuned to optimize the

placement and impact of your interactive content.

Tabs allow you to add depth to your existing social channels by

including multiple landing pages and experiences on each site.

Applications let your users interact with your content and let

you capture user data so you can follow up with participants,

identify influencers, and gather information to build moreprofitable

relationships.

Annie’s Homegrown

Annie’s Homegrown is an organic and all natural foods company

based in Berkeley, California and is best known for its bunnyshaped

macaroni and cheese. To celebrate its new Rising Crust

Pizza, Annie’s sent a fully equipped pizza truck on a cross-country

Slice of Happiness Tour and promoted the event on Facebook.

To create its Facebook promotion, Annie’s combined two of

Escape’s 90+ page and app templates. When users clicked on

the “Request a Stop” tab on Annie’s main Facebook page they

were taken to a customized landing page where an entertaining

YouTube video explained what the tour was all about and

encouraged them to participate.

Beneath the video viewers could enter their information and

request a special detour of the pizza tour. If you were one of the

lucky winners, Annie’s rerouted its pizza truck to your town and

served up a pizza party for 120 people. The tour was a big hit,

generating over 325,000 likes.

Mountain Dew used Escape to run a sweepstakes that took users from Twitter

to Facebook.

Annie’s Homegrown used Escape templates to promote a crosscountry

pizza party contest on Facebook.

Whitepaper | How Technology Can Take Your Social Where It’s Never Been Before

6

Stretch your editorial resources

Once you’ve figured out how to keep your inspired content

coming, you’re well armed for social success. But the battle is

far from over. In fact, it never ends. Every piece of content you

create is simply an invitation for engagement, just one step in

what you hope to be an ongoing relationship that’s rewarding

for both you and your customers.

Your goal is to spark relationships and then keep them going

strong, but the sheer volume of content it takes just to get

things started can make it nearly impossible to keep up with

the responses. Here’s what you’re up against:

• On average, every enterprise brand of 1,000+ employees has

178 corporate-owned social media accounts.7

• Businesses with over 40 different landing pages generate 10X

more leads than those with only 1–5 landing pages.8

• 70% of all fan questions posted to social media channels are

not responded to by brands. 9

These numbers raise three key issues that technology can help

you address:

1. Most brands have very few people responsible for managing

an overwhelming number of social accounts.

2. The payoff for creating numerous landing pages can be

huge, even if the pages vary only slightly in messaging or

other elements.

3. A staggering potential for social return on investment (ROI) is

being wasted, because social teams don’t have the resources

to follow up on the majority of conversations they initiate.

Social software can help you address these issues by making the

most of every resource available to your social team.

Use access control to increase your resources. Social software

allows you to give different team members different roles

and permissions, so you can maximize your resources while

protecting your brand. In other words, you can assign specific

responsibilities without providing unlimited access to your social

properties. For instance, you don’t want an intern responding

directly to customer comments or questions. But, you can use

that same intern to sort through the messages and queue

them up, making it easier for a senior member of your team to

respond quickly and appropriately.

Scale your messages. With the right software, you can create

content once and then post it simultaneously across multiple

pages and networks. A single person can add fresh content

to numerous accounts as quickly and easily as updating a

single account. And creating and maintaining multiple landing

pages requires a fraction of the work it would take if they were

developed one at a time. Flexible templates allow you to quickly

customize and go live after adding just your logos, images and

text—or they let you access the code and get more creative if

you have the time and need.

Filter conversations for specialized attention. Not all

conversations are created equal. You’d like to answer every

question and acknowledge every comment, but some you’ll

never get to. Others, you simply can’t afford to ignore. Software

filters let you use keyword or moderation checklists to flag the

messages that absolutely demand your attention. You can put

out fires like unhappy customers, or snap to attention if a hot

lead comes along.

The Washington Redskins

The National Football League’s Washington Redskins have some

of the most faithful fans you could wish for. The team has sold

out every home game since 1968 and has broken the NFL’s

attendance record for the last nine years running.

In a football season with new games and plenty of surprises

every week, the Redskins often need to turn on a new promotion

in a matter of days to stay relevant to their fans and provide the

excitement and sense of community fans are looking for. “If we

didn’t have a platform like Escape,” says the Redskins top social

strategist, “we’d have to spend a lot of lead time to build out

these pages, and that could take a month or more.”

7 A ltimeter, “A Strategy for Managing Social Media Proliferation,” January 2012

8 E consultancy, “The Inbound Marketing Explosion,” March 2012

9 Simply Zesty, “70% Of Brand Fan Questions On Social Media Aren’t Responded To – Live at Le Web ’12,” June 2012

Escape clients:

• Save hours per day using geo-target presets

• Can schedule a month’s worth of content in

just a few planning sessions

• Receive unlimited access to Pages and

Promotions as part of a monthly fee

7

Prior to using Escape, the Redskins were also impacted by an

artificial resource crunch. Because Administrator was the only

role available to access the social accounts, the social team had

to be very careful about who could do hands-on work. Now

that Escape provides different levels of permission, the social

team can open up different roles to interns, designers, staff,

and even partners. With more people on the job, the Redskins

can respond to opportunities faster and make the best use of

all their resources.

SOCIAL MEDIA RESULTS

By efficiently scaling your efforts, social software provides

the immediate reward of reaching a larger audience. But it also

delivers better results in two additional ways that are equally

important. First, it helps increase lead generation, brand reach,

and brand advocacy by optimizing the technology that you use

to run your campaigns. Second, it provides comprehensive

and integrated measurement and analysis tools that give you

insight into your results, so you can continually adjust your

strategy and increase your success.

Get optimal results with optimized technology

When you work with an internal team or a third-party agency

to build complicated and customized one-use applications,

you may end up with a social campaign that looks great on

your desktop but falls apart online. There’s simply no way to

thoroughly test one-off applications and optimize them for

the best user experience. When they go live, these pages or

applications may even break due to unforeseen code changes

made by the social platforms themselves.

The result can be an awkward and inconsistent user experience

that causes users to abandon a campaign before they even

enter. Many custom applications also lack an optimized viral

functionality, and that means participants can’t easily share

the campaign with their friends and followers. Either one of

these issues can seriously slow the momentum of an otherwise

brilliant campaign—combined, these problems can stop a

campaign in its tracks.

Improved access control helps the Redskins get more staff

involved with their social.

Increase lead generation, reach

and advocacy.

Adjust your strategy to improve success.

Keep a constant eye on industry benchmarks, property and page

data, tab and promotion metrics, and referral sources.

Whitepaper | How Technology Can Take Your Social Where It’s Never Been Before

8

When you build a campaign using social software, you keep the

ability to create something unique, innovative and on brand. But

you eliminate the risk that your end product will not function as

intended or that it will be incompatible with the social platforms

it was intended for.

The tab, page and application templates that come with

your social software have been used and tested hundreds or

thousands of times in live campaigns. They incorporate best

practices for all of the most popular and effective promotion

types. Their results are constantly analyzed and their coding is

continually updated and optimized to work perfectly with the

social networks they’re intended for. And, because sharing is the

key to social success, the latest and greatest viral functionality is

seamlessly built into the templates as a basic component.

You can’t fix what you can’t measure

In a recent survey by the Association of National Advertisers,

90% of U.S. marketers say they’re using social networks for their

marketing efforts. Five years ago that figure was only 20%.10

Despite this steady increase in adoption, 75% of organizations

lack a holistic measurement strategy for their social media work.11

Why is there such a huge divide between the number of

marketers using social media and the number successfully

measuring their results? An Altimeter Group survey sheds some

light on the subject by asking those responsible for measuring

social media results to identify the three biggest challenges

they face: 56% of respondents indicate the inability to tie social

media to business outcomes; 39% say there is a lack of analytics

expertise and/or resources; and 38% say they have poor tools.12

Six methods for measuring social

In its “Social Media ROI Cookbook,” Altimeter Group identifies

the six methods that organizations use to measure their

social results on a day-to-day basis. Three of the methods are

categorized as “top down” methods and three as “bottom up.” 12

Top down

The top down methods, which rely on the user to draw

conclusions based on their own observations, are:

Anecdote: Specific examples where it is known that social media

influenced a sale or had some other identifiable effect.

Correlation: Comparing two data sets to see if there may be a

relationship between them, for example the number of Likes

versus revenue.

Multivariate testing: Comparing a group exposed to social

media content with another group exposed to different content

or no content.

While top down measurements have their place, they are time

and labor intensive and fall far short of being able to provide

reliable and comprehensive data on a regular basis.

Bottom up

Bottom up measurements are technology driven and can

provide metrics that are instant, comprehensive and exact.

These methods are:

Links and tagging: Shortlinks, tags, custom URLs and cookies

identify when a user buys something from your site and where

they came from.

10 Association of National Advertisers, “2012 Digital/Social Media Survey,” July, 2012

11 A ltimeter Group, “A Strategy for Managing Social Media Proliferation,” January 2012

12 A ltimeter Group, “A Strategy for Managing Social Media Proliferation,” January 2012

13 A ltimeter Group, “Social Media ROI Cookbook,” July 2012

Compared to Escape’s top competitors’

clients, Escape’s clients see:

• 25% more people sharing their posts

• 21% more engagement with their content

Poor tools are one of the top three obstacles to measuring social success.

9

When it comes to service, Esurance takes advantage of the

personal assistance that’s built right into its contract. For upfront

strategic guidance or last-minute technical tweaking,

Esurance always knows exactly where to turn for help.

CONCLUSION

By its very nature, social is a medium that requires a higher

frequency of interaction than any other form of marketing. The

challenge may be daunting, but the payoff in terms of engaged

and loyal fans, followers, customers and advocates can’t be

beat. The good news for marketers is that recent advancements

in social marketing technology are making it easier and more

affordable to build, grow, engage, and monetize audiences

using innovative content that’s optimized for the most popular

social networks.

The key to success is social software that scales both your

content and your resources allowing you to:

• Create content once, then launch it everywhere

• Segment promotions, target content by region and language,

and schedule posts

• Control user permissions and access to make the most

efficient use of your social team and partners

• Test, measure, and analyze campaigns and competitors in real

time to adjust your strategy and ensure success

Direct commerce: Social commerce apps allow users to make a

purchase from you on Facebook, from links on Twitter, and via

other social properties.

Integrated: Specific apps that you purchase run in the

background and measure conversions, identify where leads

come from, score leads, and so on.

Measure, monitor and analyze

Integrated technology includes the measurement, monitoring and

analysis tools that come as part of your primary social software

product. Because these tools are designed from the start to work

with your pages and applications, they’re often able to give you

the most powerful, insightful and actionable measurements and

analytics available. Social software can provide:

• Property and page data for each of your social pages,

allowing you to analyze trends over time and across multiple

variables

• Tab and promotion metrics that let you quickly pinpoint

what’s working, so you can repeat successful strategies and

optimize results

• Referral sources, so you can identify demographic data

for campaigns and develop content that matches audience

preferences

• Audience engagement metrics for specific messages, so you

can fine-tune future messaging for maximum impact

• Industry benchmarks that help you understand your

performance in comparison to competitors

Esurance

As an insurance company, Esurance fully appreciates the value

of meaningful data and great customer service. So, it’s no

surprise the Esurance social team was looking for those two

things in its social software.

Esurance was able to get some data directly from the social

networks it was using, but that data wasn’t providing the deeper

insights necessary to understand what its fans and followers

really wanted. With Escape, Esurance easily gets up-to-theminute

data on all of its social properties at any time, and the

social team is able to run the analysis it needs to continually

optimize its pages, promotions and messages for better results.

Better yet, Esurance can now compare its social performance

with its competitors and adjust its strategy accordingly.

Esurance chose Escape because it needed deeper analytical

capabilities and high-end service.

http://www.escapebusinesssolutions.com | info@ escapebusinesssolutions.com

Involvers Social Media 101 in 10 Steps

Posted on by escapebusinesssolutions in Uncategorized

1.    Listen and Locate Fans- Use Involver’s Audience Management Platform to search Twitter and Facebook for mentions of your brand, products, and/or other keywords. This will enable you to identify current and potential fans that you can begin conversations with.

2.    Quality over Quantity- “Consumers are statistics. Customers are people.” Fans or followers should have actual interest and the potential to become a customer or a referral. Even though fan count does increase your ranking within Facebook’s news feed (EdgeRank), it’s more important to connect with users who will take interest, comment, interact, and promote your social media sites to actual friends. The best way to accomplish this is through targeted outreach, influencers, and asking existing fans to “send” and share your content to their own news feeds through Involver’s application suite.

3.    Partner to Build your Audience- What other fan pages share a similar fan base? Set keyword alerts to identify posts from prospective fans that are active on complementary fan pages. When a keyword is spoken make a post related to your fan page to help amplify your reach (e.g. a company producing kitchen accessories monitors and posts to a kitchen appliance fan page to raise their brand awareness and link to their own fan page.)

4.    Cross-Channel Promotion- Make sure you are linking to your fan page from all other channels and sharing product and/or service discounts to your users. Remember, you want new customers, but one of the key ways to reach this goal is by activating your existing customer base and generating earned media. For example: Are you a hotel? Do you have your vanity URL on all checkout slips and receipts?

5.    Login as Your Fan Page- Admins can “Login as Page” and interact as they would from their personal profile. You can also like things and post comments from the brands perspective, creating a more cohesive experience.

6.    Publish Engaging and Valuable Content- Don’t forget that “content is king”. Publish relevant and interesting topics. Make sure to leverage Involver’s thumbnail feature to customize the images attached to posts sent from AMP.

7.    Create Meaningful Relationships- Provide timely updates, share exclusive content, and respond to all fan posts or comments. Using AMP enables you to easily manage task assignment and keep track of follow-up.

8.    Build your Ecosystem- Do you have a YouTube channel? Flickr account? Twitter handle? If it makes sense for your brand/business, set one up. Use our application suite to syndicate your content to your fan page to create a one-stop destination for your fans. With over 40% of Americans on Facebook and spending an increasing amount of time there, it makes sense to consolidate your various media outlets to this platform.

9.    Provide Discounts, not Giveaways- Yes, everyone loves iPads, but do you want your fans thinking of Apple? It’s often times more beneficial to provide incentives for users to buy or try your own products through coupons and/or discounts.

10. Continual Confirmation- Thank and recognize your fans over the long run with shout-outs, gifts, etc.  Does a user consistently provide input and value to your fan page wall? Recognize them even if you don’t offer a gift.

Your engaged customers are your brand advocates and influencers.

What social tips do you use?

Upgrading to Microsoft SharePoint Foundation 2010

Posted on by escapebusinesssolutions in Uncategorized


 

Business continuity management for Microsoft SharePoint Foundation 2010

Posted on by escapebusinesssolutions in Uncategorized

  1. The Visual Studio assemblies for the Activities are stored in the global assembly catalog (GAC).
  2. The XML definition files (.ACTIONS files) are stored in the 14\TEMPLATE\{LCID}\Workflow directory.
  3. An XML entry to mark the activity as an authorized type is stored in the Web.config file for the Web applications in which it is used.

    If your farm workflows use custom actions, you should use a file backup system to protect these files and XML entries. Similar to SharePoint Foundation features such as Web parts and event receivers, these files should be reapplied to the farm as needed after recovery.

  • Workflows that depend on custom code, such as those that are created by using Visual Studio, are stored in two locations. The Visual Studio assemblies for the workflow are stored in the global assembly catalog (GAC), and the XML definition files are stored in the Features directory. This is the same as other types of SharePoint Foundation features such as Web parts and event receivers. If the workflow was installed as part of a solution package, backing up the content database protects these workflows.
  • If you create a custom workflow that interacts with a site collection other than the one where the workflow is deployed, you must back up both site collections to protect the workflow. This includes workflows that write to a history list or other custom list in another site collection. Performing a farm backup is sufficient to back up all site collections in the farm and all workflows that are associated with them.
  • Workflows that are not yet deployed must be backed up and restored separately like any other data file. When you are developing a new workflow but have not yet deployed it to the SharePoint Foundation farm, make sure that you back up the folder where you store your workflow project files by using Windows Backup or another file system backup application.

 

Protecting service applications

Service applications in a SharePoint Foundation environment can be made up of both service settings and one or more databases, or just service settings. You cannot restore a complete service application by restoring the database only; however, you can restore the databases for a service application and then reprovision the service application. For more information, see Restore a service application (SharePoint Foundation 2010).

 

Protecting SQL Server Reporting Services databases

SharePoint Foundation backup and recovery does not include SQL Server Reporting Services databases. You must use SQL Server tools. For more information, see Backup and Restore Operations for a Reporting Services Installation (http://go.microsoft.com/fwlink/?LinkId=186642).

  1. Back up or export the object from the unattached content database.
  2. Restore or import the output of the prior step into SharePoint Foundation 2010.

The following items can be backed up or exported from an unattached database by using granular backup and export, and then restored:

  • Site collection

    Back up by using site collection backup, and then recover by using a site collection restore.

  • Site

    Export, and then import.

  • Lists and libraries

    Export, and then import.

 

You can use import to recover content that you backed up from a database configured to use the SQL FILESTREAM RBS provider. The recovered content will be stored by SharePoint Foundation 2010 using the currently defined storage provider for that content database — that is, if the content database is not set to use RBS, the data will be stored in the content database; if the content database is set to use RBS, the data will be stored in RBS.

  • Related content

     

     

     

     

  • Plan for availability (SharePoint Foundation 2010)

    Updated: June 17, 2010

    This article describes key decisions in choosing availability strategies for a Microsoft SharePoint Foundation 2010 environment.

    As you carefully review your availability requirements, be aware that the higher the level of availability and the more systems that you protect, the more complex and costly your availability solution is likely to be.

    Not all solutions in an organization are likely to require the same level of availability. You can offer different levels of availability for different sites, different services, or different farms.

    In this article:

  • Availability overview

    Availability is the degree to which a SharePoint Foundation environment is perceived by users to be available. An available system is a system that is resilient — that is, incidents that affect service occur infrequently, and timely and effective action is taken when they do occur.

    Availability is part of business continuity management (BCM), and is related to backup and recovery and disaster recovery. For more information about these related processes, see Plan for backup and recovery (SharePoint Foundation 2010) and Plan for disaster recovery (SharePoint Foundation 2010).

     


    Note:

    When calculating availability, most organizations specifically exempt or add hours for planned maintenance activities.

     

    One of the most common measures of availability is percentage of uptime expressed as number of nines — that is, the percentage of time that a given system is active and working. For example, a system with a 99.999 uptime percentage is said to have five nines of availability.

     

     

    The following table correlates uptime percentage with calendar time equivalents.

     

    Acceptable uptime percentage

    Downtime per day

    Downtime per month

    Downtime per year

    95

    72.00 minutes

    36 hours

    18.26 days

    99 (two nines)

    14.40 minutes

    7 hours

    3.65 days

    99.9 (three nines)

    86.40 seconds

    43 minutes

    8.77 hours

    99.99 (four nines)

    8.64 seconds

    4 minutes

    52.60 minutes

    99.999 (five nines)

    0.86 seconds

    26 seconds

    5.26 minutes

     

    If you can make an educated guess about the number of total hours downtime you are likely to have per year, you can use the following formulas to calculate the uptime percentage for a year, a month, or a week:

    % uptime/year = 100 – (8760 – number of total hours downtime per year)/8760

    % uptime/month = 100 – ((24 × number of days in the month) – number of total hours downtime in that calendar month)/(24 × number of days in the month)

    % uptime/week = 100 – (168 – number of total hours downtime in that week)/168

     

    Costs of availability

    Availability is one of the more expensive requirements for a system. The higher the level of availability and the more systems that you protect, the more complex and costly an availability solution is likely to be. When you invest in availability, costs include the following:

    • Additional hardware and software, which can increase the complexity of interactions among software applications and settings.
    • Additional operational complexity.

     

    The costs of improving availability should be evaluated in conjunction with your business needs — not all solutions in an organization are likely to require the same level of availability. You can offer different levels of availability for different sites, different services, or different farms.

     

    Availability is a key area in which information technology (IT) groups offer service level agreements (SLAs) to set expectations with customer groups. Many IT organizations offer various SLAs that are associated with different chargeback levels.

     

     

     

    Determining availability requirements

    To gauge your organization’s tolerance of downtime for a site, service, or farm, answer the following questions:

    • If the site, service, or farm becomes unavailable, will employees be unable to perform their expected job responsibilities?
    • If the site, service, or farm becomes unavailable, will business and customer transactions be stopped, leading to loss of business and customers?

    If you answered yes to either of these questions, you should invest in an availability solution.

  • Choosing an availability strategy and level

    You can choose among many approaches to improve availability in a SharePoint Foundation environment, including the following:

    • Improve the fault tolerance of server hardware components.
    • Increase the redundancy of server roles within a farm.

     

    Hardware component fault tolerance

    Hardware component fault tolerance is the redundancy of hardware components and infrastructure systems such as power supplies at the server level. When planning for hardware component fault tolerance, consider the following:

    • Complete redundancy of every component within a server may be impossible or impractical. Use additional servers for additional redundancy.
    • Ensure that servers have multiple power supplies connected to different power sources for maximum redundancy.

    In any system, we recommend that you work with hardware vendors to obtain fault-tolerant hardware that is appropriate for the system, including redundant array of independent disks (RAID) arrays.

     

    Redundancy within a farm

    SharePoint Foundation 2010 supports running server roles on redundant computers (that is, scaling out) within a farm to increase capacity and to provide basic availability.

    The capacity that you require determines both the number of servers and the size of the servers in a farm. After you have met your base capacity requirements, you may want to add more servers to increase overall availability. The following illustration shows how you can provide redundancy for each server role.

     

     

     

     

     

    Availability within a server farm

     

     

     

     

     

    The following table describes the server roles in a SharePoint Foundation 2010 environment and the redundancy strategies that can be used for each within a farm.

     

    Server role

    Preferred redundancy strategy within a farm

    Front-end Web server

    Deploy multiple front-end Web servers within a farm, and use Network Load Balancing (NLB).

    Application server

    Deploy multiple application servers within a farm.

    Database server

    Deploy database servers by using clustering or high-availability database mirroring.

     

    Database availability strategies

    You can use Microsoft SQL Server failover clustering or SQL Server high-availability database mirroring to support availability of databases in a SharePoint Foundation environment.

     

    SQL Server failover clustering

    Failover clustering can provide availability support for an instance of SQL Server. A failover cluster is a combination of one or more nodes or servers, and two or more shared disks. A failover cluster instance appears as a single computer, but has functionality that provides failover from one node to another if the current node becomes unavailable. SharePoint Foundation can run on any combination of active and passive nodes in a cluster that is supported by SQL Server.

    SharePoint Foundation references the cluster as a whole; therefore, failover is automatic and seamless from the perspective of SharePoint Foundation.

    For detailed information about failover clustering, see Getting Started with SQL Server 2008 Failover Clustering (http://go.microsoft.com/fwlink/?LinkID=102837&clcid=0x409) and Configure availability by using SQL Server clustering (SharePoint Foundation 2010).

     

    SQL Server high-availability mirroring

    Database mirroring is a SQL Server technology that can deliver database redundancy on a per-database basis. In database mirroring, transactions are sent directly from a principal database and server to a mirror database and server when the transaction log buffer of the principal database is written to disk. This technique can keep the mirror database almost up to date with the principal database. SQL Server Enterprise Edition provides additional functionality that improves database mirroring performance.

    For mirroring within a SharePoint Foundation farm, you must use high-availability mirroring, also known as high-safety mode with automatic failover. High-availability database mirroring involves three server instances: a principal, a mirror, and a witness. The witness server enables SQL Server to automatically fail over from the principal server to the mirror server. Failover from the principal database to the mirror database typically takes several seconds.

    A change from previous versions is that SharePoint Foundation is mirroring-aware. After you have configured a database mirror instance of SQL Server, you then use SharePoint Central Administration or Windows PowerShell cmdlets to identify the failover (mirror) database server location for a configuration database, content database, or service application database. Setting a failover database location adds a parameter to the connection string that SharePoint Foundation uses to connect to SQL Server. In the event of a SQL Server time-out event, the following occurs:

  1. The witness server that is configured for SQL Server mirroring automatically swaps the roles of the primary and mirror databases.
  2. SharePoint Foundation automatically attempts to contact the server that is specified as the failover database.

For information about how to configure database mirroring, see Configure availability by using SQL Server database mirroring (SharePoint Foundation 2010).

For general information about database mirroring, see Database Mirroring (http://go.microsoft.com/fwlink/?LinkID=180597).

 


Note:

Databases that have been configured to use the SQL Server FILESTREAM remote BLOB store provider cannot be mirrored.

 

Comparison of database availability strategies for a single farm: SQL Server failover clustering vs. SQL Server high-availability mirroring

The following table compares failover clustering to synchronous SQL Server high-availability mirroring.


 

SQL Server failover clustering

SQL Server high-availability mirroring

Time to failover

Cluster member takes over immediately upon failure.

Mirror takes over immediately upon failure.

Transactional consistency?

Yes

Yes

Transactional concurrency?

Yes

Yes

Time to recovery

Shorter time to recovery (milliseconds)

Slightly longer time to recovery (milliseconds).

Steps required for failover?

Failure is automatically detected by database nodes; SharePoint Foundation 2010 references the cluster so that failover is seamless and automatic.

Failure is automatically detected by the database; SharePoint Foundation 2010 is aware of the mirror location, if it has been configured correctly, so that failover is automatic.

Protection against failed storage?

Does not protect against failed storage, because storage is shared between nodes in the cluster.

Protects against failed storage because both the principal and mirror database servers write to local disks.

Storage types supported

Shared storage (more expensive).

Can use less-expensive direct-attached storage (DAS).

Location requirements

Members of the cluster must be on the same subnet.

Principal, mirror, and witness servers must be on the same LAN (up to 1 millisecond latency roundtrip).

Recovery model

SQL Server full recovery model recommended. You can use the SQL Server simple recovery model, but the only available recovery point if the cluster is lost will be the last full backup.

Requires SQL Server full recovery model.

Performance overhead

Some decrease in performance may occur while a failover is occurring.

High-availability mirroring introduces transactional latency because it is synchronous. It also requires additional memory and processor overhead.

Operational burden

Set up and maintained at the server level.

The operational burden is larger than clustering. Must be set up and maintained for all databases. Reconfiguring after failover is manual.

 

Service application redundancy strategies

The redundancy strategy you follow for protecting service applications that run in a farm varies, depending on where the service application stores data.

 

Service applications that store data in databases

To help protect service applications that store data in databases, you must follow these steps:

  1. Install the service on multiple application servers to provide redundancy within the environment.
  1. Configure SQL Server clustering or mirroring to protect the data.

The following service applications store data in databases:

  • Business Data Connectivity service application
  • Application Registry service application

    We do not recommend mirroring the Application Registry database, because it is only used when upgrading Windows SharePoint Services 3.0 Business Data Catolog information to SharePoint Foundation 2010.

  • Usage and Health Data Collection service application


Note:

We recommend that you do not mirror the Usage and Health Data Collection service application Logging database.
  • Microsoft SharePoint Foundation Subscription Settings service
  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt, type the following command:

Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full | Differential} [-Verbose]

Where <BackUpFolder> is the path of a folder on the local computer or the network in which you want to store the backups.


Note:

If you are backing up the farm for the first time, you must use the Full

option. You must perform a full backup before you can perform a differential backup.

For more information, see Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx).

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

  • Use Central Administration to back up a farm

    You can use Central Administration to back up the farm.

    To back up a farm by using Central Administration

  1. To perform this procedure, you must be a member of the Farm Administrators group on the computer that is running Central Administration.
  2. In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup.
  3. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the farm from the list of components, and then click Next.
  4. On the Start Backup — Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential.


Note:

If you are backing up the farm for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup.
  1. In the Back Up Only Configuration Settings section, click Back up content and configuration settings.
  2. In the Backup File Location section, type the UNC path of the backup folder, and then click Start Backup.
  3. You can view the general status of all backup jobs at the top of the Backup and Restore Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.

    If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 6.

  • Use SQL Server tools to back up a farm

    If you want to back up the complete farm, you must use either Windows PowerShell or Central Administration. You cannot back up the complete farm by using the SQL Server tools because you cannot use the tools to back up the farm’s configuration. However, you can back up all the databases that are associated with the farm.

     

    To back up the databases associated with a farm by using SQL Server tools

  1. To use SQL Server tools to back up SharePoint Foundation 2010 databases, the account that is used to back up the databases must be a member of the SQL Server db_backupoperator fixed database role on the database server where each database is stored.
  2. Open SQL Server Management Studio and connect to the database server.
  3. In Object Explorer, expand Databases.
  4. Right-click the database that you want to back up, point to Tasks, and then click Back Up.
  5. In the Back Up Database dialog box, in the Source area, select the kind of backup that you want to perform from the Backup type list. For more information about which backup type to use, see Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396).
  6. In the Backup component area, click Database.
  7. Either use the default name provided or specify a name for the backup set in the Name text box.
  8. Specify the expiration date for the backup set. This date determines how long, or when, the backup set can be overwritten by any later backups that have the same name. By default, the backup set is set to never expire (0 days).
  9. In the Destination area, specify where you want to store the backup.
  10. Click OK to back up the database.
  11. Repeat steps 1-10 for each farm database.
  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:

Backup-SPConfigurationDatabase -Directory <BackupFolder> -DatabaseServer <DatabaseServerName> -DatabaseName <DatabaseName> -DatabaseCredentials <WindowsPowerShellCredentialObject> [-Verbose]

Where:

  • <BackupFolder> is the path to the folder with the correct backup files.
  • <DatabaseServerName> is the name of the database server for the farm that you are backing up.
  • <DatabaseName> is the name of the farm configuration database.
  • If you are not logged on with an account with db_backupoperator fixed database role on the database server where the configuration database is stored, you must specify the value for DatabaseCredentials

    parameter.

 

For more information, see Backup-SPConfigurationDatabase (http://technet.microsoft.com/library/28ddc176-1b7f-47dd-868f-39b7c403a900(Office.14).aspx).

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

  • Use Central Administration to back up a farm configuration

    You can use Central Administration to back up the configuration of the farm that Central Administration is running on. To back up the configuration of a remote farm, you must use the Central Administration Web site that is running on the remote farm. You cannot use Central Administration to back up an unattached configuration database.

     

    To back up a farm configuration by using Central Administration

  1. Verify that the user account performing this procedure is a member of the Farm Administrators group.
  2. On the Central Administration Home page, in the Backup and Restore section, click Perform a backup.
  3. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the farm from the list of components, and then click Next.


Note:

You can back up the configuration for any service or application. However, common practice is to back up configuration at the farm level.
  1. On the Start Backup — Step 2 of 2: Select Backup Options page, in the Backup Type section, select Full.
  2. In the Backup Only Configuration Settings section, select the Backup only configuration settings option.
  3. In the Backup File Location section, type the Universal Naming Convention (UNC) path of the backup folder, and then click Start Backup.
  4. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually refresh the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.

If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 5.

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin. Additionally, the user account performing this procedure must be a member of the SQL Server db_backupoperator fixed database role on the database server where each database is stored.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:

Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full | Differential} -Item <WebApplicationName> [-Verbose]

Where:

  • <BackupFolder> is the path of the folder you use for storing backup files.
  • <WebApplicationName> is the name of the Web application.


Note:

If you are backing up the Web application for the first time, you must use the Full

option. You must perform a full backup before you can perform a differential backup.

 

For more information, see Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx).

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

  1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group.
  2. In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup.
  3. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the Web application from the list of components, and then click Next.


Note:

The Web application might consist of several components. You must select the top-level component.
  1. On the Start Backup — Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential.


Note:

If you are backing up the Web application for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup.
  1. In the Back Up Only Configuration Settings section, click Back up content and configuration settings.
  2. In the Backup File Location section, type the Universal Naming Convention (UNC) path of the backup folder, and then click Start Backup.
  3. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.

    If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 6.

  1. Verify that the user account that is used to back up the databases is a member of the SQL Server db_backupoperator fixed database role on the database server where each database is stored. Additionally, verify that the user account has Full Control permissions on the backup folder.
  2. Open SQL Server Management Studio and connect to the database server.
  3. In Object Explorer, expand Databases.
  4. Right-click the database that you want to back up, point to Tasks, and then click Back Up.
  5. In the Back Up Database dialog box, in the Source area, select the kind of backup that you want to perform from the Backup type list. For more information about which backup type to use, see Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396).
  6. In the Backup component area, click Database.
  7. Either use the default name provided or specify a name for the backup set in the Name text box.
  8. Specify the expiration date for the backup set. This date determines how long, or when, the backup set can be overwritten by any later backups that have the same name. By default, the backup set is set to never expire (0 days).
  9. In the Destination area, specify where you want to store the backup.
  10. Click OK to back up the database.
  11. Repeat steps 1-10 for each database that is associated with the Web application.
  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt, type the following command:

    Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full | Differential} -Item <ServiceApplicationName> [-Verbose]

     

    Where:

  • <BackupFolder> is the path of a folder on the local computer or on the network in which you want to store the backups.
  • <ServiceApplicationName> is the name of the service application that you want to back up.


Note:

To back up all the service applications, at the Windows PowerShell command prompt, type the following command:

Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full | Differential} -Item “Farm\Shared Service Applications” [-Verbose]


Note:

If you are backing up the service application for the first time, you must use the Full

option. You must perform a full backup before you can perform a differential backup.

Some service applications always require a full backup. For these service applications, even if you select the Differential

option, the system performs a full backup.

 

For more information, see Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx).

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

  • Use Central Administration to back up a service application

    You can use Central Administration to back up a service application.

     

    To back up a service application by using Central Administration

  1. Verify that the user account that performs this procedure is a member of the Farm Administrators group.
  2. In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup.
  3. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the service application from the list of components, and then click Next. To back up all the service applications, select the Shared Service Applications node.


Note:

The service application might consist of several components. You must select the top-level component.
  1. On the Start Backup — Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential.


Note:

If you are backing up the service application for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup.

Some service applications always require a full backup. For these service applications, the system performs a full backup even if you select the Differential option.
  1. In the Backup File Location section, in the Backup location box, type the path of the backup folder, and then click Start Backup.
  2. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.

    If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 5.

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt type the following command:

    Backup-SPSite -Identity <Site collection name> -Path <backup file> [-Force] [-NoSiteLock] [-UseSqlSnapshot] [-Verbose]

    If you want to overwrite a previously used backup file, use the Force

    parameter. You can use the NoSiteLock

    parameter to keep the read-only lock from being set on the site collection while it is being backed up. However, using this parameter can allow users to change the site collection while it is being backed up and might lead to possible data corruption during backup.

    If the database server is running an Enterprise Edition of Microsoft SQL Server, we recommend that you also use the UseSqlSnapshot

    parameter for more consistent backups. You can also export sites or lists from these snapshots.


Important:

When you perform a backup that uses the UseSqlSnapshot

parameter, a backup will be completed successfully. However, you will see an error similar to the following:

Backup-SPSite : Operation is not valid due to the current state of the object.

At line:1 char:14

+ Backup-SPSite <<<< http://site -Path + CategoryInfo : NotSpecified: (:) [Backup-SPSite], InvalidOperationException + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.SharePoint.PowerShell.SPCmdletBackupSite\\yourpath


Note:

If the RBS provider that you are using does not support snapshots, you cannot use snapshots for content deployment or backup. For example, the SQL FILESTREAM provider does not support snapshots.

For more information about using SQL snapshots, see Back up databases to snapshots (SharePoint Foundation 2010).

For more information, see Backup-SPSite (http://technet.microsoft.com/library/d4c31a1a-82a7-425f-b1bb-22e70bedd338(Office.14).aspx).


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

  • Use Central Administration to back up a site collection

    You can use Central Administration to back up a site collection.

    To back up a site collection by using Central Administration

  1. Verify that the user account performing this procedure is a member of the Farm Administrators group. Additionally, verify that the Windows SharePoint Services Timer V4 service has Full Control permissions on the backup folder.
  2. In Central Administration, on the Home page, in the Backup and Restore section, click Perform a site collection backup.
  3. On the Site collection backup page, select the site collection from the Site Collection list.
  4. Type the local path of the backup file in the Filename box.


Note:

If you want to reuse a file, select the Overwrite existing file check box.
  1. Click Start Backup.
  2. You can view the general status of all backup jobs at the top of the Granular Backup Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Site Collection Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.

    If you receive any errors, you can review them in the Failure Message column of the Granular Backup Job Status page.

  1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group.
  2. In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup.
  3. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select Solutions, and then click Next.

    You can also select an individual solution, if you only want to back up a single solution.

  4. On the Start Backup — Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential.


Note:

If you are backing up the solution for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup.
  1. In the Backup File Location section, type the Universal Naming Convention (UNC) path of the backup folder, and then click Start Backup.
  2. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status of the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.

    If you receive any errors, review the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 4.

 

To back up trusted solutions by using Windows PowerShell

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt, type the following command to back up all of the solutions in the farm. To back up a single solution, add the name of the solution to the item path “farm\solutions”.

Backup-SPFarm -backupmethod full -directory <UNC location> -item “farm\solutions”

Where:

  • <UNC location> is UNC location of the directory that you want to back up to.

For more information, see Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx).

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

 

Backing up sandboxed solutions

You cannot back up only sandboxed solutions. Instead, you must back up the farm, Web application, or content database with which the sandboxed solution is associated. For more information about these methods of backing up, see Related content.

  1. The Visual Studio 2010 assemblies for the actions are stored in the global assembly cache (GAC).
  2. The XML definition files (.ACTIONS files) are stored in the 14\TEMPLATE\<LCID>\Workflow directory.
  3. An XML entry to mark the action as an authorized type is stored in the Web.config file for the Web applications in which it is used.

    If the farm workflows use custom actions, you should use a file backup system to protect these files and XML entries. Similar to SharePoint Foundation features such as Web Parts and event receivers, these files should be reapplied to the farm as needed after recovery.

  • Workflows that depend on custom code, such as those that are created by using Visual Studio 2010, are stored in two locations. The Visual Studio 2010 assemblies for the workflow are stored in the GAC, and the XML definition files are stored in the Features directory. This is the same as other types of SharePoint Foundation features such as Web Parts and event receivers. If the workflow was installed as part of a solution package, backing up the farm, Web application, content database, or site collection protects these workflows.
  • If you create a custom workflow that interacts with a site collection other than the one where the workflow is deployed, you must back up both site collections to protect the workflow. This includes workflows that write to a history list or other custom list in another site collection. Performing a farm backup is sufficient to back up all site collections in the farm and all workflows that are associated with them.
  • Workflows that are not yet deployed must be backed up and restored separately. When you are developing a new workflow but have not yet deployed it to the SharePoint Foundation farm, make sure that you back up the folder where you store the workflow project files by a file system backup application.
  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:

    Backup-SPFarm -Directory <Backup folder> -BackupMethod {Full | Differential} -Item <Content database name> [-Verbose]


Note:

If you are backing up the content database for the first time, you must use the Full

option. You must perform a full backup before you can perform a differential backup.

For more information, see Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx)

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

  • Use Central Administration to back up a content database

    You can use Central Administration to back up a content database.

    To back up a content database by using Central Administration

  1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group.
  2. In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup.
  3. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the content database that you want to back up from the list of components, and then click Next.


Note:

Not all content databases can be selected in the list. If a database is not selectable, you must use Windows PowerShell to back up the content database.
  1. On the Start Backup — Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential.


Note:

If you are backing up the content database for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup.
  1. In the Backup File Location section, type the Universal Naming Convention (UNC) path of the backup folder, and then click Start Backup.
  2. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status of the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.

    If you receive any errors, review the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 4.

  • Use SQL Server tools to back up a content database

    You can use SQL Server tools to back up a content database.

     

    To back up a content database by using SQL Server tools

  1. Verify that the user account that is performing this procedure is a member of the SQL Server db_backupoperator fixed database role on the database server where each database is stored.
  2. Open SQL Server Management Studio and connect to the database server.
  3. In Object Explorer, expand Databases.
  4. Right-click the database that you want to back up, point to Tasks, and then click Back Up.
  5. In the Back Up Database dialog box, in the Source area, select the kind of backup that you want to perform from the Backup type list. For more information about which backup type to use, see Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396) in SQL Server Books Online.
  6. In the Backup component area, click Database.
  7. Either use the default name provided or specify a name for the backup set in the Name text box.
  8. Specify the expiration date for the backup set. This date determines how long, or when, the backup set can be overwritten by any later backups that have the same name. By default, the backup set is set to never expire (0 days).
  9. In the Destination area, specify where you want to store the backup.
  10. Click OK to back up the database.
  11. Repeat steps 1-9 for each content database that you want to back up.
  1. Verify that the account that is used to back up the databases is a member of the SQL Server db_owner fixed database role.
  2. Open SQL Server Management Studio and connect to the database server.
  3. In Object Explorer, expand Databases.
  4. Select the database that you want to back up, and then click New Query.
  5. Copy the following text, and then paste it to the query pane.

CREATE DATABASE <snapshot name>
ON
(
NAME=<logical name of the database file>,
FILENAME = ‘c:\WSS_Backup1.ss’)
AS SNAPSHOT OF <database name>;
  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:

    Export-SPWeb -Identity <Site URL> -Path <Path and file name> [-ItemUrl <URL of site, list, or library>] [-IncludeUserSecurity] [-IncludeVersions] [-NoFileCompression] [-GradualDelete] [-Verbose]

    If you are exporting a large site, list, or document library, you can use the GradualDelete

    parameter. When this parameter is used, the site collection is marked as deleted, which immediately prevents any further access to its content. The data in the deleted site collection is then deleted gradually over time by a timer job instead of all at once, which reduces its impact on the performance of farm servers and SQL Server.

    To specify which version of the site, list, or document library to include, use the IncludeVersions

    parameter and specify “LastMajor” (default), “CurrentVersion”, “LastMajorandMinor”, or “All”. To include the user security settings with the list or document library, use the IncludeUserSecurity

    parameter. If you want to overwrite the file that you specified, use the Force

    parameter. To view the progress of the backup operation, use the Verbose

    parameter.

    The NoFileCompression

    parameter lets you specify that no file compression is performed during the export process. Using this parameter can lower resource usage up to 30% during the export process. Using this parameter will result in a backup folder being created instead of a compressed file. If you use the NoFileCompression

    parameter in the Export-SPWeb

    command, you must also use it when you import the content by using the Import-SPWeb

    command.

For more information, see Export-SPWeb (http://technet.microsoft.com/library/cd85bf19-6f24-4f13-bd9c-37bbf279ea2b(Office.14).aspx)

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

  • Use Central Administration to export a site, list, or document library

    You can use Central Administration to export a site, list, or document library. You can only export one site, list, or document library at a time.

     

    To export a site, list, or document library by using Central Administration

  1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group.
  2. In Central Administration, on the Home page, click Backup and Restore.
  3. On the Backup and Restore page, in the Granular Backup section, click Export a site or list.
  4. On the Site or List Export page, in the Site Collection section, select the site collection from the Site Collection list, and then select the site from the Site list.
  5. If you are exporting a site, skip this step, Select the list or document library from the List list.
  6. In the File Location section, in the Filename box, type the UNC path of the shared folder and the file to which you want to export the list or document library. The file name must use the .cmp extension.
  7. If the file already exists and you want to use this file, select the Overwrite existing files check box. Otherwise, specify a different file name.
  8. If you want to export all the security and permissions settings with the list or library, in the Export Full Security section, select the Export full security check box.
  9. If you want to specify which version of the list or library to export, select one of the following versions from the Export versions list:
  • All Versions
  • Last Major
  • Current Version
  • Last Major and Last Minor
  1. When you have specified the settings that you want, click Start Export.
  2. You can view the status of all backup jobs at the top of the Granular Backup Job Status page. You can view the status of the current backup job in the Content Export section of the page. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.

    If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the <file name>.export.log file at the UNC path that you specified in step 6.

 

 

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt, type the following command:

    Merge-SPLogFile -Path “<path to merged log file>.log” -Overwrite

    For example, Merge-SPLogFile -Path “C:\Logs\MergedFiles\AllFarm_merged_12.20.2009.log” -Overwrite


Important:

Merging all log entries for all farm servers can take a long time and use resources. We recommend filtering the entries to match a specific set of criteria before merging.

To merge log entries that match a specific set of criteria, type the following command:

Merge-SPLogFile -Path “<path to merged log file>.log” -Area “<Area>” -Category “<Category>”

You can filter by one or more of the following:

  • Area (one or more, wildcard)
  • Category (one or more, wildcard)
  • Level
  • Correlation (one or more)
  • EventID (one or more, wildcard)
  • Message (wildcard)
  • StartTime
  • EndTime
  • Process (one or more, wildcard)
  • ThreadID (one or more)


Tip:

You can name the merged log file however you want. We recommend that you use a naming convention that makes it easy to determine what the log file contains, such as “<date merged>_<farm name>_<filtering criteria>. For example, to signify all the farm server log entries forSharePoint Foundation 2010 that involve the database category and are marked as “High” use, “Dec_2009_ContosoInternet_Foundation_Database_High.log”.

 

For more information, see Merge-SPLogFile (http://technet.microsoft.com/library/759702d7-bda2-4302-9345-abb43b609ad4(Office.14).aspx)

 

To archive diagnostic logs for a specific server by using Windows PowerShell

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt, type the following command:

    Copy-Item <Log folder path> -Destination <Archive folder path> -Recurse

For more information, type Get-Help Copy-Item -Full

.

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

 

 

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:

    Add-SPShellAdmin -Username <User account> -Database <Database ID>

    To add a user account to all the databases in the farm, type the following command, and then press ENTER:

    ForEach ($db in Get-SPDatabase) {Add-SPShellAdmin -Username <User account> -Database $db}

    To remove a user account from all the databases in the farm, type the following command, and then press ENTER:

    ForEach ($db in Get-SPDatabase) {Remove-SPShellAdmin -Username <User account> -Database $db}

    To view the user accounts currently added to the databases in the farm, type the following command, and then press ENTER:

    ForEach ($db in Get-SPDatabase) {Get-SPShellAdmin -Database $db}

For more information, see Add-SPShellAdmin (http://technet.microsoft.com/library/2ddfad84-7ca8-409e-878b-d09cb35ed4aa(Office.14).aspx)

You might also have to grant additional permissions to the users running the backup or restore operation by using Windows PowerShell. The following table shows the permissions that are required.

 

Required permissions for Windows PowerShell

 

Farm component

Member of Administrators group on the local computer

Member of Farm Administrators SharePoint group

Full Control on backup folder

Farm

Yes

No

Yes

Content database

Yes

No

Yes

Site collection

No

Yes

Yes

Site, list, document library

Yes

No

Yes

 

 

 

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:

    Add-SPShellAdmin -Username <User account> -Database <Database ID>

    To add a user account to all the databases in the farm, type the following command, and then press ENTER:

    ForEach ($db in Get-SPDatabase) {Add-SPShellAdmin -Username <User account> -Database $db}

    To remove a user account from all the databases in the farm, type the following command, and then press ENTER:

    ForEach ($db in Get-SPDatabase) {Remove-SPShellAdmin -Username <User account> -Database $db}

    To view the user accounts currently added to the databases in the farm, type the following command, and then press ENTER:

    ForEach ($db in Get-SPDatabase) {Get-SPShellAdmin -Database $db}

 

For more information, see Add-SPShellAdmin (http://technet.microsoft.com/library/2ddfad84-7ca8-409e-878b-d09cb35ed4aa(Office.14).aspx)

You might also have to grant additional permissions to the users running the backup or restore operation by using Windows PowerShell. The following table shows the permissions that are required.

 

Required permissions for Windows PowerShell

 

Farm component

Member of Administrators group on the local computer

Member of Farm Administrators SharePoint group

Full Control on backup folder

Farm

Yes

No

Yes

Service application

Yes

No

Yes

Content database

Yes

No

Yes

Site collection

No

Yes

Yes

Site, list, document library

Yes

No

Yes

 

 

 

  1. The change logs for all databases are retained when you restore a farm.
  2. The change log for content databases is retained when you reattach or restore a database.

    When a database ID and change log are retained, the search system continues crawling based on the regular schedule that is defined by crawl rules.

    When you restore an existing database and do not use the overwrite option, a new ID is assigned to the restored database, and the database change log is not preserved. The next crawl of the database will add data from the content database to the index.

    If a restore is performed and the ID in the backup package is already being used in the farm, a new ID is assigned to the restored database and a warning is added to the restore log. The ability to perform an incremental crawl instead of a full crawl depends on the content database ID being the same as before and the change log token that is used by the search system being valid for the current change log in the content database. If the change log is not preserved, the token is not valid and the search system has to perform a full crawl.

  • SharePoint Foundation 2010 backup backs up the Business Data Connectivity service external content type definitions but does not back up the data source itself. To protect the data, you should back up the data source when you back up the Business Data Connectivity service or the farm.

    If you restore the Business Data Connectivity service or the farm and then restore the data source to a different location, you must change the location information in the external content type definition. If you do not, the Business Data Connectivity service might be unable to locate the data source.

  • SharePoint Foundation 2010 restores remote Binary Large Objects (BLOB) stores only if you are using the FILESTREAM remote BLOB store provider to put data in remote BLOB stores.

    If you are using another provider, you must manually restore the remote BLOB stores.

  • If a user has taken copies of content for off-line editing in Microsoft SharePoint Workspace 2010 and the content is restored from a backup on the server, when the user re-connects, the server automatically synchronizes the off-line content with the restored content. This might result in data loss on the user’s copies of the content.
  • If you are sharing service applications across farms, be aware that trust certificates that have been exchanged are not included in farm backups. You must back up your certificate store separately or retain the certificates in a separate location. When you restore a farm that shares a service application, you must import and redeploy the certificates, and then re-establish any inter-farm trusts.

    For more information, see Exchange trust certificates between farms (SharePoint Foundation 2010) (http://technet.microsoft.com/library/679d334b-913d-49b3-b086-66a60093b261(Office.14).aspx)

  • After a Web application that is configured to use claims-based authentication has been restored, duplicate or additional claims providers are often visible. If duplicates appear, you must then manually save each Web application zone to remove them. For more information, see Restore a Web application (SharePoint Foundation 2010).
  • Additional steps are required when you restore a farm that contains a Web application that is configured to use forms-based authentication. For more information, see Restore a Web application (SharePoint Foundation 2010).

  • Use Windows PowerShell to restore a farm

    You can use Windows PowerShell to restore a farm.

    To restore a farm by using Windows PowerShell

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt, type the following command:

Restore-SPFarm -Directory <BackupFolder> -RestoreMethod Overwrite [-BackupId <GUID>]

Where:

  • <BackupFolder> is the path of the folder you use for storing backup files.
  • <GUID> is the identifier of the backup to restore from.


Note:

If you are not logged on as the Farm account, you are prompted for the Farm account’s credentials.

If you do not specify the BackupId

, the most recent backup will be used. To view the backups for the farm, type the following command:

Get-SPBackupHistory -Directory <BackupFolder> -ShowBackup [-Verbose]

Where:

  • <BackupFolder> is the path of the folder you use for storing backup files.

    You cannot use a configuration-only backup to restore content databases together with the configuration.

  1. To restart a service application, type the following command:

Start-SPServiceInstance -Identity <ServiceApplicationID>

Where:

For more information about restoring the farm by using Windows PowerShell, see Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx)

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

  • Use Central Administration to restore a farm

    You can use the Central Administration Web site to restore a farm.

     

    To restore a farm by using Central Administration

  1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
  2. In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup.
  3. On the Restore from Backup — Step 1 of 3: Select Backup to Restore page, from the list of backups, select the backup job that contains the farm backup, and then click Next. You can view more details about each backup by clicking the (+) next to the backup.


Note:

If the correct backup job does not appear, in the Backup Directory Location text box, type the Universal Naming Convention (UNC) path of the correct backup folder, and then click Refresh.

You cannot use a configuration-only backup to restore the farm.
  1. On the Restore from Backup  — Step 2 of 3: Select Component to Restore page, select the check box that is next to the farm, and then click Next.
  2. On the Restore from Backup — Step 3 of 3: Select Restore Options page, in the Restore Component section, ensure that Farm appears in the Restore the following component list.

    In the Restore Only Configuration Settings section, ensure that the Restore content and configuration settings option is selected.

    In the Restore Options section, under Type of Restore, select the Same configuration option. A dialog box will appear that asks you to confirm the operation. Click OK.


Note:

If the Restore Only Configuration Settings section does not appear, the backup that you selected is a configuration-only backup. You must select another backup.

Click Start Restore.

  1. You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start.

    If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 3.

  2. When the restore process has completed, you may need to restart one or more service applications. In Central Administration, on the Home page, in the Application Management section, click Manage services on server.
  3. On the Services on Server page, start any services related to service applications that you want to run by clicking Start in the Actions column next to the service application.
  4. Re-establish any trust relationships. For more information, see Exchange trust certificates between farms (SharePoint Foundation 2010) (http://technet.microsoft.com/library/679d334b-913d-49b3-b086-66a60093b261(Office.14).aspx).

  • Use SQL Server tools to restore a farm

    Although you cannot restore the complete farm by using SQL Server tools, you can restore most of the farm databases. If you restore the databases by using SQL Server tools, you must restore the farm configuration by using Central Administration or Windows PowerShell. For more information about how to restore the farm’s configuration settings, see Restore a farm configuration (SharePoint Foundation 2010).

     


    Note:

    The search index is not stored in SQL Server. If you use SQL Server tools to back up and restore search, you must perform a full crawl after you restore the content database.

     

    Before you restore SharePoint Foundation 2010, we recommend that you configure a recovery farm for site and item recovery.

    Restore the databases by following these steps:

  1. If possible, back up the live transaction log of the current database to protect any changes that were made after the last full backup.
  2. Restore the last full database backup.
  3. Restore the most recent differential database backup that occurred after the most recent full database backup.
  4. Restore all transaction log backups that occurred after the most recent full or differential database backup.

 

To restore a farm by using SQL Server tools

  1. Verify that the user account that is performing this procedure is a member of the sysadmin fixed server role.
  2. If the Windows SharePoint Services Timer service is running, stop the service and wait for several minutes for any currently running stored procedures to finish. Do not restart the service until after you restore all the databases that you have to restore.
  3. Start SQL Server Management Studio and connect to the database server.
  4. In Object Explorer, expand Databases.
  5. Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database.

    The database is automatically taken offline during the recovery operation and cannot be accessed by other processes.

  6. In the Restore Database dialog box, specify the destination and the source, and then select the backup set or sets that you want to restore.

    The default values for destination and source are appropriate for most recovery scenarios.

  7. In the Select a page pane, click Options.
  8. In the Restore options section, select only Overwrite the existing database. Unless your environment or policies require otherwise, do not select the other options in this section.
  9. In the Recovery state section:
  • If you have included all the transaction logs that you must restore, select RECOVER WITH RECOVERY.
  • If you must restore additional transaction logs, select RECOVER WITH NORECOVERY.
  • The third option, RECOVER WITH STANDBY is not used in this scenario.


Note:

For more information about these recovery options, see Restore Database (Options Page) (http://go.microsoft.com/fwlink/?LinkId=114420).
  1. Click OK to complete the recovery operation.
  2. Except for the configuration database, repeat steps 4 through 9 for each database that you are restoring.

 

 

  1. To restore the configuration settings, you must use the existing configuration database or manually create a new database and restore the configuration to that database. For more information about restoring the farm configuration, see Restore a farm configuration (SharePoint Foundation 2010).
  2. Start the Windows SharePoint Services Timer service.
  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. From the Windows PowerShell command prompt (that is, PS C:\>), type the following command and press ENTER:

    Restore-SPFarm -Directory <RestoreShare> -RestoreMethod Overwrite -ConfigurationOnly

    You must use the ConfigurationOnly

    parameter. To view the progress of the operation, use the Verbose

    parameter.

For more information, see Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx)

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

  • Use Central Administration to restore a farm’s configuration

    You can use Central Administration to restore a farm’s configuration.

    To restore a farm’s configuration by using Central Administration

  1. Ensure that you are a member of the Farm Administrators SharePoint group on the computer that is running Central Administration and a member of the sysadmin fixed server role on the database server where each database is stored.
  2. In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup.
  3. On the Restore from Backup — Step 1 of 3: Select Backup to Restore page, select the backup job that contains the farm backup from the list of backups, and then click Next.


Note:

You can view additional information about the backups by expanding the row that contains the backup.


Note:

If the correct backup job does not appear, in the Backup Directory Location text box, enter the UNC path of the correct backup folder, and then click Refresh.
  1. On the Restore from Backup  — Step 2 of 3: Select Component to Restore page, select the check box that is next to the farm, and then click Next.
  2. On the Restore from Backup  — Step 3 of 3: Select Restore Options page, in the Restore Component section, ensure that “Farm” appears in the Restore the following content list.

    In the Restore Only Configuration Settings section, ensure that the Restore content and configuration settings option is selected.

    In the Restore Options section, select the Type of Restore option. Use the Same configuration setting. A dialog box will appear that asks you to confirm the operation. Click OK.


Note:

If the Restore Only Configuration Settings section does not appear, then the backup that you selected is a configuration-only backup.

Click Start Restore.

  1. You can view the general status of all recovery jobs at the top of the Backup and Restore Status page in the Readiness section. You can view the status of the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start.

    If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 2.

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. Using Notepad, create a text file and then copy and paste the following script into the file. The commands in the example create XML files that document the configurations of the Web applications and service applications in the current farm. Choose only those commands that are relevant to your environment.

##
## Common SharePoint configuration settings
##
#Retrieve Web Application information. The default depth of 2 does not return much detail–we recommend that you use a depth of 4 for this cmdlet.
Get-SPWebApplication | Export-Clixml .\ WebAppFilename.xml -depth 4

#Retrieve custom layout information.
Get-SPWebApplication | Get-SPCustomLayoutsPage | Export-Clixml .\Get-SPCustomLayoutsPage.xml

#Determine how SharePoint designer access is configured
Get-SPWebApplication | Get-SPDesignerSettings | Export-Clixml .\Get-SPDesignerSettings.xml

#Retrieve information about alternate access mapping
Get-SPAlternateURL | Export-Clixml .\Get-SPAlternateURL.xml

#Retrieve information about content databases
Get-SPContentDatabase | Export-Clixml .\Get-SPContentDatabase.xml

#Retrieve database properties for each database
Get-SPDatabase | Export-Clixml .\Get-SPDatabase.xml

#Retrieve information about all SharePoint Products installed in the farm, and the versions of all updates installed for each product.
Get-SPProduct | Export-Clixml .\Get-SPProduct.xml

#Retrieve farm information
Get-SPFarm | Export-Clixml .\Get-SPFarm.xml
Get-SPFarmConfig | Export-Clixml .\Get-SPFarmConfig.xml

#Retrieve information about the servers in the farm
Get-SPServer | Export-Clixml .\Get-SPServer.xml

#Retrieve information about installed features
Get-SPFeature | Export-Clixml .\Get-SPFeature.xml

#Retrieve information about globally-installed site templates
Get-SPWebTemplate | Export-Clixml .\Get-SPWebTemplate.xml

#Retrieve information about deployed solutions
Get-SPSolution | Export-Clixml .\Get-SPSolution.xml

#Retrieve information about sandboxed solutions deployed in a site collection
Get-SPSite | Get-SPUserSolution | Export-Clixml .\Get-SPUserSolution.xml

#Retrieve information about installed Help
Get-SPHelpCollection | Export-Clixml .\Get-SPHelpCollection.xml

#Retrieve information about the logging levels that have been set
Get-SPLogLevel | Export-Clixml .\Get-SPLogLevel.xml

#Retrieve information about the sites in the farm
Get-SPSite | Export-Clixml .\Get-SPSite.xml
Get-SPSiteAdministration | Export-Clixml .\Get-SPSiteAdministration.xml
Get-SPSiteSubscription | Export-Clixml .\Get-SPSiteSubscription.xml

#Retrieve ULS logging information
Get-SPDiagnosticConfig | Export-Clixml .\Get-SPDiagnosticConfig.xml
Get-SPDiagnosticsPerformanceCounter | Export-Clixml .\Get-SPDiagnosticsPerformanceCounter.xml
Get-SPDiagnosticsProvider | Export-Clixml .\Get-SPDiagnosticsProvider.xml

#Retrieve information about accounts registered in the configuration database
Get-SPManagedAccount | Export-Clixml .\Get-SPManagedAccount.xml
Get-SPProcessAccount | Export-Clixml .\Get-SPProcessAccount.xml
Get-SPShellAdmin | Export-Clixml .\Get-SPShellAdmin.xml

#Retrieve information about the Mobile Messaging account.
Get-SPWebApplication | Get-SPMobileMessagingAccount | Export-Clixml .\Get-SPMobileMessagingAccount.xml

##
##Common service infrastructure settings
##
#Retrieve information about the service applications in the farm
Get-SPServiceApplication | Export-Clixml .\Get-SPServiceApplication.xml
Get-SPServiceApplicationPool | Export-Clixml .\Get-SPServiceApplicationPool.xml
Get-SPServiceApplicationProxy | Export-Clixml .\Get-SPServiceApplicationProxy.xml
Get-SPServiceApplicationProxyGroup | Export-Clixml .\Get-SPServiceApplicationProxyGroup.xml
Get-SPServiceApplication | Get-SPServiceApplicationEndpoint | Export-Clixml .\Get-SPServiceApplicationEndpoint.xml

#Retrieve information about the services running in the farm
Get-SPServiceInstance | Export-Clixml .\Get-SPServiceInstance.xml

#Retrieve information about common Web service settings
Get-SPServiceHostConfig | Export-Clixml .\Get-SPServiceHostConfig.xml

##
## Common service application configurations
##

#Application Discovery and Load Balancer Service Application
Get-SPTopologyServiceApplication | Export-Clixml .\Get-SPTopologyServiceApplication.xml
Get-SPTopologyServiceApplicationProxy | Export-Clixml .\Get-SPTopologyServiceApplicationProxy.xml

#Business Data Connectivity Service
#Retrieve information about data connection files. ###WARNING: The following cmdlet requires run as administrator rights
Get-SPDataConnectionFile | Export-Clixml .\Get-SPDataConnectionFile.xml
###WARNING: The following cmdlet requires run as administrator rights
Get-SPDataConnectionFile | Get-SPDataConnectionFileDependent | Export-Clixml .\Get-SPDataConnectionFileDependent.xml

#Security Token Service Application
#Retrieve information about the security token service used for incoming SOAP messages.
Get-SPSecurityTokenServiceConfig | Export-Clixml .\Get-SPSecurityTokenServiceConfig.xml

#Usage and Health data collection
#Retrieve information about the Usage and Health Data Collection service application.
Get-SPUsageApplication | Export-Clixml .\Get-SPUsageApplication.xml
Get-SPUsageDefinition | Export-Clixml .\Get-SPUsageDefinition.xml
Get-SPUsageService | Export-Clixml .\Get-SPUsageService.xml

###Note: These cmdlets are commented out because you are unlikely to want to run them. ###
#Get-SPSite | %{$web=Get-SPWeb $_.Url;$webid=$web.Id;$web | Get-SPUser | Export-Clixml .\Get-SPUser-$webid.xml}

# Get-SPSite | %{$web=Get-SPWeb $_.Url;$webid=$web.Id;$web | Export-Clixml .\Get-SPWeb-$webid.xml}
  1. To run the script, in the Windows PowerShell console, at the command prompt (that is, PS C:\>), type the following command and press ENTER:C:\<path>\<filename>.ps1

 

For more information, see Export-Clixml (http://technet.microsoft.com/en-us/library/dd347657.aspx) Get-SPWebApplication (http://technet.microsoft.com/library/11d6521f-f99c-433e-9ab5-7cf9e953457a(Office.14).aspx), Get-SPServiceApplication (http://technet.microsoft.com/library/71a467dc-3b95-4b65-af93-0d0d6ebb8326(Office.14).aspx).

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt, type the following command to document the current Web application URLs and content database mappings.

Get-SPWebApplication | %{$_.Name;$_.Url;%{$_.ContentDatabases|%{$_.Name};Write-Host “”}}
  1. Either dismount all content databases, as in the following example:

Get-SPContentDatabase | Dismount-SPContentDatabase

Or dismount a specific content database, as in the following example:

Get-SPContentDatabase WSS_Content | Dismount-SPContentDatabase
  1. Back up the farm.

Backup-SPFarm -Directory \\servername\share -BackupMethod Full


Note:

You can view the progress of the backup by looking at the \\servername\share\spbr####\spbackup.log file.
  1. After the backup is complete, re-mount the content databases. Replace <WSS_Content> and <http://servername&gt; with each of the mappings documented in step 5).

Mount-SPContentDatabase -Name <WSS_Content> -WebApplication <http://servername&gt;
  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt, type the following command:

Restore-SPFarm -Directory <BackupFolderName> -RestoreMethod Overwrite -Item  <WebApplicationName> [-BackupId <GUID>] [-Verbose]

Where:

  • <BackupFolderName> is the full path to the folder you use for backup files.
  • <WebApplicationName> is the name of the Web application that was backed up.
  • <GUID> is the identifier of the back up to use for the restore operation.

    If you do not specify the value of the BackupID

    parameter, the most recent backup will be used. You cannot restore a Web application by using a configuration-only backup. You can view the backups for the farm by typing the following:

Get-SPBackupHistory -Directory <BackupFolderName> -ShowBackup

For more information, see Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx).

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

  1. Verify that the user account performing this procedure is a member of the Farm Administrators group. Additionally, verify that the Windows SharePoint Services Timer V4 service and the Farm Database Access account have Full Control permissions on the backup folder.
  2. In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup.
  3. On the Restore from Backup — Step 1 of 3: Select Backup to Restore page, from the list of backups, select the backup job that contains the farm or Web application backup, and then click Next. You can view more details about each backup by clicking the (+) next to the backup.


Note:

If the correct backup job does not appear, in the Current Directory Location text box, type the Universal Naming Convention (UNC) path of the correct backup folder, and then click Refresh.

You cannot use a configuration-only backup to restore the Web application.
  1. On the Restore from Backup — Step 2 of 3: Select Component to Restore page, select the check box that is next to the Web application, and then click Next.
  2. On the Restore from Backup — Step 3 of 3: Select Restore Options page, in the Restore Component section, make sure that Farm\<Web application> appears in the Restore the following content list.

    In the Restore Only Configuration Settings section, make sure that the Restore content and configuration settings option is selected.

    In the Restore Options section, under Type of Restore, select the Same configuration option. A dialog box appears that asks you to confirm the operation. Click OK.


Note:

If the Restore Only Configuration Settings section does not appear, the backup that you selected is a configuration-only backup. You must select another backup.

Click Start Restore.

  1. You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start.

    If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified.

  • Use SQL Server tools to restore databases associated with a Web application

    You cannot restore the complete Web application by using SQL Server tools. However, you can restore all the databases that are associated with the Web application. To restore the complete Web application, use either Windows PowerShell or Central Administration.

    To restore databases associated with a Web application by using SQL Server tools

  1. Verify that the user account performing this procedure is a member of the sysadmin fixed server role.
  2. If the Windows SharePoint Services Timer service is running, stop the service and wait for several minutes for any currently running stored procedures to finish. Do not restart the service until after you restore the databases.
  3. Start SQL Server Management Studio and connect to the database server.
  4. In Object Explorer, expand Databases.
  5. Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database.

    The database is automatically taken offline during the recovery operation and cannot be accessed by other processes.

  6. In the Restore Database dialog box, specify the destination and the source, and then select the backup set or sets that you want to restore.

    The default values for destination and source are appropriate for most recovery scenarios.

  7. In the Select a page pane, click Options.
  8. In the Restore options section, select only Overwrite the existing database. Unless the environment or policies require otherwise, do not select the other options in this section.
  9. In the Recovery state section:
  • If you have included all the transaction logs that you must restore, select RECOVER WITH RECOVERY.
  • If you must restore additional transaction logs, select RECOVER WITH NORECOVERY.
  • The third option, RECOVER WITH STANDBY is not used in this scenario.


Note:

For more information about these recovery options, see Restore Database (Options Page) (http://go.microsoft.com/fwlink/?LinkId=114420).
  1. Click OK to complete the recovery operation.
  2. Repeat steps 4 through 10 for each database that you are restoring.
  3. Start the Windows SharePoint Services Timer service.
  1. Re-register the membership and role providers in the Web.config file.
  2. Redeploy the providers.

For more information, see Configure forms-based authentication for a claims-based Web application (SharePoint Foundation 2010) (http://technet.microsoft.com/library/f7b57d4b-87d7-41e6-9e55-350d6ad41894(Office.14).aspx).

  1. In Central Administration, click Manage Web application, select a Web application that uses claims-based authentication, and then click Authentication Providers.
  2. Select a zone that the Web application is associated with to open the Edit Authentication page, and then click Save.
  3. Repeat for each zone, and then for each Web application that uses claims-based authentication.
  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt, type the following command:

    Restore-SPFarm -Directory <BackupFolder> -Item <ServiceApplicationName> -RecoveryMethod Overwrite [-BackupId <GUID>] [-Verbose]

    To specify which backup to use, use the BackupId

    parameter. You can view the backups for the farm by typing the following: Get-SPBackupHistory -Directory <Backup folder> -ShowBackup

    . If you do not specify the BackupId

    , the most recent backup will be used. You cannot restore a service application from a configuration-only backup.

 

For more information, see Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx).


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

  • Use Central Administration to restore a service application

    Use the following procedure to restore a service application by using the SharePoint Central Administration Web site.

     

    To restore a service application by using Central Administration

  1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
  2. In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup.
  3. On the Restore from Backup — Step 1 of 3: Select Backup to Restore page, select the backup job that contains the service application backup, or a farm-level backup, from the list of backups, and then click Next. You can view more details about each backup by clicking the (+) next to the backup.


Note:

If the correct backup job does not appear, in the Backup Directory Location text box, type the path of the correct backup folder, and then click Refresh.

You cannot use a configuration-only backup to restore the farm.
  1. On the Restore from Backup — Step 2 of 3: Select Component to Restore page, expand Shared Services Applications, select the check box that is next to the service application, and then click Next.
  2. On the Restore from Backup — Step 3 of 3: Select Restore Options page, in the Restore Component section, make sure that Farm\Shared Services Applications\<Service application> appears in the Restore the following component list.

    In the Restore Options section, under Type of restore, select the Same configuration option. A dialog box will appear that asks you to confirm the operation. Click OK.

    Click Start Restore.

  3. You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically.

    You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take a several seconds for the recovery to start.

    If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 3.

  • Use SQL Server tools to restore the databases for a service application

    You cannot restore the complete service application by using SQL Server tools. However, you can use SQL Server tools to restore the databases that are associated with the service application. To restore the complete service application, use either Windows PowerShell or Central Administration.

     

    To restore the databases for a service application by using SQL Server tools

  1. Verify that the user account that you are using to restore the databases is a member of the SQL Server sysadmin fixed server role on the database server where each database is stored.
  2. Open SQL Server Management Studio and connect to the database server.
  3. In Object Explorer, expand Databases.
  4. Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database.
  5. In the Restore Database dialog box, on the General page, select the database to restore to from the To database drop-down list.
  6. Select the restore source from the From database drop-down list.
  7. In the Select the backup sets to restore section area, select the check box next to the database.
  8. On the Options tab, select the recovery state from the Recover state section.

    For more information about which recovery type to use, see Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396) in SQL Server Books Online.

  9. Click OK to restore the database.
  10. Repeat steps 1-9 for each database that is associated with the service application.

 

 

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin. Additionally, verify that the user account performing this procedure has read permissions to the backup folder and is a member of the db_owner fixed database role on both the farm configuration database and the content database where the site collection is being restored.
  2. On the Start menu, click Administrative Tools.
  3. Click SharePoint 2010 Management Shell.
  4. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:

    Restore-SPSite -Identity <Site collection URL> -Path <Backup file> [-DatabaseServer <Database server name>] [-DatabaseName <Content database name>] [-HostHeader <Host header>] [-Force] [-GradualDelete] [-Verbose]

    If you want to restore the site collection to a specific content database, use the DatabaseServer

    and DatabaseName

    parameters to specify the content database. If you do not specify a content database, the site collection will be restored to a content database chosen by Microsoft SharePoint Foundation 2010.

     

    If you are restoring a host-named site collection, use the Identity

    parameter to specify the URL of the host-named site collection and use the HostHeader

    parameter to specify the URL of the Web application that will hold the host-named site collection.

    If you want to overwrite an existing site collection, use the Force

    parameter.

     


Note:

If the site collection that you are restoring is 1 gigabyte or larger, you can use the GradualDelete

parameter for better performance during the restore process. When this parameter is used, the site collection that is overwritten is marked as deleted, which immediately prevents any additional access to its content. The data in the marked site collection is then deleted gradually over time by a timer job instead of all at the same time, which reduces the impact on server performance.

For more information, see Restore-SPSite (http://technet.microsoft.com/library/90f19a58-0455-470c-a8ee-3129fc341f62(Office.14).aspx).

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

  1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
  2. In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup.
  3. On the Restore from Backup — Step 1 of 3: Select Backup to Restore page, from the list of backups, select the backup job that contains the solution package, and then click Next. You can view more details about each backup by clicking the (+) next to the backup.


Note:

If the correct backup job does not appear, in the Backup Directory Location text box, type the Universal Naming Convention (UNC) path of the correct backup folder, and then click Refresh.

  1. On the Restore from Backup  — Step 2 of 3: Select Component to Restore page, select the check box that is next to the solution, and then click Next.
  2. On the Restore from Backup — Step 3 of 3: Select Restore Options page, in the Restore Component section, ensure that Solution appears in the Restore the following component list.

    In the Restore Only Configuration Settings section, ensure that the Restore content and configuration settings option is selected.

    In the Restore Options section, under Type of Restore, select the Same configuration option. A dialog box appears that asks you to confirm the operation. Click OK.

    Click Start Restore.

  3. You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start.

    If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 3.

     

To restore a trusted solution by using Windows PowerShell

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.

 

  1. At the Windows PowerShell command prompt, type the following command:

Restore-SPFarm -Directory <BackupFolder> -RestoreMethod Overwrite -BackupId <GUID> -Item <SolutionPath>

Where:

  • <BackupFolder> is the UNC location of the directory that you want to restore from.
  • <GUID> is the GUID of the backup ID that you want to restore from. If you do not specify a backup, the most recent one is used.
  • <SolutionPath> is the path of the solution within the backup tree (usually farm\solutions\SolutionName).

 

For more information, see Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx).

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

Restoring a sandboxed solution

You cannot restore only customizations that were deployed as sandboxed solutions. Instead, you must restore the farm, Web application, content database, or site collection with which the customization is associated. For more information about these methods of restoring, see Related content later in this article.

  • Restoring authored site elements

    You cannot restore only authored site elements. Instead, you must restore the farm, Web application, or content database with which the authored site element is associated. For more information about these methods of backing up, see Related content.

  • Restoring workflows

    Workflows are a special case of customizations that you can restore. Make sure that the backup and recovery plan includes any of the following scenarios that apply to the environment:

    • Declarative workflows, such as those created in Microsoft SharePoint Designer 2010, are stored in the content database for the site collection to which they are they are deployed. Restoring the content database or site collection restores these workflows.
    • Custom declarative workflow actions have components in the following three locations:
  1. The Microsoft Visual Studio 2010 assemblies for the actions are stored in the global assembly cache (GAC).
  2. The XML definition files (.actions files) are stored in the 14\TEMPLATE\<LCID>\Workflow directory.
  3. An XML entry to mark the action as an authorized type is stored in the Web.config file for the Web applications in which it is used.

    If the farm workflows use custom actions, you should use a file restore system to restore these files and XML entries. You can reapply the files as needed after recovery.

  • Workflows that depend on custom code, such as those that are created by using Visual Studio 2010, are stored in two locations. The Visual Studio 2010 assemblies for the workflow are stored in the GAC, and the XML definition files are stored in the Features directory. This is the same as other types of SharePoint Foundation features such as Web Parts and event receivers. If the workflow was installed as part of a solution package, follow the instructions for restoring solution packages.
  • If you create a custom workflow that interacts with a site collection other than the one where the workflow is deployed, you must restore both site collections to recover the workflow. Restoring a farm is sufficient to recover all site collections in the farm and all workflows that are associated with them.
  • Workflows that have not been deployed must be restored separately by using a file system backup application.
  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:

    Restore-SPFarm -Directory <Backup folder name> -RestoreMethod Overwrite -Item <Content database name> [-BackupId <GUID>] [-Verbose]


Note:

If you are not logged on as the Farm account, you are prompted for the Farm account’s credentials.

If you do not use the BackupId

parameter, the most recent backup will be used. To view a list of the backups, including their Backup IDs, type the following command, and then press ENTER:

Get-SPBackupHistory -Directory <Backup folder>

For more information, see Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx).

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

  • Use Central Administration to restore a content database

    You can use Central Administration to restore a farm or components of a farm.

     

    To restore a content database by using Central Administration

  1. Verify that you are logged on as a member of the Farm Administrators group.
  2. In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup.
  3. On the Restore from Backup — Step 1 of 3: Select Backup to Restore page, from the list of backups, select the backup job that contains the content database backup, and then click Next.


Note:

If the correct backup job does not appear, in the Current Directory Location text box, enter the path of the correct backup folder, and then click Refresh.
  1. On the Restore from Backup — Step 2 of 3: Select Component to Restore page, select the check box that is next to the content database, and then click Next.


Note:

If the content database is not selectable, you must use Windows PowerShell or SQL Server tools to restore the content database.
  1. On the Restore from Backup — Step 3 of 3: Select Restore Options page, in the Restore Options section, under Type of Restore, click the Same configuration option. A dialog box appears that asks you to confirm the operation. Click OK.

    Click Start Restore.

  2. You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start.

    If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 2.

  • Use SQL Server tools to restore a content database

    You can use SQL Server tools to restore a content database by following these steps:

  1. If possible, back up the live transaction log of the content database to protect any changes that were made after the last full backup.
  2. Restore the last full database backup.
  3. Restore the most recent differential database backup that occurred after the most recent full database backup.
  4. Restore all transaction log backups that occurred after the most recent full or differential database backup.

 

To restore a content database by using SQL Server tools

  1. Verify that the user account performing this procedure is a member of the sysadmin fixed server role.
  2. If the Windows SharePoint Services Timer service is running, stop the service and wait for several minutes for any currently running stored procedures to finish. Do not restart the service until after you restore the content databases.
  3. Start SQL Server Management Studio and connect to the database server.
  4. In Object Explorer, expand Databases.
  5. Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database.

    The database is automatically taken offline during the recovery operation and cannot be accessed by other processes.

  6. In the Restore Database dialog box, specify the destination and the source, and then select the backup set or sets that you want to restore.

    The default values for destination and source are appropriate for most recovery scenarios.

  7. In the Select a page pane, click Options.
  8. In the Restore options section, select only Overwrite the existing database. Unless the environment or policies require otherwise, do not select the other options in this section.
  9. In the Recovery state section:
  • If you have included all the transaction logs that you must restore, select RECOVER WITH RECOVERY.
  • If you must restore additional transaction logs, select RECOVER WITH NORECOVERY.
  • The third option, RECOVER WITH STANDBY is not used in this scenario.


Note:

For more information about these recovery options, see Restore Database (Options Page) (http://go.microsoft.com/fwlink/?LinkId=114420).
  1. Click OK to complete the recovery operation.
  2. Repeat steps 4 through 10 for each database that you are restoring.
  3. Start the Windows SharePoint Services Timer service.
  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:

    Mount-SPContentDatabase -Name <Database name> -WebApplication <Web application ID> [-Verbose]


Note:

Attaching a content database by using the Mount-SPContentDatabase

cmdlet differs from attaching a database in SQL Server by using SQL Server tools. Mount-SPContentDatabase

associates the content database with a Web application so that the contents can be read.

 

For more information, see Mount-SPContentDatabase (http://technet.microsoft.com/library/20d1bc07-805c-44d3-a278-e2793370e237(Office.14).aspx).

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:

    Import-SPWeb -Identity <Site URL> -Path <Export file name> [-Force] [-NoFileCompression] [-Verbose]


Important:

The site or subsite that you are importing must have a template that matches the template of the site specified by Identity

.

You can also use the Get-SPWeb

cmdlet and pass the ID to Import-SPWeb

by using the Windows PowerShell pipeline. The value of the Path

parameter specifies the path and file name of the file from which to import the list or library. To include the user security settings with the list or document library, use the IncludeUserSecurity

parameter. To overwrite the list or library that you specified, use the Force

parameter. You can use the UpdateVersions

parameter to specify how versioning conflicts will be handled. To view the progress of the operation, use the Verbose

parameter.

The NoFileCompression

parameter lets you specify that no file compression is performed during the import process. Using this parameter can lower resource usage up to 30% during the export and import process. If you are importing a site, list, or document library that you exported from Central Administration, or if you exported a site, list, or document library by using Windows PowerShell and you did not use the NoFileCompression

parameter in the Export-SPWeb

cmdlet, you cannot use this parameter in the Import-SPWeb

cmdlet.


Note:

There is no facility in the Import-SPWeb

cmdlet import a subset of the items in the export file. Therefore, the import operation will import everything from the file.

For more information, see Import-SPWeb (http://technet.microsoft.com/library/2ecc5b6e-1b23-4367-a966-b7bd3377db3a(Office.14).aspx).

 


Note:

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

 

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Click SharePoint 2010 Management Shell.
  5. At the Windows PowerShell command prompt, type the following commands, and then press ENTER:

    $db = get-spdatabase | where {$_.Name -eq “database name“}

    $db.AddFailoverServiceInstance(“mirrored database name“)

    $db.Update()

For more information, see Get-SPDatabase (http://technet.microsoft.com/library/c9802bf8-5216-4ade-b559-7ee25fcfa666(Office.14).aspx).

  1. On the principal server, create a certificate and open a port for mirroring.

–On the master database, create the database master key, if needed
CREATE MASTER KEY ENCRYPTION BY PASSWORD = ‘<test1234->’;
GO
— Make a certificate for this server instance.
USE master;
CREATE CERTIFICATE <MASTER_HostA_cert>
WITH SUBJECT = ‘<Master_HostA certificate>’;
GO
–Create a mirroring endpoint for server instance by using the certificate
CREATE ENDPOINT Endpoint_Mirroring
STATE = STARTED
AS TCP (
LISTENER_PORT=5024
, LISTENER_IP = ALL
)
FOR DATABASE_MIRRORING (
AUTHENTICATION = CERTIFICATE <MASTER_HostA_cert>
, ENCRYPTION = REQUIRED ALGORITHM RC4
, ROLE = ALL
);
GO
  1. On the principal server, back up the certificate.

–Back up the HOST_A certificate.
BACKUP CERTIFICATE MASTER_HostA_cert TO FILE = ‘<c:\MASTER_HostA_cert.cer>’;
GO
  1. On the principal server, back up the database. This example uses the configuration database. Repeat for all databases.

USE master;
–Ensure that SharePoint_Config uses the full recovery model.
ALTER DATABASE SharePoint_Config
SET RECOVERY FULL;
GO
USE SharePoint_Config
BACKUP DATABASE SharePoint_Config
TO DISK = ‘<c:\SharePoint_Config.bak>’
WITH FORMAT
GO
BACKUP Log SharePoint_Config
TO DISK = ‘<c:\SharePoint_Config_log.bak>’
WITH FORMAT
GO
  1. Copy the backup file to the mirror server. Repeat for all databases.
  2. By using any secure copy method, copy the backup certificate file (C:\HOST_HostA_cert.cer, for example) to the mirror server.
  3. On the principal server, create a login and user for the mirror server, associate the certificate with the user, and grant the login connect permissions for the partnership.

–Create a login on HOST_A for HOST_B
USE master;
CREATE LOGIN <HOST_HostB_login> WITH PASSWORD = ‘<1234-test>’;
GO
–Create a user for that login.
CREATE USER <HOST_HostB_user> FOR LOGIN <HOST_HostB_login>;
GO
–Associate the certificate with the user
CREATE CERTIFICATE <HOST_HostB_cert>
AUTHORIZATION <HOST_HostB_user>
FROM FILE = ‘<c:\HOST_HostB_cert.cer>’ –do not use a network path, SQL Server will give an error about the key not being valid
GO
–Grant CONNECT permission on the login for the remote mirroring endpoint.
GRANT CONNECT ON ENDPOINT::Endpoint_Mirroring TO [<HOST_HostB_login>];
GO

 

To set up the mirror server for outbound connections

  1. On the mirror server, create a certificate and open a port for mirroring.

–On the master database, create the database master key, if needed.
USE master;
CREATE MASTER KEY ENCRYPTION BY PASSWORD = ‘<1234-test>’;
GO
— Make a certificate on the HOST_B server instance.
CREATE CERTIFICATE <HOST_HostB>
WITH SUBJECT = ‘<HOST_HostB certificate for database mirroring>’;
GO
–Create a mirroring endpoint for the server instance on HOST_B.
CREATE ENDPOINT Endpoint_Mirroring
STATE = STARTED
AS TCP (
LISTENER_PORT=5024
, LISTENER_IP = ALL
)
FOR DATABASE_MIRRORING (
AUTHENTICATION = CERTIFICATE <HOST_HostB>
, ENCRYPTION = REQUIRED ALGORITHM RC4
, ROLE = ALL
);
GO
  1. On the mirror server, back up the certificate.

–Back up the HOST_B certificate.
BACKUP CERTIFICATE <HOST_HostB> TO FILE = ‘<C:\HOST_HostB_cert.cer>’;
GO

  1. By using any secure copy method, copy the backup certificate file (C:\HOST_HostB_cert.cer, for example) to the principal server.
  2. On the mirror server, restore the database from the backup files. This example uses the configuration database. Repeat for all databases.

RESTORE DATABASE SharePoint_Config
FROM DISK = ‘<c:\SharePoint_Config.bak>’
WITH NORECOVERY
GO
RESTORE log SharePoint_Config
FROM DISK = ‘<c:\SharePoint_Config_log.bak>’
WITH NORECOVERY
GO

 

To set up the mirror server for inbound connections

  1. On the mirror server, create a login and user for the principal server, associate the certificate with the user, and grant the login connect permissions for the partnership.

–Create a login on HOST_B for HOST_A
USE master;
CREATE LOGIN <MASTER_HostA_login> WITH PASSWORD = ‘<test1234->’;
GO
–Create a user for that login.
CREATE USER <MASTER_HostA_user> FOR LOGIN <MASTER_HostA_login>;
GO
–Associate the certificate with the user
CREATE CERTIFICATE <MASTER_HostA_cert>
AUTHORIZATION <MASTER_HostA_user>
FROM FILE = ‘<c:\MASTER_HostA_cert.cer>’ –do not use a network path, SQL Server will give an error about the key not being valid
GO
–Grant CONNECT permission on the login for the remote mirroring endpoint.
GRANT CONNECT ON ENDPOINT::Endpoint_Mirroring TO [<MASTER_HostA_login>];
GO

 

To set up the principal server for inbound connections

  1. On the principal server, create a login and user for the mirror server, associate the certificate with the user, and grant the login connect permissions for the partnership.

–Create a login on HOST_A for HOST_B
USE master;
CREATE LOGIN <HOST_HostB_login> WITH PASSWORD = ‘<1234-test>’;
GO
–Create a user for that login.
CREATE USER <HOST_HostB_user> FOR LOGIN <HOST_HostB_login>;
GO
–Associate the certificate with the user
CREATE CERTIFICATE <HOST_HostB_cert>
AUTHORIZATION <HOST_HostB_user>
FROM FILE = ‘<c:\HOST_HostB_cert.cer>’ –do not use a network path, SQL Server will give an error about the key not being valid
GO
–Grant CONNECT permission on the login for the remote mirroring endpoint.
GRANT CONNECT ON ENDPOINT::Endpoint_Mirroring TO [<HOST_HostB_login>];
GO

 

To set up the mirroring partners

  1. On the principal server, set up the mirroring partnership. This example uses the configuration database. Repeat for all databases.

–At HOST_A, set the server instance on HOST_B as a partner (mirror server).
ALTER DATABASE SharePoint_Config
SET PARTNER = ‘<TCP://databasemirror.adatum.com:5024>’;
GO
  1. On the mirror server, set up the mirroring partnership. This example uses the configuration database. Repeat for all databases.

–At HOST_B, set the server instance on HOST_A as a partner (principal server):
ALTER DATABASE SharePoint_Config
SET PARTNER = ‘<TCP://databasemaster.adatum.com:5024>’;
GO

  • Set up a witness server

    Each step lists the server on which it should be performed. Use Transact-SQL to send these commands to SQL Server. Placeholder information is denoted by angle brackets (<>); replace this with information that is specific to your deployment.

  1. On the witness server, set up the certificate and open the port.

–On the master database, create the database master key, if needed
CREATE MASTER KEY ENCRYPTION BY PASSWORD = ‘<1234test->’;
GO
— Make a certificate for this server instance.
USE master;
CREATE CERTIFICATE <WITNESS_HostC_cert>
WITH SUBJECT = ‘<Witness_HostC certificate>’;
GO
–Create a mirroring endpoint for server instance by using the certificate
CREATE ENDPOINT Endpoint_Mirroring
STATE = STARTED
AS TCP (
LISTENER_PORT=5024
, LISTENER_IP = ALL
)
FOR DATABASE_MIRRORING (
AUTHENTICATION = CERTIFICATE <WITNESS_HostC_cert
, ENCRYPTION = REQUIRED ALGORITHM RC4
, ROLE = ALL
);
GO
  1. On the witness server, back up the certificate.

–Back up the HOST_C certificate
BACKUP CERTIFICATE <WITNESS_HostC_cert> TO FILE = ‘<c:\ WITNESS_HostC_cert.cer>’;
GO
  1. By using any secure copy method, copy the backup certificate file (C:\WITNESS_HOSTC_cert.cer, for example) to the principal server and the mirror server.
  2. On the witness server, create logins and users for the principal and mirror servers, associate the certificates with the users, and grant the logins connect permissions for the partnership.

–Create a login on witness HOST_C for principal HOST_A
USE master;
CREATE LOGIN <MASTER_HostA_login> WITH PASSWORD = ‘<test1234->’;
GO
–Create a user for that login.
CREATE USER <MASTER_HostA_user> FOR LOGIN <MASTER_HostA_login>;
GO
–Associate the certificate with the user
CREATE CERTIFICATE <MASTER_HostA_cert>
AUTHORIZATION <MASTER_HostA_user>
FROM FILE = ‘<c:\MASTER_HostA_cert.cer>’ –do not use a network path, SQL Server will give an error about the key not being valid
GO
–Grant CONNECT permission on the login for the remote mirroring endpoint.
GRANT CONNECT ON ENDPOINT::Endpoint_Mirroring TO [<MASTER_HostA_login>];
GO
–Create a login for the mirror Host_B
CREATE LOGIN <HOST_HostB_login> WITH PASSWORD = ‘<1234-test>’;
GO
–Create a user for that login.
CREATE USER <HOST_HostB_user> FOR LOGIN <HOST_HostB_login>;
GO
–Associate the certificate with the user
CREATE CERTIFICATE <HOST_HostB_cert>
AUTHORIZATION <HOST_HostB_user>
FROM FILE = ‘<c:\HOST_HostB_cert.cer>’ –do not use a network path, SQL Server will give an error about the key not being valid
GO
–Grant CONNECT permission on the login for the remote mirroring endpoint.
GRANT CONNECT ON ENDPOINT::Endpoint_Mirroring TO [<HOST_HostB_login>];
GO
  1. On the principal server, create a login and user for the witness server, associate the certificate with the user, and grant the login connect permissions for the partnership. Repeat for the mirror server.

–Create a login on master HostA for witness HostC
USE master;
CREATE LOGIN <WITNESS_HostC_login> WITH PASSWORD = ‘<1234test->’;
GO
–Create a user for that login.
CREATE USER <WITNESS_HostC_user> FOR LOGIN <WITNESS_HostC_login>;
GO
–Associate the certificate with the user
CREATE CERTIFICATE <WITNESS_HostC_cert>
AUTHORIZATION <WITNESS_HostC_user>
FROM FILE = ‘<c:\WITNESS_HostC_cert.cer>’ –do not use a network path, SQL Server will give an error about the key not being valid
GO
–Grant CONNECT permission on the login for the remote mirroring endpoint.
GRANT CONNECT ON ENDPOINT::Endpoint_Mirroring TO [<WITNESS_HostC_login>];
GO
  1. On the principal server, attach the witness server. This example uses the configuration database. Repeat for all databases.

–Set up the witness server
ALTER DATABASE SharePoint_Config
SET WITNESS =
‘<TCP://databasewitness.adatum.com:5024>’
GO
Posted on by escapebusinesssolutions in Uncategorized


 

Getting started with Microsoft SharePoint Foundation 2010

Posted on by escapebusinesssolutions in Uncategorized

  1. Run the Microsoft SharePoint Products Preparation Tool, which installs all required prerequisites to use SharePoint Foundation 2010.
  2. Run Setup, which installs binaries, configures security permissions, and sets registry settings for Microsoft SharePoint Foundation.
  3. Run SharePoint Products Configuration Wizard, which installs and configures the configuration database, the content database, and installs the SharePoint Central Administration Web site.
  4. Configure browser settings.
  5. Run the Farm Configuration Wizard, which configures the farm, creates the first site collection, and selects the services that you want to use in the farm.
  6. Perform post-installation steps.

 


Important:

To complete the following procedures, you must be a member of the Administrators group on the local computer.

 

Run the Microsoft SharePoint Products Preparation Tool

Use the following procedure to install software prerequisites for SharePoint Foundation 2010.

To run the Microsoft SharePoint Products Preparation Tool

  1. Insert your SharePoint Foundation 2010 installation disc.
  2. On the SharePoint Foundation 2010 Start page, click Install software prerequisites.


Note:

Because the preparation tool downloads components from the Microsoft Download Center, you must have Internet access on the computer on which you are installing Microsoft SharePoint Foundation.
  1. On the Welcome to the Microsoft SharePoint Products Preparation Tool page, click Next.
  2. On the License Terms for software product page, review the terms, select the I accept the terms of the License Agreement(s) check box, and then click Next.
  3. On the Installation Complete page, click Finish.

 

Run Setup

The following procedure installs binaries, configures security permissions, and sets registry settings for SharePoint Foundation 2010.

To run Setup

  1. On the SharePoint Foundation 2010 Start page, click Install SharePoint Foundation.
  2. On the Read the Microsoft Software License Terms page, review the terms, select the I accept the terms of this agreement check box, and then click Continue.
  3. On the Choose the installation you want page, click Server farm.
  4. On the Server Type tab, click Complete.
  5. Optional: To install SharePoint Foundation 2010 at a custom location, click the Data Location tab, and then either type the location or click Browse to find the location.
  6. Click Install Now.
  7. When Setup finishes, click Close.

 


Note:

If Setup fails, check the TEMP folder of the user who ran Setup. Ensure that you are logged in as the user who ran Setup, and then type %temp% in the location bar in Windows Explorer. If the path %temp% resolves to a location that ends in a “1” or “2”, you will need to navigate up one level to view the log files. The log file name is Microsoft SharePoint Foundation 2010 Setup (<timestamp>).

 


Tip:

To access the SharePoint Products Configuration Wizard, click Start, point to All Programs, and then click Microsoft SharePoint 2010 Products. If the User Account Control dialog box appears, click Continue.

 

Run the SharePoint Products Configuration Wizard

The following procedure installs and configures the configuration database, the content database, and installs the SharePoint Central Administration Web site.

To run the SharePoint Products Configuration Wizard

  1. On the Welcome to SharePoint Products page, click Next.
  2. In the dialog box that notifies you that some services might need to be restarted during configuration, click Yes.
  3. On the Connect to a server farm page, click Create a new server farm, and then click Next.
  4. On the Specify Configuration Database Settings page, do the following:
    1. In the Database server box, type the name of the computer that is running SQL Server.
    2. In the Database name box, type a name for your configuration database, or use the default database name. The default name is SharePoint_Config.
    3. In the Username box, type the user name of the server farm account. Ensure that you type the user name in the format DOMAIN\user name.


Important:

The server farm account is used to create and access your configuration database. It also acts as the application pool identity account for the SharePoint Central Administration application pool, and it is the account under which the Microsoft SharePoint Foundation Workflow Timer service runs. The SharePoint Products Configuration Wizard adds this account to the SQL Server Login accounts, the SQL Server dbcreator server role, and the SQL Server securityadmin server role. The user account that you specify as the service account must be a domain user account, but it does not need to be a member of any specific security group on your front-end Web servers or your database servers. We recommend that you follow the principle of least privilege and specify a user account that is not a member of the Administrators group on your front-end Web servers or your database servers.
  1. In the Password box, type the user password.
  1. Click Next.
  2. On the Specify Farm Security Settings page, type a passphrase, and then click Next.

    Ensure that the passphrase meets the following criteria:

  • Contains at least eight characters
  • Contains at least three of the following four character groups:
    • English uppercase characters (from A through Z)
    • English lowercase characters (from a through z)
    • Numerals (from 0 through 9)
    • Nonalphabetic characters (such as !, $, #, %)


Note:

Although a passphrase is similar to a password, it is usually longer to enhance security. It is used to encrypt credentials of accounts that are registered in Microsoft SharePoint Foundation; for example, the Microsoft SharePoint Foundation system account that you provide when you run the SharePoint Products Configuration Wizard. Ensure that you remember the passphrase, because you must use it each time you add a server to the farm.
  1. On the Configure SharePoint Central Administration Web Application page, do the following:
    1. Either select the Specify port number check box and type the port number you want the SharePoint Central Administration Web application to use, or leave the Specify port number check box cleared if you want to use the default port number.
    2. Click either NTLM or Negotiate (Kerberos).
  2. Click Next.
  3. On the Completing the SharePoint Products Configuration Wizard page, review your configuration settings to verify that they are correct, and then click Next.


Note:

If you want to automatically create unique accounts for users in Active Directory Domain Services (AD DS), click Advanced Settings, and enable Active Directory account creation.
  1. On the Configuration Successful page, click Finish.


Note:

If the SharePoint Products Configuration Wizard fails, check the PSCDiagnostics log files, which are located on the drive on which SharePoint Foundation is installed, in the %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\LOGS folder.


Note:

If you are prompted for your user name and password, you might need to add the SharePoint Central Administration Web site to the list of trusted sites and configure user authentication settings in Internet Explorer. You might also want to disable the Internet Explorer Enhanced Security settings. Instructions for how to configure or disable these settings are provided in the following section.


Note:

If you see a proxy server error message, you might need to configure your proxy server settings so that local addresses bypass the proxy server. Instructions for configuring proxy server settings are provided later in the following section.

 

Configure browser settings

After you run the SharePoint Products Configuration Wizard, you should ensure that SharePoint Foundation 2010 works properly for local administrators in your environment by configuring additional settings in Internet Explorer.

 


Note:

If local administrators are not using Internet Explorer, you might need to configure additional settings. For information about supported browsers, see Plan browser support (SharePoint Foundation 2010).

 

If you are prompted for your user name and password, perform the following procedures:

  • Add the SharePoint Central Administration Web site to the list of trusted sites
  • Disable Internet Explorer Enhanced Security settings

If you receive a proxy server error message, perform the following procedure:

  • Configure proxy server settings to bypass the proxy server for local addresses

For more information, see Getting Started with IEAK 8 (http://go.microsoft.com/fwlink/?LinkId=151359&clcid=0x409).

 

To add the SharePoint Central Administration Web site to the list of trusted sites

  1. In Internet Explorer, on the Tools menu, click Internet Options.
  2. On the Security tab, in the Select a zone to view or change security settings area, click Trusted Sites, and then click Sites.
  3. Clear the Require server verification (https:) for all sites in this zone check box.
  4. In the Add this Web site to the zone box, type the URL to your site, and then click Add.
  5. Click Close to close the Trusted Sites dialog box.
  6. Click OK to close the Internet Options dialog box.

 

To disable Internet Explorer Enhanced Security settings

  1. Click Start, point to All Programs, point to Administrative Tools, and then click Server Manager.
  2. In Server Manager, select the root of Server Manager.
  3. In the Security Information section, click Configure IE ESC.

    The Internet Explorer Enhanced Security Configuration dialog box opens.

  4. In the Administrators section, click Off to disable the Internet Explorer Enhanced Security settings, and then click OK.

 

To configure proxy server settings to bypass the proxy server for local addresses

  1. In Internet Explorer, on the Tools menu, click Internet Options.
  2. On the Connections tab, in the Local Area Network (LAN) settings area, click LAN Settings.
  3. In the Automatic configuration area, clear the Automatically detect settings check box.
  4. In the Proxy Server area, select the Use a proxy server for your LAN check box.
  5. Type the address of the proxy server in the Address box.
  6. Type the port number of the proxy server in the Port box.
  7. Select the Bypass proxy server for local addresses check box.
  8. Click OK to close the Local Area Network (LAN) Settings dialog box.
  9. Click OK to close the Internet Options dialog box.

 

Run the Farm Configuration Wizard

You have now completed Setup and the initial configuration of SharePoint Foundation 2010. You have created the SharePoint Central Administration Web site.

You can now create your farm and sites, and you can select services by using the Farm Configuration Wizard.

To run the Farm Configuration Wizard

  1. On the SharePoint Central Administration Web site, on the Configuration Wizards page, click Launch the Farm Configuration Wizard.
  2. On the Help Make SharePoint Better page, click one of the following options, and then click OK:
  • Yes, I am willing to participate (Recommended.)
  • No, I don’t want to participate.
  1. On the Configure your SharePoint farm page, click Walk me through the settings using this wizard, and then click Next.
  2. In the Service Account section, click a service account that you want to use to configure your services.


Note:

For security reasons, we recommend that you use a different account from the farm administrator account to configure services in the farm.

If you decide to use an existing managed account — that is, an account that SharePoint Foundation is aware of — ensure that you click that option before you continue.
  1. Select the services that you want to use in the farm, and then click Next.
  1. On the Create Site Collection page, do the following:
    1. In the Title and Description section, in the Title box, type the name of your new site.
    2. Optional: In the Description box, type a description of what the site contains.
    3. In the Web Site Address section, select a URL path for the site.
    4. In the Template Selection section, in the Select a template list, select the template that you want to use for the top-level site in the site collection.


Note:

To view a template or a description of a template, click any template in the Select a template list.
  1. Click OK.
  2. On the Configure your SharePoint farm page, review the summary of the farm configuration, and then click Finish.
  1. Run the Microsoft SharePoint Products Preparation Tool, which installs all prerequisites to use SharePoint Foundation 2010.
  2. Run Setup, which installs SQL Server 2008 Express and the SharePoint product.
  3. Run SharePoint Products Configuration Wizard, which installs the SharePoint Central Administration Web site and creates your first SharePoint site collection.
  4. Configure browser settings.
  5. Perform post-installation steps.


Important:

To complete the following procedures, you must be a member of the Administrators group on the local computer.

 

Run the Microsoft SharePoint Products Preparation Tool

Use the following procedure to install software prerequisites for SharePoint Foundation 2010.

To run the Microsoft SharePoint Products Preparation Tool

  1. Insert your SharePoint Foundation 2010 installation disc.
  2. On the SharePoint Foundation 2010 Start page, click Install software prerequisites.


Note:

Because the preparation tool downloads components from the Microsoft Download Center, you must have Internet access on the computer on which you are installing SharePoint Foundation.
  1. On the Welcome to the Microsoft SharePoint Products Preparation Tool page, click Next.
  2. On the Installation Complete page, click Finish.

Run Setup

The following procedure installs SQL Server 2008 Express and the SharePoint product. At the end of Setup, you can choose to start the SharePoint Products Configuration Wizard, which is described later in this section.

To run Setup

  1. On the SharePoint Foundation 2010 Start page, click Install SharePoint Foundation.
  2. On the Read the Microsoft Software License Terms page, review the terms, select the I accept the terms of this agreement check box, and then click Continue.
  3. On the Choose the installation you want page, click Standalone.
  4. When Setup finishes, a dialog box prompts you to complete the configuration of your server. Ensure that the Run the SharePoint Products Configuration Wizard now check box is selected.
  5. Click Close to start the configuration wizard.

 


Note:

If Setup fails, check the TEMP folder of the user who ran Setup. Ensure that you are logged in as the user who ran Setup, and then type %temp% in the location bar in Windows Explorer. If the path %temp% resolves to a location that ends in a “1” or “2”, you will need to navigate up one level to view the log files. The log file name is Microsoft SharePoint Foundation 2010 Setup (<timestamp>).

 


Tip:

To access the SharePoint Products Configuration Wizard, click Start, point to All Programs, and then click Microsoft SharePoint 2010 Products. If the User Account Control dialog box appears, click Continue.

 

Run the SharePoint Products Configuration Wizard

The following procedure installs and configures the configuration database, the content database, and installs the SharePoint Central Administration Web site. It also creates your first SharePoint site collection.

To run the SharePoint Products Configuration Wizard

  1. On the Welcome to SharePoint Products page, click Next.
  2. In the dialog box that notifies you that some services might need to be restarted during configuration, click Yes.
  3. On the Configuration Successful page, click Finish.


Note:

If the SharePoint Products Configuration Wizard fails, check the PSCDiagnostics log files, which are located on the drive on which SharePoint Foundation is installed, in the %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\LOGS folder.


Note:

If you are prompted for your user name and password, you might need to add the SharePoint Central Administration Web site to the list of trusted sites and configure user authentication settings in Internet Explorer. You might also want to disable the Internet Explorer Enhanced Security settings. Instructions for how to configure or disable these settings are provided in the following section.


Note:

If you see a proxy server error message, you might need to configure your proxy server settings so that local addresses bypass the proxy server. Instructions for configuring proxy server settings are provided later in the following section.

 

Configure browser settings

After you run the SharePoint Products Configuration Wizard, you should ensure that SharePoint Foundation works properly for local administrators in your environment by configuring additional settings in Internet Explorer.

 


Note:

If local administrators are not using Internet Explorer, you might need to configure additional settings. For information about supported browsers, see Plan browser support (SharePoint Foundation 2010).

 

If you are prompted for your user name and password, perform the following procedures:

  • Add the SharePoint Central Administration Web site to the list of trusted sites
  • Disable Internet Explorer Enhanced Security settings

If you receive a proxy server error message, perform the following procedure:

  • Configure proxy server settings to bypass the proxy server for local addresses

For more information, see Getting Started with IEAK 8 (http://go.microsoft.com/fwlink/?LinkId=151359&clcid=0x409).

 

To add the SharePoint Central Administration Web site to the list of trusted sites

  1. In Internet Explorer, on the Tools menu, click Internet Options.
  2. On the Security tab, in the Select a zone to view or change security settings area, click Trusted Sites, and then click Sites.
  3. Clear the Require server verification (https:) for all sites in this zone check box.
  4. In the Add this Web site to the zone box, type the URL to your site, and then click Add.
  5. Click Close to close the Trusted Sites dialog box.
  6. Click OK to close the Internet Options dialog box.

    If you are using a proxy server in your organization, use the following steps to configure Internet Explorer to bypass the proxy server for local addresses.

 

To disable Internet Explorer Enhanced Security settings

  1. Click Start, point to All Programs, point to Administrative Tools, and then click Server Manager.
  2. In Server Manager, select the root of Server Manager.
  3. In the Security Information section, click Configure IE ESC.

    The Internet Explorer Enhanced Security Configuration dialog box opens.

  4. In the Administrators section, click Off to disable the Internet Explorer Enhanced Security settings, and then click OK.

 

To configure proxy server settings to bypass the proxy server for local addresses

  1. In Internet Explorer, on the Tools menu, click Internet Options.
  2. On the Connections tab, in the Local Area Network (LAN) settings area, click LAN Settings.
  3. In the Automatic configuration area, clear the Automatically detect settings check box.
  4. In the Proxy Server area, select the Use a proxy server for your LAN check box.
  5. Type the address of the proxy server in the Address box.
  6. Type the port number of the proxy server in the Port box.
  7. Select the Bypass proxy server for local addresses check box.
  8. Click OK to close the Local Area Network (LAN) Settings dialog box.
  9. Click OK to close the Internet Options dialog box.