Exxhange SQL And IIS- P57 ppt

Managing the Client Access Server • Chapter 5 257 Figure 5.15 Enabling Outlook Anywhere NOTE The external host name you specify should match the common name entered in the SSL certifi cate that has been used to secure your Default Web Site. Typically, this name is something like mobile.domain.com, mail.domain.com, or owa.domain.com. 258 Chapter 5 • Managing the Client Access Server 4. Select the type of external authentication method you want to use for Outlook clients accessing their mailbox over the Internet. You can select Basic or NTLM authentication, but it is recommended you select NTLM authentication, especially if you have a fi rewall such as an ISA 2006 Server, which supports this authentication method. SOME INDEPENDENT ADVICE So, why is it I should choose NTLM over Basic authentication when enabling Outlook Anywhere? Well, because if you choose Basic authentication, you will need to enter your password each time Outlook is opened, even when you’re located on your internal network. 5. You have the option of allowing secure channel (SSL) offl oading, which should be selected if you have a device that can handle this capability. 6. When you have made your selections, click the Enable button and then select Finish to exit the wizard. SOME INDEPENDENT ADVICE If for some reason you would rather enable Outlook Anywhere using the Exchange Management Shell, you can do so with the Enable-OutlookAnywhere cmdlet. In order to enable Outlook Anywhere with the same settings as those confi gured in Figure 5.15, you would need to type: Enable-OutlookAnywhere –Server <servername> -ExternalHostname “mobile.exchangedogfood.dk” –ExternalAuthenticationMethod “NTLM” –SSLOffl oading $False Confi guring the Outlook Client In this section, we’ll go through the needed steps required to confi gure an Outlook 2007 client to be able to take advantage of Outlook Anywhere. To confi gure an Outlook 2007 client for Outlook Anywhere access, perform the following steps: 1. Open the respective Outlook client (Outlook 2003 or 2007), and then click Tools | Account Settings. 2. Double-click the E-mail profi le, and then select More Settings. Managing the Client Access Server • Chapter 5 259 4. Enable and fi ll out each fi eld as shown in Figure 5.17. Make sure you select NTLM Authentication if that’s the method you use in the publishing rule on your ISA server. Click OK twice, then select Next, Finish, and Close to exit Outlook Account Settings. Figure 5.16 Enabling Outlook Anywhere in Outlook 2007 3. Choose the Connection tab and check Connect to Microsoft Exchange using HTTP (as shown in Figure 5.16), and then click Exchange Proxy Settings … 260 Chapter 5 • Managing the Client Access Server The next time the respective end user is away from the offi ce, they will be able to connect to the Exchange Server using their Outlook client. Managing Outlook Web Access 2007 During the development of Exchange Server 2007, one of the goals for the Exchange Product group was to make the best Web mail client in the world even better. This task resulted in Outlook Web Access (OWA) 2007 having to be completely rewritten in managed code in order to make it scale even better, and to make it easier to add new features to the UI in the future. Speaking of the UI, one thing you’ll notice immediately is that it has been completely redesigned. The number of clicks required to get tasks done has been drastically reduced. Actions and responses are now in place, meaning they are opened in the same browser window instead of in separate multiple dialogs or property sheets. All pop-up notifi cations have been removed Figure 5.17 Confi guring the Exchange Proxy Settings Managing the Client Access Server • Chapter 5 261 so there are no concerns of being blocked by pop-up blockers. In addition, the drag-and-drop functionality and right-click context menus have been vastly improved. Additionally, OWA 2007 supports 47 different languages! Finally, unlike OWA 2003, which did all the UI rendering on the back-end server, OWA 2007 now does all the UI rendering on the CAS, thereby signifi cantly reducing the load on the Mailbox server. Confi guring Outlook Web Access Server-Side After having installed the CAS role on a server, you can manage most of the OWA-related features directly from within the Exchange Management Console, more specifi cally under the Client Access node located beneath the Server Confi guration work center. As you can see in the Work pane, when selecting one of the CAS servers in the Result pane, Outlook Web Access 2007 displays all of the virtual directories listed in Table 5.2. Notice all of them but one (owa) are legacy OWA virtual directories, only used when accessing mailboxes and/or Public Folders stored on a legacy Exchange Server (Exchange 2000 or 2003). Table 5.2 Exchange 2007 and Legacy Exchange Virtual OWA Directories Virtual Directory Version Description Exadmin Exchange 2000, 2003 The /Exadmin virtual directory is used when administering Public Folders via the Exchange 2000 or 2003 System Manager. Exchange Exchange 2000, 2003 The /Exchange virtual directory is used by OWA when accessing mailboxes on legacy Exchange Servers (Exchange 2000 or Exchange 2003). ExchWeb Exchange 2000, 2003 The /ExchWeb virtual directory is used by the /Exchange virtual directory for accessing mailboxes on legacy Exchange Servers (Exchange 2000 or Exchange 2003). owa Exchange 2007 The /owa virtual directory is used by Outlook Web Access when accessing mailboxes on Exchange 2007 mailbox servers. Continued . or 2007), and then click Tools | Account Settings. 2. Double-click the E-mail profi le, and then select More Settings. Managing the Client Access Server • Chapter 5 259 4. Enable and fi ll out. which should be selected if you have a device that can handle this capability. 6. When you have made your selections, click the Enable button and then select Finish to exit the wizard. SOME INDEPENDENT. twice, then select Next, Finish, and Close to exit Outlook Account Settings. Figure 5.16 Enabling Outlook Anywhere in Outlook 2007 3. Choose the Connection tab and check Connect to Microsoft Exchange