Mastering Microsoft Exchange Server 2003 phần 10 potx

Figure 19.3: Configuring Exchange ActiveSync at the user level using the Exchange Features page of a user's dialog box Outlook Mobile Access OMA presents a simple text interface for accessing Exchange server−based e−mail, calendars, contacts, and tasks. As you'll see in the next section, 'Wireless Networking Clients,' the text on OMA screens includes URLs to make navigating around your Exchange mailbox fairly easy. OMA was designed for telephones with small screens and at least basic web browser capabilities. OMA can generate differently formatted output for different devices. It can provide screens formatted in WML, HTML, xHTML, and cHTML. This allows for very simple−looking screens or very fancy ones. Some phone vendors have worked with Microsoft to set up special page formats for their devices. However, any device that supports at least HTML can use OMA to access Exchange mailboxes. In the next section, I'll also show you OMA on a Dell Windows−based PDA. Implementing OMA By default, OMA is disabled. You enable it on the same dialog box that you use to configure EAS (see Figure 19.1, shown earlier). To make OMA available to your users, select Enable Outlook Mobile Access. If you want OMA to send pages to web−enabled devices that haven't been specially set up to receive OMA output, select Enable Unsupported Devices. As with other Exchange HTTP−based services−OWA and RCP over HTTP−OMA clients can access a mailbox's home server through front−end servers. They can use the same front−end servers as the other two services. You turn on OMA SSL security the same way you turn on OWA SSL security. See Chapter 18, 'Exchange Server System Security' for more information. Blackberry Enterprise Server The Blackberry Enterprise Server (BES) has gained great popularity for three reasons: It handles all aspects of wireless networking.• It takes a sensible approach to network bandwidth.• It has been doing everything that MIS and EAS do for about as long.• Exchange Server 2003 629 When you send a message from your Blackberry wireless device, it travels over the Mobitex or GPRS network to BES. BES then sends the message from your Exchange server, even putting a copy of the sent message into your Sent Items folder if you so requested in Outlook. Once the message is sent, it travels the Internet just as any other Exchange message. BES picks up incoming messages and sends them to your Blackberry via the Internet through a Blackberry−supported SMTP server. Mobitex or GPRS provides the final link between the Blackberry SMTP server and your Blackberry wireless device. Setting up your Blackberry PDA to use a wireless network is a total no−brainer, because the network provider does the setup. Basically you turn on your device and off you go. The Blackberry SMTP server treats 9 to 19kbps networks like the tiny pipes that they are. It doesn't try to send your Blackberry a 25KB message with a 50KB attachment all in one gulp. It sends 800 bytes. If you want to see more, you can ask for more. And you don't have to sit there watching your Blackberry device to make sure it doesn't lose contact with the outside world. The device recovers from network problems without forgetting what it was doing before its connection failed. About the time of the release of MIS, BES came out. Over the next couple of years, BES became more and more sophisticated. As of this writing, BES synchronizes Exchange server e−mail, calendars, and contacts in both directions. This is the same functionality provided by EAS. So why should you consider BES? First, it's a known product. Second, though it's a bear to install, once installed, it works flawlessly. Third, EAS is new to Exchange server. I expect it'll work just fine, but if you need a certifiably reliable wireless e−mail solution, you could do worse than to go with BES. Check out www.blackberry.com for more on BES. Note There is a desktop version of the Blackberry system for Outlook/Exchange. It works much like the desktop version of ActiveSync when you're connecting through Outlook and not directly to your Exchange server. I used this version before moving to BES. This version is not BES, though BES integrates with the desktop version beautifully once BES has been installed. Implementing BES I'm not going to walk you through all of the steps involved in implementing BES. Rather I'll talk a bit about a few quirks in product installation and give you some tips regarding various BES management tools. Once you've set up a user and given rights to the user and various Windows security groups, installing BES is very easy. The BES rights−granting process is truly grueling. This is partly because you have to grant rights to the same group to do different tasks (run BES as a service, monitor BES activities, manage a BES server). Some tasks require fewer privileges than others. Instead of creating a list indicating the most rights that you need to grant if your group will perform a particular set of tasks, the BES documentation lists the rights required task by task. As you work your way through the documentation, you could find yourself removing rights that you assigned to a group earlier. The result of all this is that BES won't work at all or it works but can't initiate certain functionality. The best advice I can give you when installing BES: Print out the documentation and follow it line by line using a ruler to keep your place. Actually installing BES is very straightforward. You can install it on an Exchange server or on another server. Be sure Outlook isn't installed on the server where you plan to install BES. Also, be sure that the correct Blackberry Enterprise Server 630 version of CDO.DLL is installed on the BES server before you do the installation. The BES documentation is very specific on these two requirements, both of which relate to CDO.DLL, the DLL that supports Exchange calendar access and, as such, is essential to BES calendar synchronization. Once BES is installed, managing it is very easy. Figure 19.4 shows the interface for managing a specific BES server. You're looking at the BESAlert page, where you can set up e−mail alerts to notify managers of problems on the server. Figure 19.4: Setting parameters for a range of BES functions using the Blackberry Server Properties dialog box You set up the equivalent of product ID and outgoing server contact information on the General page. Users can set up their own filters for which messages get sent to their Blackberry devices (only if I'm in the To field; if the message has this subject; and so on). You use the Global Filters page to set filters on the BES server that override any user filter settings. The E−Mail Options page lets you set a disclaimer message that is appended to each message sent through the BES server; send a copy of all messages sent from Blackberry handhelds to a specific address; support S/MIME encryption on the BES server; and allow a handheld to force e−mail reconciliation with the server. Finally, you use the Logging page to set up activity and error logging on the BES server. Monitoring user activity on a BES server is pretty simple. Figure 19.5 shows the Statistics dialog box for my Exchange mailbox. This is my real Blackberry setup. I've been using my Blackberry for almost three years. As you can see, a lot of messages−37,290−have been sent out to the PDA. The dialog box shows that all is well with my connection: Status, (EXCH011) Running and Pending to Handheld, 0. Blackberry Enterprise Server 631 Figure 19.5: Using the Blackberry User Statistics dialog box to check the status of a BES server's activities on behalf of a user There are other BES management interfaces that support such tasks as adding and removing users, sending test or informational messages to all users, checking server status, and disabling redirection of messages to a specific user's Blackberry handheld. Wireless Networking Clients I'm going to focus here on wireless clients supported directly by Exchange Server 2003 over TCP/ IP connections. These include Pocket Outlook with EAS• POP3 and IMAP4• OMA and OWA• I'm going to show you some of these clients in action and talk about what you need to do to make them work with Exchange Server 2003. Pocket Outlook with EAS Pocket Outlook runs on Pocket PC PDAs and Windows−enabled telephones. It includes Inbox, Calendar, Contacts, Tasks, and Notes from the MAPI Outlook/Exchange mailbox. Full synchronization with all of Pocket Outlook's folders is supported only by the desktop version of ActiveSync. As I noted earlier in this chapter, EAS supports only Inbox, Calendar, and Contacts. You can use ActiveSync to set up Pocket Outlook for EAS on your PC or PDA. Let's do it on a PDA, specifically, my Dell AXIM X5 with Pocket PC 2002 and a Symbol Wireless Networker 802.11b Compact Flash WLAN card installed. Open ActiveSync on your PDA (Start > ActiveSync). When ActiveSync opens, select Tools > Options and tab over to the Server page (see Figure 19.6). In this page, you can choose the folders you want to synchronize. Remember only the Inbox, Calendar, and Contacts can be synced. Click Settings to enter specific synchronization parameters for each of the folders. The server name should be a fully−qualified domain name registered in a public DNS if you're going to access EAS from the Internet. Wireless Networking Clients 632 Figure 19.6: Setting folder and server name parameters for EAS synchronization Note The PDA screens you see here are from my AXIM X5. They were displayed on my PC monitor using Microsoft's Remote Display Control v2.03 (www.microsoft.com/windowsmobile/resources/downloads/pocketpc/ powertoys.mspx). The screens were then captured using my regular screen−capturing software, Jasc Software's PaintShop Pro v8 (www.jasc.com). Next, click Advanced. You use the Connection page of the Advanced Connection Options dialog box, shown in Figure 19.7, to enter logon information for your Exchange server and set logging detail options. When you're done with the Server page, tab over to the Rules page. It's safest to leave the replacement rule set as it is in Figure 19.8. Wireless Networking Clients 633 Figure 19.7: Setting Exchange server logon information and selecting a level of logging for EAS synchronization Figure 19.8: Selecting a rule to be applied when there is a conflict between an Exchange server and Pocket Outlook during EAS synchronization Click OK to close the Advanced Connection Options dialog box and return to the main ActiveSync tools dialog box. Tab to the Schedule page (see Figure 19.9). This is where you set intervals for regular synchronization and specify whether you want your device to disconnect when synchronizing with your PC. The last option is not relevant for server−based synchronization. Wireless Networking Clients 634 Figure 19.9: Setting synchronization schedules When you're done with the Schedule page, click OK to return to the main ActiveSync window, shown in Figure 19.10. Any time you want to manually synchronize with your Exchange server, just open ActiveSync on your PDA and click the Sync icon. I can't show you how to set up EAS notifications that would trigger automatic PDA−Exchange 2003 synchronization, because that requires Windows Mobile 2003, which was not available at the time of this writing. Figure 19.10: The main ActiveSync page from which EAS synchronization is initiated Wireless Networking Clients 635 POP3 and IMAP4 If you have a POP3 and/or IMAP4 client on your PDA and a TCP/IP connection, you can access Exchange servers just as you would with the same clients available in such products as Outlook Express. When I'm on the road or even roaming around the office or the house, I use Pocket PC's IMAP4 client to stay in touch with e−mail. It's faster than ActiveSync because it syncs only e−mail and I can keep track of e−mail folders other than my Inbox as easily as with ActiveSync. Figure 19.11 shows my IMAP4 Inbox folder. I set up my IMAP on my PDA so that I can see other folders in my Exchange mailbox. To look in one of these folders, I simply click the Inbox icon with the little down− pointing arrow on it and pick the folder from a drop−down list. Figure 19.11: A Pocket PC IMAP4 mailbox wirelessly connected to an Exchange server I showed you how to set up POP3 and IMAP4 clients in Chapter 14, 'Managing Exchange 2003 Services for Internet Clients.' You should have no trouble applying that information to the Pocket PC versions of these two clients. One of the nice things about POP3 and IMAP4 is that their availability is not limited to Pocket PC devices. If you have a Palm PDA and a POP3 or IMAP4 client for it, you can do anything that a Pocket PC owner with the same clients can do. OMA and OWA In Figure 19.12, I've connected to my Exchange server mailbox using OMA. Dell hasn't created special support specs and web pages for my Dell AXIM PDA, so OMA starts up telling me that. However, because I set up OMA to handle unsupported devices, it will work just fine. So I'll just click OK. POP3 and IMAP4 636 Figure 19.12: The OMA warning screen appears when support for a particular client has not been set up by the client's manufacturer. And lo and behold, doesn't the home page in Figure 19.13 look just perfect for a telephone with a tiny graphics screen? Truth be told, it doesn't look so bad on my Dell PDA, even with its small graphics screen. Figure 19.13: The home page for an Exchange mailbox as displayed by OMA Let's look at my mail. After I tap Inbox on the home page, I'm transported to a view of my messages. In Figure 19.14, I've scrolled down because I want to open the message from Jane Dough. Before I do, notice the four URLs at the bottom of the screen. In this case, they let me do such tasks as move to the top of the list of my messages, compose a new message, see my other folders, and go back to the home page. OMA makes POP3 and IMAP4 637 very good use of in−context action URLs. Figure 19.14: The contents of an Exchange Inbox as displayed by OMA Okay, to open the message, I tap it with my stylus. And there it is in Figure 19.15. This is the message from Jane Dough with the graphical stack of currency that you might remember from Chapter 14 (Figure 14.19). No money, but the message is easy to read−and notice the in−context action URLs at the bottom of the message. Figure 19.15: Reading a message with OMA POP3 and IMAP4 638 [...]... on them There are two server products that support Exchange Server 2003 worth talking about One is Exchange 2003 itself with its new Exchange ActiveSync and Outlook Mobile Access options The other server option is Blackberry Enterprise Server with its proprietary client devices Both options synchronize Outlook /Exchange Inbox, Calendar, and Contacts folders Blackberry Enterprise Server offers no alternative... number of locations: • An Exchange Server organizational forms library • Your own personal forms library • Your own Outlook folders • Exchange Server public folders Exchange Server organizational forms libraries reside on an Exchange server and are available to all users by default Forms in your personal forms library are available only to you when you're logged in to your Exchange Server mailbox, as are... the Pocket Outlook Inbox, Calendar, and Contacts folders with the same folders on Exchange Server 2003 PDAs with POP3 or IMAP4 clients can also be used to access Exchange 2003 servers This includes both Pocket PC and other devices such as Palm PDAs Outlook Mobile Access provides a nice HTML−based interface to Exchange 2003 mailboxes for devices with small screens Some vendors have created customized... such as Microsoft Word or Excel is pasted or inserted as an object into an Exchange message The message becomes the application Exchange Application Programming Interfaces (APIs) APIs are used to develop custom−coded applications using Visual Basic, C++, J++, or any other compatible programming language Exchange Server 2003 file− and web−based data access Use file− and web−based access to Exchange. .. Basic scripting for Microsoft Office You might even want to buy Microsoft' s Visual Basic.NET Standard Edition It sells for less than $100 and is a good way to get started on VB as a language rather than just VB scripting 663 Summary Summary There are a number of ways to develop applications in the Exchange Server 2003 environment This includes using electronic forms, customized Exchange folders, OLE−based... create an organizational forms library on one of your Exchange Servers That means that you have to shift gears, go over to your Exchange Server, open your MMC, and go to the Exchange System Manager, your constant companion since way back in Chapter 8, 'Installing Exchange Server 2003. ' To create an organizational forms library, right−click your Public Folders container and select View System Folders from... form must be published in an Exchange Server organizational forms library Even a public folder won't do I'll show you why in a short while Creating an Organizational Forms Library So you're probably asking, 'Where's this Exchange Server organizational forms library thingie?' Right now, it's nowhere You must create an organizational forms library on one of your Exchange Servers That means that you have... folders, including the capability for replication and easy management of user access Well, folks, this is the last chapter of Mastering Exchange Server 2003 For me, researching and writing the book has been a lot of fun and relatively painless I hope that your experiences with Exchange Server are as positive and rewarding 664 ... drink controls This is the cyberworld equivalent of a nagging spouse Microsoft doesn't want you to forget to bind each control to an Exchange Server database field Until you do, the Properties dialog box always opens in the Value page Click New in the Value page This opens the New Field dialog box Type in a name for the new Exchange Server database field I like to use a combination of the form name and... features up and running in minutes As with any piece of technology−Outlook and Exchange Server included−your OFD watchwords should be plan, do, test, and have fun Where to Get Sample Forms and Help with Forms Development Exchange Server comes with a number of sample forms−based applications, and you can download more at Microsoft' s website These apps support such functions as customer tracking and . are two server products that support Exchange Server 2003 worth talking about. One is Exchange 2003 itself with its new Exchange ActiveSync and Outlook Mobile Access options. The other server. it on an Exchange server or on another server. Be sure Outlook isn't installed on the server where you plan to install BES. Also, be sure that the correct Blackberry Enterprise Server 630 version. long.• Exchange Server 2003 629 When you send a message from your Blackberry wireless device, it travels over the Mobitex or GPRS network to BES. BES then sends the message from your Exchange server,