You are the Exchange administrator for your company. All seven servers in the Exchange organization run Exchange Server 2003.
Your company acquires another company that uses a single Novell GroupWise server that runs on NetWare.
The GroupWise mailboxes are assigned SMTP addresses in a namespace that is different from the namespace used by the Exchange mailboxes. For business reasons, it is not possible for you to migrate the GroupWise users to Exchange immediately.
You configure one of the Exchange servers, which has no local mailboxes, as a dedicated bridgehead server for communications to the GroupWise server.
Exchange users can see the GroupWise users in the Exchange global address list (GAL) and can send messages to them.
However, when the Exchange users want to meeting requests, they cannot view the free or busy status of GroupWise users.
You need to ensure that the Exchange users can view the free or busy status of the GroupWise users. What should you do?

A.
On the Exchange bridgehead server, configure the Calendar Connector.

B.
On the Exchange bridgehead server, install the Gateway Service for NetWare.

C.
On the Exchange bridgehead server, add a replica of the Schedule+ Free Busy folder.

D.
On the Exchange bridgehead server, create an SMTP connector to one of the GroupWise SMTP bridgehead servers.

E.
On all Exchange servers, install the Microsoft Exchange Connector for Novell GroupWise.

Explanation:

The Calendar Connector always stores free and busy information in its administrative group’s public folder, specifically the Schedule+
Free Busy public folder. If there are multiple administrative groups on an Exchange 2003 server, each administrative group has its
own public folder. In this case, free and busy information for Exchange 2003 users may be stored in a different public folder than the
free and busy information for users on partner computers. You cannot initiate real-time queries to downstream Exchange 2003
routing groups. Exchange users in routing groups that are not directly connected by the Calendar Connector to a partner system
(routing groups downstream of the routing group in which the Calendar Connector is installed) are not able to initiate real-time
queries. Instead, they receive the calendar data that has been replicated from the Calendar Connector�s site (routing group). If you
want to provide real-time free and busy access to all Exchange users, install and configure a Calendar Connector in each Exchange
site (routing group). There is no way to relay a real-time free and busy query over a Site Connector or Routing Group connector. You
cannot use the Calendar Connector as a free and busy switch between Notes and GroupWise. Exchange does not support free and
busy switches or queries from one partner computer to another by using Exchange as a backbone. In addition, you cannot use a
partner computer as a backbone between two Exchange computers. You cannot configure multiple Calendar Connectors in a single
administrative group that connects to the same partner post office
Reference
Appendix B -Configuration Procedures for Migrating from Novell Groupwise Messaging Functionality