06 March 2008

SharePoint Conference 2008

I just finished my time at the 2008 SharePoint conference in Seattle (admittedly a little early).  By all accounts, this conference was well attended with over 3800 participants.  Keynotes at the conference were given by Bill Gates, Kurt DelBene and three-time Tour de France winner (and first non-European winner) Greg LeMond.  In addition there were a whole slew of sessions on everything from Search Server 2008, Branding SharePoint and Microsoft's latest technology acquisition search vendor Fast.

Most significantly, Microsoft made a few announcements/general statements -- some surprising and some expected:

  • "Cloud" Strategy
    Microsoft is making a commitment to introduce managed SharePoint and Exchange services to a broad range of organizations.  Up to now, only firms with 5000 or more seats could participate in their managed strategy (primarily because they were testing and hadn't worked out a multi-tenant approach).  During the conference Bill Gates and Kurt DelBene (Senior Vice President, Office Business Platform Group) announced that they are introducing multi-tenant (more than one client on a "box") managed services for both Exchange and SharePoint (in addition to rolling in LiveMeeting).  Both services will also enable single sign-on, so that historical issues with multiple authentication prompts should be a thing of the past, and a provisioning workflow for both sites and users.  Ultimately, the strategy seems to create an offering where clients can get an "enterprise" experience, where users can leverage a full compliment of traditionally on-premise applications -- like Exchange, SharePoint, Live Communications Server -- through the cloud.  Based on the demo they showed it looks promising.   You can read more here.
  • SharePoint-like Lists in SQL
    One of the more surprising announcements by Bill Gates was a suggestion that the next version of SQL may contain a SharePoint list-like construct within a table.  Taking that a step further, it may also be possible to directly link a SharePoint list to a single table!  After speaking with some of the product team members, I think this announcement was a bit premature (they appeared to cringe when reminded of what Bill had said during his keynote), but I'll be interested to see how both SQL Server and SharePoint progress in the next release.
  • Office Online
    While the executives stopped short of saying "we're going to give you Office over the web," they hinted we could be seeing versions of some of the Office suite products being offered over the web -- in thin-client form.  Never one to shy away from a good dig, Bill Gates took aim at Google's "consumer" centric approach, offering that they're (Google's) online productivity products aren't ready for the enterprise.
  • Visual Studio 2008 compatible Extensions for SharePoint in June
    One source of frustration is the constant marketing of VS 2008 improvements over 2005, but a complete lack of support for SharePoint projects (with the exception of workflow).  Product team members were on hand to assure everyone that the extensions are coming, with cool enhancements over the current 1.1 release for 2005.  They estimate these extensions will be available by June of this year.
  • Fast Search Integrated with SharePoint
    What was both disappointing and encouraging, Fast has folks onsite to discuss their work to integrate with SharePoint.  The downside was that it felt more like a marketing pitch than a "real" discussion regarding how they were going to enhance SharePoint.  That said, they did demonstrate some of the key advantages of their tool, in the SharePoint context.  In addition, they demonstrated some admittedly very slick Silverlight-enabled search result/interaction controls.  They also demonstrated a search-centric personalization approach with faceted navigation that was novel, even if it was not entirely new.
  • Browser Compatibility and Accessibility 
    This is less of an announcement and more of what should be a red-faced admission that SharePoint isn't as cross-browser compatible as anyone would have hoped, nor as accessible.  While 2007 is vastly improved over 2003, there are still pretty significant issues on both front.  In both cases, the product team assured everyone that this was a priority for vNext (Office 14/2010ish).  As a short term fix, they're pointing people to Telerik for their "upgrades" to the rich text editor, blog editor and wiki editor.  For accessibility, there's  a "toolkit" (developed with HiSoftware), to help with the accessibility aspects.

Beyond the announcements, the conference was full of the usual information sessions.  Microsoft seemed to have a good mix of services partners, ISVs and  Microsoft employees (both Microsoft Consulting Services and product team folks).

I was able to attend a number of sessions, but was generally dismayed at the lack of real depth or new material.  As mentioned earlier, the Fast search sessions were only slightly better than marketing pitches for their software.  Sessions on best practices rehashed the same stuff that virtually anyone in this space would know and has already heard a dozen times. If you had attended the previous SharePoint conference, it seemed like many of those sessions were repeated at this event (more than a year later).  And, in what seemed like a bizarre event, other attendees reported that in one session, two speakers began to disagree with each other during their presentation and  the talk degraded into unintelligible babble.

There were a few bright spots however.  The sessions on the new Search Server 2008 struck a nice balance between technical detail and actual usage.  Customers like EasyJet and Chesapeake Energy did a good job of relating how their SharePoint implementations progressed and the value that they received (a similar presentation by Best Buy for Business was less interesting though).  Finally, the session on the latest version of the Community pack for Wikis was quite interesting, if only to demonstrate how SharePoint can be extended beyond it core competencies, as well as the community support behind the product.

In all, the conference wasn't a waste of time, but I would have preferred better material.  I would have liked to have seen deeper material around all of the topics (in fact for developers, the Office Developers Conference earlier this year in San Jose was the place to be).   Better titles for some session would have also helped -- a sessions titled "My Content is in SharePoint, now what" sounded like it would have been about adoption or user experience, but really ended up being about securing content.  A good topic, to be sure, but poorly "branded." Finally, the best practices session is something everyone wants (the room was packed), but they should have focused more on the specific challenges in running a SharePoint implementation like: provisioning (the explosion that can occur), the challenge around taxonomy development, when to create site definitions vs. site templates, how to train users, dealing with varying levels of Office and so on.

If you were at the conference, I'd love to hear your feedback.  Like it?  Thought it was a waste of time?  Were there particular sessions that piqued your interest?

01 February 2008

Simple SharePoint Backup Routine

Like many of our clients, Consejo uses SharePoint to collaborate -- both with our clients and amongst our employees.  As a result, it has become a critical service to maintain -- thereby making it critical from a business continuity planning perspective as well. 

Recently a number of clients have all asked the same question:  how can we easily create backups of our SharePoint sites so that we can restore them in the event of a disaster?  While there are some good backup options built into SharePoint and some commercial vendors like AvePoint that provide backup and restore solutions, there are some relatively simply approaches that will provide baseline protection in the event of a disaster.

To begin, you should really read this post from Microsoft's SharePoint Developer Documentation Team blog on the various backup mechanisms and elements that need to be protected.  The blog entry does a great job of highlighting all of the moving parts, but doesn't provide a straightforward approach to getting the basics.  What we've tried to do, below, is provide you with an easy mechanism to automate and schedule backing up SharePoint site collections.  These backups can easily be restored in the event of a disaster.   To be clear, this approach is kind of the sledge hammer approach for site collections only and may not be right for the needs of individual sites.  However, this represents the very least you should have in place for your SharePoint environment.

NOTE:  The backup process described will backup only the site collections specified in the backup routine.  As the Microsoft article suggests, there are a lot of other parts to a SharePoint environment.   When designing your complete disaster recovery/business continuity plan, please ensure you have all of your bases covered.

Identifying the Site Collections

Depending on the type of SharePoint environment you have, your complete SharePoint environment will have one or more site collections.  When using the approach illustrated in this post, you must backup each site collection separately (or include them in a single job).  In any event, you should inventory the various site collections you want included in the backup routine.  If you're unsure what collections exist, you can look them up in the Central Administration tool by going to the Applications tab and clicking on the Site Collection List option under the SharePoint Site Management category (show in figure 1-1).

image

Figure 1-1 The site collection list for a given SharePoint application

If the site collections that appear aren't what you expect, make sure that you've selected the right web application, using the drop down list just above and to the right of the site collection list.

If you have found the right set of collections, take note of all the ones that are important to include in your backup routine.  You'll need the URLs to each of the collections.  Because you can have multiple collections off of the same web application, SharePoint may only show a relatively URLs; make sure that you know the full-qualified URL for this backup process.

Creating and Automating the Process

To create some basic automation and logging, we're going to create a CMD file that contains all of the commands necessary to use the STSADM command-line utility to backup one or more site collections and add some basic logging to a text file.

CMD code

The code in the CMD file should contain at least the following:

@echo off
echo --------------------------------------------------------------------- >> SharePoint_backup.log
echo SharePoint Backup Began >> SharePoint_backup.log
date /t  >> sharepoint_backup.log
time /t >> sharepoint_backup.log
"c:\program files\common files\microsoft shared\web server extensions\12\bin\stsadm" -o backup -url [URL TO YOUR SITE COLLECTION] -filename [PATH TO BACKUP FILE] -overwrite >> sharepoint_backup.log
if errorlevel 0 goto finish_backup
:error
echo An error has occured and the backup did not complete properly >> sharepoint_backup.log
goto end
:finish_backup
echo The backup completed successfully >> sharepoint_backup.log
:end
echo SharePoint Backup Finished >> sharepoint_backup.log
date /t >> sharepoint_backup.log
time /t >> sharepoint_backup.log

Keep in mind that the code contains bracketed text (like [URL]).  This bracket text should be replaced with settings specific to your environment, like the URL to your site collection or the path to your backup file.

Once you've made the modifications to your specific site, save the file to a directory on your SharePoint server; keep in mind that the log file will be written to the same directory and will collect entries over time.

Before proceeding, I would recommend testing your finalized CMD file to ensure it operates as you expect.  Once it does, proceed to the next step.

Scheduling the CMD File

There are a number of ways to schedule a process to run on a server, but Windows has a built-in scheduling system that you can use for this purpose.  The service is the Windows Scheduled Tasks.  A scheduled task can be created and run on a specific period and within the context of a given user.  To create the backup scheduled task, using the following instructions:

  1. Open up the Windows Control Panel
  2. Click on Scheduled Tasks
  3. Click on Add New Task
  4. The Scheduled Task Wizard appears

    image
  5. Click Next

    image
  6. Click on the browse button and locate the CMD file you created earlier
  7. Now name the task and choose the schedule as shown below

    image
    image
  8. Click Next
  9. Enter the credentials for the user that the system will use to run the task.  In this example, we're using the Administrator account, but you should choose a user with the minimum privileges necessary to complete the backup.   Keep in mind that the user must have access to both the SharePoint site collections and the file system.

    image
  10. Once you click next, the final confirmation dialog will appear; simply click Finish to schedule the job.

To confirm that the job runs as expected, you can reopen the Scheduled Tasks option in the control panel and right click on the new job.  From the context menu, pick RUN.

After you have your job scheduled, your SharePoint site collection(s) will be backed up every time the job runs.  I would recommend at least once every 24 hours.

NOTES:

  1. When I developed this routine, I made the assumption that you will get a full backup on the specified site collections every time the job runs.
  2. The backup files are overwritten every time the job runs, so if you want historical backups, you'll need to develop some process for making a copy of the resulting backup file elsewhere.  Ideally, you could move the backup file to tape or another file system once the SharePoint backup is complete.
  3. This backup process will backup all of the data and the security settings.  In the event of a disaster, the security context may not be the same when the site is restored.  For example, the domain used by SharePoint may change in the new environment.  As a result, you'll have to set the owner of the site through Central Administration to the new user ID who will control the site.  Then, you must grant the appropriate users in the new domain access to the SharePoint site collection.  This can get complicated if you use a lot of item or container-level security (e.g. sites within a collection or lists/libraries within a site don't use inherited permissions).
  4. The text file that holds the log entries can fill up quickly over time.  Make sure someone is reviewing that file periodically to ensure it does get too big AND that the backups are completing successfully.

I'd love to hear your feedback on this approach and/or whether this was helpful to you. 

25 January 2008

REVIEW: Insignia Bluetooth Stereo Headphones

While I typically don't like to post consumer product reviews on our corporate blog, this one is different... really.

As a developer, I have fallen prey to what appears to be a stereotypical developer behavior -- listening to music while coding.   Whether it's a behavior picked up through "peer pressure" or my own personal inability to focus without some sort of constant noise to block out my surroundings, I don't know.  However, listening to music has become critical.

In addition to my music listening, I have also begun to extensively use Skype.  Over the last two years, Skype has become an indispensable tool for all Consejo consultants to communicate with each other and our clients -- whether through VOiP, IM or file transfers; Skype just works. 

As a result of all of these uses of audio with my laptop, I began searching for a decent set of stereo headphones that had an integrated microphone.   For me, I was specifically looking for something that had the following characteristics:

  • Stereo headphones that produced good quality sound
  • Integrated microphone that could be used with Skype or other audio recording tools
  • Wirelessly attached -- I've tried wired headphones and they're just inconvenient
  • Long battery run-time -- I looked for something that had more than a continuous 8 hour run-time (tough to find)
  • Rechargeable via a USB cable
  • Rechargeable via AC cord
  • Reasonably priced.  For me, this meant under $100.

Although I found a number of candidates, most had short runtimes, were too bulky to fit in my laptop case (since I travel extensively, this was also key) or were too expensive.  Ultimately, I found the Insignia brand Bluetooth-attached headphones at Best Buy.  At $49.99 and a 10 hour run-time, they fit the bill.


Figure 1 - Insignia Bluetooth Headphones (model: NS-BTHDP)

I have been using these headphones for about three months now.  In that time, I've never run the battery totally down.  In addition, they can pair with more than one Bluetooth device (e.g. my computer and my cell phone), making it possible to listen to music and, when a call comes in to my cell phone, switch to that device and then switch back when the call has completed.  

Beyond all of this, here's what I really liked about these headphones:

Advantages

  • Decent run-time. 
    My experience is that they easily last a full eight hours of continuous use, but will likely last longer.  In addition, should the batteries start to run down, you can have the headphones simultaneously connected to a USB port and continue to list simultaneously.  The cord defeats the wireless nature of the unit, but at least you can keep using them while they recharge.
  • Multiple Device Pairing
    The headphones can pair with more than one device.  I'll typically pair the headphones with my cell phone and my computer.  This allows me to take calls on my mobile phone and listen to music without having to switch listening devices.  It may seem trivial, but given the number of calls I get throughout the day and the fact that when I'm not talking on the phone, I'm usually using my laptop, switching between headsets is really inconvenient!  One other advantage is that the A/V control profile on my laptop will pause Windows Media player when a call comes in and resume music play once I disconnect the call.  As a side note, my cell phone is a Samsung BlackJack, I've also used the headphones to listen to music on that device as well; it works very well.
  • Controls on the headset
    The headphones have audio control controls right on the headset.  Volume, connect/disconnect, play/pause, track selections and power are all conveniently located on the right headphone.  It took a bit to get used to the location of the controls, but once my muscle memory kicked in, I was able to control both my phone and my laptop without too much trouble.
  • Range
    I have been very impressed with the range.  Bluetooth is supposed to be good for up to 33 ft and I have, on many occasions, used all of that range plus some.  Whether this is a consequence of my laptop's ability to transmit or the headphone's ability to receive I don't know.  In fact, (for better or worse) it seems that the connection is either there or not; there's no graceful degradation in sound quality as I move away from my laptop  -- when you get too far away, the sound stutters and then ends.  I regularly use the headphones on my laptop in the basement of my home (where my home office resides) and walk up to the first floor without an interruption in sound.
  • Price
    At $49.99, the headphones are a real bargain.  I had originally thought about buying the Motorola Rokr stereo Bluetooth headset at $99, but with only a six hour run-time, I didn't think they'd fit my work schedule.
  • Comfortable and Light
    The headphones are only 2.8 ozs and are very comfortable to wear for long periods.  I've not had a huge success in wearing most headphones for long periods -- most  are either too tight or too loose and become very uncomfortable after two to three hours.  I've worn these for four hours or more without a problem.  That said, everything eventually becomes uncomfortable and I'm often glad when I can take them off.

Disadvantages

  • Microphone Sound Quality
    The microphone in the headphones is built in to the right ear piece.  There's no boom and it seems like it picks up more than its share of the surroundings background noise.  It does work reasonable well, but it's not as good as a dedicated wireless headset.
  • Profile Madness
    Whether it's a consequence of my laptop's Toshiba Bluetooth module, the driver or simply "the way things work," I can't use the headphones as headphones with a mic on my laptop.  In order to use the mic on my laptop, I needed to create two profiles -- one for dedicated headphones (no mic) and one as a headset (with a mic).  I would probably be content to listen music in "headset" mode, except the sound quality takes a dive in this mode (sound quality is noticeably fuzzy).  For this reason, I tend to use the headphones paired with my mobile phone for conversations and my laptop for music, unless I'm going to use Skype extensively.
  • No Convenient Carrying Case
    As I mentioned earlier, I travel a great deal.  As a result, I rely on my laptop case to contain all of the equipment and supplies I need to haul around from client to client.  As it is, my case weighs in at around 25 lbs (with all of my gear).  It's become quite packed and space is at a premium.  In addition, because of the amount of stuff, everything is packed tight and when the bag is tossed (thrown into a rental car seat or shoved under an airline chair), items inside the bag are crunched.  For these reasons, I wanted to protect my investment by buying something that would keep them safe while occupying minimal space in my laptop bag.  Unfortunately, a quick search around the Best Buy did not yield a suitable option.  In fact, Best Buy does not sell any sort of case for them at all.  After looking for about 20 minutes, trying everything from a CD case to a camera case, I couldn't find a good solution.  As a result, I've been carrying them around, precariously floating around the inside of my bag.  So far, nothing has broken, but we'll have to see after a year...
  • Difficult pairing with a iMAC
    I happen to have both iMAC (PPC not Intel-based) and Windows machines in my office.  The MAC is primarily used for testing, but I do have Skype and some other common services (like e-mail) configured on the machine.  I've had difficulty pairing the headphones with the MAC and have not had success (once paired) getting them to work.  Looking through some discussion boards leads me to believe I'm not the only one.  However, I'm not committed enough to spend time trying to fix the problem. 

So, in short, if you're looking for a pair of decent, reasonably priced, wireless headphones, you should consider the Insignia NS-BTHDP.   If you have them, I'd love to hear your feedback as well.

11 December 2007

SharePoint 2007 Service Pack Update

Microsoft has finally released the new service pack for SharePoint 2007.  The individual downloads for WSS and MOSS can be found here:

We will be upgrading our own servers and will post our findings shortly.

03 December 2007

SharePoint Service Pack (SP) 1

If you haven't seen it, Microsoft recently released some information on the upcoming service pack 1 for SharePoint (both WSS and MOSS).  This new service pack not only includes a number of hot fixes for both platforms, but introduces some new functionality.   In addition to Server 2008 support, Microsoft is now officially supporting AJAX-enabled web parts.  They've also included some new STSADM commands (and who doesn't like STSADM).

Unfortunately, Microsoft has only really stated that it will be released by 2008.  Recently, Arpan Shah posted in his blog that the service pack could be released "anytime between now and Q1 of 2008."  So, for those of you waiting for your issue to be corrected or some of the new features, you now have a potentially four month window to sit patiently...

12 November 2007

Using SharePoint Search as a Research Content Source

Back in Office 2003, Microsoft introduced the concept of the "task pane."  The task pane was a panel that appeared on the right side of the Office interface (at least for the "first class" Office products).  The task pane represented a few different functions -- from showing the status of a document in SharePoint, to allowing you to manage permissions on a document.   Included with these functions was something called the "Research" task pane. 

The Research task pane allows you to search various information sources using basic keyword-type searches.  For example, if you highlight a word in a document and right click, you see a function called "Look Up."  When you select that option, the feature searches through the dictionary (for example) for the definition of the term you highlighted.  You can see this function in figure 1-1.

image

Figure 1-1 The context menu allows you to lookup a term in Office 2007

When you execute this function, the Research task pane dutifully appears on your right.  By default, the task pane appears to the right and displays the search result. In addition, it exposes a number of other sources that the search can be executed against (shown in figure 1-2).

image

Figure 1-2 The task pane and the content sources.

When I first saw this feature, I thought it was a way to extract additional dollars out of buyers of Office, since a good number of the research sources were premium sites that wouldn't allow you access to the content without a subscription.  However, I then noticed a link at the bottom of the task pane labeled "Research Options."  Clicking on this link allows you to control what sources are included in your task pane, as well as allowing you to add addition sources as shown in figure 1-3.

image

Figure 1-3 The Research Options dialog

As it turns out, it's easy to add your own sources, in addition to enabling ones already defined within Office.  In fact, one of the best sources of "research" is SharePoint.  SharePoint's own search web service is already setup to be included as a search source (MOSS, not WSS). 

To add your SharePoint site as a search source, follow the instructions below:

  1. Click on Add Services button
  2. Type in the URL of the SharePoint search service.  The default URL for the search web service is: http://[server_name]/_vti_bin/search.asmx.  Simply replace [server_name] with the host of your SharePoint site.
  3. Click on OK and Office will validate the selection to determine whether there's a compatible search service.  
  4. Once Office validates the search service, it will show you the name of the search service available to be included.  The service name will be the name of the primary MOSS site where search is hosted.

    image
  5. Simply click on Install and your MOSS search service will be added to your research source.

Once you've added your own internal search as a source, any lookup done within first class citizens of Office (Word, PowerPoint, Excel and Access), can use that source to look up terms and return search results, just as any other source.   When users click on a search result, Internet Explorer automatically opens, preserves the search results in pane on the left side of the interface and show the specific, chosen result in the main window (as shown in figure 1-4).  Now, all users have to do is navigate the various results until they find the one they feel meets their requirement.

image

Figure 1-4 Search results preserved in IE

This feature is particularly valuable for organizations that need to connect employees with content throughout the enterprise.  In addition, it adheres to a good rule of thumb about portals: don't make your employees leave the applications they're comfortable using -- surface the functionality in the applications where they do their work

08 November 2007

IIR/SharedInsights Portals, Collaboration and Content Management Conference

[UPDATED: 25 November 2007 - Slight flow changes to the content]

I've just returned from the IIR/SharedInsights Portals, Collaboration and Content Management conference.  While I've been speaking at this conference for a few years, this year's conference was a bit unique.  Unlike past conferences, where the vast majority of the attendees were more business oriented and "non-denominational" when it came to technology, this year's attendees were more technical and were very interested in specific technologies -- a good many of them interested in SharePoint.  It seemed that many of the attendees were either starting to implement or had implemented "phase 1," a smaller percentage were making their final decisions around what portal platform they would implement in the coming months -- almost universally, SharePoint was in the product mix, if not the chosen portal platform (hence the interest).  However, there still seemed to be a lot of basic questions about how SharePoint would fit in the enterprise.  To that end, I wanted to recommend a book written by some former colleagues of mine.  It's called Essential SharePoint 2007. 

What makes this book somewhat unique in the space (since there are absolutely tons of book on SharePoint 2007) is that it takes a less technological route.  The book focuses on business usage more than technological implementation.  I would recommend it as good starting point for anyone interested in SharePoint -- whether or not you're technically inclined.  In addition, CMSWatch also has a number of reports which compare SharePoint to other tools in the ECM/Portal space.  These reports would also be valuable for anyone considering SharePoint.

Now, even in the SharePoint 2003 days, there was great interest in SharePoint -- organization's interest in 2007 is not really unique.  In a good majority of the cases, the Windows SharePoint Services component was and is a very big leap in accessible (easily obtained and easy to install) collaborative technology, but it is also just darn easy to use for the vast majority of typical Office users.  Contributing to this ease of use is the fact that the technology is directly integrated with Office -- even people with older versions of Office can use it (you don't have to match SharePoint's version with your Office version).  However, the 2007 version (and WSS v3) seems to have created a great deal more buzz.

From what I heard from attendees, most organizations were hoping to leverage the portal capabilities found in MOSS.  There was a slightly smaller group interested in pure team collaboration management -- project teams need a place to deposit assets and work from one "song book."  Finally, there were those groups who felt that SharePoint was almost a "blight," but needed to figure out how to manage it (my guess is that these individuals got caught in the WSS explosion that occurs in many organizations). 

If I were to identify the biggest changes/advantages, it would be in two categories: 1) expanding content management capabilities and 2) improved extensibility.  On the content management side, web content management tops the list.  This feature allows you to manage traditional web sites using SharePoint.   In addition, Microsoft has added new forms of contribution with the addition of Wiki and Blog templates.    When you add these capabilities to the business intelligence and forms processing features, Microsoft has taken SharePoint native content management function to a whole new level.

For the developer types, 2007 represents a leap forward in extensibility, where almost everything inside of SharePoint is accessible through the object model.   For example, you can write your own authentication provider, to enable SharePoint to use something other than Active Directory to authenticate users (unheard of in SharePoint 2003).  It's also now possible to easily add new interface elements to native SharePoint administrative screens using the "features" capability.

For those of you who might be interested in some of the content at the conference, IIR has posted some podcasts on their web site.   More podcasts will be posted as time goes by (include my own).  If you're interested in attending the spring conference, you can find more details on the IIR web site (you may want to wait a few days before searching around, since the current conference is still running as of 8 November).