Force Left Nav To at least 200 Pixels wide
Force Body To at least 500 Pixels high
Know More. Do More.

 Posts

Sep 01
Published: September 01, 2010 23:09 PM by  Paul Schaeflein   Powered by: Mindsharp and Summit 7

Have you ever noticed the security paradox in computers? Most people will agree that managing Active Directory or LDAP directories is an administrative task. Not necessarily the password resets and account create (those tend to get pushed to the help desk), but the installation, configuration and general maintenance of these vital data stores is performed by the top-of-the-heap admin. (Rightly so!)

However, if the authentication provider is not one of these, say an ASP.NET Membership provider (FBA), then it usually falls to the developer to configure the solution. It seems short sighted to me that the person charged with monitoring the system would wash their hands of the technology used to secure it! But, I’m not here today to change this activity. No, I am writing about a wonderful little utility that developers and admins alike can use to get up to speed on the new claims-based identity world!

First, a little background. To setup claims authentication with SharePoint, you need to follow the directions on TechNet: Configure authentication using a SAML security token (SharePoint Server 2010). The big stumbling point for those just getting started – where do I find a Security Token Service Web application?  The answer is either ADFS2 or the WIF SDK. Well, now you have a third, and much easier option - SelfSTS.

SelfSTS is a security token service that is designed to issue tokens without a lot of configuration. For a full explanation, refer to Vittorio’s blog post. (If you are not subscribed to Vittorio’s blog, then you are not serious about claims auth!) To get SelfSTS working with SharePoint, there are a few little tweaks required outside of the steps laid out by TechNet and Vittorio. The steps below are copied and adjusted from the TechNet directions.

  1. Extract SelfSTS and run the executable from the bin\Release directory.
  2. Save the X509 Certificate that SelfSTS is using
    1. In the browser, navigate to the federation metadata page. (Be sure to start SelfSTS first. Otherwise, you will get a DNS error.) Hint: You can copy the url of the page from the SelfSTS UI. Click the "C" next to the link.
    2. In the metadata page, look for a tag named X509Certificate. Copy the inner text from any of these tags and paste it into Notepad.
    3. Save the file in Notepad. I put mine in the SelfSTS bin\Release folder with the name SelfSTS.cer
  3. In the SharePoint Management Console (PowerShell), read the certificate into a variable.
     $cert = New-Object
    System.Security.Cryptography.X509Certificates.X509Certificate2("path to cert file") 
  4. Map the claim that SelfSTS provides to one that is understood by SharePoint
     $map1 = New-SPClaimTypeMapping "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress" -IncomingClaimTypeDisplayName "EmailAddress" -SameAsIncoming 
  5. The Realm setting is used by the STS to identify the source of the authentication request. In ADFS2, there is a user interface for mapping this identifier with the url of the application. However, SelfSTS does not have such a UI. Instead, it will automatically redirect to the value provided as the realm. So, this must be the url of the SharePoint claim service.

     $realm = "https://[WebApplicationUrl]/_trust/"
  6. You will need to tell SharePoint the url of the identity provider. This is the endpoint in SelfSTS. (I’ve listed the default value below.)
    $signinurl = "http://localhost:8000/STS/Issue/"
  7. Now, the trusted login provider can be created as shown in the TechNet article.
    New-SPTrustedIdentityTokenIssuer -Name
    "SelfSTS" -Description "SelfSTS sample" -Realm $realm -ImportTrustCertificate $cert -ClaimsMappings $map1 -SignInUrl $signinurl -IdentifierClaim $map1.InputClaimType

Upon completion of these steps, the SelfSTS provider will be available for selection in the Trusted Identity Provider section when creating a new Web Application or modifying the Authentication Providers of an existing claims-based web application.

Before attempting to login to a site collection using SelfSTS, there are a few other items to address. The token signing certificate used by SelfSTS must be trusted by SharePoint. This is accomplished by the New-SPTrustedRootAuthority cmdlet in PowerShell, or via the Manage Trust link in the Security section of Central Administration. Also, be sure to grant permissions to the account provided by SelfSTS (or the all users account).

Again, the key differences when using SelfSTS is the Realm property, and that https is not required. (You are not leaving the box, so no need to incur that overhead.) Lastly, I want to point out that THIS IS FOR DEVELOPMENT PURPOSES ONLY. You should never use SelfSTS in production.

Update: Works fine under Windows 7.



Sep 01
Published: September 01, 2010 08:09 AM by  Bill English   Powered by: Mindsharp and Summit 7

I met some people this past week at the Best Practices Conference who didn't know how to find my contact information, so I thought I'd blog it.

Email: bill@mindsharp.com
Twitter: @minnesotabill
LinkedIn: Bill English
FaceBook: Bill English

Phone: 763-458-3722 (I'm terrible at returning phone calls – FYI.)

www.mindsharp.com

Please don't confuse me with the New Zealand politician named Bill English.

 

Thanks!



Aug 28
Published: August 28, 2010 03:08 AM by  Mike Walsh   Powered by: Mindsharp and Summit 7
Note: All of the addresses below were valid at the time I added them to the WSS v4 FAQ site and to this file. I can't guarantee that they still are.
 
(Items are added to the WSS v4 FAQ throughout the week so you will find new items more quickly by checking at wssv4faq.mindsharp.com daily.)
 
From 20nd to 28th August 2010
 
NOTE: Amendments to KB articles are now only listed when a version is x.0. MS no longer change the dates of KB articles when version changes are minor.
 
I.1 2010 KB Articles
 
New
 
 
You are prompted to enter your credentials when you try to edit a SharePoint 2010 webpage (ver 2.0)
 
26th August 2010
 
 
A Content Query Web Part does not return results from folders that are in a custom list on SharePoint Server 2010 (ver 2.0)
 
25th August 2010
 
 
Crawl fails with an error The SharePoint item being crawled returned an error when requesting data from the web service. ( Error from SharePoint site: Data is Null. This method or property cannot be called on Null values. ) (ver 2.0)
 
23rd August 2010
 
 
Failed Restore of Web Analytics Service Application via PowerShell (ver 2.0)
 
23rd August 2010
 
 
"Connection not open" error when you close a LobSystemInstance object on a server that is running BCS in SharePoint Server 2010 or in SharePoint Foundation 2010 (ver 2.0)
 
19th August 2010
 
 
Only the first 200 resources can be displayed in the Resource Schedule drop-down list of a group calendar in SharePoint Server 2010 (ver 2.0)
 
18th August 2010
 
 
SharePoint 2010: "My Newsfeed" does not categorize the activities as Today, Yesterday and Earlier (ver 4.0)
 
17th August 2010
 
 
SharePoint 2010 - Configuring Adobe PDF iFilter 9 for 64-bit platforms (ver 4.0)
 
8th August 2010
 
 
Unable to Perform a query on a One-Way trust Domains Scenario when an User from the trusted domain performs the query and the SSA Application Pool account is from the Trustee Domain (ver 5.0)
 
7th August 2010
 
 
Error message when you try to overlay an Exchange calendar in a SharePoint page on a server that is running SharePoint Server 2010 or SharePoint Foundation 2010: "Could not establish trust relationship for the SSL/TLS secure channel with authority" (ver 2.0)
 
3rd August 2010
 
 
Some images may not be displayed in a PowerPoint 2010 Presentation on a BlackBerry device (ver 2.0)
 
2nd August 2010
 
 
No forms authentication providers listed when you try to add a Profile Synchronization connection (ver 2.0)
 
1st August 2010
 
 
Description of the SharePoint Server 2010 hotfix package (wosrv-x-none.msp, pplwfe-x-none.msp, osrv-x-none.msp): July 21, 2010
 
29th July 2010
 
 
Crawls stop responding in SharePoint Server 2010 when there are SQL Server connectivity issues
 
29th July 2010

Modified
 
None
 
I.b Forefront Protection 2010 for SharePoint KB Articles
 
New
 
 
How to manually update scan engines in Microsoft Forefront Protection for Exchange Server or Microsoft Forefront Protection for SharePoint (ver 2.0)
 
3rd August 2010
 
Modified
 
None
 
I.c InfoPath 2010 KB Articles
 
New and Modifed
 
None
 
I.d SPD 2010 KB Articles
 
New
 
 
You cannot select the Serializer to create the proxy to connect to a data source in External Content Type Designer in SharePoint Designer 2010 (ver 2.0)
 
11th August 2010
 
 
The External Content Type designer in SharePoint Designer 2010 generates the wrong type names for TypeDescriptors when you use the GenerateAll option to generate methods (ver 2.0)
 
2nd August 2010
 
 
Data source elements that have a data type that is supported by Outlook are mapped to a native Office property or to a custom property when you create an External Content Type in SharePoint Designer 2010 (ver 2.0)
 
27th July 2010
 
Modified
 
None
 
I.e SharePoint Workspace 2010 KB Articles
 
New
 
 
"System.Xml.XmlException" error when you try to deploy an external list that contains a "less than" character (<) in its name in an Office 2010 environment (ver 2.0)
 
27th August 2010
 
Modified
 
None
 
II. Articles - 2010 Products
 
New
 
A. Office 2010 Server Products
 
 
Managed Metadata and Taxonomy in SharePoint Server 2010 (Links Only) [Resource Center]
 
28th August 2010 (date added)
 
 
Maintain Remote BLOB Storage (RBS) (published 27th August 2010) [Ed: SPF 2010]
 
27th August 2010
 
 
Maintain Remote BLOB Storage (RBS) (published 27th August 2010) [Ed: SPS 2010]
 
27th August 2010
 
 
Overview of SQL Server in a SharePoint environment (SharePoint Foundation 2010) (published 27th August 2010)
 
27th August 2010
 
 
Overview of SQL Server in a SharePoint environment (published 27th August 2010) [Ed: SPS 2010]
 
27th August 2010
 
Planning worksheets (updated 27th August 2010)
 
27th August 2010  *this one is SPF 2010*
 
 
Planning worksheets (updated 27th August 2010)
 
27th August 2010 *this one is SPS 2010*
 
 
HP Sizer for Microsoft SharePoint
 
27th August 2010 (date added)
 
 
SharePoint 2010 Quick Note: Getting Started with Web Development in SharePoint 2010: Create Silverlight Applications to Access SharePoint 2010 Data (Frank Rice)
 
25th August 2010 (date added - article date August 2010)
 
 
SharePoint 2010 Quick Note: Getting Started with Web Development in SharePoint 2010: Create Silverlight Graphs with SharePoint 2010 Data by Using LINQ (Frank Rice)
 
25th August 2010 (date added - article date June 2010)
 
B. Other Office 2010 products
 
None

C. Other relevant products
 
 
Microsoft Exchange Server 2010 Service Pack 1 (SP1)
 
24th August 2010
 
Modified
 
 
Incoming e-mail planning (updated 27th August 2010)
 
27th August 2010      ** Name changed - was Plan Incoming E-Mail (SharePoint Foundation 2010)
 
 
Incoming e-mail planning (updated 27th August 2010)
 
27th August 2010      ** Name changed - was Plan Incoming E-Mail
(SharePoint Server 2010)
 
[Note: Yes it IS madness. They now have two articles with the same Title. You have to look into the article to see if it applies to SPF 2010 or SPS 2010. This now occurs often.]
 
 
Technical diagrams (updated 27th August 2010)
 
27th August 2010
 
III WebCasts (+ PodCasts, On-Line courses) for 2010 Products
 
None

IV WSS v4 FAQ
 
New
 
 
V.0094 Top 60 custom solutions built on Microsoft SharePoint Server 2010 (Yaroslav Pentsarskyy - CreateSpace) *released*
 
V.0095 SharePoint Foundation 2010 - Construire un intranet collaboratif en PME (in French) (ENI - Patrick Carraz)
 
V.0096 Microsoft Sharepoint 2010 (in French) (Hermes Science Publications - several authors under the guidance of Pierre Erol Giraudy)
 
 
X.1010 SharePoint 2010 Consultant's Handbook - A Field Guide to Managed Metadata Services (Kindle Edition) (Chris McNulty)
 
Modified
 
 
V.0012 Essential SharePoint 2010: Overview, Governance, and Planning (Addison-Wesley - Scott Jamison, Mauro Cardarelli, Susan Hanley) *released*
 
 
V.0004 Microsoft SharePoint 2010 - Das Praxisbuch für Anwender (in German) (Addison-Wesley, München - Melanie Schmidt, Britta Seidler) *released*
 
 
V.0031 SharePoint 2010 How-To (Sams - Ishai Sagi) *released*
 
 
V.0036 Microsoft SharePoint 2010 PerformancePoint Services Unleashed (Sams - Tim Kashani, Ola Ekdahl, Kevin Beto, Rachel Vigier) *released*
 


Aug 24
Published: August 24, 2010 14:08 PM by  Todd Bleeker   Powered by: Mindsharp and Summit 7

SharePoint Project Items (SPIs) are new to Visual Studio 2010.

Historically, organizing projects into folders containing files with a type affinity for one another was common. For example, developers often organize disparate CSS files into a styles folder; GIFs, JPGs, and PNGs into an images folder; and disparate JavaScript files into a scripts directory. The benefit is that, if another developer had to support someone else's work, he or she would be able to anticipate where assets of a common type would be found.

SPIs are effectively folders that hold a motley collection of files with a common purpose, rather than a common type. Each file may have a unique deployment location and a unique purpose, but they are organized into the SPI folder because they work together for a common purpose—typically to create some type of SharePoint platform extension. This would be akin to keeping the CSS, images, and JavaScript in a folder along with the .aspx page that consumes them. The SPI model definitely takes some getting used to, but it isn’t going to change any time soon—if ever. "Embrace and extend" is my motto.

The chart below lists all the SPIs along with the ways that they can be created. The first column shows the SPIs that can be created at the same time that a new SharePoint Project is created (along with the four SharePoint Projects that are not also SPIs). The second column shows the SPIs that can be added from the {ProjectRoot} of any SharePoint Project. The third column shows the SPIs that can be added from the context of another SPI; that doesn't imply that they will be created within the SPI folder, just that they are available in that context.

New SharePoint Project Item

Enjoy!

<Todd />



Aug 18
Published: August 18, 2010 10:08 AM by  Paul Papanek Stork   Powered by: Mindsharp and Summit 7

s2logo

Are you an experienced SharePoint or ASP.NET developer?

If you are, then ShareSquared is looking for you.  Our business is expanding and we are hoping to hire some more highly talented people to join our company.  ShareSquared architects and developers are seasoned computer science professionals with a thorough understanding of proper software construction, design patterns and best practices.

Our team is comprised of:

  • Microsoft SharePoint MVP's
  • Senior .NET Architects and Developers
  • 100% Microsoft Certified Professionals
  • Technology leaders in the SharePoint community
  • Former Microsoft SharePoint Dev-Team Members

If you would like to work with some of the best of the best than please check out: http://www.sharesquared.com/company/Pages/Careers.aspx and send your resume to careers@sharesquared.com



Aug 13
Published: August 13, 2010 17:08 PM by  Penny Coventry   Powered by: Mindsharp and Summit 7
Once again, I'm packing my bags for the flight to the US. This time it's the SharePoint Best Practices Conference, 24th – 27th August, at the Hyatt Regency Reston Hotel in Washington, DC - over 120 sessions, 4 tracks, 4 post-conference workshops and 60+ speakers. It's definitely one to attend.

It's the first time I've been to a US Best Practices Conference and the first time in Washington, DC, so I'm really looking forward to it. I can't wait to meet up with so many friends and colleagues. I'll be presenting two sessions:

If you can't make, follow: Twitter hash is #BPC2010 and I've also seen #BPC10 used too. There is also going to be live blogging.



Aug 11
Published: August 11, 2010 12:08 PM by  Brian Alderman   Powered by: Mindsharp and Summit 7
Not too long after releasing SharePoint 2010 (in April), Microsoft has released the first SharePoint 2010 CU which can be found:
 
 
Review the hotfixes, ironically, one hotfix fixes another hotfix in the CU. :)
 
...Brian


Jul 02
[Long post!]
 

Two weeks ago, the conference I’d been helping organize came to fruition and was held here in Sydney over two days – 16th and 17th June. The conference has since been referred to by many as one of the best and most successful SharePoint conferences ever held! The conference, in its first year here in Australia, had in excess of 600 attendees, it attracted speakers like Arpan Shah from Microsoft in Redmond, Todd Bleeker from Mindsharp (USA), Michael Noel (USA and author of the upcoming SharePoint Server 2010 Unleashed book by SAMS) and numerous other well known and respected international and national SharePoint experts and speakers. Delegates who attended the event travelled from all around Australia, including Perth, Melbourne, Brisbane, Adelaide and Canberra.

Debbie Ireland – SharePoint MVP from New Zealand (SPEvents) – was at the helm of organizing the Australian (and New Zealand) event/s – this year also saw the second New Zealand conference, held over in Wellington the week prior to the Australian conference, and which saw a 25% increase in attendance on last year’s conference! Debbie, and her team from New Zealand, did an absolutely outstanding job in organizing the conference, conference logistics and behind the scenes project management – it was a pleasure to meet and work with them – and I look forward to working with them and supporting them in future like endeavours. It was also a pleasure to work alongside the other conference organizers (both Australian and New Zealand), including James Milne (Brisbane), Mark Orange (NZ) and Brendan Law (Melbourne).

We had a fantastic line-up of sponsors – we also received favourable feedback from delegates on our conference sponsors, including the fact that exhibitor stands were easily accessed throughout the conference and session breaks. See the conference sponsors page here: - http://www.sharepointconference.com.au/sponsors.htm. Plus, a huge thank you to those sponsors who provided the prize draw prizes for both Day 1 and Day 2.

So, what made the conference a success? I believe the fact that (1) we (the key organizing team) all worked as a team – with a shared vision - from the outset and throughout the 6-7 month period leading up to the event; (2) we are all SharePoint experts (or SharePoint subject matter experts and actively working with (and in) SharePoint 2007 and SharePoint 2010 and related technologies), so we had a good feeling for the market and what people would be interested in, and we carried out market research from the outset; (3) we had a good assortment of topics and allocation of speakers; (4) we included a number of tracks to suit all audiences, including business, technical, Voice of the customer (real-life implementation scenarios) and vendor-specific sessions – this attracted a diverse group of people – many from the same company/ies who saw having the multiple tracks of real benefit - including System admins, developers, designers, business analysts, project managers, CTO’s and CIO’s and other business stakeholders – having such a diversity of tracks and people allowed for cross-pollination and sharing of information all at once!; (5) it was a ‘community focussed’ event and we had the SharePoint community behind us who greatly promoted the event and provided support throughout the two days, with the likes of a User Group Community Booth (the go-to spot for SharePoint questions and post-session follow-up) which was manned by the Australian and New Zealand SharePoint community throughout the entire conference; (6) We had Microsoft’s full support, both as a sponsor and as a community-focussed supporter, from the outset; (7) the venue – the Hilton Hotel – was the perfect venue, in terms of location, rooms and comfort – I constantly heard very positive feedback about the food – FOOD is an important part of any IT event! (8) The sponsor/exhibition area was well laid out and easily accessible to delegates throughout the conference; (9) the Ask the Experts panel – this was a great way of winding up the conference on the final day and we encouraged several international and local speakers to get involved and to include a good cross-section of SharePoint skills – including admin, developer and infrastructure.

This post is by no means the first, or only, post-conference write up. We’ve (the organizers) received numerous congratulatory e-mails and feedback; I’ve included a couple of links below:

Craig Bailey (@craigbailey) – convenor of the popular ‘Sydney Business and Technology user group’ and who attended the conference - provided a great post conference review - http://www.craigbailey.net/australian-sharepoint-conference-review/ (thanks, Craig)

IDM – our media sponsor and partner throughout the conference – also wrote a good post-conference review - http://idm.net.au/article/007910-australia-sharepoint-conference-schedule-return-2011 - interestingly, this article cites the percentage of female conference attendees at 25% - a vast (and welcomed) contrast to that number usually seen at IT events.

Also, a big thank you to Rose Stamell, Microsoft, for organizing the wrap-up networking drinks for MVPs and Speakers at The Hilton – it was a nice way for the conference speakers to reflect on the conference and discuss SharePoint goodness. Plus, a big thank you to Emantra Hosting Solutions (Australia) – and Mark Rhodes – for providing and hosting the main MYSPC SharePoint 2010 site used throughout the conference and provisioning and hosting the individual delegates trial SharePoint (server) 2010 sites.

Well, what about next year’s event? We hear you and planning is already underway for next year’s (2011) Australian SharePoint Conference. Thank you to all those conference attendees who completed the preferred conference location survey during (and post) the conference – even those who cheekily completed the survey multiple times! J At this stage, Sydney is the favoured location. In terms of next year’s conference dates, based on feedback received from this year’s event from Microsoft, sponsors and delegates, next year’s conference looks to be 8th and 9th March, 2011, at The Hilton Hotel. Keep an eye on the conference site – http://www.sharepointconference.com.au for further updates. Now is the time to start planning to attend!  Also, if you are interested in attending next year’s New Zealand event, then keep an eye on the New Zealand conference site – http://www.sharepointconference.co.nz – for updates, including dates and location.

If you are interested in speaking at next year’s conference, then initial speaker interested is being captured via http://spevents.co.nz/AUSPC2011/default.aspx - simply visit the site and complete the Speaker Registrations survey by clicking on the link in the left-hand column. Similarly, if you are interested in speaking at next year’s New Zealand SharePoint conference, then visit http://spevents.co.nz/NZSPC2011/default.aspx and complete the Speaker Registrations survey.

Hungry for more SharePoint information now? In terms of other SharePoint events happening between now and next year’s SharePoint conference, here’s a list of some of the events happening here in Australia:

SharePoint Saturdays Australia: Sydney (7th August - http://www.sharepointsaturday.org/sydney); Canberra (18th September - http://www.sharepointsaturday.org/canberra); Melbourne (16th October - http://www.sharepointsaturday.org/melbourne) – they are FREE but you need to visit the registration sites shown in order to register for each event.

SharePoint Saturdays globally (some of these happen as online events!) – see http://www.sharepointsaturday.org for a full listing of SharePoint Saturday locations.

TechEd Australia – will include a number of Office and SharePoint tracks - http://australia.msteched.com/ - up on the Gold Coast again this year (2nd year running at the same location!). Don’t forget about user group registration discounts for TechEd AU - if you are involved in a UG then you should ask your UG leader for further details. Unfortunately, I will not be attending this year’s TechEd due to a number of existing Sydney-based commitments.

Office DevCon, Sydney (will include both Office and SharePoint tracks) – http://www.officedevcon.com.au  – FREE plus a two-day weekend event – but you must visit the registration site in order to register for the event so we can properly cater for all for both food and space.

Australian SharePoint user groups – see http://www.sharepointusers.org.au/default.aspx - for a user group location near you. SharePoint user groups are a great place for meeting other SharePoint enthusiasts and experts!

SharePoint MVP online chats hosted by Microsoft – these chat sessions happen on a monthly basis (as of writing this blog post) – see details of the latest chat session -  http://blogs.msdn.com/b/sharepoint/archive/2010/06/17/live-chats-to-learn-more-about-sharepoint-with-the-mvp-experts.aspx – and are a great place to ask your SharePoint questions, ranging from administration, development, infrastructure and design.

SharePoint 2010 MSDN forums – a great place for asking (and answering) SharePoint 2010 questions - http://social.msdn.microsoft.com/Forums/en/category/sharepoint2010.

SharePoint 2007 MSDN forums – questions and answers specific to the SharePoint 2007 versions - http://social.msdn.microsoft.com/Forums/en-AU/category/sharepoint

PLUS, Microsoft has announced their SharePoint 2011 conference, happening over in Anaheim, California, in October, 2011 -  http://blogs.msdn.com/b/sharepoint/archive/2010/06/08/save-the-date-sharepoint-conference-2011.aspx.  

2010 – it’s a wrap!

 



Mar 31
Published: March 31, 2010 10:03 AM by  Daniel Galant   Powered by: Mindsharp and Summit 7
The folks over at SSWUG.org will be hosting another of their virtual conferences this April 7-9. If you have never thought of attending a conference held over the Internet, give this a look. The people behind the SSWUG VPCs do a wonderful job and you might just pick up some really good information as well.
To register just go to SSWUG Spring 2010 VPC and be sure to use the VIP code DGalantSPVC10 to save $30 off the cost. I'll be giving four different sessions thia time around, two on SharePoint 2007 and two on SharePoint Designer 2010. Check out their site for a full listing of the sessions and speakers.
 
Hope to see some of you there.


Mar 16

Introduction

I have a client that wanted to convert their outdated HTML district website to an external facing SharePoint portal. The client was brand new to SharePoint and brought me in to build an external facing portal using MOSS 2007 Enterprise. After setting up the new farm it was time to brand the site and create content. The one thing I had the client do before I started branding the site was have them send me references to sites they liked along with a list of elements they liked about the sites.

Read the full Article on EndUserSharePoint.com

01_Overlay



Dec 20

 

Corro'll Driskell

December 20, 2009

Happy holidays to all, I am Corro’ll (Corel) Driskell, a SharePoint Architect on the SharePoint platforms. As many of you know I do many things around the SharePoint platforms and found it difficult to pick a starting place since my involvement on the TAP program.

So, I wanted to kick off my blogs, referencing the SharePoint 2010 platform and its tools, with SharePoint Designer 2010 (Beta). I will post a number of blogs, as a part of this blog series, referencing the many features of SharePoint Designer 2010, such as, the new User Interface (UI), the ribbon, and a number of other features. Bottom line, this blog provides an overview focusing on the UI of SharePoint Designer 2010. This is not a deep dive into the capabilities of SharePoint Designer 2010 (BETA).

Microsoft SharePoint Designer 2010 (Beta) allows Designers – non-programmers - and, encourages, Developers, and I mean encourage, to build web based applications on SharePoint’s latest platforms (SharePoint Foundation 2010 and SharePoint Server 2010).

To start, you must locate SharePoint Designer 2010 in the Microsoft Office application group – its default location.

image

SharePoint Designer 2010 (Beta) UI 1

One of the great things about the, new, SharePoint Designer 2010 experience is the initial start. Immediately, the user (Designers and Developers) is provided visual feedback upon the start of the application. It is my experience that the loading is rather quick versus the experience with the previous version, SharePoint Designer 2007.

image

SharePoint Designer 2010 (Beta) UI 2

After SharePoint Designer 2010 (Beta) initially starts, you will notice that there are two primary focuses. The user has the option to Open a SharePoint Site or Create a New SharePoint Site. The new initial UI is a far step from the traditional experience of SharePoint Designer 2007. In fact, the user does not need to browse around the interface attempting to introduce them to the application. It is all there front and center.

In contrast, the fact that there is an option to use SharePoint Designer 2010 (Beta) on the My Site is discouraging. In another blog posting we will discuss the new features available on the, new, SharePoint 2010 platforms that afford the SharePoint administrators and Site Collection Administrator better control now is not the time to dive into those features, also, we will focus on the various options in more detail in a future blog as a part of this series.

image

SharePoint Designer 2010 (Beta) UI 3

After, either, Opening the Site or Creating a New Site, the user is presented with the Site Setting information page. Of course, the most notable change, in the SharePoint Designer 2010 UI, is the presentation of the, new, Ribbon. Again, I will dive deeper in the various features afforded by the Ribbon in a later blog as a part of this series.

The Settings Page provides a significant amount of information , such as, the Site Information, Permissions, SubSites, also known as Webs, Settings and Customization. The fact that this Designer Dashboard, yes, I called it a dashboard, and no it isn’t Microsoft’s official terminology, is forthcoming with quite a bit of information. This information was, either, lacking or wasn’t as easy to obtain in SharePoint Designer 2007. Again, we will dive deeper into many of the features during this series in a future blog. Although the tab interface is not new to SharePoint Designer 2007, I find the tab interface in SharePoint Designer 2010 (Beta) a bit more inviting and user friendly.

image

SharePoint Designer 2010 (Beta) UI 4

Lists and Libraries are nested in a simple view in SharePoint Designer 2010 (Beta). It is more similar to a report versus a hierarchical structure, as leveraged in SharePoint Designer 2007. Also, I want to encourage you to focus on the changes in the context of the Ribbon’s interface as we navigate from the Site Settings page. Of course, we can witness a heavy use of the bread crumbs in the SharePoint Designer 2010’s interface. The bread crumb was presented as a simple navigation control in the SharePoint Designer 2007 interface. Again, there was an emphasis on the hierarchical structure.

image

SharePoint Designer 2010 (Beta) UI 5

Workflows are also presented in a report form. The Workflows’ report provides summary information referencing workflows leveraged by the site or web. In the SharePoint Designer 2007 interface, Workflows were presented nested in a Workflow library or folder, depends on whom you ask. Again, there is an emphasis on the actual artifacts’ hosted on the SharePoint 2010 platform. Of course, there is a significant amount of new features for SharePoint Designer 2010 (Beta) and its capabilities to build flexible workflows. Again, we will dive deeper into those capabilities through-out this blog series.

image

SharePoint Designer 2010 (Beta) UI 6

The Site Pages provides summary information about located in the Sites Pages Library. The Site Pages Library is used to create and store pages for a specific Site or Web.

image

SharePoint Designer 2010 (Beta) UI 7

The Site Assets provides a reports view of files that are included on the pages of a Site or Web. In the SharePoint Designer 2007 UI, the storage locations for files included on the pages were stored in a number of locations, such as, the images folder.

image

SharePoint Designer 2010 (Beta) UI 8

The Content Types page provided a summary report about the various collection of content types, leveraged by the Site or Web, to establish consistent management of content. Immediately, you will find information, such as, Group, Parent, Source and Description. Most importantly, the UI provides quick access to manage the various content types. SharePoint Designer 2007 did not afford users this type of reporting feature. We will explore this new feature further as a part of this blog series.

image

SharePoint Designer 2010 (Beta) UI 9

The Site Columns UI provides a summary report referencing a collection of columns available to Lists, which includes, Column Name, Type, Group and Source. In the SharePoint Designer 2007 UI we did not have a central presentation of the linked columns for a Site or Web.

image

SharePoint Designer 2010 (Beta) UI 10

The External Content Types summary reports provides information, such as, Display Name, Name, External System, Type and Namespace, about External Lists, also known as SharePoint Lists, that exposes data from various back-end repositories – databases, web services and other Line-of-Business applications. The beauty of it all is that this feature is provided in the SharePoint Designer 2010 UI.

image

SharePoint Designer 2010 (Beta) UI 11

The Data Sources summary report provides information, Name, Type and Description, about the various data sources available to the Site or Web. The report is categorized based on type, for instance, Lists and Libraries. Again, this is a great presentation in the UI so that users are not required to leverage the hierarchical structure to obtain the information similar to the SharePoint Designer 2007 UI.

image

SharePoint Designer 2010 (Beta) UI 12

The Master Pages summary report provides information, Name, Title, Content Type, Size, Modified Date, Modified By and Comments, about all of the artifacts, Master Pages, Page Layouts, images and xml files, found in the Master Page Gallery.

image

SharePoint Designer 2010 (Beta) UI 13

The Site Groups summary report provides some information, Group Name and Description, about the various Groups with, some level, of access to the Site or Web. You have to ask yourself, where are the contributor settings. Again, we will dive deeper into the many changes in a later blog.

image

SharePoint Designer 2010 (Beta) UI 14

The SubSites summary reports provide a list of the Sites or Webs within the hierarchical structure. The report provides information, such as, Site Name, URL and Modified Date.

image

SharePoint Designer 2010 (Beta) UI 15

Finally, the All Files provides a summary report of all content for a Site or Web, which includes the SubSites. The information provided includes, Name, Title, Size, Type, Modified Date, Modified By and Comments. The significance here is users have a more efficient way to ascertain the information about the artifacts that make up SharePoint 2010 sites.

image

SharePoint Designer 2010 (Beta) UI 16

The overarching selling point is that SharePoint Designer 2010 encourages rapid building and deployment of, web-based, solutions that meet business needs, leveraging the various features – lists, content types, workflows and a number of other features – of an organization. Here is the catcher, there is no-coding. Included in this blog series, I will work to cover the various use cases and features.



Dec 08
Published: December 08, 2009 13:12 PM by  Kim Lund   Powered by: Mindsharp and Summit 7

Depending on who you are in your organization, you may either LOVE SharePoint or HATE it. There are many promises on what SharePoint will deliver; however, have those promises become a reality in your organization? The answer may be the key to why your colleagues, employees, and end users use SharePoint or create work-arounds to avoid taking the time to understand it.

If you find that user adoption of SharePoint is avoided or slower than anticipated in your working environment, you are not alone. Many students that I have trained, consulted and listened to have expressed their pain points for SharePoint adoption. As I am blessed to work with and interact with many SharePoint users I have discovered and witnessed what works and what doesn't for successfully increasing people's use, acceptance, knowledge and confidence of SharePoint.

Pain Points

Some of the Pain Points I've heard expressed as it relates to slow user adoption are:

  • Employees Unaware of Powerful SharePoint Features
  • SharePoint Deployed Without Governance
  • User Community Not Involved in Planning SharePoint Site Use
  • End Users Expected to Create or Manage SharePoint Sites
  • Inefficient Use of Document Management Features
  • Uncertainty that Confidential Information is Secure
  • Added Training Needs Burden Staff
  • SharePoint Training Not Based on End User Needs
  • Help Desk Unable to Answer SharePoint Questions
  • Change in Organizational Culture Required for SharePoint to Be Accepted

How to

The key to overcoming these pain points and increasing end user adoption of SharePoint and achieving better buy-in from users at large is to develop a plan that includes:

  • Governance planning that includes:
    • Key members from various business units - not just IT
    • Focus on the vision and long-range goals
    • Ability to adapt to changes in requirements
    • Relevancy to needs of the organization
  • Taxonomy planning that includes:
    • Governance team that will own and manage the taxonomy
    • Classification of information according to categories
    • Focus on the business, not on SharePoint
  • Communication plan that includes:
    • What SharePoint is
    • Governance and taxonomies for use in SharePoint
    • Building excitement for what SharePoint will be able to do in their environment
    • How it fits into the existing ecosystem of technologies
    • What it might be replacing
    • Discovering and building SharePoint advocates
  • A training plan that provides succinct training that:
    • Focuses on the needs of individual users
    • Available when needed
    • Holds users accountable
    • Teaches the technical "how-to" about SharePoint
    • Shares the reasons and best practices for using SharePoint
    • Incentivizes employees
    • Provides key competency certifications that encourage and build confidence when key concepts are mastered

If any of these important steps are missing in a SharePoint adoption plan, you will find that the effectiveness of the other steps will be less. For example, if you have not provided governance and have a poor taxonomy plan, use of SharePoint will be inconsistent. When this occurs, even if users receive useful training, there will be confusion about the proper use of SharePoint features. Even if governance and taxonomy planning has been completed but this information is not communicated to employees, there will still be confusion and inconsistency with the use of SharePoint. Lastly, if you have planned for proper governance and taxonomy, communicated to your employees that SharePoint is coming, but then fail to train employees, end users will not know how to utilize the new features provided by SharePoint.

For this reason, in order to receive the anticipated return on investment (ROI) of a SharePoint deployment, the key for success in usability and user adoption is tied closely to implementing a plan that includes governance and taxonomy, communication to employees, and relevant training.

First Get Help!

If you think the suggestions included in the previous section are a tall order, you are right. You are probably not staffed to handle all of the steps that are recommended and you likely do not have the SharePoint expertise in-house to accomplish this plan. Mindsharp has the expertise, services, and products to help you implement all four key areas mentioned above. The biggest struggle for any company is a well thought out, effective training plan that meets the needs of the end user population.

That is why we developed UserVersity to deliver an end-to-end turnkey SharePoint communication and training program. We work with your staff to compliment the talent you have in-house, and then provide expertise in areas you may not have. UserVersity provides communication tools and a variety of training tools including:

  • Adoption Manager
  • E-learning
  • Online or in person instructor-led training
  • Quizzes
  • Certifications
  • Incentives and motivation for employees you would like to target

We are excited to be the first to offer such a flexible solution that encompasses all of your needs and provides a customized approach to training.

If you would like to learn more about this you can also attend a free 30 minute webinar about Increasing End User Adoption and about our UserVersity program. Please check out our website at http://mindsharp.com/Default.aspx?top=TRAINING&left=END_USER_ADOPTION

 

The following chart summarizes how Mindsharp and UserVersity can assist organizations when dealing with one or many of the pain points highlighted in this paper.

Pain Point 

How Mindsharp Can Help 

Pain Point 1: Employees Unaware of Powerful SharePoint Features 

Mindsharp's UserVersity provides a communication plan that informs users about the key SharePoint features. Our communication plan includes e-mail templates, posters, and additional resources as requested.

Pain Point 2: SharePoint Deployed Without Governance 

Mindsharp has SharePoint experts that can guide your governance and taxonomy planning or provide you with resources to assist your team in planning these important components.

Pain Point 3: User Community Not Involved in Planning SharePoint Site Use 

Mindsharp can help obtain feedback about who should be part of the team that develops your SharePoint governance and taxonomy plans.

Pain Point 4: End Users Expected to Create or Manage SharePoint Sites 

Mindsharp's UserVersity includes training in various formats that provides end users with the information they need to create and manage sites. 

Pain Point 5: Inefficient Use of Document Management Features

Mindsharp's UserVersity provides training on correct document management including topics such as:

  • Creating and saving documents
  • Adding metadata
  • Searching
  • Collaborating
  • Using check in and check out
  • Version history

Users can choose training that meets their needs and fits into their busy schedule. 

Pain Point 6: Uncertainty that Confidential Information is Secure 

Mindsharp's UserVersity provides training for end users on the topic of security. We provide thorough coverage on how SharePoint security works, as well as how to add or remove users from the SharePoint groups and permission levels. Users will gain confidence that they are securing their content appropriately.

Pain Point 7: Added Training Needs Burden Staff

Mindsharp's UserVersity provides an adoption manager that guides you through the program so you can make training decisions confidently. The advantage is that you are working with a SharePoint expert with years of training experience. 

Pain Point 8: SharePoint Training Not Based on End User Needs

Mindsharp's UserVersity is structured to provide specific training for every role and function in your organization to ensure competency in appropriate SharePoint functionality. UserVersity provides over 90 different lessons that simplify SharePoint by breaking training into six key functional competencies. This allows end users to focus on the aspects of SharePoint that relate to them currently, and then grow into other areas as their use and knowledge of SharePoint expands. Training can be repeated when knowledge of a skill needs to be refreshed or reinforced.

Pain Point 9: Help Desk Unable to Answer SharePoint Questions 

Mindsharp's UserVersity provides multiple ways to assist your Help Desk including:

  • Mindsharp has the leading SharePoint experts on staff who can answer questions from your Help Desk employees.
  • UserVersity has help desk crash courses to provide your IT and Help Desk staff with a thorough understanding of SharePoint.
  • The Help Desk can refer employees to specific computer-based training modules that address the user's problem. This is another way to provide the needed help without the Help Desk employee guiding users through each step.

Pain Point 10: Change in Organizational Culture Required for SharePoint to Be Accepted

Training with Mindsharp's UserVersity helps users understand the value of using SharePoint functionality. It goes beyond showing the "how" to teach the best practices and answer the "whys" in SharePoint. This approach helps increase end-user adoption and satisfaction.

 

Summary

SharePoint is one of the fastest growing corporate technologies on the market today. In fact, SharePoint has surpassed anticipated sales within Microsoft but has the frequency of its use in your organization surpassed expectations? Just because your organization has deployed SharePoint does not mean it is being used successfully.

I have identified some of the reasons end user adoption of SharePoint is slow in companies and offered ways to change that slow adoption. If companies create a SharePoint adoption plan that meets end user needs, SharePoint will be a tool they depend on to work smarter and faster.

 

If you would like to learn more about this you can also attend a free 30 minute webinar about Increasing End User Adoption and about our UserVersity program. Please check out our website at http://mindsharp.com/Default.aspx?top=TRAINING&left=END_USER_ADOPTION

UserVersity

 

 

 



Nov 15
Published: November 15, 2009 12:11 PM by  Ben Curry   Powered by: Mindsharp and Summit 7
I'll be speaking at the ATL users group tomorrow night at 6:30 EST. For directions and more info, see http://www.atlspug.com/default.aspx.
 
The topics are:
 
Session 1 Installing SharePoint Server 2010
Topic Description

Much has changed from the 2007 version of SharePoint. I'll be discussing a server farm installation of SharePoint Server 2010 to include the new Shared Services model (service applications), how those will upgrade, and limitations of 2007 and 2010 integration. Just for fun, I'll also give you a quick demonstration of building service applications and configuration using Central Administration and PowerShell!

Session 2 Enterprise Content Management Upgrades in SharePoint Server 2010
Topic Description

Wow! We have some really cool features that are new to SharePoint Server 2010 - DocumentIDs, robust Information Management Policies, and Document Sets. BUT, one of the most anticipated features is the centralized taxonomy and content type hub. Come see a live demonstration and early best practices for creating a content type hub and managed metadata service.

 
My apologies for posting this late. I hope to see you there!
 
Ben Curry


Oct 19
Published: October 19, 2009 17:10 PM by  James Curry   Powered by: Mindsharp and Summit 7
But for DBAs, you will have to set configure it. So no worries about SharePoint doing SP evilness.


Oct 19
Published: October 19, 2009 11:10 AM by  Rick Taylor   Powered by: Mindsharp and Summit 7
My first session at SPC09 is now done.  It was Part 1 of 2, "Upgrading to SharePoint 2010".
 
At first I was worried, because I was competing with breakfast being served at the same time.  With 1 minute to go, there was one person in a seat.  Bill English said, "Preach and they will come."  He was right.  I started talking to one person and 5 minutes later, the chairs were all full.
 
Part 2 will be tomorrow at 12:30pm.  Need to make sure my demos work!


Jul 15
Published: July 15, 2009 13:07 PM by  Dave Pileggi   Powered by: Mindsharp and Summit 7

The first few minutes of my presentation, I will be doing at the Best Practice Conference.  Trust me, it gets even better, but you have to attend to get the rest!

chooseyourownadventure

Back in the day, a literary Labyrinth was called a Choose your Own Adventure Book.  I actually have somewhere in my parents house the very same book that is pictured above.  Reading these was an adventure.  Did you choose the right path? Putting your finger(s) in multiple pages, just in case you did not choose the right path.  Planning your SharePoint environment is very much the same way, there can be multiple out comes, with lots of twists and turns along the way, and depending on the choices you made earlier, could force the outcome later.

Page 1 & 2

 Labyrinth

Your company hears about this SharePoint “thing.”  It sounds like a good idea.  You and a bunch of co-workers are standing around the water cooler talking about it.

Hey Sarcastic Sally, how is the paper your working on?”

As good as an ulcer,” Sally retorted.

Did you hear about that program called SharePoint?”

”Stop smiling, the light shinning off your teeth is going to blind me.  Yeah, it sounds cool.”

”Maybe we should look at the business problems it could solve before we move forward with it?” you ask yourself out loud.

Sarcastic Sally Scoffs.  “It’s a cool application, let’s just move forward.  You are such a worry wart.”



Go to page 21 if you agree with Sally
Go to page 37 if you want to follow your own idea

Sally scares me, I think we better listen to her.  However, I am not sure if this is the right way, so lets put our finger in here JUST IN CASE.

Page 21 & 22

BurgersonGrill

 

Your SharePoint environment is installed and takes a life of its own, causing chaos and mayhem everywhere in your company.  You are blamed for the IT nightmare and sent to a small town in Idaho to flip burgers.

THE END

Oh no! I like burgers, but not that much.  What happened!

In reality, this is a very common mistake.  More companies than not introduce a application into their environment without understanding the problems they are targeting to solve.  This can be fatal to the success of releasing the application, especially if it is SharePoint.  You have to understand the new workforce you are dealing with is Generation X, Generation Y, and the Lost Generations who have had Internet for the better part of their lives.  They are the My Space, Facebook, iGoogle, My Yahoo, My MSN, instant messaging, tweeting generations.  They know how to use we based applications very well.  SharePoint being a web based application will be instantly second nature to them to use.  That being said, if you do not know what business problems SharePoint is going to solve for your company, they will make those choices for you.  There is a LOT of power with just out of the box features and web parts that they can take advantage of.  At first glance this may sound like a good thing, however, there is one caveat. If you have legacy applications or applications that are not as intuitive to use, user friendly or “cool” to look at this new workforce can and will use SharePoint to replace those applications.  This will then spread your information over multiple systems causing search ability issues and segmented data.  This is not the desired effects SharePoint should have.  SharePoint is extremely powerful, and I will dare say more powerful then Microsoft even realizes.  This is a good thing, but has to be managed properly.  In time those legacy applications may very well be absorbed by SharePoint based applications, but you want to keep it under control.  Spotting the business problems SharePoint is designated to solve is the first step in a healthy deployment.

Good thing we put our finger in the page.  Lets go back and try the other path… That's, page… 37. Lets go!

Page 37 & 38

tattoo 

You shoot back, “No, I think it will be a good idea to figure out the business problems we want to solve for the company.”

“Like what?” asks Jeff from accounting.

Sally and you watch him drain half the water cooler bottle of its contents into his water bottle. “Well, Sally already gave us one. She is having trouble collaborating with her team. The paper they are working on isn’t as easy as it should be. So collaboration is a big one I would think.”

“Oh, sorry to hear that Sally, but we have our own problems,” Jeff informed us.

“How so?” Sally inquired.

“Well, we have all of these reports we are forced to do, but they are so time consuming, I don’t have time to do what I am supposed to do.” Jeff wrinkled his nose.

“The enterprise version of SharePoint has Excel Services and BI capabilities,” I offered. “That could be another business problem we could solve initially.”

“Do you have an executive sponsor?” Jeff wondered.

“We are IT, why would we need that?” Sarcastic Sally snapped.

“To get funding and support.” Jeff said defending himself.

 

 

Go to Page 13 if you want to get an executive sponsor.
Go to Page 25 if you agree with Sally

I say we go with Sally, she still scares me.  Lets go to page 25, but I am going to put my finger here again, JUST IN CASE!

Page 25 & 26

watercooler

Oh no, SharePoint has been considered a rogue project. Lack of funding has landed us in trouble. We are forced to use an old Commodore 64 and two TRS 80’s to try and build the environment. The project and idea has died before it could even go forward. A walk to the water cooler for you and Sally is now known as the Walk of Shame.

THE END

Sally did it to us again! What happened?!

Find out at the SharePoint Best Practices conference.  If you want more information about the Best Practices Conference click on the banner below.  Hope to see you there, as the line up of speakers is UNBELIEVABLE!  Two of which are the authors of the book that inspired this entire event.  Microsoft Office SharePoint Server 2007: Best Practices published by Microsoft Press.

 

BPC180x150



May 22
Published: May 22, 2009 05:05 AM by  Enrique Lima   Powered by: Mindsharp and Summit 7
Something has just come to light, here is an extract of the posting found on the SharePoint Team Blog ...

"During the installation of SP2, a product expiration date is improperly activated. This means SharePoint will expire as though it was a trial installation 180 days after SP2 is deployed. The activation of the expiration date will not affect the normal function of SharePoint up until the expiration date passes. Furthermore, product expiration 180 days after SP2 installation will not affect customer’s data, configuration or application code but will render SharePoint inaccessible for end-users." Jeff Teper/Microsoft Corporate VP/SharePoint.



Here is the link to the full text on plans to resolve and manual resolution of the issue.

http://blogs.msdn.com/sharepoint/archive/2009/05/21/attention-important-information-on-service-pack-2.aspx



Mar 04
Published: March 04, 2009 22:03 PM by  Tami Bolton   Powered by: Mindsharp and Summit 7

Folders can be used for large list support.

 

But...

 
 

01. Folders organize content when a item is saved, rather than when it is displayed

02. Folders/subfolders make finding an item difficult

03. A folder obscures the number of items it contains until the Folder is opened

04. Sort, filter, group, and paginate can only be applied to items within one folder at a time or to the entire list

05. It is more difficult to move an item between two folders than to change the value of a property

06. A single list item can have multiple properties but cannot be presented in two folders

07. A list item can have a required property but a folder can never be required

08. The browser URL is limited to 255 characters; nested folders make the URL unnecessarily long

09. Properties on a folder cannot be used to sort, filter, group, or paginate list items within that folder

10. New columns are added to the list items within the folder but not the folder itself



Jan 23
Published: January 23, 2009 10:01 AM by  Daniel Webster   Powered by: Mindsharp and Summit 7

There are many manual methods for making a central search center available across your SharePoint implementation:

·         Adding to either Global (Top Nav Bar) or Local (Quick Launch) navigation in each site collection and/or site.

·         Adding Links to pages

·         Teaching Users to add to My Links list

In this post, I would like to suggest three methods of automating the publication of centralized search center access without having to touch individual SharePoint sites. The first two preferably use Active Directory group policies but are achievable for users on machines that are not members of your domain.

Add as Search Provider for Internet Explorer

Internet Explorer now supports multiple Search Providers for its built-in search box as shown in the figure below.

Your users can use the built-in tools to create a search provider for your central search center or you can provide a file which they can use to place the correct settings in their local registry.

To create this file, place the following test in Notepad:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SearchScopes\{1EF4B245-681F-493C-9EF7-7AAE8262CC81}]

"DisplayName"="Portal"

"URL"="http://moss01/search/Pages/Results.aspx?k={searchTerms}&s=All%20Sites"

"Codepage"=dword:0000fde9

Replace “Portal” with the name you want displayed. Quotes are required.

In the URL, replace http://moss01/search/Pages/results.aspx with the location of your search results page. You could also change or remove the default scope (&s=All%20Sites).

The save the file with a .REG extension.

To share the file via email or in a document library, you may need to save the file with a .TXT extension and instruct your users how to download the file, change the extension back to .REG and import into their registry.

Add to Internet Explorer Links Toolbar

Although some users do not like to give up the space occupied by Internet Explorer’s Links toolbar, I am addicted to it for the sites that I use frequently. Also, it can quickly be activated / deactivated from the Tools menu as needed as well as collapsed / expanded.

Like most configurations of Internet Explorer, the contents of the Links toolbar can be pushed out to members of the domain using group policies. I find the easiest method of creating this policy is to configure IE in the desired format on a machine from which I can open the domain (or OU) group policy. Then I can simply import the local settings into the group policy and tweak them within the policy.

However, for those users whose machines are not members of your domain, the links shortcuts are contained in a folder in their favorites (C:\Documents and Settings\username\Favorites\Links). So your options are to train them how to go to the site and create the shortcut on the links toolbar or save as a Favorite in the Links folder. I suppose that zipping a links folder and sending out to users to place in the Favorites folder but that would probably be harder to teach them than saving as a favorite.

Add Link to Site Actions

Making the link to the site available to all users globally across your SharePoint farm is relatively easy even for administrators who do not normally write code.

Additions to the Site Actions menu are deployed as features. For the non-programmers, do not stop reading at this point. We are just going to do some simple cut and paste.

As long as we understand the basic components of a feature and have the basic code for two XML files, we can easily modify the menu.

A feature requires a folder containing two files, Elements.xml and Feature.xml. The folder should have a name that identifies the feature to administrators and must be unique within the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES folder. In my example, the folder (and feature) is named EntSearch for Enterprise Search.

The contents of the Elements.xml file are:

<?xml version="1.0" encoding="utf-8" ?>

<Elements xmlns="http://schemas.microsoft.com/sharepoint/">

  <CustomAction Id="CustomWebManagementPage"

      Location="Microsoft.SharePoint.StandardMenu"

      GroupId="SiteActions"

      ImageUrl="/_layouts/images/search.gif"

      Sequence="1000"

      Title="Enterprise Search Site"

      Description="Use this site for Enterprise and Internet Searches.">

    <UrlAction Url="HTTP://moss01/search"/>

  </CustomAction>

</Elements>

The Sequence entry controls the placement of the link on the menu list.

The Title controls the menu item name and the Description text appears below the menu item name as shown in the figure below.

The UrlAction Url is the link that is opened when the menu item is selected.

The contents of the Feature.xml are:

<?xml version="1.0" encoding="utf-8"?>

<Feature xmlns="http://schemas.microsoft.com/sharepoint/" Id="BEA70765-63BB-4bd1-927C-E72C3559D07D" Title="Enterprise Search Site" Description="This site is customized for Enterprise and Internet Searches." Scope="Farm">

  <ElementManifests>

    <ElementManifest Location="Elements.xml" />

  </ElementManifests>

</Feature>

The crucial line in this file is the Feature xmlns= line. In this line the Id must be a unique guid. Since we are not developers and probably do not have Visual Studio installed, we can use http://createguid.com/ to generate a new guid. The Title and Description need to be identical to those in the Elements.xml. for this feature, we want the scope to be Farm so that it does not need to be activated at lower levels. Farm level features are automatically activated.

Place the folder containing your two modified files in the  C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES   folder.  The feature is then deployed with the following command line:

"c:\program files\common files\microsoft shared\web server extensions\12\bin\stsadm.exe" -o installfeature -name "EntSearch" –force

Now across all sites and pages in your farm, your Site Actions menu contains an item as shown below:

Remember that a Site Actions menu does not appear unless a user has access to a link in the menu due to security trimming. So, for many of your users this may be the first time they have seen this item.

Hopefully, this post will at least cause you to think about some options for making your central search center more accessible for all your users.