Welcome to Kraft Kennedy

Kraft & Kennedy, Inc. provides technology and strategic consulting services to law firms, corporate legal departments and financial services firms. We can help you analyze, plan, implement and manage business and technology solutions to optimize your organization's functionality and processes.

Kraft Kennedy | Technology Blog

Archive for August, 2010

The Search Centers in SharePoint 2010 use “minimal.master,” which is a very basic layout without navigation.  While this might be fine for the search center, it doesn’t work well for a corporate intranet, where users expect to navigate between many sites.  With the default search center, once a user goes there he’s stuck there, since there’s no easy way to navigate back to another site.
 
Search Center with Default Master Page
 Search Center with Default Master Page

You might expect to be able to just switch the master page to one with navigation, but doing so causes the search box to disappear.  So you end up with a search site with your custom branding, but no search box. 

The reason for this is that the search control is actually located in the breadcrumb navigation, which only works for minimal.master.  The associated page layouts also contain controls to hide what’s in the search area of the master page, so that you don’t end up with two search boxes. 

You can fix all this when you use a custom master page by just modifying the search layout pages with the following steps:

1)  Open SharePoint Designer 2010 to your site, and click the “Master Pages” object

2)  Check out the following pages: SearchMain.aspx, SearchResults.aspx, and PeopleSearchResults.aspx

3)  Find the following section and delete it.  This removes the control that hides the search area from your master page.

<asp:Content ContentPlaceHolderID=”PlaceHolderSearchArea”  runat=”server”>
……
</asp:Content>

4)  Check-in, Publish, and Approve the pages.

Note, if there’s anything else from the breadcrumb navigation that you want to appear on the page, you would have to add it back into ContentPlaceHolderMain. 

At that point, your Search Center should take on the layout from your custom master page, and it will use the same search box as the master page.

Search Center with Custom Master Page

Search Center with Custom Master Page

Microsoft has just announced that Exchange 2010 Service Pack 1 has been released!  Please refer to http://msexchangeteam.com/archive/2010/08/25/455861.aspx for the official announcement and download link.  Additionally, I previously discussed some of the more notable features of SP1 in blog posts here and here.  This is a compelling upgrade for all Exchange 2010 implementations and introduces a number of key new features such as the ability to host archive mailboxes on separate mailbox databases from the primary mailbox, archive support for Outlook 2007 SP2, and Continuous Replication Block Mode.

The 2010 12th Annual ILTA Golf Tournament was a great success! Kraft Kennedy would like to thank our co-sponsors: WorkShare, Cypress Communications and Dell-Equallogic for helping to put on a great event.

Over 60 people came out and we would like to congratulate the following teams who received trophies this year:

1st Place
Fernando Monteleone, Robinson & Cole LLP
Brandon Monteleone, Robinson & Cole LLP
John Sroka, Younts
Vito Squarciafico, Pullman & Comley

2nd Place
Chris Owens, Kraft Kennedy
John Sawyer, Partridge Snow & Hahn LLP
Dana Rotter, Holme Roberts & Owen
Frank Nelson, Linquist & Vennum PLLP

3rd Place
Joey Perez, American LegalNet, Inc.
Ken Levonaitis, McCarter & English
Mike Walls, US Army
Ted Glutz, Kraft Kennedy

Thanks to everyone who came out and we look forward to seeing you again next year!

 

Viva Las ILTA 2010

It is hot, the end of summer, it must be time for ILTA. This year the annual conference will be held in Las Vegas and the theme is Strategic Unity. Kraft Kennedy will again play an active role in conference. In fact, we will have 13 management and technical consultants attending the conference this year.  We’re also a Platinum Sponsor once again.  We’d love for you to stop by and talk about technology, enter our raffle, or just say hello.  Here is where you can find us:
Continue reading…

I was always amazed when attorneys first got Outlook 2007, they quickly uncovered that well known bug when trying to print search results from the Tools -> Instant Search -> Advanced Find feature in Table Style.   It’s almost as if they were trying their best to stump the product.

What they may not have realized is that even though the Advanced Find option is listed under the new Instant Search menu, it is really the old iteration of Outlook searching.    There are a couple of workarounds, including copying the Advanced Find search results into a new subfolder, and then printing that folder in Table Style.  However, the best thing they can do is use the Instant Search bar of their mailbox itself.  The syntax of this search can include metadata criteria in addition to keywords, and when using Cached Mode with Windows 7, the search truly is instant.

Outlook 2007 Instant Search

Outlook 2007 Instant Search

The other nice feature is the suggestion to search All Mail Items if you aren’t happy with the results.    And printing in Table Style from these results works like a charm.

So what about Outlook 2010?  Is this still a bug?  No!  So did Microsoft fix it?  No!  Looks like they simply removed the File menu options in the Advanced Search dialog, so you can’t print from here.   They are sneaky like that…..   See for yourself:

Outlook 2010 - Advanced Find

Outlook 2010 - Advanced Find

In summary, for your email searching needs, you should advise your users to begin using the Instant Search feature.  The Advanced Find is dying a slow death.

Are you protected?

On August 2nd, Microsoft released an out-of-band patch addressing a critical security flaw in the Windows shell.  This flaw affects all versions of Windows and could allow remote execution of code under certain circumstances.  Obviously, any critical patch released outside of Microsoft’s normal patch release schedule should be treated with a sense of urgency.  We in the Support Practice Group have already taken steps to implement this patch at all of our clients and can happily report that we have not seen any issues whatsoever with the patch, so far.  Additional information on the security flaw and the associated patch is available from Microsoft here.

One of our SPG consultants, Joe Szabo, recently noticed an issue where even though it looked like our BES 5.0 server should be prepopulating users’ new Blackberry devices with 200 previous email messages it, was not doing so.  In the Blackberry Administration console, he expanded BlackBerry Solution Topology > BlackBerry Domain > Component view > Email and checked to ensure that the server was set to prepopulate 200 previous messages.  Joe did some research and found that by default Blackberry only prepopulates messages for new users on their first Enterprise Activation.  It will not prepopulate messages if those existing users activate a new Blackberry device.

To force prepopulation for all users, Joe added the following registry keys:

[HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Agents]
“ForceMsgPrepopOnActivation”=dword:00000001
“ForceMsgPrepopDays”=dword:0000000e
“ForceMsgPrepopMessages”=dword:000002ee

On an x64 server, you would add these entries under:

[HKEY_LOCAL_MACHINE\Software\WOW6432Node\Research In Motion\BlackBerry Enterprise Server\Agents]

We have confirmed that this works for BES 5.0, but it should work for older BES versions as well.

SharePoint 2010 can be easily deployed to a single box with local administrator accounts using the standalone, out-of-the-box install, but this forces you to use SQL Express 2008 (which comes with SharePoint).  What if you want to do a complete farm install on the box, but stick with local accounts?  Then this becomes a lot more tricky.

The complete install, using the configuration dialogs, will not let you enter local accounts, and will force you to use a domain account.  The best practice seems to be to promote the server to a domain controller, and use domain accounts, however this might not be possible or desired if you’re working in a DMZ, or on a development machine.  Also, you might want to do the complete install so that you can leverage the 10 GB data limit and remote BLOB storage in SQL 2008 Express R2, rather than being stuck to the earlier version of SQL Express which comes with SharePoint.   Luckily, there’s some ways to bypass the domain account requirement by using PowerShell scripting to set up the environment.  I found two helpful blog posts below which get you part of the way there, and I’ll help clarify some of the missing pieces.
Continue reading…