Showing posts with label SharePoint 2010. Show all posts
Showing posts with label SharePoint 2010. Show all posts

Wednesday, May 2, 2012

Use Windows PowerShell to restore a farm


Use Windows PowerShell to restore a farm

You can easily restore the farm using Windows PowerShell. Please follow the below steps as shown below:

1. On the Start menu, click All Programs.
2. Click Microsoft SharePoint 2010 Products.
3. Click SharePoint 2010 Management Shell.

4. To view the backups for the farm, type the following command:



Get-SPBackupHistory -Directory {BackupFolder} -ShowBackup [-Verbose]


5. At the windows PowerShell command prompt, type the following command:


Restore-SPFarm -Directory {BackupFolder} -RestoreMethod Overwrite [-BackupId ]

For More details : http://technet.microsoft.com/en-us/library/ee428311.aspx
 

Tuesday, March 27, 2012

Conditional Formatting in SharePoint 2010 using SharePoint Designer 2010


Conditional Formatting in SharePoint 2010 using SharePoint Designer 2010

We can do conditional formatting on both rows and columns.
The conditional formatting are usually takes the html formatting on the page level. So you have to design in the html format using SharePoint designer 2010.


The following are the steps to do Formatting Row/column:
  1. Open the site in SharePoint Designer.
  2. Right click the file, and make backup copy.
  3. Edit the file in advanced mode.
  4. Click on the grid page and then click on Conditional Formatting, available on the ribbon.
  5. Select Format row/column.
  6. Put the condition as per the requirement.
  7. Set the style, by clicking on the set style button
If you need to put image, do the following:
  1. Create the image using any image editor like Photoshop.
  2. And drop the image to the location 14 hive in SharePoint 2010 i.e., C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES
  3. And update the settings as shown in the below screenshot.







Monday, March 26, 2012

Key Points of SharePoint Designer 2010


Key Points: 


1.  SharePoint Designer is “the preferred” tool to design powerful no-code solutions and applications in SharePoint 2010.
2.    Use SharePoint Designer to produce solutions that are easily maintainable and supportable.
3.    SharePoint Designer is not a tool for general use by all those who visit or have access to a SharePoint site. The browser should be used to complete tasks such as adding static content (text, images, or hyperlinks) to Web pages, uploading documents, or creating and modifying list items.
4.    SharePoint Designer 2010 can be used only with SharePoint Foundation 2010 or SharePoint Server 2010 sites. These are server-based products and need to be installed prior to using SharePoint Designer 2010.
5.    SharePoint Designer 2010 cannot be used to customize non-SharePoint Web sites, nor can you use it to customize sites based on previous versions of SharePoint, such as Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007. Use Expression Web for non-SharePoint sites and SharePoint Designer 2007 with sites created in previous versions of SharePoint.
6.    SharePoint Designer can remember the last site you worked on and open it when you start the program. This is not the default configuration, but you can select this setting on the General tab of the Application Options dialog box. The Application Options dialog box can be opened by clicking Options in Backstage view.
7.  SharePoint Designer uses the security settings of your browser to decide whether to prompt for credentials.
8.    The SharePoint Designer shell consists of Backstage view and On Stage view. On Stage view consists of a number of elements, including the Quick Access Toolbar, ribbon, breadcrumb, Navigation pane, mini-gallery, workspace, task panes, and status bar. Web pages initially created in a SharePoint site point to files on a file system, known as uncustomized pages; however, when pages are customized by using SharePoint Designer, they are stored in the SQL Server databases, where they are known as customized pages.
9.    In SharePoint Designer 2010, uncustomized (site definition) pages can only be customized (unghosted) when a page is in advanced edit mode.
10. A SharePoint Web application consists of one or more site collections that contain one or more Web sites.
11. When a Web application is created, by default each site collection within that Web application can be modified using SharePoint Designer only by users who are members of the Site Owners and Designers site groups. However, these users cannot customize site definition pages, nor can they see the hidden URL structure of a SharePoint site.

 Source: Step by Step SharePoint Designer 2010 by Penelope Coventry 




Sunday, March 25, 2012

URL Naming convention in SharePoint 2010


URL Naming convention:
Check the spelling of words you include in the URL name and be consistent in your naming conventions; for example, don’t call a picture library pictures in one site and images in another. For some SharePoint components, such as the URL for a site, you cannot change the URL later.
If your aim is to make the URL readable and the URL consists of several words, use an underscore (“_”) in place of a space or remove the space and capitalize the first character in each word. For example, replace the three words Wide World Importers, with either Wide_World_Importers or WideWorldImporters. The underscore is the better of these options because all popular search engines and spiders understand it as a word separator.

Although the space character is a legal URL character, there are several issues with having one or more spaces in the URL, such as the following:

Readability: A space in the URL name is URL-encoded as %20, so the resulting name is difficult for people to read. A site with a URL of s p f would result in an encoded version of s%20p%20f, six extra characters.

URL length limitation: A URL must contain no more than 260 characters. SharePoint refers to every site, list, library, list item, or document as a URL. SharePoint prefixes the document name by the document library’s URL, which is prefixed by the site’s URL, then by its parent’s site’s URL, and so on. In addition, when a user edits documents or list items, SharePoint appends the URL of the document library or list, so that when the user clicks Save or Close, the browser redirects them to the list or library in which the item was saved. If the URL for the list or library contains two spaces, it contains six extra characters. Then, as the URL is appended for editing, that adds another six extra characters, making 12 extra characters. Therefore, if you consistently use long names, you’ll eventually have problems, which is exaggerated if you use spaces.

Links in e-mails: If you incorporate a URL in an e-mail message, some e-mail programs truncate the URL at the first space when sending the clickable link to the recipient, resulting in a broken link. When users click the link, they are taken to an invalid location in the browser and won’t understand why they can’t find the document.


Source: Step by Step SharePoint Designer 2010 by Penelope Coventry

New features in SharePoint Designer 2010

SharePoint Designer 2010
New features in SharePoint Designer 2010
Source: Step By Step SharePoint Designer 2010 by Penelope Coventry







1. User interface (UI): The SharePoint Designer user interface (UI) is redesigned and uses the Office Fluent UI, which was designed to make it easier for users to use and find features within a product. It incorporates the ribbon and Backstage view, which can be accessed from the File tab.

2. Easier management of SharePoint components: The new Navigation pane, which replaces the Folder List task pane in SharePoint Designer 2007, focuses on SharePoint artifacts and not where the artifacts are stored. You can now manipulate major SharePoint components—such as content types, site columns, and external lists—and modify site and list permissions natively within SharePoint Designer. Using SharePoint Designer to manipulate SharePoint components is now much faster and more efficient than using a Web browser to complete similar tasks.

3. New tools to help users create better composites (solutions): Two areas of tool improvement are-
i.       Workflows: The challenge in implementing a new workflow is that the person who creates the workflow is usually not the one who defines the requirements. SharePoint 2010 addresses this challenge by allowing people to create workflows in Visio 2010 and export them into SharePoint Designer 2010, where business logic and additional rules are added. Workflows developed in SharePoint Designer can be exported from one SharePoint site and imported into another, as well as into Visual Studio 2010. This enables development and testing of the SharePoint Designer custom workflow to take place in a trusted environment before deployment to the production system. In the previous version of SharePoint, this was available only with workflows created using Visual Studio.
ii.       Business Connectivity Services (BCS): Originally called the Business Data Catalog, BCS is now available in the base product, Microsoft SharePoint Foundation 2010. SharePoint Designer is the major tool for information workers and business analysts to define how to access external systems and create dashboards and composite applications based on data from the external systems.

4. Performance and stability improvements: Until the release of Service Pack 2, SharePoint Designer 2007 had major performance and stability issues. Some users also complained about the code SharePoint Designer 2007 generated. Microsoft has invested heavily in this area.

Tuesday, March 20, 2012

Required Service Accounts in SharePoint 2010 Installation & Configuration

Service Accounts

One of the most important aspects of planning for deployment is to identify the service accounts that will be needed. There are several accounts that must be specified, even for the most basic farm topologies. Other accounts will be required depending on the additional functionality deployed.

NOTE: It is a recommended best practice to install SharePoint 2010 using “least-privileged” accounts. This decreases the potential damage in the case where an account is compromised.

Table 1-3 lists the service accounts required for all SharePoint 2010 installations, and Table 1-4 lists other service accounts.

TABLE 1-3 Required Service Accounts

ACCOUNT
PURPOSE
REQUIREMENTS
SQL Server
service
account

Run SQL Server processes:
·         For the default instance, use MSSQLSERVER and SQLSERVERAGENT
·         For a named instance, use MSSQL$InstanceName and SQLAgent$InstanceName

Either a local system account or domain account.
Ensure that this account has access to any external resources used to backup or restore. If using a local system account (Network Service or Local System), grant access to domain_name\SQL_hostname$.
Setup user
Account
Run installation and
SharePoint Products and
Technologies Configuration
Wizard

·      Domain account
·      Member of the Administrators group on each server where setup is run
·      SQL Server login on database server
·      Member of securityadmin and dbcreator server roles
·      If using Windows PowerShell, you must be a member of the dbowner fixed role on the database
Server farm account/ database access account
·         Configure and manage server farm
·         Application pool identity for Central Administration Web site
·         Run SharePoint Foundation Timer Service

·      Domain account
Additional permissions are also granted on Web front-end and application servers because they are added to the farm.
This account is also added to the following SQL Server roles on the farm database server:
·      dbcreator fixed server role
·      securityadmin fixed server role
·      db_owner fixed database role on all SharePoint databases for the farm

TABLE 1-4 Other Service Accounts

ACCOUNT
PURPOSE
REQUIREMENTS
Search Service account
Run Search Service
This account will default
to the farm administrator
account, but you should
specify a different account
for security purposes.
Content Access account
Used to access content sources for crawling. Defaults to Search Service account.
Domain account with read
access to content to be
crawled.
Application pool
Accounts
Used for running IIS Web applications that host SharePoint site collections.
Can be a local system account or domain account.

Reference: SharePoint 2010 Administrator Pocket Consultant (Book)