Removing Recently Modified

In SharePoint 2010 we all are familiar with the following annoying quicklaunch menu:

In SharePoint 2010, the recently modified items is one of many less-used feature. In software industry we are familiar with 80-20 principal. If 80% custom wants a feature then we should go with it and if you can satisfy 80% users then you have the successful product. I guess the ‘Recently Modified’ quick link doesn’t even needed by 10% people but the link is enable by default. Maybe this is a security feature to let administrator know what files have been modified recently. But there should have an on/off option as this is less wanted feature and most of the administrators want to hide this link. Justin has already found a way to hide the option by modifying template file asdescribed in his blog. However, we can fix the issue without modifying the shared file. Specially in case of shared hosting we don’t want to modify the files from 14 hive. The two approaches described here is implemented by modifying master page. The first approach is acceptable but may have unknown side effects. On the other hand second approach is much better and less chance of side effects.

In order to solve this problem, here is my approach:

As shown in the following screen, the ‘recently modified’ quick launch uses a css class named ‘s4-recentchanges’ (shown with firebug).

So we can another property ‘display:none’ to the same css class by adding the following extra attribute to master page’s header section:

<style type="text/css">
    .s4-recentchanges
    {
        display:none;
    }
</style>

You can even put the above section in a css file and refer the file in master page. The following image shows the master page with the css class:


If you have any problem, just let me know.

Enjoy!

Sharepoint Main Roles!

Typically in a SharePoint project the the main roles are:

• SharePoint Administrator
• SharePoint Developer
• SharePoint Designer
• SharePoint Architect

SharePoint Administrator

The role of SharePoint administrator includes setting up the SharePoint infrastructure with servers and services; SharePoint 2007/2010, Exchange Server, Active Directory, Windows 2003 and 2008 Servers, SQL Server 2005/2008, IIS 6.0 and 7.0, network infrastructure, ISA server, etc. He is responsible for maintaining and optimizing the SharePoint farm.

A SharePoint administrator requires knowledge of both SQL Server and Windows Server. Since SharePoint stores all of its data in SQL Server databases, DBA knowledge is critical. However, the Windows Server knowledge required to build and maintain a SharePoint farm is considerable. The administrator role is often split between two people who work closely together: a Windows Server administrator and a SQL Server DBA.The DBA skills required are the standard set required for any SQL Server but the features of Windows Server that a SharePoint Administrator needs to have some knowledge of include:

• Good knowledge in IIS and the architecture of it
• Windows Server Manager
• Active Directory (LDAP,ADLDS,ADAM etc)
• DNS and SMTP
• Network Load Balancing (NLB)
• Firewall (Hardware and software NLB)
• Event Viewer and Performance Monitor
• PowerShell scripting will be added advantage if looking in SharePoint 2010

But I suggest some knowledge of SharePoint development experience will add extra benefits to this role.

SharePoint Developer

The main role of a developer is developing custom web parts and component for SharePoint. They should have experience in Asp.net, C#.net, web parts, master pages, Ajax developer, detailed knowledge of the SharePoint 2007 object model / 2010 client object model, JavaScript experience etc. A SharePoint developer should be well versed on .NET frame work and windows workflow foundations (WFF). The Developer should have a solid understanding of C# and or VB.net and a solid understanding of the SharePoint API as a whole. Building workflows from a completely custom Visual studio direction as well as custom coding SQL and SQL server manipulation and maintenance also required so some knowledge in DB side also needed.  XML/XSLT knowledge will also provide some extra value in development. Since most things in SharePoint are xml based or can be converted and fed as xml/xsl, these are just another set of skills are another way that the developer can increase their value. A solid understanding of IIS and editing web config files are needed for a developer.

However, the main thing is to understand the out-of-the-box functionality and SharePoint web services well enough so that you don't program something SharePoint has Out of the box. SharePoint development involves tuning functionality that SharePoint has out of the box. So we should explain how to achieve project requirements with the least amount of programming.

SharePoint Designer

There are some wiles that a SharePoint Designer is really needed for the SharePoint project. But as per my experience it is good to have a Designer in your team so the developers can focus on programming no need to waste their time on customization. Designers are responsible for all the "non-programming" customization of the SharePoint solution. Good understanding of SharePoint and the different out of the box web parts and their functionality are needed for this role. Experience with html, style sheet, caml, xml, xslt, java script, SharePoint Designer 2007/2010 and InfoPath 2007/2010 are the main areas they have to focus.

SharePoint Architect

A SharePoint Architect needs to have a thorough understanding of SharePoint (admin, developing, functions) including when and how new components/web parts should be developed. Also Microsoft Technologies in general, especially .NET 3.5, C#, Exchange, Active Directory, Office 2007/2010, IIS and infrastructure in general. Pivotal specialized role is of SharePoint architect. This is the person who can:

1.       Collect, transform, validate and map functional and non-functional requirements

2.       Plan and architect infrastructure integration

3.       Define solution

4.       Map MOST of solution requirements to existing configurable features of SharePoint

5.       Architect and POC custom code as needed.

The Architect also needs to set up the projects environments. In some cases this can be a full blown Development, Staging and Production environment. If that is the case it's very important to have all the environments match as close as possible if not be exact. The Architect also needs to understand fail over's, clustering and load balancing, for large farms. A SharePoint Architect also needs a solid understanding of alternate access mapping in MOSS, host headers, DNS entries, Kerberos configuration and multiple forms of authentication (forms auth, ntml etc).  

NOTE: Thanks people of C# Corner!

Related Note >>> http://www.c-sharpcorner.com/uploadfile/Roji.Joy/sharepoint-roles-and-responsibilities/

Talking about sharepoint as a project

Hi There!

In this post, I would like to share some of my experience related to MSF.

I expect you enjoy reading this article!

Microsoft Solution Framework: 

Contains the following Phases:

1. Envision
2. Planning
3. Development
4. Stabilizing
5. Deploying

 

 

Envision

In this phase the development team must work with the client on their SharePoint vision by aligning ideas with results. This has to be done in workshops or can be done one-on-one with client and other team members. The primary activities accomplished during envisioning are the formation of the core team and the preparation and delivery of a vision/scope document. The description of the project vision and the identification of the project scope are the main activities; we have to prepare a risk document and present the top risks along with a scope document. In this phase the development team can focus on making prototype development and technology options; feasibility analysis etc. Testing team can focus on testing strategies, testing acceptance criteria, implications etc

Planning

This is one of the important phases, here we have to develop a Statement of Work functional specification, works through the design process, and prepares work plans, cost estimates, and schedules for the various deliverables. There are three levels in the design process: conceptual design, logical design, and physical design. Each level is completed and baselined in this phase. In this phase the development team can focus on technology evaluation, logical and physical design, development plans, development estimates etc. Testing team can focus on design evaluation, testing requirements, test plan/schedule etc. Here we have to develop and finalize the Master Project Plan.

Development

In this phase developers have to focus on the scope complete milestone. Most of the development activities should be accomplished in this phase but some development work may continue into the stabilization phase. Most of this additional work is bug fixing that are raised by the testing team. In this phase we have our critical deliverables source code, executables Installation scripts and configuration settings for deployment will be handled in this. From the testing team we have to deliver test specifications and test cases. Mostly development team must concentrate on code development, infrastructure development, configuration documentation etc. Testing team must focus on functional testing, issues identification, documentation testing, updated test plan etc.

Stabilizing

The Stabilize phase is the critical step in ensuring that our solution meets client's requirements and performance to the desired level of performance.  Quality Assurance, User Acceptance testing and pilot user training all take places during this phase. Once a build has been deemed stable enough to be a release candidate, the solution is deployed to a pilot group. The stabilizing phase culminates in the release readiness milestone. Once reviewed and approved, the solution is ready for full deployment to the live production environment. Some of the important deliverables in this phase is Test results, Release notes etc. In this phase the development team must primarily focus on bug resolution, code optimization etc. Testing team must focus on testing, bug reporting and status and configuration testing.

Deploying

In this Phase our solution is finalized and is ready to bring SharePoint solution live in client environment. But if tweaking is needed then that can also be done.

Next post, I will talk about Sharepoint roles and responsabilities.

Till next post!

Sharepoint Manager 2013 / SPX

Hi There,

Here I found a cool solution when you need to deleted views inherited fromm CTs.

I expect this will help you!

Nice Coding!

Steps:

• Connect to your site – using the “Connections” menu

• Expand the RootWeb node – and then Webs
• Find the Web you’re looking for – check within the Webs node (for sub-webs)
• Expand the Lists node
• Find the list you’re looking for – for my case it’s “OATR_Test1”

• Expand the Views node – and you’ll see the RELINK and MERGE entries
• Right-click – and select “DeleteObject” (these are methods via Reflection)

• Repeat for both MERGE and RELINK
• Can close out of SPx / SharePoint Manager

That’s all you need to do !    If you look at the site/library – you’ll see they’re GONE.

Hopefully this helps with your SharePoint environment – viva la SPx !!

Adding PDF Search Capability on Sharepoint 2010

PreRequisites

• Install Windows Server 2008 following the SharePoint prerequisites (Pre-upgrade utility).
• Install SharePoint 2010 with the complete option and run the PSconfig wizard. 
• Configure required Server Farm Topology. In this example we use a Single Server Farm. 
• Create a new Search Service application. 

Configure Adobe iFilter based on steps mentioned below:

1. Install PDF iFilter 9.0 (64 bit) from http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025
2. Download PDF icon picture from Adobe web site http://www.adobe.com/misc/linking.html and copy to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES\ 
3. Add the following entry in docIcon.xml file, which can be found at: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML
   
4. Add pdf file type on the File Type page under Search Service Application
5. Open regedit
6. Navigate to the following location:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\ContentIndexCommon\Filters\Extension
7. Right-click > Click New > Key to create a new key for .pdf
8. Add the following GUID in the default value
   {E8978DA6-047F-4E3D-9C78-CDBE46041603}

• Restart the SharePoint Server Search 14
• Reboot the SharePoint servers in Farm
• Create a Test site (with any out-of-box site template) and create a document library upload any sample PDF document(s).
• Perform FULL Crawl to get search result.

Once the crawl is completed we will get search results.

NOTE: If this is a SharePoint Foundation 2010 environment additional steps will be required instead of step 4 above

Adding Searchable File Types to SharePoint Foundation 2010
http://support.microsoft.com/kb/2518465

Configuring My Sites

SharePoint My Sites are commonly referred to as “Facebook for the enterprise” and are personal site collections providing each user with the ability to store private and public information such as documents, pictures, status updates, etc easily and efficiently.  My Sites in SharePoint 2010 takes social enterprise computing to the next level and builds upon what we have come to love in previous versions.  Microsoft saw the need to continue to invest and enhance SharePoint’s social networking capabilities, and as web 2.0 technologies continue to sprawl all over the world wide web, Microsoft have again successfully set the bench mark in the enterprise by introducing an array of social computing features to enhance end user collaboration in SharePoint 2010.

In my last article I introduced and configured our first service application for our SharePoint 2010 deployment, User Profiles, which provided us with a central location for storing user details that will later be imported from a content source such as Active Directory.  Today we will continue our journey to plan and configure User’s My Sites in SharePoint 2010.

Prerequisites

This article is the 5th in my series on deploying SharePoint 2010 for the enterprise, so if you have missed the first 4, you can easily catch-up via the links below;

1. Installing SharePoint 2010 using Least Privilege Service Accounts
2. Configuring incoming email in SharePoint 2010 with Exchange 2010
3. Configuring outgoing email in SharePoint 2010 with Exchange 2010
4. Configuring the User Profile Service in SharePoint 2010

Create the My Site Web Application

We begin by first creating a Web Application that will eventually house our My Site Host and subsequent site collections.

Navigate to Central Administration / Application Management / Web Applications

Click New

Authentication: Select either Claims or Classic depending on your requirements.  I will select “Classic”

IIS Web Site: Create a new IIS web site (enter your details as per your requirements)

Authentication Provider: Select your preferred provider based on your requirements.

Public URL: Specify the URL that users will type to access their My Sites.

Application Pool: Create a new application pool and give it a descriptive name

As we have been utilizing the least privilege model whilst configuring our SharePoint farm in this series, we will click on Register a new managed account and enter the details for our My Site Application Pool Identity.  Note: This account will be required to be provisioned in Active Directory before you can proceed. e.g. In my example I have created an account called DOMAIN\sp_mysite.

Click OK

Database Name and Authentication: Specify your Database server and Database name.

Failover Server: Specify your failover server if you are utilising SQL Server database mirroring.

Click OK

You should receive the below confirmation that the Web Application has been successfully created.

Click on our newly created “SharePoint – My Site” Web Application and click on General Settings.  Proceed to fill out your Web Application specific settings such as the Default Time Zone etc.

Create the My Site Host Site Collection

Now that we have successfully created our My Site Web Application, we can now proceed to create our My Site Host Site Collection.  This will be the top level site that will house our individual user’s site collections.

Navigate to Central Administration / Application Management / Create site collections.

Ensure that the recently created My Site Web Application is selected, enter in a Title and click select the My Site Host Template located under the Enterprise Tab.  Lastly, specify your site collection administrators and click OK.

You should then receive confirmation that the top level My Site Host has been successfully created.

Setup My Sites

Now that we have successfully provisioned our My Site Web Application and Top Level Site Collection that will host our My Sites, we can continue to configure our My Site Settings.

Navigate to Central Administration / Application Management / Manage service applications.

Click on User Profiles.

Click on Setup My Sites located under My Site Settings.

Enter the details of your Preferred Search Center if you have one setup already.

Enter the URL of your My Site Host that we have just created in the previous step and the personal site location.

Finally, select your Site Naming format, configure your Language Options, Permissions and My Site Email Notifications.

Click OK.

Add our Managed Path

Because we have specified “personal” as our Personal Site Location, we will need to define our managed path against our My Site Web Application.

Navigate to Central Administration / Application Management / Manage Web Applications.

Click on your My Site Web Application and click on Managed Paths from the Ribbon.

Add “personal” as a Wildcard inclusion, click Add Path and click OK

Enable Self-Service Creation

Our last configuration step provides our users with the privilege to provision their own My Site’s by enabling the Self-Service Creation.

Navigate back to Central Administration / Application Management / Manage Web Applications.

Click on your My Site Web Application and click on Self-Service Site Creation.

Select On and click OK.

If I now browse to my My Site URL I will be presented with the following “What’s New” Page.

It is only until I click on “My Content”, that SharePoint will proceed to create my personal site as per SharePoint 2007.

My Content

As you can see, we have now successfully completed our setup of a My Site Host which will house our user’s My Sites.

There is a whole bunch of new exciting features within SharePoint 2010 and its latest iteration of My Site in which I will deep dive in future articles.

Talking about SPSchedule

The SPSchedule class allows one to specify repeating schedules for timer jobs using derived classes such as SPMinuteSchedule, SPHourlySchedule, etc. Those are pretty easy to figure out from the SDK (http://msdn2.microsoft.com/en-us/library/microsoft.sharepoint.spschedule.aspx). 

SPSchedule also provides a FromString(recurrenceValue) method that allows you to specify the same kinds of schedules from a text string, but allowable formats for the recurrenceValue string are not well documented.  Here are legal formats I’ve discovered through testing.

Formats Used Below

Format	Description	Allowable values
m	minutes	0-59
s	seconds	0-59
ddd	abbreviated name of day of week	mon, tue, wed, thu, fri, sat, sun
d	numeric day of month	1-31
mmm	abbreviated name of month	jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec
HH:MM:SS	Time of day as hours, minutes, seconds using 24 hour-clock.	00:00:00 - 23:59:59

Minute Schedule

Syntax	Description
every Interval minutes	Repeat every Interval minutes (starting at 0 seconds)
every Interval minutes at Begin	Repeat every Interval minutes starting at Begin seconds
every Interval minutes between Beginand End	Repeat every Interval minutes starting between Begin and Endseconds

Parameter	Format	Sample
Interval	m	every 15 minutes
Begin	s	every 15 minutes at 0
End	s	every 15 minutes between 0 and 15

Hourly schedule

Syntax	Description
hourly at Begin	Repeat every hour starting at Begin minutes
hourly between Begin and End	Repeat every hour starting between Begin and End minutes

Parameter	Format	Sample
Begin	m	hourly at 1
End	m	hourly between 1 and 10

Daily schedule

Syntax	Description
daily at Begin	Repeat every day starting at Begin time
daily between Begin and End	Repeat every day starting between Begin and End times

Parameter	Format	Sample
Begin	HH:MM:SS	daily at 09:00:00
End	HH:MM:SS	daily between 09:00:00 and 17:30:00

Weekly schedule

Syntax	Description
weekly at Begin	Repeat every week starting at Begin day and time
weekly between Begin and End	Repeat every week starting between Begin and End day and times

Parameter	Format	Sample
Begin	ddd HH:MM:SS	weekly at mon 09:00:00
End	ddd HH:MM:SS	weekly between mon 09:00:00 and fri 17:30:00

Monthly schedule

Syntax	Description
monthly at Begin	Repeat every month starting at Begin day of month and time
monthly between Begin and End	Repeat every month starting between Begin and End day of month and times

Parameter	Format	Sample
Begin	d HH:MM:SS	monthly at 1 09:00:00
End	d HH:MM:SS	monthly between 1 09:00:00 and 15 17:30:00

Yearly schedule

Syntax	Description
yearly at Begin	Repeat every year starting at Begin month, day of month and time
yearly between Begin and End	Repeat every year starting between Begin and End month, day of month and times

Parameter	Format	Sample
Begin	mmm d HH:MM:SS	yearly at jan 1 09:00:00
End	mmm d HH:MM:SS	yearly between feb 1 09:00:00 and apr 15 17:30:00