ICal and Exchange Server

Does Apple's licensing of Active Sync lead to any speculation of better integration of Apple applications with Exchange Server on the desktop?
Right now running Leopard in a Exchange Server business world is not ideal in the least...
Has anyone speculated on this, or has anything of the sort come from Apple? Links would be greatly appreciated (if they exist)...

I am in a similar position.
Hopefully, the iCal Server will not slow down the adoption of better enterprise Exchange Server compatibility. I do not see my company switching from Exchange Server anytime soon.
What are your thoughts on actually using the iPhone as the mechanism to keep the two synchronized? For example, iPhone negotiates calendar and contact information via Active Sync with Exchange Server. You then cradle the iPhone to your desktop and it syncs with Address Book and iCal - now your data is everywhere it needs to be...
Seems clunky, but at least it would be something for Leopard users (who also own an iPhone) in the interim...

Similar Messages

  • ICal and Exchange Server 2003

    Hello from Barcelona,
    I am a new mac user trying to sync iCal with Exchange Server 2003. I have followed all instructions regarding domain, user name, password and URL address but it does not work. The last answer received was "account info not found" & "“HTTP/1.1 440 Login Timeout”. Incredible but when using the program AddressX (downloaded from internet) with the above mentioned configuration...it works and can get my company's global book address.
    Just to make sure I am following all "mac" rules. What I am using is:
    Domain/UserName
    Password
    https://company.com/exchange/User.Name
    Am I missing any important thing? Please help!!
    Thanks in advanced!!

    There are several discussions regarding this same topic on the Apple forums and elsewhere. None of them have solved the problem. This seems to be an issue that has been around for a long time but never addressed by Apple or Microsoft. From some simple tests that I have done, it appears the the Microsoft Exchange Server is not interpreting the iCal event (.ics extension) properly. I have seen discussions saying that Apple is not formatting the event properly or is using a newer standard that MS Exchange does not support. I believe it is the later as I can make the event work properly without any software changes but I have to do some steps manually. Here is how I can make it work and why I believe something is wrong in MS Exchange:
    - create event in iCal and add an Outlook user
    - send the event/email (ignore this email on the PC as it does not work)
    - open the just sent email and save the attached iCal event
    - find the saved iCal event and add a letter to the extension such as ".icss"
    - (Note: I don't know if there is a way to rename an attachment already in a message)
    - attach this renamed event to a new message and send it to the Outlook user
    - the Outlook user must open the message, save the attachment and rename it back to ".ics"
    - double clicking / opening this renamed file now works perfectly in Outlook
    Now, if I could only automate some of these steps on the Mac before I send the message would be very helpful. This is not a great solution but I use it for events that I want to sync between my home Mac and my office PC.
    Because the renamed attachment (.icss) works through Exchange (by ignoring it), I am lead to believe that MS Exchange will interpret an ".ics" extension and mess up the handling of it for some reason. Microsoft is never one to follow standards very carefully or adopt them very quickly. Our company is using Exchange 2003 so maybe that is part of the problem as it is an older version.

  • Deploying Windows Server 2012 and Exchange Server 2013

    Hi All,
    Our Clinet is planning to implement Exchange Server 2013 as an email solution. There is no Active Directory Domain exists in the environment. So, we have planned to configure a Windows Server 2012 R2 Standard as a Domain Controller and Exchange
    Server 2013 Standard would be installed on another Windows Server 2012 R2 Standard.
    The setup would be for 250 users. Please guide me about the Cost of OS + Exchnage and CAL for 250 Users.
    Warm Regards,
    Prosenjit Sen
    Thanks & Regards, Prosenjit Sen.

    Another option would be to consider signing up for Office 365 instead of setting up the hardware and software for such a small number of users.  It will take a long time for the cost of the hardware, maintenance, and support to be less costly than Office
    365, if it would ever be less expensive.  There is a lot of maintenance required for Exchange, so unless your client already has someone experienced in configuring and maintaining Exchange, there is a lot of expense in bringing someone up to speed to
    perform those functions capably.
    Just a suggestion.  I do not work for Microsoft and I have no financial incentive to propose an Office 365 environment.  I just know that if I were running my own business, I would have to be convinced that my business required its own internal
    mail system when there are so many fully functional and capable mail systems available via subscription.
    . : | : . : | : . tim

  • Upgrading from SBS 2008 and Exchange Server 2007 and Adding Modest Failover Protection

    I haven't seen anyone describe this scenario, so maybe it can't be done, but it seems it should work. Can someone either confirm this is viable or set me straight and tell me it's not wise (and if not, why not).
    I currently have SBS 2008 (2008 Server + Exchange Server 2007 + some other components). I use redirected folders so all my user data is stored primarily on the server, and then sync'd with their local harddrives for roaming use and as an additional
    backup precaution. I want to upgrade to a modern version of Exchange (don't care too much about the underlying server OS, but seems like a good time to upgrade everything). I also want to improve the reliability for rapid recovery in the event of a system
    failure. I have always felt nervous with SBS because it only runs on a single server.
    My plan is:
    Install Windows Server 2012 Standard on a new server machine
    Join that new server to the existing SBS domain and sync the users, etc.
    Install Exchange Server 2013 on the new 2012 Server
    Migrate the existing Exchange data and account info to the new server
    Demote the SBS Server and promote the new server to primary DC
    Reformat the old SBS server and install Windows Server 2012 on it too, and join it to the domain as a second DC
    Set up DFS Replication and keep all my user data folders between the two servers (so if one server fails, the other can take over, just not automatically like with a cluster)
    Install Exchange Server 2013 on the reformatted 2012 Server box (so second instance on the domain) and set it up to sync with the first Exchange Server 2013 via DAG (so if either computer crashes, the other can take over for both Exchange Server and file
    services)
    Wouldn't that give me a complete slow-response failover system without the need for setting up a cluster (I know a cluster would provide instant failover protection, but I don't need that kind of speed - a manual switchover in the rare event of a server
    failure is acceptable for us)? I could do this using cheap hardware for each server, because unless both servers fail at the same time, clients can point to the other server. And because it's not a formal cluster, I don't need to buy anything for a shared
    SAN. This seems like such an obvious more cost-effective solution for a small network, I don't understand why this isn't a common approach, which makes me wonder if there is some reason it won't work.
    Any suggestions or feedback? Are Redirected Folders still recommended for users on a Server 2012-based domain?
    Thanks,
    Colin
    Colin

    Ed, thanks again for your help. OK, so here's my updated plan (I realize I should probably check on some of these pieces on the Server group, instead of this Exchange group).
    Constraints/objectives:
    None of the machines are truly server grade hardware, but only 5 people on the network, so performance is generally not an issue, unless a given server is just pegged on CPU or HD due to its own internal maintenance tasks and can't respond to user requests.
    Haven't seen any problems, since upgrading server from 4GB RAM to 8GB a few years ago.
    Not going to buy any new hardware at this time, but do have several unused consumer-grade computers I can deploy as wimpy or moderate servers.
    Main issue is to limit repair time in the event of a system failure (instant failover is not required, but want to be able to restore network functions within less than 24 hours in the event of a hardware failure) and minimize time spent on IT
    maintenance.
    Because of light IT maintenance (not anyone's primary job and we're too small to justify a dedicated IT person or to pay for outside help), almost every touch takes me research and time to re-learn what I haven't done in weeks, months, or years -- so also
    want to keep all IT tasks as simple as possible.
    We philosophically want to invest now for the next 5 years and avoid ongoing cloud fees (so zero interest in Windows Server Essentials with Exchange Online)
    A little nervous about using VM's, just because I never have before, but I do respect that's probably the right way to do many of these things...
    Currently I have SBS 2008 (Windows Server 2008 R2, Exchange Server 2007, WSUS 3, all with latest SP's, also includes SharePoint and other stuff, but I don't really care about most of it) on a single 8GB consumer grade system, which functions as a file
    server and Exchange server. We use Redirected Folders and Offline files for all users, which works great for us and provides additional file redundancy (if server goes down, all of each user's files are also on their own machine and they can even continue
    to work just fine w/o the server, losing only ability to send and receive e-mail). It has been sufficient, but I want to upgrade our version of Exchange and I am nervous that if that current one server fails, it would take me a long time to restore everything
    from backup, easily many days, especially if I need to buy any replacement hardware. It is RAID1, so a single drive failure is easy to handle, but that's the only hardware redundancy for the current server.
    New Plan:
    Install Windows Server 2012 R2 Standard on a new modest machine (16GBR RAM, Core i7, 1TB RAID1 (may upgrade to 3 or 4 TB), 256 GB SSD boot drive, this had been my old personal computer)
    Join that new server to the existing SBS domain (2008 R2/Exchange 2007), make it a DC, sync the users, etc.
    Install Windows Server 2012 R2 Standard on a wimpy computer (4GB RAM Core i3 processor), leave it as a member server
    Install Exchange Server 2013 on the wimpy new 2012 R2 Server (and nothing else, this will be dedicated to Exchange to make the most of such a wimpy machine)
    Migrate the existing Exchange data from the old SBS Exchange 2007 server and account info to the new server
    (or should I just create new accounts and copy the data from the user end through Outlook -- is that safer and cleaner than attempting any kind of server-level Exchange data migration?)
    Demote the old SBS Server and promote the new 16GB server to primary DC. Now it's OK to take the old SBS server off the network.
    Reformat the old SBS server and install Windows Server 2012 R2 on it too, and join it to the domain as a second DC (and possibly DCPROMO it to be the main server)
    Install Exchange Server 2013 in a VM on the reformatted 2012 R2 Server box (so second instance on the domain for Exchange redundancy) and set it up to sync with the first Exchange Server 2013 via DAG OR set up another physical wimpy member server and install
    it there. In any case, do NOT install Exchange directly on either DC.
    Set up DFS Replication or a Failover Cluster (still need to research this, but I had planned on DFS, thinking Cluster required shared drive, but Ed corrected me on this) between the two DC's for redirected files and keep all my user data folders between
    the two servers. We don't need automatic failover, like with a cluster, a manual switch would be acceptable, but if no additional cost or risk to clustering the two DC's, then the auto-failover protection that provides would be better than DFS.
    I think this incorporates all of your points, Ed. Does this sound right now? What's your advice on #5 (how to best migrate user data)?
    Thanks so much for all your help,
    Colin

  • I need my home calendar to sync with both a google cal and exchange server. What is the best way?

    I need my home calendar to sync with both a google cal and exchange server. What is the best way?

    use the same google mail addy for the razr you use for the calander
    also make sure that when you put it in the phone it is a google event and not a phone event

  • VLAN and Exchange server

    Hi everyone,
    We need help on the configuration of our Exchange server and VLAN.
    Since I'm a beginner in VLAN configurations.
    We are using Cisco SG300 switch and Exchange server.
    We have 2 NICs on our server, with 1 having a static Public(internet) IP for internet which is directly connected to our ISP modem(complete with IP Address, Subnet Mask, Default Gateway and DNS), the other NIC has a static Local(intranet) IP for local network(with IP Address and Subnet Mask only).
    Our Problem is we cannot add an Default Gateway on the 2nd NIC(intranet) because it says conflict with the gateway specified on the other NIC.
    We want to add a Default Gateway on the 2nd NIC(intranet) to be become accessible from other VLANs.
    How can the server be accessible to other different VLANs on our network?
    What will be the best approach on this?
    Thanks in advance.
    J

    You should add routes to your windows routing table.
    So if your server is in VLAN 10.10.10.0/24 and has the IP of 10.10.10.2 and your router is 10.10.10.1 then you can add routes to all your VLANs by adding the networks and routing them through 10.10.10.1.
    For example, in your command prompt on Windows you would type:
    route -p ADD 10.10.11.0 MASK 255.255.255.0 10.10.10.1
    route -p ADD 10.10.12.0 MASK 255.255.255.0 10.10.10.1
    route -p ADD 10.10.13.0 MASK 255.255.255.0 10.10.10.1
    That would make your computer access all the internal VLANs as well as make it reachable from those VLANs.

  • What is available on new Windows servers that allow you to write scripts that can work directly with Windows, SQL Server, and Exchange Server?

    What is available on new Windows servers that allow you to write scripts that can work directly with Windows, SQL Server, and Exchange Server?
    a. PowerShell
    b. isql
    c. osql
    d. sqlcmd

    All questions seem to be from the interview or a test. I think I even took this test once, it's KForce test.
    For every expert, there is an equal and opposite expert. - Becker's Law
    My blog
    My TechNet articles

  • ICal and Exchange Errors

    Hi everyone.  I'm new to Mac but experienced with iPhone and iPad.  I have a brand new iMac running Lion with all the latest updates.  I have my corporate Exchange account configured just like I do with my iOS 5 iPhone and iPad.  On the Mac, Address Book and Mail work fine.  iCal however is having some issues. 
    I have two calendars on my Exchange account, my main one "Calendar" and another one "Team Calendar".  When I fire up iCal it just says "Updating..." for a long time.  Clicking on "Calendars" I see both of my calendars listed.  This is what happens on my iOS devices.  However, only events from "Team Calendar" show in iCal.  Nothing from "Calendar" shows.  Not a single event.  "Team Calendar" is very simple with basic events (not meetings with attendees).  My main "Calendar" has tons of repeating events, meetings with attendees, events that I've yet to respond to, etc.  I'm suspecting something is tripping up iCal.  Like I said, works fine on iPhone and Pad.
    I saw some posts in this community to delete ~/Library/Calendars/Calendar Cache    I did that but it didn't fix the problem.  And like I said, this is a brand new Lion install and this is the first time I've used iCal.  My company runs Exchange 2007 from what I understand.  I checked Console and found this:
    3/1/12 7:40:54.089 PM iCal: Could not find Meta Data for persistent Store
    3/1/12 7:43:02.150 PM iCal: Unexpected type EWSMeetingResponseMessageType for calendar Calendar in account Pega
    Any ideas?
    Thanks.
    Adam

    With 10.7 I could not see either of the mentioned cache files to delete them - which puzzled me (I did not have to unhide Libaries, and I could see other cache entries, so pretty sure it wasn't just hidden?!)
    I changed the port to 443 with SSL on and this allowed the Delegates tab to populate, and could even resolve a name of one of the exchange server users - so I know the connection is good. (And contacts and email are synching to the same work server). And like abfield, the iPhone and iPad sync the calendar perfectly both ways.
    My errors are
    25/06/14 12:38:04.233 PM iCal:  error = Error Domain=CalExchangeErrorDomain Code=-11 "iCal can’t refresh events in the calendar “Calendar”." UserInfo=0x7fcf4cb9af90 {CalFailedOperationKey=<CalExchangeSyncFolderItemsOperation: 0x7fcf3a978fd0>, NSLocalizedDescription=iCal can’t refresh events in the calendar “Calendar”., NSLocalizedFailureReason=The account "work" currently can’t be refreshed.}
    25/06/14 12:37:36.462 PM iCal: Unexpected type EWSMessageType for calendar Calendar in account work
    Apple phone support were apologetic but basically said that connections to Exchange Server were too hard as there were too many settings. Duh.
    Reading others' posts it appears that if a user has Outlook 2013, that there are now some incompatible Status options that can be set for appointments.
    This is similar to the issue in this thread but also an issue reported here https://discussions.apple.com/message/22514700
    I have copied the content here:
    Checked out the Console logs and it throws these three errors below.  There is something with the "LegacyFreeBusyStatus" that is causing the sync to fail.  Outlook 2013 has a new status of "working somewhere else".  I had used it for a few items.  I also found an item that had a Null status (like what it is pointing to in the error).  Removed that item and changed all the others to a valid stauts for previous versions of outlook.  ie. Free, Busy, etc.
    2/12/13 3:29:32.871 PM CalendarAgent[19447]: [com.apple.calendar.store.log.exchange.queue] [-[CalOperationQueue executeOperations] :: [<EWSCalendarItemType 0x7f9dfac9e9b0> setNilValueForKey]: could not set nil as the value for the key LegacyFreeBusyStatus.]
    This all suggests that one or more of my appointments has a status that iCal can't cope with.
    Is there a way to narrow down which these are and to blanket change them in Outlook 2013?

  • Updated to 10.6.3, can no longer sync iCal with Exchange Server

    My syncing with our exchange server used to work fine. I updated my 3 Macs and now they all have the same issue. They will not sync with the server and they all show 4 notifications that have not yet been responded to. When I view the notifications, they are all for old entries. I accept all 4, but doesn't seem to work - still shows iCal offline. Anyone else having this issue? Any suggestions? I tried removing the calendars cache file and plist files.

    I spent an hour on the phone with Apple today, got elevated to an engineer AND talked to a Server Guy at my University.
    The cause is still unclear, but the remedy has become painfully clear. To have a working copy of iCal, Mail, and AddressBook, one needs to remove all three accounts from the three client apps, and restart from Mail. This approach is the only way to preserve correct links among the three client apps.
    I got iCal working temporarily by deleting my Exchange account and rebuilding it. The problem is that by rebuilding an iCal account, it created duplicate accounts in Mail and AddressBook. Also, the Apple apps autodiscovered slightly different server names, which caused problems sending me and I was getting duplicate email messages as well as contacts and calendar events. I deleted the redundant mail and contact accounts, but continued to have problems with sending mail and I lost my ToDos in Mail. So, I bit the bullet and have blitzed all my exchange accounts on my MBP and am waiting for it to repopulate the 5+ GB of data. Then tomorrow, I will do the same on my iMac.
    Sheesh!

  • MacBook Pro, Snow Leopard and Exchange Server

    My wife is considering a MacBook Pro for her business (we have one at home). At her work they have Exchange Server. With our home MacBook Pro I have been able to connect to her Exchange server through Entourage. (however I think her Exchange server is version 4 and not 7). Anyway, we are getting mail, contacts and her calendar through Exchange but we are not getting shared calendars and I don't know how to access her files on the Exchange server. I really want her to buy a MacBook but we need to make sure that shared calendars and file sharing works. Can someone inform me about this?
    Her company is upgrading to Exchange server 7 in December and I know that Snow Leopard allows Exchange to work through Mail, Address Book and iCal. Again, I need to know if calendar sharing and file sharing can work. Thanks.

    Hello,
    Wondering if you had any luck getting this issue resolved (I have the exact same question).
    Thanks,
    -Todd / Chicago

  • ICal and Exchange 2010

    I have a user whos iCal is not syncing with Exchange 2010. When creating a new event, it gives the message "iCal can't save the event "xxxx" to the Exchange server. The account "xxxx" currently can't be modified. To discard your changes and continue using the version of your calendars that's on the server, click Revert to Server. To save your changes on your computer until the problem is resolved, click Go Offline."
    The user is on a 2011 13" Macbook Air, 1.86 GHz Core 2 Duo. Snow Leopard 10.6.7, iCal 4.0.4. Mail and Address Book sync fine. The calendar works fine from the users iPhone, Outlook Web Access, and Outlook 2011 on the computer.
    I have tried deleting the account, deleting all caches, and recreating it, but it still doesn't work. I made sure Tasks weren't the problem, and checked time zone support as well.
    I set up the exchange account on my Macbook and it works fine, no problems syncing over wired or wireless connections. Macbook is also on 10.6.7, iCal 4.0.4. So I was thinking it was a user account issue. I created a new account on the Macbook Air, set up the exchange account in iCal, and I get the same problem as on the original account, no syncing.. I have everything set up exactly the same as on my Macbook, but the Macbook Air refuses to sync. This error only appears when an event created on the Macbook Air is in the calendar. It pulls events from the server fine, but once an event is created it refuses to cooperate.
    Do Macbook Airs just not play nice with Exchange?

    It's a time zone issue. checkhttps://discussions.apple.com/message/10108361#10108361

  • ICal and exchange 2007 in 10.6

    Mail.app and Addressbook.app work perfectly fine. I set up all my exchange information in the Mail.app preferences just like i was told to. iCal comes back with an error message saying that my email address isn't valid. It is. I am using exchange 07 with auto discovery on.
    here is my server info.
    Mailbox owner: Bradley Maskell [[email protected]]
    User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6; en-us) AppleWebKit/531.9 (KHTML, like Gecko) Version/4.0.3 Safari/531.9
    Outlook Web Access experience: Basic
    User language: English (United States)
    User time zone: (GMT-05:00) Eastern Time (US & Canada)
    Exchange mailbox address: /o=ALOL/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=B.Maskell
    Outlook Web Access host address: http://win.alol.net.br/owa
    Outlook Web Access version: 8.1.393.1
    Outlook Web Access host name: win.alol.net.br
    Client Access server name: WIN.alol.net.br
    Exchange Client Access server .NET Framework version: 2.0.50727.4016
    Client Access server operating system version: Microsoft Windows NT 6.0.6002 Service Pack 2
    Client Access server operating system language: en-US
    Microsoft Exchange Client Access server version: 8.1.240.0
    Client Access server language: en-US
    Client Access server time zone: E. South America Standard Time
    Microsoft Exchange Client Access server platform: 64bit
    Mailbox server name: WIN.alol.net.br
    Mailbox server Microsoft Exchange version: 8.1.240.0
    Other Microsoft Exchange server roles currently installed on the Client Access server: Mailbox, Hub Transport
    Authentication type associated with this Outlook Web Access session: Basic
    Public logon: Yes

    I'm seeing pretty much the same thing...
    Mail.app and Contacts are working perfectly. iCal, on the other hand, is only half working. I can accept invitations from my Exchange account no problem, but cannot send invites once created.
    The error messages are random (like n748 is seeing)... sometimes it says the user/pass are wrong, other times it says "iCal cant save the event to the Exchange server".
    Exchange server is 2007 with auto discovery.
    I hope someone can help shed some light on this. I'd like to completely remove the train wreck that is Entourage from my system

  • SBS Server 2003 and Exchange Server - need to access but only have HDD

    Hi,
    I have been redirected here from a Microsoft Community Forum. I am reasonably conversant with windows systems but am not a computer professional, just trying to see if I can solve a problem without spending a great deal of cash at this stage as
    our office has been completely flooded out and we are still struggling to regroup....Here is the original question.
    A couple of years ago our sever died completely, we kept the HDD's, but unfortunately not the CD's with the software on or the software keys. So I have now 2HDD's, the original boot partition and one with data on. both clean and fully working and
    connected now to an old desktop. I can see everything fine, but I cannot boot from the original boot drive (I have tried simply disconnecting the desktop's boot drive and the windows logo shows for 1 second an d then chucks me back to the initial (DOS?) load.
    The point is that I need to boot into SBS2003 with the exchange server installed in order to access a handful of old emails which have become extremely important, and also to run an old version of Filemaker server which will not run on any newer O.S.
    I have tried, incidentally, a converter for the exchange files and I can see the directories but I think that unless I pay $xxx for something, which I cannot afford now, then I will not get the emails and all attachments back.
    So my question is this - is there anyway I can use the original boot disk in a new hardware environment to restore both sbs 200 and exchange to working condition? I have paid vast sums for both so I do feel that I should be able to use them still!
    Many thanks
    Gor

    Hello
    tip:
    get one pc with hyper-v or VMware. with enough memory.
    install 2003 OS with sp2
    run dcpromo  add same domain name wich is old.
    install exchange 2003  /with same ORG name / and install exch 2003 sp2
    open exch console and Enabling the database to be overwritten on mailbox database
    dismount database, rename database, and copy old database to new and mont database
    run clean mailbox
    create new user without mailbox.
    select disconect mailbox and connect to new user.
    sorry my english

  • Address Book and Exchange Server - NO NOTES SYNCING???

    I have my address book syncing very nicely with my exchange server, but notes do not seem to want to sync. If I create a note on the web access, it doesn't copy to the address book, and none of the address book notes copy to the exchange.
    I can't get an answer out of Apple Support either if they are supposed to sync or not! Has anyone here gotten notes to sync with exchange?
    Thanks so much. I have searched for over 4 hours on Google and these boards, and noone even mentions notes, leaving me to believe that they SHOULD sync.

    Arrgggh! That's a bummer, they could just strip out the notes if they had attachments or something.. or give an error. I have no attachments, and notes are extremely important to me.
    Oh well.. there goes my ability to do away with Entourage!

  • Mail.app and Exchange Server Problems?

    I am an Apple Mail user and my university just switched to an Exchange Server 2003 for student e-mail. The university is only supporting Entourage, but I have configured Mail to work with Exchange without any major problem. This week, I have noticed that I have a problem where Mail.app will say that I have four new e-mails in my Exchange in-box. When I click on my Exchange in-box, no new e-mail appears. After experiencing this problem for about a week, I finally logged onto our Exchange web access site for the university. I discovered that I did indeed have four new e-mails in my in-box, but these e-mails were not showing up in Mail.app. Interestingly, all of the e-mails were undeliverable e-mails that had popped back because I had the wrong address. I am wondering why these e-mails would show up in on web access, but not show up in Mail.app.
    I have spoken with our university tech. support numerous times and they have been unable to figure out the problem. It seems this may be a Mail.app isse as opposed to an Exchange problem.
    Thanks,
    Joe Biedlingmaier

    I use Exchange at work and have 5 Macs working with it w/o problems. The trick is to correctly specify SMPT and Outlook Web Access Server.
    Do the following:
    When you create a new mail account, choose IMAP or Exchange (if it shows on the list)
    for Email Address specify your exchange email address
    continue
    for Incoming Mail Server: use name of the server without any prefixes such as mail. (The example shown under the box is wrong. It took me forever to figure it out)
    for username and password use the same one you use when log in into exchange webmail
    continue
    for outgoing email server use the name of the server, again without smtp.
    you may need to use authentification in order to send mail. In that case use the same user and password as when you log into your exchange
    I was doing it as I was writing this to make sure it workes. It does.

Maybe you are looking for