27 December, 2010

Office Web Apps

Office Web Apps are online mechanisms to Microsoft Word, Microsoft Excel, Microsoft PowerPoint and Microsoft OneNote applications that allow us to access documents from anywhere. Some of the features include concurrent editing with Excel files, meaning you can have several people all editing the same file at the same time. Way cool! Another is dynamic saving, which works in all apps except Word. This means there is no save button and changes are automatically saved back to the server.

Windows browser support includes IE 7 and IE 8, Firefox 3.5 and later, and Safari 4 and later. Expect good results when working from a Mac or Linux machine. You also have pretty good mobile support for viewing, but not editing files. Office Web Apps works on Windows Mobile, BlackBerry, iPhone, and some others.

Don’t look to Office Web Apps to replace your Office client; rather, it’s a complementary offering. Although the viewing support is fantastic, editing is limited and is only practical for lightweight tasks.

I would like to share some vital points that i had observed after the deployment of office web apps:

1. Office Web Apps must be installed on every server in SharePoint 2010 Farm

2. Office Web Apps is it is not a part of SharePoint 2010, its Office 2010 functionality and is integrated with SharePoint 2010.

3. SharePoint 2010 has to be installed first before you can install Office Web Apps.

4. Office Web Apps works with SharePoint Server 2010 or SharePoint Foundation 2010.

5. Installing Office web applications on SharePoint 2010 installed on Win 7 client is not supported.

6. Office web applications are meant for intranet and not for Extranet Collaboration Environments where there are large numbers of users.

7. You can control default open behavior to open using Office Web Apps, you cannot control the default new behavior to use Office Web Apps. What I mean by this is if you have Office Installed on Client its always going to use office client when you try to add new document to document library.

If you have any queries/questions regarding the above mentioned info then please let me know, Thanks...

18 December, 2010

How to disable protected mode in office 2010 (protected view

Protected mode is a new security feature available in Microsoft Office 2010.It enhances protection against risky Outlook email attachments, files that came from the Internet, files that fail validation or files that are located in potentially unsafe locations.

“By default Office 2010 will open documents in protected mode that fail validation, have been downloaded from the internet, are located in potentially unsafe location and include attachments. Protected view opens the document in read-only mode thus minimizing the exposure to some potential security threat.

If you are an experienced user who is annoyed by the protected view, you can always disable it even though it is not recommended by Microsoft.


Please refer the following steps as how to disable the protected mode in Office 2010:

-Run one of the Microsoft Office 2010 applications (e.g. Word 2010/Excel 2010/PowerPoint 2010).


-Click on Office button, and select Options.

-In the “Options” dialog, select Trust Center in the left pane.

-Click on Trust Center Settings in the right pane.

-Select Protected View in the left pane of “Trust Center” dialog.

-Disable any of all of the protected mode options as below by clicking the check boxes:

-Click OK.

If you have any queries/questions regarding the above mentioned info then please let me know,Thanks..



22 September, 2010

SharePoint 2010: Installing and Configuring Features

Features are SharePoint Server 2010–specific declarative (XML) programming elements.
Features configure, associate, define, create, and copy.

Features are most commonly used for the following:
■ To define the columns that make up list types and the fields that the columns
are based on
■ To copy Web parts and master pages to their respective galleries
■ To associate Visual Studio workflows with a list or site
■ To modify and extend the configuration of the SharePoint Server 2010 user
interface
■ To serve as a control panel that allows code and configuration changes to be
turned on and off in the browser

Note: Features can affect four different scopes: farm, Web application, site collection, and site. Site-scoped and site collection–scoped features can be controlled by information workers, which allows farm administrators to delegate responsibility for them.

Feature Location:

Features are XML files and must be contained in a folder in C:\Programs Files\Common
Files\Microsoft Shared\Web Server Extensions\ 14\TEMPLATE\FEATURES.

Basic Know-how:

Features are generally composed of two types of files: a feature header file and one or more element files. Because the feature files are simply XML and because they are located in TEMPLATE\FEATURES, they can be easily inspected by browsing to the appropriate folder and examining the contents of the files. Feature header files are generally named Feature.XML.

Feature Life Cycle
There is a four-stage feature life cycle.
-Features are installed, activated, deactivated, and uninstalled.
-Features can be manipulated with Stsadm.exe, Central Administration,and Windows Power Shell.
-Features are deployed using solution packages with either full-trust or sandboxed deployment mechanisms.

How to install a Feature:
Features are deployed with solution packages and should be automatically installed when deployed. Although it is uncommon to have to manually install features, you should know what the installation process does to install features.

To install a feature, the necessary feature files must already be deployed to the
TEMPLATE\FEATURES directory on all servers in the farm. Installing a feature simply
makes it available to be activated. Any installed feature that does not have the
property Hidden=True can be seen and activated through the SharePoint Server
2010 user interface.

Features must be installed using either Stsadm.exe or Windows Power-Shell.

Stsadm.exe is located in C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\14\BIN. To install a feature using Stsadm.exe, use the following
command:

stsadm.exe -o installfeature
{-filename
|
-name
} [-force]

To install a feature using Windows PowerShell, use the following command:

Install-SPFeature -Path
[-AssignmentCollection
] [-Confirm []]
[-Force
] [-WhatIf []]
[
]

How to Activate/Deactivate features:

To activate or deactivate a farm-scoped feature using Central Administration,
do the following:
1. Browse to Central Administration, System Settings, Manage Farm Features.
2. Click either the feature’s Activate or Deactivate button.
3. To deactivate a feature, confirm the deactivation.

Activating Web application–scoped features in Central Administration has changed considerably and is now accomplished using the new management Ribbon.

To activate a Web application–scoped feature, do the following:
1. Browse to Central Administration, Application Management, Manage Web
Applications.
2. Click the row that contains the Web application that the feature should be
activated on.
3. Click the Web Application tab in the management Ribbon.
4. Click the Manage Features button in the management Ribbon
5. Click either the feature’s Activate or Deactivate button.
6. To deactivate the feature, confirm the deactivation.

ACTIVATING AND DEACTIVATING FEATURES IN A SITE COLLECTION

If a feature has been installed to the farm and scoped to a site collection, a site collection administrator can then either activate or deactivate the feature. To activate or deactivate a site collection–scoped feature, do the following:

1. Open the appropriate site collection in the browser.
2. From the Site Actions drop-down menu, click Site Settings.
3. Click the Site Collection Features hyperlink in the Site Collection Administration
group,If the Site Collection Administration group contains a Go To Top Level Site Settings hyperlink, click on it to go to the top-level site, and then click the Site Collection Features hyper-link.
4. Click the Activate or Deactivate button.
5. To deactivate a feature, confirm the deactivation.

ACTIVATING AND DEACTIVATING FEATURES IN A SITE

If a feature has been installed to the farm and scoped to a site, a site owner can activate and deactivate the feature. To activate or deactivate a site-scoped feature,
do the following:
1. Open the site in the browser.
2. From the Site Actions drop-down menu, click Site Settings.
3. Click the Manage Site Features hyperlink in the Site Actions group
4. Click the Activate or Deactivate button.
5. Confirm the deactivation.

ACTIVATING AND DEACTIVATING FEATURES USING STSADM.EXE

Features can also be activated and deactivated from the command line using Stsadm.exe. Activate or deactivate features using the appropriate stsadm.exe command:

stsadm.exe -o activatefeature
{-filename
| -name |
-id
} [-url ] [-force]

Or

stsadm.exe -o deactivatefeature
{-filename
| -name |
-id
} [-url ] [-force]

ACTIVATING AND DEACTIVATING FEATURES USING WINDOWS POWERSHELL

Windows PowerShell uses a slightly different naming system than Stsadm.exe and
the user interface. Instead of using the activate and deactivate parameters, Windows
PowerShell use the verbs Enable and Disable. To activate (enable) or deactivate
(
disable) features with Windows PowerShell, use the appropriate cmdlet:

Enable-SPFeature -Identity

[-AssignmentCollection
]
[-Confirm [
]]
[-Force
] [-PassThru ] [-Url ]
[-WhatIf [
]] []

Or

Disable-SPFeature -Identity

[-AssignmentCollection
]
[-Confirm [
]]
[-Force
] [-Url ] [-WhatIf []]
[
]

21 September, 2010

SharePoint 2010:Office Features

Some of the capabilities made available in SharePoint are directly tied to Microsoft Office programs.These capabilities use SharePoint to extend the functionality of Microsoft Office.

Microsoft Office programs that have extended capabilities when used in conjunction with SharePoint include Excel, InfoPath, and Visio. There are a set of SharePoint enterprise services that directly integrate with these programs to provide additional information sharing, visualization, and management capabilities.

• Excel Services: Used in conjunction with Excel 2007 or Excel 2010 to publish spreadsheet content and calculations for access with the web browser

• Form Services: Used in conjunction with InfoPath 2007 or InfoPath 2010 to publish forms as web pages allowing for the entry of data through a web-based interface

• Visio Services: Used in conjunction with Visio 2010 to publish diagrams as dynamic web images allowing for viewing and information visualization through the web browser

While we will not be going into detail about how to create complex Excel sheets, InfoPath forms, or Visio diagrams, the information you learn here will allow you to take those files and make them available in SharePoint.

Excel Services

Excel Services is available in SharePoint Server and is designed to extend Excel data analysis and business intelligence capabilities by allowing you to publish Excel resources to SharePoint for access via the web browser. This allows Excel-based information and capabilities to be leveraged as online reporting and analytical tools.

For example, you can create corporate sales reports in Excel using all of the data analysis and visualization tools available in this product, such as PivotTables and pie charts. This information can be configured to represent the organization’s sales statistics and then published to SharePoint and organized into dashboards or online report structures allowing for easy access by individuals with appropriate rights.


Excel Services within SharePoint Server 2010 allows you to publish an entire Excel workbook, a sheet within a workbook, or specific objects, such as PivotTables, pie charts, and named ranges located within Excel worksheets.

Once published, the Excel content can be accessed from within the library via the web browser or added to a SharePoint page using the Excel Web Access web part.

Publishing Excel content to Excel Services is possible using either Excel 2007 or Excel 2010. Once published, the Excel content can be integrated with other SharePoint resources to create business solutions.

Publishing to Excel Services

Excel Services requires that the SharePoint Server Enterprise Site Features be enabled within the site where you wish to publish the content. With this feature enabled, you can publish Excel content in files located within the site’s libraries to Excel Services.

To publish Excel resources to Excel Services using Excel 2007 perform the following steps:

1. Click the Office button and from the Office Button menu highlight the Publish option. Then select Excel Services as seen in following figure:



2. On the Save As window, select a SharePoint library in a site that has the SharePoint Server Enterprise Site Features enabled and click the Excel Services Options button.

3. On the Excel Services Options window:
a. On the Show tab select the type of items to include. Items available for inclusion are:
• Entire Workbook: This will publish the entire Excel document for use in Excel Services.
• Sheets: This will allow you to identify specific worksheets in the workbook that should be made available within Excel Services.
• Items in the Workbook: This allows you to identify specific objects in the Excel document to publish for use in Excel Services. Objects to publish can include named ranges, charts, tables, and PivotTables.

b. On the Parameters tab specify any cells that should be made editable in the published sheets. Only cells that have been named in the Excel sheet can be set as parameters.

c. Once all of the appropriate options have been selected click the OK button.

4. On the Save As window click the Save button.

The Excel items are saved for use within Excel Services, and the items are opened in the web browser.
To publish Excel resources to Excel Services using Excel 2010 perform the following steps:


1. Select the File ribbon and choose the Save & Send option.

2. On the Save & Send page select the Save to SharePoint option, select a library in a site that has the SharePoint Server Enterprise Site Features enabled and click the Publish Options button (Please refer the following figure)



3. On the Publish Options window:
a. On the Show tab select the type of items to include. Items available for
inclusion are:
• Entire Workbook: This will publish the entire Excel document for use in Excel Services.
• Sheets: This will allow you to identify specific worksheets in the workbook that should be made available within Excel Services.
• Items in the Workbook: This allows you to identify specific objects in the Excel document to publish for use in Excel Services. Objects to publish can include named ranges, charts, tables, and PivotTables.

b. On the Parameters tab specify any cells that should be made editable in the published sheets. Only cells that have been named in the Excel sheet can be set as parameters.

c. Once all of the appropriate options have been selected click the OK button.

4. On the Save & Send page click the Save As option.

5. On the Save As window click the Save button.

The Excel items are saved for use within Excel Services, and the items are opened in the web browser.

If you have any queries or doubts regarding the above mentioned information then please let me know,Thanks..

19 September, 2010

SharePoint 2010: Content Variations

Organizations that operate globally often need to publish resources in several languages to properly support all users. The process of creating the various translations, or variations, of the content can be time consuming and difficult to manage.

SharePoint Server provides site owners the ability to define site variations and define primary and variation locations for content needing to be translated. Changes made to the primary location can be automatically or manually propagated to the associated variations. The variation capabilities can be integrated with SharePoint workflows that drive the updating process for variations. These workflows can also be integrated with third-party translation services to automate the actual creation of the translated versions.

When users access a site that participates in a variation set, they will be automatically taken to the variation supporting their language. SharePoint Server makes this determination based on the web browser’s language preferences. If no variation exists that supports the users’ browser language preferences, they are taken to the primary site page for the variation set.

To use the SharePoint Server variation capabilities, you must configure the variation settings within the site collection. These settings include the identification of the source location where variations will be created and the configuration of variation creation management and notification settings.

To configure the variation settings for the site collection, follow these steps:

1. Navigate to the Site Settings page for the top-level site in the site collection.


2. On the Site Settings page, in the Site Collection Administration section, click the Variations link.

3. On the Variation Settings page, follow these steps:

a. In the Variation Home section, enter the site that will act as the starting point for creating variations.

b. In the Automatic Creation section, select if site and page variations should be automatically created.

c. In the Recreate Deleted Target Page section, select if new target pages should be re-created when source pages are republished.

d. In the Update Target Page Web Parts section, select if changes to web parts should be propagated to target pages.

e. In the Notification section, identify if e-mail notifications should be sent to the site owner when the variation system creates or updates a site page.

f. In the Resources section, select if the variation page should use the same resources as the source or if copies of the resources should be created for use by the variation.

g. Once all information has been appropriately updated, click the OK button.

Done !!-The variation details are updated and you are returned to the Site Settings page.


If you have any doubts/queries regarding the above mentioned information then please let me know,thanks..

SharePoint 2010:Working with Site and Site Collection Features

Site and site collection features provide added capabilities to your SharePoint environment. While SharePoint Foundation 2010 only provided a couple of site and site collection features, SharePoint Server introduces many additional features. Some of these features support the capabilities provided through the site templates while others introduce a variety of new capabilities.

Before publishing a post on how to activate the site features, I am writing this post to describe brief introduction behind some usefull features which would be beneficial from business point of view.

Site Features

The site features available by default in SharePoint Server follow:

Content Organizer: Allow for the creation of rules based on metadata to route content to the appropriate location.

E-mail Integration with Content Organizer: Extend the site content organization features to receive and route e-mail messages.

Group Work Lists: Use this to identify if the Group Work Calendar list should be made available.

Hold and eDiscovery: Allow for the tracking of external actions that suspend the disposition of documents.

Metadata Navigation and Filtering: Provide lists with settings pages allowing them to be configured to use metadata tree views and filter controls.

Offline Synchronization for External Lists: Enable the ability to synchronize lists with Outlook and SharePoint Workspace.

PerformancePoint Services Site Features: Make the PerformancePoint Services list and document library templates available.

SharePoint Server Enterprise Site features: For enterprise license deployments of SharePoint Server, this feature activates the enterprise services, such as the business data catalog, forms services, and Excel services.

SharePoint Server Publishing: Include resources like the Pages library needed to create and publish web pages within a site.

SharePoint Server Standard Site features: Enable the standard SharePoint Server features, such as user profiles and searching.

Team Collaboration Lists: Also available in SharePoint Foundation and this feature enables team collaboration services in a site that allows for the use of lists and libraries.

Wiki Page Home Page: Create a wiki page as the site’s home page.



Site Collection Features

The following site collection features are available in SharePoint Server 2010:

Advanced Web Analytics: Makes web analytics reports available.

Content Type Syndication Hub: Creates a site that will act as the enterprise metadata hub site.

Custom Site Collection Help: Creates a library used to store custom help documents for the site collection.

Disposition Approval Workflow: Makes available a standard workflow that is used to manage the expiration of documents.

Document ID Service: Assigns IDs to documents. (These IDs can be used to retrieve documents independent of their current location.)

Document Sets: Provides the content types needed to create document sets that allow the grouping of multiple documents to be managed as a single entity.

In Place Records Management: Enables the ability to define and declare records

Library and Folder Based Retention: Allow list managers to set retention schedules on libraries and folders.

PerformancePoint Services Site Collection Features: Enables the PerformancePoint Services content types and site definitions

Publishing Approval Workflow: Enables a workflow for the routing of pages for approval as part of the page publishing process

Reporting: Enables SharePoint Foundation 2010 report creation capabilities.

Search Server Web Parts: Makes available web parts that are needed by Search Center sites

SharePoint 2007 Workflows: Makes the set of workflows that are available as part of SharePoint 2007 (MOSS) available within the SharePoint 2010 server environment

SharePoint Server Enterprise Site Collection features: Enables enterprise site features that are available with the enterprise license of SharePoint Server, such as business data catalog, forms services, and Excel services

SharePoint Server Publishing Infrastructure: Enables publishing-related functionality, such as welcome page management, master pages, and page layouts.

SharePoint Server Standard Site Collection features: Enables standard features introduced by SharePoint Server, such as user profiles and enterprise searches

Three-state workflow: Makes available a standard workflow that is used to track the state of items in a list

Workflows: Enables the SharePoint Server 2010 standard workflows

Any of the listed site and site collection features can be enabled or disabled to control the capabilities made available in the SharePoint environment.

Note: Some site and site collection features work together to provide sets of capabilities. It is important to understand the complete impact of disabling a site or site collection feature before making changes.

If you have any doubts/queries regarding the above mentioned information then please let me know,thanks..

12 September, 2010

Item-Level Permissions:Part2

In addition to managing security for the list as a whole, you can set security on an individual list item to further refine who can access the information stored in the list. List item security is managed similar to list security, using the same concept of inheritance and permission levels.

To edit permissions on a specific list item, perform the following steps:

1. On the list page, click the Manage Permissions link in the context menu of the desired list item. You can also select the Item Permissions command from the Manage group of the List Tools - Items ribbon after selecting the desired list item.

2. On the Permissions screen, select the Stop Inheriting Permissions command from the Inheritance group on the Permission Tools – Edit ribbon.

3. On the confirmation message, click the OK button.

4. On the Permissions screen, check the box next to one or more users, and select the Edit User Permissions command from the Modify group on the Permission Tools Edit ribbon.

5. On the Edit Permissions window, select the appropriate permission levels for this user.

6. Click the OK button.

The Permissions page will refresh and display the updated user permissions. Giving users Read access to a specific list item will cause them to not see the Edit Item option in that list item’s context menu or anywhere else where it would otherwise be displayed.

Just like list security, you can grant a user access to a specific list item by selecting the GrantPermissions command from the Grant group of the Permission Tools-Edit ribbon and performing the same actions described previously to add users to a list. You can also revoke users’ access to the list item completely by checking the box next to their names and selecting the Remove User Permissions command from the Modify group. Revoking a user’s access completely will cause the list item to never
be displayed to that user when viewing the list.

Note: List item security can be applied to folders within the list by following the same steps needed for list items after selecting the Manage Permissions option in a folder’s context menu. Use this to control user permissions to groups of related list items or to hide entire folders of content from specific users or groups.


If you have any doubts or queries regarding the above mentioned information then please let me know,Thanks...

SharePoint 2010: List Permissions-Part1

An important decision when managing your list is who will have access to the content and how much control over the content they will be given. Lists leverage the permission levels of the site they live in to determine the security of the user. When first created, a list inherits the security settings of the site it is in.

Unique List Permissions

You can decide to break this inheritance and give unique permissions to the list. This is most common when working with lists that contain sensitive information that not all site users should see. Another example is a list that all users should have the ability to update, even those site users who normally have only a Read permission level.

To break permission inheritance for a list, perform the following steps:

1. On the list page, select the List Permissions command from the Settings group on the List Tools - List ribbon.
2. On the Permissions screen, select the Stop Inheriting Permissions command from the Inheritance group on the Permission Tools – Edit ribbon.
3. On the confirmation message, click the OK button.

Once these steps are completed, you will be able to manage the permissions levels for users within the list. At any time, you can revert to the site’s users and permission level security by selecting the Inherit Permissions command from the Inheritance group on the Permission Tools – Edit ribbon.

As an administrator, you have many options for changing list permissions. Access can be granted based on SharePoint groups or domain users and groups.

To add users to the list security, perform the following steps:

1. On the Permissions page, select the Grant Permissions command from the Grant group on the Permission Tools - Edit ribbon.
2. On the Grant Permissions window, enter the e-mail address or account name of one or more users or groups you wish to add in the Users/Groups box. You can verify that the information you entered is correct by clicking the Check Names icon.
3. If you do not know the exact e-mail addresses or account names of the people or groups you want to give access to, you can click the Browse icon. This icon will open a window that will allow you to search for accounts within your organization. When you have found a user you wish to grant list access to, select that user in the list, and click the Add button. After you have done this for all of the users and groups you wish to add, click the OK button.
4. Select the permission level that you want to use to determine your new users abilities in the list. These permission levels are managed in the site.
5. Click the OK button.

You will now notice that the users you have added show up in the list of users on the Permissions page. You can edit the permissions of a user or group by checking the box next to the name and selecting the Edit User Permissions command from the Modify group of the Permission Tools - Edit ribbon.

Likewise, you can revoke a user’s access to the list by checking the box next to the name and selecting the Remove User Permissions command from the same ribbon group.


If you have any doubts or queries regarding the above mentioned information then please let me know,Thanks...

SharePoint 2010: Creating Lists

A custom list is the most basic type of list in SharePoint and provides a good introduction to using and managing SharePoint lists. There are multiple ways to create a custom list in SharePoint. The quickest way is to choose the Custom List option on your site’s Create page or window.

SharePoint’s list creation functionality is provided in two varieties depending on the availability of Microsoft Silverlight on your computer. Without Silverlight, you are presented with a Create page that contains links to various types of list organized into sections based on their functional usage. With Silverlight, you are shown a Create window allowing you to filter items you can create by Type and Category.

You will also notice an option on the Create page or window that will enable you to create a custom list using the Datasheet view rather than the standard view that the Custom List option uses.

To create a new custom list without Silverlight installed, follow these steps:

1. On the site’s home page, click the More Options… link in the Site Actions menu.
2. On the Create page, click the Custom List link in the Custom Lists section.
3. On the New page, enter a name and description for the list.
4. Select Yes under the Navigation options if you want to show a link to this list
on the Quick Launch area of the site.
5. Click the Create button.


To create a new custom list using the Silverlight Create window,follow these steps:

1. On the site’s home page, click the More Options… link in the Site Actions menu.
2. On the Create window, select the Custom List icon in the Installed Items section.
3. In the Custom List section, click the More Options button.
4. In the Name and Description section, enter a name and description for the list.
5. Select Yes under the Navigation options if you want to show a link to this list on the Quick Launch area of the site.
6. Click the Create button.

That's it-Done, The custom list has been successfully created.. If You have any queries or doubts regarding the above mentioned info then please let me know,Thanks..

SharePoint2010: Site Collection Auditing



SharePoint Server provides the ability to audit the usage of your SharePoint environment. The SharePoint Server auditing capabilities allow you to track all activities that occur within the environment. The site collection administrator has the ability to set auditing requirements within the environment that determine the types of actions that should be tracked. Reports are then available that can be used to review the logged events. These reports could also be used to create any needed audit reporting or statistics. You also have the ability to set audit logging settings to control the volume of audit information kept over time.

To manage audit settings for a site collection, follow these steps:

1. Navigate to the Site Settings page for the top-level site in the site collection.

2. On the Site Settings page, in the Site Collection Administration section, click
the Site Collection Audit Settings link.

3. On the Configure Audit Settings page, identify any audit log trimming settings,
and select the items to audit:

a. In the Audit Log Trimming section, identify if automatic audit log trimming
should be enabled, identify the number of days of audit log data to retain,
and specify a location to store audit reporting before trimming the audit log.

b. In the Documents and Items section, check the boxes in front of the events
to audit which can include the following:
• Opening or downloading documents, viewing items in lists, or viewing
item properties
• Editing items
• Checking out or checking in items
• Moving or copying items to another location in the site
• Deleting or restoring items

c. In the Lists, Libraries, and Sites section, check the boxes in front of the items
to audit which can include the following:
• Editing content types and columns
• Searching site content
• Editing users and permissions

d. Once all of the appropriate audit options have been set, click the OK button.

The auditing options are set, and you are returned to the Site Settings page.
The information about audited actions will be tracked as the associated actions occur in the environment. You can then run the audit reports to view the audit history for captured events.

To view the auditing reports, follow these steps:

1. Navigate to the Site Settings page for the top-level site in the site collection.
2. On the Site Settings page, in the Site Collection Administration section, click
the Audit Log Reports link.
3. On the View Auditing Reports page, click the name of the report you want to
execute.
4. For the Run a Custom Report option, the Run a Custom Report Page is
presented.


On this page, follow these steps:

a. In the File Location section, select where the report should be saved once it
is generated.

b. In the Location section, check if the report should be restricted to a specific
list, and if so, select the web site where the list is located and select the list.

c. In the Date Range section, specify the optional Start Date and/or End Date to
which the report should be restricted.

d. In the Users section, specify which users the report should be restricted to.

e. In the Events section, specify the events the report should be restricted to.

This list can include the following events:
• Opening or downloading documents, viewing items in lists, or viewing
item properties
• Editing items
• Checking out or checking in items
• Moving or copying items to another location in the site
• Deleting or restoring items
• Editing content types and columns
• Searching site content
• Editing users and permissions
• Editing auditing settings and deleting audit log events
• Workflow events
• Custom events

f. Once all of the appropriate report settings have been entered, click the OK

5. The report is generated, and the file is saved to the library specified.The generated XML file is saved to the location you specify, and you are returned to the View Auditing Reports page.

You can select to download any of the listed auditing reports. The following are
the reports included:
• Content Activity Reports
• Content modifications: Lists logged events for changes to site content
including documents, list items, and pages
• Content type and list modifications: Lists logged events for modifications to
content types, lists, and libraries
• Content viewing: Lists logged events for viewing content within the site
• Deletion: Lists logged events for content deletions and restorations
• Custom Reports
• Run a custom report: Enables you to create a custom report to retrieve logged
events for specific actions
• Information Management Policy Reports
• Expiration and Disposition: Lists logged events related to the expiration and
disposition of content
• Policy modifications: Lists logged events related to the creation and use of
content information management policies
• Security and Site Settings Reports
• Auditing settings: Lists logged events related to changes made to the auditing
settings
• Security settings: Lists logged events related to SharePoint security
configuration settings


If you have any queries or doubts regarding the above mentioned information then please let me know,Thanks...

10 September, 2010

SharePoint Server 2010 Web Parts

When SharePoint Foundation is installed, there are only a few web parts available, but that number jumps to many dozens of web parts when your environment includes SharePoint Server 2010; also, that number is dependent on whether the standard or enterprise version is installed. With large collections of web parts like this, it is beneficial to maintain the category information for all web parts by editing the information in the Web Part Gallery; this helps ensure that users are able to easily find relevant web parts for their pages.

Business Data

These web parts allow you to display and interact with data in SharePoint Server 2010Business Data Connectivity. Business Data Connectivity allows SharePoint to integrate with external data sources. This group also contains web parts to display information from Excel Services or Visio Services.

Examples of web parts in the Business Data category follow:

•Business Data Item: Displays a single item from a source in Business Data Connectivity
•Business Data List: Displays a list of items from a source in Business Data Connectivity
•Excel Web Access: Displays an Excel 2007 workbook in a web page format

Content Rollup


This category exists in SharePoint Foundation, but it includes many more web parts when SharePoint Server 2010 is installed in your environment.

Examples of web parts in the Content Rollup category include:

•Content Query: A powerful web part that provides numerous web part properties
to specify how it displays data from multiple lists, libraries, and sites within the site collection
•RSS Viewer: Displays the results of an RSS feed, which is either an external feed or from a SharePoint list
•Site Aggregator: Allows you to create a tab for each site you choose that displays documents and tasks that are assigned to you

Filters

These web parts allow you to filter information in other web parts using web part connections.

Examples of web parts in the Filter category follow:

•Choice Filter: Filters the contents of a web part by allowing the user to pick an option from a list of values
•Date Filter: Filters the contents of a web part by allowing the user to pick a date
•Query String Filter: Filters the contents of a web part by using data in the query string (URL) of the page

Outlook Web App

These web parts connect to Outlook Web Access to incorporate your Outlook information into the page.

Each of these web parts requires Exchange 2003 or later. Examples of web parts in the Outlook Web Access category follow:

•My Calendar: Displays your Exchange calendar
•My Contacts: Displays your contacts from Exchange
•My Inbox: Displays your Exchange inbox

PerformancePoint

This category allows you to display and control PerformancePoint reports and scorecards to create an interactive dashboard. The use of these web parts requires that PerformancePoint be properly configured in your environment and that the necessary objects be created before configuring the web parts.

Examples of web parts in the PerformancePoint category follow:

•PerformancePoint Report: Displays a report from PerformancePoint that can be
connected to other web parts to create an interactive dashboard
•PerformancePoint Scorecard: Displays a scorecard from PerformancePoint that
can be connected to other web parts as part of a dashboard


Search
These web parts provide the functionality needed for searching within SharePoint. Most of these web parts are used in the Search Center site template and in the standard search and search results pages.

Examples of web parts in the Search category follow:

•Search Box: The standard search entry
•Search Core Results: Displays search results

Social Collaboration

This category exists in SharePoint Foundation, but it includes many more web parts when SharePoint Server 2010 is installed in your environment.

Examples of web parts in the Social Collaboration category follow:

•Note Board: Provides the ability for users to leave notes on the page for feedback
or collaboration purposes that are viewable by other users
•Tag Cloud: Displays tag information about the current page

09 September, 2010

SP2010: Exporting and Importing Web Parts

After you have properly configured a web part, including both common and unique properties, you may want to reuse the web part with the same settings in other sites or pages. SharePoint provides you with this capability by allowing you to export most web parts and import them into another site.

Exporting the web part creates an XML file with a .webpart or .dwp extension that contains the properties of the web part and the information SharePoint needs to duplicate its functionality. If the Export Mode web part property is set to the Non-sensitive Data Only option, the export will not include certain properties marked as sensitive information (such as passwords).

To export a web part, follow these steps:

1. On the page, click the Edit Page link in the Site Actions menu.
2. On the title bar of the web part you wish to export, open the Web Part Menu by
clicking the down arrow on the right.
3. On the Web Part Menu, click the Export... option.
4. On the File Download dialog box, click the Save button.
5. On the Save As dialog box, browse to the directory where you want the webpart file placed and click the Save button.

To use this exported web part (or any other .webpart or .dwp file provided to you by other users), you must import it into the site as a user with the Full Control permission level where you want to use the web part. You can import a web part in one of two ways. The first way to import the file prevents others from using the web part, but it must be done each time you want to add it to a page.


To import a web part using this method, follow these steps:

1. On the page, click the Edit Page link in the Site Actions menu.
2. On the page, select the Web Part command from the Web Parts group on the Editing Tools - Insert ribbon.
3. On the Web Parts bar, click the down arrow next to Upload a Web Part.
4. On the Upload a Web Part pane, click the Browse button.
5. On the Choose File dialog box, browse to the .webpart or .dwp file, select it, and click the Open button.
6. On the Add Web Parts pane, click the Upload button.
7. In the Categories section of the Web Parts bar, select the Imported Web Parts category and add the web part to the page

The other process used to import a web part file causes the web part to appear in the other categories available in the Web Parts bar. This is beneficial because other users can easily add instances of this imported web part by using the appropriate category, whereas the previous import method was a one-time-use scenario.

To import a web part using this method, follow these steps:

1. On the site, click the Site Settings link in the Site Actions menu.
2. If the site is not a top-level site, click the Go to Top Level Site Settings link
under the Site Collection Administration section.
3. On the Site Settings page, click the Web Parts link under the Galleries section.
4. On the Web Part Gallery page, select the Upload Document command from
the New group on the Library Tools - Document ribbon.
5. On the Upload Web Part window, click the Browse button.
6. On the Choose File dialog, browse to the .webpart or .dwp file, select it, and
click the Open button.
7. On the Upload Web Part window, click the OK button.
8. On the Edit Item window, edit the name, title, and description that were
loaded from the file. Select a Group and, optionally, any of the
Recommendation Settings to determine how the web part is organized and
presented to users on the Web Parts bar.
9. Click the Save button.

The Web Part Gallery page will refresh and contain your newly uploaded webpart in the list. The Web Part Gallery page also lets you edit, delete, and manage security for web partsusing the same familiar capabilities found in lists and libraries. The Edit Item window for a web part in the Web Part gallery contains an Export command in the Actions group on the Edit ribbon, allowing you to export the web parts as files for importing elsewhere.


Please let me know in case of any queries/questions,I hope the above information will helps you to understand the detailed know-how about export-import process of webparts..Thanks..

SP2010:How to Manage Webparts On Pages

After adding web parts to a page, you may need to do many other tasks to create a useful SharePoint page. Rearranging, closing, deleting, and connecting web parts are all done after placing the page in Edit mode. Edit mode provides you with the option to modify the presentation of the page; note that you don’t need any programming knowledge.

After placing web parts on the page, you may determine that the page would function better if the web parts were presented in a different order or in a different location. SharePoint allows you to easily rearrange the web parts on the page once the page is in Edit mode. Edit mode displays the current page, making the management features available to you. To set the page to Edit mode and rearrange web parts, follow these steps:

1. On the page, click the Edit Page link in the Site Actions menu.
2. The page will be refreshed, displaying the content areas and web part zones. The page is now in Edit mode.
3. Click the title bar of a web part you want to move; and while holding down the mouse button, drag the web part to another location in a content area or web part zone on the page. If placing the web part in a zone, a bar will appear when the mouse is in a valid location to place the web part.
4. When the mouse is in the correct location within the content area or the bar
appears in the desired location within a web part zone, release the mouse button.

You may also want to remove web parts that you have determined should no longer appear on the page. There are three ways to keep a web part’s content from displaying on the page. The first is to minimize it. Minimizing a web part keeps the title bar displayed, but does not display the contents of the web part to the user.

To minimize a web part on a page, follow these steps:

1. On the web part page, click the Edit Page link in the Site Actions menu.
2. On the title bar of the web part you wish to minimize, open the Web Part menu by clicking the dropdown arrow on the right.
3. On the Web Part menu, click the Minimize option. You can also select the Minimize command from the State group on the Web Part Tools - Options ribbon.

If you face any issues/queries regarding the above procedure then please let me know,Thanks...

08 September, 2010

SharePoint 2010: How to add a webpart to Pages

Web parts are an important factor in determining how information is presented to SharePoint users.These reusable components can be placed on pages and configured to present SharePoint content in themost beneficial way for your site.

Web parts are not limited to displaying SharePoint information. They can also provide you with the ability to search and manage data in external databases and file systems. Custom web parts can bedeveloped to provide much of the functionality found in other applications, thereby integrating your SharePoint environment with your other existing systems.

Once you have created a site or have added either a Web Part page, Publishing page, or general content page to an existing site, you will want to customize the display of the page by adding web parts. This is accomplished directly on the page using ribbon commands.

For Web Part pages and some Publishing page layouts, web part zones are provided to manage where web parts are placed within the page. Add a web part to a web part page in a collaboration siteusing the following steps:

1. On the page, click the Edit Page link in the Site Actions menu.

2. On the web part page, click the Add a Web Part link in the web part zone where you want the new web part placed.

3. In the Categories section of the Web Parts bar, select the category that most closely corresponds to the type of functionality you are looking for in a web part.

4. In the Web Parts section, select the web part you want to place on the page.

5. In the About The Web Part section, select the desired web part zone in the Add The Web Part To selection box.

6. Click the Add button.

7. Select the Stop Editing command from the Edit group on the Page ribbon.


Done !! The webpart has been successfully placed on your page..

If you have any queries/doubts regarding the above mentioned procedure then please let me know,Thanks..

07 September, 2010

Dataview does not work work in SP 2010

Hey Guys, 

This is another post based on Office 2010 issue in combination with SharePoint.

Error Message:

The list cannot be displayed in Datasheet view for one or more of the following reasons:
-A datasheet component compatible with Microsoft SharePoint Foundation is not installed.
-Your Web browser does not support ActiveX controls.
-A component is not properly configured for 32-bit or 64-bit support.

What happens exactly:
I have Office 2010 installed but when I tried to open a list in Sharepoint Server 2010 in dataview I get the "datasheet component combatible with SharePoint Foundation is not installed" error.

Resolution:

after lots of research n troubleshooting, i found out this great article which is published from Microsoft:

If your business needs justify using the 64-bit version of Office 2010, you can install the 2007 Office System Driver: Data Connectivity Components to enable the Datasheet component. These components are available from the 


Microsoft download center:http://www.microsoft.com/downloads/details.aspx?familyid=7554F536-8C28-4598-9B72-EF94E038C891&displaylang=en

Office 2007: Microsoft Office Diagnostics

This is one of the vital feature which is enclosed by Microsoft in Office 2007.

Microsoft Office Diagnostics in the 2007 Microsoft Office system is a series of diagnostic tests that can help you discover why your computer is crashing (closing abnormally). The diagnostic tests can inform you about problems and might identify ways that you can solve other problems.
When Office Diagnostics determines that the data might help diagnose and fix a problem.

The Office Diagnostics are:

Setup Diagnostic:
This test checks for corruption in the files and registry settings in your 2007 Microsoft Office system installation. Files and settings can be corrupted by malicious viruses or by hardware that is faulty or incorrectly configured.

Disk Diagnostic:
This test looks for evidence of problems with your hard disk. Specifically this test checks for errors logged by the following:

-The Windows system event log.

-The Self-Monitoring, Analysis and Reporting Technology (SMART) feature of your hard disk. SMART is a feature that some disk drive manufacturers provide to give users advance notice of potential hard disk failure.

Memory Diagnostic:
This test verifies the integrity of your computer's random access memory (RAM).

Check for known solutions:
This test reviews the data on crashes of the 2007 Office release that have recently occurred on your system. The test then connects to a server to look for any solutions that might be available for the problems that caused these crashes.

How to run Office Diagnostics:

Click the Microsoft Office Button, and then click Excel Options.
Click Resources.
Click Diagnose, click Continue, and then click Start Diagnostics.


If you face any issues/queries regarding the above information then please let me know,Thanks.

29 August, 2010

Change the Site Logo in SharePoint 2010

One of the most important section of SharePoint site is a LOGO (A name, symbol, or trademark designed for easy and definite recognition)

Please refer the following steps as How to change the site logo on your SharePoint site:

One of the most vital thing is logo location.URL location- Upload a logo to a document library/“14 hive” (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES).

1. Click on Site Actions from the top left of the site and select Site Settings.

2. Click “Title, description, and icon” under the Look and Feel section on the Site Settings page.

3.Enter your logo URL location and a description

For 12 hive image location: the URL location would be /_layouts/images/yourlogo.gif

4.Click Ok and Site logo has been successfully applied on your site...

If you face any issues regarding the above information then please let me know, Thanks..

SP 2010: Certification exam details for SharePoint 2010 published

SharePoint 2010 certifications are mainly classified into two main sections:

1. For IT Professionals: SharePoint 2010 drives productivity and offers a scalable unified infrastructure and flexible deployment.

2. For developers, SharePoint 2010 provides a business collaboration platform you can use to rapidly build solutions for your business needs.



For the IT Pros

New on for IT Pros are 2 certifications. MCTS SharePoint 2010 Configuring and MCITP SharePoint 2010.

•70-667 TS: Microsoft SharePoint 2010, Configuring
Microsoft Official Curriculum: Will cover configuration of SharePoint 2010 including deployment, upgrade, management, and operation on a server farm.

•70-668 PRO: SharePoint 2010, Administrator
Microsoft Official Curriculum: Will cover advanced SharePoint 2010 topics including capacity planning, topology designing, and performance tuning.

For developers

Also for developers there will be 2 new certifications. MCTS SharePoint 2010 Application Development and MCPD SharePoint 2010.

•70-573 TS: Microsoft SharePoint 2010, Application Development
Microsoft Official Curriculum: Five-day instructor-led course designed for developers with six months or more of .NET development experience. Course covers what you need to know to be an effective member of a SharePoint development team using Visual Studio 2010.

•70-576 PRO: Designing and Developing Microsoft SharePoint 2010 Applications
Microsoft Official Curriculum: Five-day instructor-led training course designed for development team leads who have already passed the Developing on SharePoint 2010 technical specialist exam. The course covers choosing technologies for and scoping a SharePoint project, best practices for SharePoint development, configuring a SharePoint development environment, advanced use of SharePoint developer features, and debugging of code in a SharePoint project.

For more information, Please refer this site:
https://partner.microsoft.com/40121316?msp_id=sharepoint2010ready

Please let me know in case of any doubts/queries, I would be more than happy to help you as well as resolves your issues,Thanks...

09 July, 2010

Site Prompts for Credentials + How to add your sharepoint site in trusted file location zone - SharePoint 2007 and SharePoint 2010

This is a very common issue in which the SharePoint site prompts for credentials i.e. username and password. By default, SharePoint sites should automatically log you in via your existing Windows credentials without ever asking any identity.

Yesterday, one of my user faced the same problem n would like to share the resolution with all of u.

Internet Explorer Security Settings: How to add your SharePoint site in trusted file location zone

Open the Internet Explorer/Browser

1.   Tools

2.   Internet Options

3.   Select Security Tab

4.   Sites Button

5.   Enter the website name (URL) in Add this website to the zone.

6.   If your SharePoint site is NOT using SSL, make sure you uncheck the box require server verification (https :) for all sites in this zone prior to adding it.

7.   Click Ok once and you will be redirected to following window:

8.   Click on Custom Level Tab now

Note: If you are getting the above tab greyed out then it means that you don’t have admin rights on your machine.

9.   Scrolls towards the bottom and select the option that says
"AUTOMATIC LOGON WITH CURRENT USERNAME AND PASSWORD"

Click OK Everything

Open your SharePoint site in a new browser and check the results

The above steps will resolves your login prompts issue and you should be able to access the SharePoint without any problems!!!

If you face any issue then please let me know... I would be more than happy to help you and resolves your queries as soon as possible. Thanks you.

05 July, 2010

The form submission cannot be processed

The form submission cannot be processed because it exceeded the maximum length allowed by the web administrator. Please resubmit the form with less data.
Troubleshoot issues with Windows SharePoint Services.
 
Whenever you are trying to upload a file into the SharePoint with more than 50MB, you will get this error. By default, files in SharePoint document libraries are limited to 50mb.

Solution: (How 2 change the Upload Limit)
Go to Central Administration Site
1)   Go to Application Management tab
2)   Select the specific web application in which you are facing the problem-->select General Settings
3)   Click on “Web application general settings” under “SharePoint Web Application management”, and change the “Maximum upload size” to 60 MB (as per your requirement).
4)   Click “OK”

Please try to upload the document again and check the results

This time the document will upload without any issues..

Note:
Client machines have some problems as uploading large files may have additional issues due to HTTP timeout, IIS thread execution time outs. Check the web.config file under your web app. There is a setting under system.web to change the file size upload limit. The UI version saves the setting in the content db not the physical web.config under the inetpub\wwwroot folder structure.

I hope the above information will be useful to resolve this issue... in case of any problems then please let me know, Thanks!!