Exchange 2007

[Timur Shevekhman]

I noticed the updated FAQ now mentions Exchange 2003/2007 Mixed Mode,
but not Exchange 2007. I want to confirm that Exchange 2007 stand-
alone, without any legacy Exchange versions in the organization, is
not supported.

Thank you.

P.S. I believe there is also a type in FAQ:
# Exchange 2000 Server:

* Windows Server 2000 SP4
* Exchange 2003 SP3 <--- should probably say Exchange 2000 SP3

[Darrell]

We do not support Exchange 2007 running in a native mode as the free/
busy service model changes from that of Exchange 2003. Running in
mixed mode Exchange maintains the Exchange 2003 compatibility and this
is why the service works with Exchange 2007 in mixed mode.

Thanks for the typo note it has been updated to Exchange 2000 SP3.

Thanks,
Darrell
On Mar 13, 2:23 pm, Timur Shevekhman

[Timur Shevekhman]

Darrell,
When say "Exchange 2007 in mixed mode", do you mean Exchange 2007 that
has public folders installed? Or is it the requirement to have the
environment that has both Exchange 2003 and Exchange 2007?

Maybe, a better way to ask this would be: if I had Exchange 2007
installed in the organization that never had previous versions of
Exchange (which Microsoft calls the pure Exchange 2007 organization, I
believe), how would I switch it to mixed mode? Would installing Public
Folders do it? The installation of Public Folders in Exchange 2007 is
done by answering "Do you have any client computers running Outlook
2003 and earlier or Entourage in your organization?" during the set
up. I am hoping this is all I would need to do.

Thank you.

[Darrell]

Timur,

We do require the Public folder store as this is where Exchange 2003
and the Google Calendar Connectors write free/busy data. You can try
to run Exchange 2007 native mode with a Public Free/Busy store, but I
doubt it will work. There are a few unknowns I can think of that have
never been tested:

1) Will Exchange 2007 support the WebDAV calls we use to read and
write to the Public free/busy store? We always used an Exchange 2003
server with OWA in a mixed mode setup.
2) Will Exchange 2007 and Exchange 2007 Clients try to read free/busy
data from the Public store since Exchange 2007 deals with free/busy in
a new way?
3) If I recall we use the LegacyExchangeDN value in our code to
determine the correct path for writing the free/busy details. Not sure
how this is affected in Exchange 2007 in Native mode.

You can create the Public store and try to read and write free busy
data. Having the Exchange 2007 install create this public folder
structure should not have any negative impact on your Exchange 2007
implementation.

Darrell


On Mar 16, 12:25 pm, Timur Shevekhman

[JimD]

Hello Timur and Darrell,

I've been working on this exact scenario recently and I'm not able to
get the Calendar Connector Web completely working.
We're running Exchange 2007 native, but we migrated from Exchange 2003
so I have the Free/Busy structure from that earlier version, even
though the 2003 server has been decommissioned. Also, our end users
are running Outlook 2003 so the Public Free/Busy folder is still being
actively used.
I've followed the steps in the Installation Guide, the YouTube video
installation guide, and adapted for Exchange 2007 where necessary. I
also had Google Support configure my Calendar Connector URL (I didn't
see the post on this forum that you don't need that step anymore at
the time) and they've verified that it's configured on the Google
side.
Running the Diagnostics page, the "Verify Free/Busy information can be
found in Exchange" step fails.

In case you have any ideas of what else I can try, I'm going to post
the results I get at the point of failure:
-- From Google Calendar I receive the "Calendar does not exist or
isn't shared" message.
-- In the WebServices log (at Debug level) I get: [6868] ERROR
GCalExchangeLookup.ExchangeQuerier -
Google.GCalExchangeSync.Library.GCalExchangeException: GCalRequest is
null or empty
-- On the Diagnostics page I get:
Google.GCalExchangeSync.Library.GCalExchangeException: Error occured
while retrieving free busy ranges ---> System.Net.WebException: The
remote server returned an error: (501) Not Implemented. at
System.Net.HttpWebRequest.GetResponse() at
Google.GCalExchangeSync.Library.WebDav.XmlRequestImpl.IssueRequest
(String url, Method method, String body, HttpHeader[] headers) at
Google.GCalExchangeSync.Library.WebDav.WebDavQuery.LoadFreeBusy(String
exchangeServerUrl, ExchangeUserDict users, DateTimeRange window) at
Google.GCalExchangeSync.Library.FreeBusyService.LookupFreeBusyTimes
(ExchangeUserDict users, DateTimeRange window)

[Darrell]

JimD,

From log it looks like 501 Not Implemented means the Exchange 2007
server no longer supports the web service call we are making to read
the free/busy data from the Exchange store. This is not surprising
since Exchange 2007 in native mode does not support free/busy in the
same way it has to when you have still a mix 2003/2007 Exchange
environment.

We only support using the product against an Exchange 2003 server. It
does work in a mixed mode environment so long as the connector is
communicating with an Exchange 2003 server. Since you have a native
2007 environment I don't think the Google Calendar Connectors will
work for your situation in this configuration.

The only suggestion I have is consider setting up a small Exchange
2003 infrastructure and use a tool to replicate free/busy data from
your Exchange 2007 environment to this Exchange 2003 environment. Then
you could point the connector to the Exchange 2003 server. There are a
number of tools out there that help you with free/busy replication.
Many companies have to deal with this situation when they merge and
have two separate Exchange organizations.

Darrell Kuhn
Google Inc.

[JimD]

Darrell,

Thanks for examining my post and replying. I'm a sys admin, not a
programmer, but I have a sharp programmer in my department. I'm going
to see if he can take a look at the connector source code this week
and adapt it for Exchange 2007. I'll report back on any progress we
make.

Thanks again,
Jim