SharePoint Dan

So it would seem that when installing the “Google Apps Sync for Microsoft Outlook” plugin there’s a minor issue with the Outlook 2007 client’s Instant Search Capability.  After installing the plugin the drop down for Instant Search within the Outlook client is disabled.  I suppose this is to be expected since the Google Search engine has a better grasp of the mail stored in the depths of my Google Apps mail account and its 25 GB of space.  However, when changing profiles back to my Exchange profile, I find that the Instant Search is still disabled.

Epic Fail.

While I understand Google’s intent is to be able to assist users in replacing their Exchange profile with their Google Apps e-mail profile with the sync plugin, there are those of us that will continue to use an Exchange profile and the Google Apps capability is a nice to have to be able to use the Outlook client interface.

At first, I thought perhaps this was an Outlook client issue that had been affected by SP2 or some other cumulative update that was applied, however after doing a little Googling, it seemed that no one else had reported a similar experience.  I also realized that this behaviour only became apparent after installing the Google – Outlook plugin.  So I uninstalled the plugin and wondered, “Will Instant Search work once more?”  Negative, Instant Search was still disabled.

Looking within the Search Interface, Windows Desktop Search was telling me that Indexing Outlook had been disabled by the System Administrator.  Doing a bit of digging around, it became apparent that I hadn’t disabled WDS, and the mail admins hadn’t done so either, so it was back to square one of looking through the registry to see what had been tweaked.  Where else to begin but Microsoft’s documentation pertaining to Group Policy settings and Windows Desktop Search which can be found at:

http://technet.microsoft.com/en-us/library/cc732491(WS.10).aspx

A registry key had been created at:

Computer\HKLM\Software\Policies\Microsoft\Windows\Windows Search

with a registry key named “PreventIndexingOutlook” set to a value of “1″, telling WDS not to search Outlook under any means.  Simply changing this value to “0″ and restarting the Outlook client and WDS and Instant Search were back up and running properly across all profiles.

Uninstalling and reinstalling the Google Sync plugin quickly reverted the registry key back to “1″, preventing WDS from indexing Outlook.  Even upon uninstalling the plugin, the registry key remained.  This seems like a bit of configuration management that should be corrected so as to ensure that users are not limited by Google’s plugin should they decide not to use it without hindering their search capabilities.

Bottom line, this is a registry change that is unexpected that is caused by the Google Sync Plugin.  Am I happy to see Google integration with the Outlook client, sure, but not at the cost of Search.

The other evening, I discovered that my esteemed colleague, Spencer Harbar, will be presenting a MSDN webcast on the topic of “SharePoint Products and Technologies for Internet Site Development: Content Deployment”.  Upon registering, I realized that I didn’t have Outlook setup to connect to my work e-mail (rather it’s set up for my test servers on the home network) so there wasn’t an easy way to add the iCalendar reminder to my Outlook calendar that I use for work that alerts me on my BlackBerry.

Perhaps it would work on my Google Apps domain that I have setup for personal e-mail, right?  Unfortunately the iCalendar file (ics format) was not readable by the Google Calendar on my first attempt.  Doing a little Googling, I came across several articles that stated compatibility issues between Microsoft iCalendar reminders and other non-Microsoft iCalendar systems.

So that led me to download the iCalendar object, open it in Outlook and then save it to yet another iCalendar object, slightly reformatted which then apparently could be imported into my Google Calendar.  “Huh?”

Reading through the IETF RFC 2445, I pondered whether or not Microsoft is following the proper format to provide a well formed iCalendar object.  From the looks of it they are, however I’m perplexed as to why the Google Calendar is incapable of importing the object without having it reformatted through Outlook first.  Is it due to the fact that it’s looking for the PRODID field which looks to be missing?

The initial iCalendar reminder form Microsoft:

BEGIN:vCalendar
VERSION:2.0
METHOD:PUBLISH
BEGIN:vEvent
DTSTART:20090127T173000Z
DTEND:20090127T183000Z
UID:1032396521
DTSTAMP:20090104T205527Z
DESCRIPTION:Thank you for your interest in Microsoft Events. We w
ould like to remind you of the following event: TechNet Webcast:
How Microsoft Does IT: Designing, Developing, and Deploying Share
Point Server 2007 Publishing Portals (Level 300). \n\nPlease revi
ew the information below.\n\nEvent Code: 1032396521\nEvent Name:
TechNet Webcast: How Microsoft Does IT: Designing, Developing, an
d Deploying SharePoint Server 2007 Publishing Portals (Level 300)
\nStart Date: 1/27/2009\nStart Time: 9:30 AM (GMT-08:00) Pacific
Time (US & Canada)\nEnd Date: 1/27/2009\nEnd Time: 10:30 AM (GMT-
08:00) Pacific Time (US & Canada)\n\nPlease click on the followin
g link for more information regarding this Event https://msevents
.microsoft.com/cui/r.aspx?r=1300308275&c=en-US&t=4. We look forwa
rd to seeing you at the Event!
SUMMARY:Live Webcast - TechNet Webcast: How Microsoft Does IT: De
signing, Developing, and Deploying SharePoint Server 2007 Publish
ing Portals (Level 300)
PRIORITY:3
BEGIN:vAlarm
TRIGGER:P0DT0H15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:vAlarm
END:vEvent
END:vCalendar

What I received upon exporting from Microsoft Outlook 2007:

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 12.0 MIMEDIR//EN
VERSION:2.0
METHOD:PUBLISH
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VEVENT
CLASS:PUBLIC
CREATED:20090104T205909Z
DESCRIPTION:Thank you for your interest in Microsoft Events. We would like
    to remind you of the following event: TechNet Webcast: How Microsoft Does
    IT: Designing\, Developing\, and Deploying SharePoint Server 2007 Publishi
    ng Portals (Level 300). \n\nPlease review the information below.\n\nEvent
    Code: 1032396521\nEvent Name: TechNet Webcast: How Microsoft Does IT: Desi
    gning\, Developing\, and Deploying SharePoint Server 2007 Publishing Porta
    ls (Level 300)\nStart Date: 1/27/2009\nStart Time: 9:30 AM (GMT-08:00) Pac
    ific Time (US & Canada)\nEnd Date: 1/27/2009\nEnd Time: 10:30 AM (GMT-08:0
    0) Pacific Time (US & Canada)\n\nPlease click on the following link for mo
    re information regarding this Event https://msevents.microsoft.com/cui/r.a
    spx?r=1300308275&c=en-US&t=4. We look forward to seeing you at the Event!
DTEND:20090127T183000Z
DTSTAMP:20090104T205527Z
DTSTART:20090127T173000Z
LAST-MODIFIED:20090104T205909Z
PRIORITY:1
SEQUENCE:0
SUMMARY:Live Webcast - TechNet Webcast: How Microsoft Does IT: Designing\,
    Developing\, and Deploying SharePoint Server 2007 Publishing Portals (Leve
    l 300)
TRANSP:OPAQUE
UID:1032396521
X-ALT-DESC;FMTTYPE=text/html:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//E
    N">\n<HTML>\n<HEAD>\n<META NAME="Generator" CONTENT="MS Exchange Server ve
    rsion 08.00.0681.000">\n<TITLE></TITLE>\n</HEAD>\n<BODY>\n<!-- Converted f
    rom text/plain format -->\n\n<P><FONT SIZE=2>Thank you for your interest i
    n Microsoft Events. We would like to remind you of the following event: Te
    chNet Webcast: How Microsoft Does IT: Designing\, Developing\, and Deployi
    ng SharePoint Server 2007 Publishing Portals (Level 300). </FONT></P>\n\n<
    P><FONT SIZE=2>Please review the information below.</FONT>\n</P>\n\n<P><FO
    NT SIZE=2>Event Code: 1032396521</FONT>\n\n<BR><FONT SIZE=2>Event Name: Te
    chNet Webcast: How Microsoft Does IT: Designing\, Developing\, and Deployi
    ng SharePoint Server 2007 Publishing Portals (Level 300)</FONT></P>\n\n<P>
    <FONT SIZE=2>Start Date: 1/27/2009</FONT>\n\n<BR><FONT SIZE=2>Start Time:
    9:30 AM (GMT-08:00) Pacific Time (US &amp\; Canada)</FONT>\n\n<BR><FONT SI
    ZE=2>End Date: 1/27/2009</FONT>\n\n<BR><FONT SIZE=2>End Time: 10:30 AM (GM
    T-08:00) Pacific Time (US &amp\; Canada)</FONT>\n</P>\n\n<P><FONT SIZE=2>P
    lease click on the following link for more information regarding this Even
    t <A HREF="https://msevents.microsoft.com/cui/r.aspx?r=1300308275&c=en-US&
    t=4">https://msevents.microsoft.com/cui/r.aspx?r=1300308275&c=en-US&t=4</A
    >. We look forward to seeing you at the Event!</FONT></P>\n\n</BODY>\n</HT
    ML>
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-IMPORTANCE:2
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR

Is it just me or is there some variance between the two iCalendar objects?  The Google iCalendar specification for formatting of an iCalendar object merely requires:

BEGIN: VCALENDAR
VERSION:2.0
PRODID:< [enter ID information here] >
(other header information goes here)
BEGIN:VEVENT
(event details for individual event)
END:VEVENT
BEGIN:VEVENT
(event details for individual event)
END:VEVENT
END: VCALENDAR

Any thoughts on why the variance of the objects would cause an issue for the first ICS to not be importable, but the second could be after being processed by Outlook 2007?

At a minimum, remember to signup for the event to hear Spence on SharePoint

MSDN Webcast ICS
Outlook 2007 MSDN Webcast iCalendar ICS file

Now Playing: Coldplay – X & Y – Swallowed In The Sea