Through this blog, it is my effort to share experiences with the community and make the journey enjoyable.

Thursday, January 14, 2010

SharePoint 2010 - SharePoint Designer settings

Microsoft Office SharePoint Designer is a free WYSIWYG HTML editor and web design program from Microsoft for SharePoint and other websites and is part of the SharePoint family of products. It is part of the Microsoft Office 2007 & 2010 family.

In SharePoint 2010, administrators would be able to control usage of SharePoint Designer in their environment. Now several administration controls and commands help channel SharePoint Designer into the right hands and onto the right pages. There are following settings available for SharePoint Designer administrator :
  • De-activate SharePoint Designer entirely (but only if it's absolutely necessary!)
  • Disable unghosting of web pages
  • Turn off master page editing
  • Lock the URL of a web site

These settings are available at following places -

  1. Central Administration : 'General Application Settings' group ( below snapshot )

  • On clicking of 'Configure SharePoint Designer Settings' link, product displays the SharePoint Designer settings at webapplication level. ( Below Snapshot ). At webapplication level, all the settings are enabled. Farm Administrators can change their settings at the webapplication level. If SharePoint Designer is disabled at the webapplication level, it also disables the usage at all the containing sitecollections.


2. In Site Settings page in Site Collection : Under 'Site Collection Administration' group.



On clicking of 'SharePoint Designer Settings' link, product displays the SharePoint Designer settings at sitecollection level. ( Below Snapshot ).




SharePoint Designer Groups - Furthermore, a new permission group, called Designer, helps target those users who really need SharePoint Designer.

Wednesday, January 13, 2010

SharePoint 2010 Management Shell - Features CmdLets

The SharePoint Management Shell in SharePoint Foundation 2010 provides an extensive set of Windows PowerShell cmdlets that make development, deployment, and administration of SharePoint 2010 easier and more efficient. Management Shell contains the Powershell cmdlets for SharePoint, by using this we control and manage the SharePoint operations like we done in STSADM command.

Powershell cmdlets for managing SharePoint Features -

PS C:\Users\Administrator> get-command *feature*

CommandType Name Defintion


----------- -------- ------------------------------------

Cmdlet Disable-SPFeature Disable-SPFeature [-Identity...

Cmdlet Enable-SPFeature Enable-SPFeature [-Identity]...

Cmdlet Get-SPFeature Get-SPFeature [[-Identity] <...

Cmdlet Install-SPFeature Install-SPFeature [-Path] <S...

Cmdlet Uninstall-SPFeature Uninstall-SPFeature [-Identi...

Help is available for these SharePoint 2010-specific cmdlets in Windows PowerShell. Type get-help and then type the name of the cmdlet. For example, to find help about SPServiceApplication, type get-help get-SPServiceApplication.


PS C:\Users\Administrator> get-help get-spfeature

NAME

Get-SPFeature

SYNOPSIS

Returns the SharePoint Features based on a given scope.

SYNTAX

Get-SPFeature [-Identity <SPFeatureDefinitionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Limit <String>] [<CommonParameters>]

Get-SPFeature [-Identity <SPFeatureDefinitionPipeBind>] [-AssignmentCollect ion <SPAssignmentCollection>] [-Farm <SwitchParameter>] [-Limit <String>] [ <CommonParameters>]

Get-SPFeature [-Identity <SPFeatureDefinitionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Limit <String>] [-Sandboxed <SwitchParameter>] [-Site <SPSitePipeBind>] [<CommonParameters>]

Get-SPFeature [-Identity <SPFeatureDefinitionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Limit <String>] [-Web <SPWebPipeBind>] [<CommonParameters>]

Get-SPFeature [-Identity <SPFeatureDefinitionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Limit <String>] [-WebApplication <SPWebApplicationPipeBind>] [<CommonParameters>]

DETAILED DESCRIPTION

All SPFeature sets take the Identity parameter, which can be either the relative path of the SharePoint Feature (considered the feature name) or the GUID of a Feature definition. If the Identity parameter is provided, the cmdlets attempt to find the given Feature definition or instance for the given scope. If no parameters are specified, all installed features are returned.

The Get-SPFeature cmdlet behaves differently at each scope, returning the enabled Features at each level. If no scope is provided, all installed Features are returned.

get-spfeature (returns all the installed Feature definitions in the farm )

get-spfeature -farm ( returns all the enabled Feature in the farm)

get-spfeature -webapplication (returns all enabled the Features in the Webapplication)

get-spfeature -site (returns all the enabled Features on the site <<both full trusted and particially trusted code>>)

get-spfeature -site -sandboxed (returns all installed the ptc Feature definitions on the site)

get-spfeature -web (returns all the enabled Features in the Web)

RELATED LINKS

REMARKS
For more information, type: "get-help Get-SPFeature -detailed".

For technical information, type: "get-help Get-SPFeature -full".


Share:

Wednesday, January 06, 2010

Up and running with the SharePoint 2010 Public Beta

Although, I am late by few weeks, I started with the installation for SharePoint 2010 Public Beta last week. Although, I have been following and reading lot of stuff on SharePoint 2010 in last few months. Installation was pretty neat. Very good experience as compared to SharePoint 2007 beta.

Although, I missed on installing the prerequisites through the setup and started running the prerequisites on my own. After running the required all the prerequisites, setup kept on giving me the error for 'Windows Server Features or Role Services required by the product are not enabled'. ( Attached snapshot). I tried multiple things - enabled the role services on the server.


I ran the SharePoint 2010 prerequisites which added administration roles. After that SharePoint 2010 installation was pretty straight forward. Way to go …

I am planning to share lot of technical details on different areas of SharePoint 2010 in next few weeks.

Search This Blog

Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway. All posts are provided "AS IS" with no warranties, and confers no rights. In addition, my thoughts and opinions often change, and as a weblog is intended to provide a semi-permanent point in time snapshot you should not consider out of date posts to reflect my current thoughts and opinions.

Popular Posts

Total Pageviews