Help: <http://www.lists.apple.com/evangelist.html> or <evangelist-info@public.lists.apple.com> ===========================================================================
Date: Fri, 29 May 1998 02:06:55 -0800 From: John Halbig <john@garage.com> Subject: Followup - Exchange-Schedule+ on Mac
This follow-up message is from:
<Dick@ix.netcom.com>
Thanks very much for your replies and information about Mac support for MS Exchange and Schedule +. I received nearly 150 responses from all over the world. The response was really quite overwhelming.
I used every bit of the information and together we 'saved' the Macs at Intermec Technologies. The Mac users are glad to not have PeeCees. The Exchange group doing the rollout don't like me much, but I who cares. I'm using the Exchange 5.0 client very successfully on my PB3400, both at the office and remotely from home. It actually works pretty slick, if you are used to the Windoze interface.
Here is a summary of the answers I received.
1) Can Mac users publish their schedules so that Windoze users can view them also?
Definitely. I've used this feature myself. The only caveat from the responses is when Outlook (not Outlook Express) starts to be deployed. The Windoze version of Outlook uses a different file format for the calendar that is only partially compatible with the Mac version. (The Mac version of Schedule+ and Outlook uses the older .scd type files)
2) Are there any kind of hardware or software considerations?
Works on both PPC and 68K Macs. Use the highest version of OT available. MacOS 7.5.3 to 8.x all work well. The faster the processor the better. (It may be me but the Mac client feels faster on my PB3400 than on a Wintel 233 MMX laptop I use at work!!!)
The RAM footprint is 10-12MB without virtual memory, and 4-5Mb with virtual memory. The application requires about 20Mb of disk with 5Mb for each profile configured.
3) Are there any network considerations?
Either TCP/IP or AppleTalk will work to connect to the Exchange server. If AppleTalk is used then Services for Macintosh must be turned on at the Exchange server. A hosts file is required if access to public folders is desired. An NT domain account is required. And, Services for Macintosh must be running on the Primary Domain Controller for Mac users to be able to change their Exchange password.
4) Is Thursby's DAVE product required?
No. DAVE is only needed to have NT file and print services when Services for Macintosh is not executing on the NT server.
5) Anything else...
Lots of interface concerns were expressed.
Dial up connections work well. I've used this quite a bit.
There are bugs and crashes when trying to use color text in your own message. Drag and drop doesn't when trying to add enclosures; you must use the Insert menu. You are unable to view/send forms, if your company is using forms.
Several large installations of Macs (1,000s) are successfully using the client.
Exchange 5.0 uses an Exchange client and Schedule+. Exchange 5.5 uses and Outlook client, which only changes the UI and not the Schedule+ file format. Outlook Web Access works with the Mac but the Exchange Server must run additional processes. Outlook Express (comes with IE 4.x and Office98) is e-mail only. (I have not tried to connect Outlook Express to our Exchange server but it can be done if Exchange is configured for POP e-mail.)
The URL to download the Exchange client is:
<ftp://198.105.232.1//bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Sp 2/Mac/SP2_50MA.hqx> (You can also use www.softwatcher.com to check on the latest URL)
The MS Knowledgebase keyword is: XMAC for information about the Mac Exchange client.
Thanks again for all of your support. All of you really came through for me and I appreciate it very much.
Converting personal address books from MS Mail for Mac is a pain. (Thomas Berens, <berens@ari2.com> has a workaround if interested.)
Frederick L. Dick Designer/Analyst IV Intermec Technologies
------------------------------
End of EvangeList Digest V1 #1199 *********************************
