Category: 3rd Party Software
Link: Microsoft's Entourage now has an update to allow it work with MS's own Exchange Server.
Posted on MacBytes.com
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Microsoft's Entourage now has an update to allow it work wi...
- Thread starter MacBytes
- Start date
- Sort by reaction score
Category: 3rd Party Software
Link: Microsoft's Entourage now has an update to allow it work with MS's own Exchange Server.
Posted on MacBytes.com
I thought this sounded pretty fishy, considering Panther will support Exchange too. Is Microsloth trying to downplay Panther with this update? Or is it just coincidence?
MS said this was comming long before people knew Panther would support it. Besides, from one of the screen shots from Panther, I suspect that it's Exchange support will use Exchange's web access on the back end - not a direct connection to the Exchange server. (Then again, maybe that's what MS is doing too!)
In case that didn't make sense:
Windows and Mac OS 9 users:
MS Office connects directly to MS Exchange server.
Web access version (like what Snerdware's AddressX app does):
Application connects to http(s) Exchange web server. Web serves up html mail box, application "screen scrapes" responses and provides a pop/imap interface to Mail. (Now, MS may be providing an XML interface on that http(s) port but I doubt it.
In case that didn't make sense:
Windows and Mac OS 9 users:
MS Office connects directly to MS Exchange server.
Web access version (like what Snerdware's AddressX app does):
Application connects to http(s) Exchange web server. Web serves up html mail box, application "screen scrapes" responses and provides a pop/imap interface to Mail. (Now, MS may be providing an XML interface on that http(s) port but I doubt it.
Just installed it - account wizard didn't find our Exchange server so I tried manual config. Still getting problems... 
My own issues
So, here's what I'm seeing so far:
1. If I type in the domain name and all the other good bits I put into the MS Outlook for OS 9 client - it doesn't connect.
2. So, I click "manual setup". It asks for the Exchange server address - I give it. It <i>then</i> tells me it needs an SMTP server address.
Uh-oh. See, I work at a security place (*please* don't ask why we use Exchange - it was *not* my idea) and we've pretty much disabled SMTP for everything so that, in theory, we won't get spam mail bombed and such.
So I put one in anyway, knowing the SMTP part won't work. And then it gives me the error that I saw coming a mile away:
IMAP folder error, blah, blah, blah.
See, it *looks* like to me that this isn't a 100% "hey, kids - let's talk to an Exchange server all nice and happy in the native way!". It's the "So - you Mac jackasses felt like you needed Keynote, huh? Well, here's your prescious Exchange support - we'll hook up the Calender and crap, but if you think we were going to use anything other than a basic auto-configured IMAP and SMTP service system - you were wrong! Bwahaha! Bwahahahahaha!"
I'm sure I'm wrong on some levels, but I am very dissapointed in this so-called Exchange Server compatibility. My old crappy Outlook for OS 9 works fine enough - so how hard would it have been to get Entourage to really, truly integrate with Exchange?
So - fine. I'll wait for Panther (it's version of Mail is suppose to be Exchange compatible - maybe I'll give it a shot) and push the company to use some other mail server in the future. (Anybody know if Lotus Domino has a Mac client? And no - not a web one, I can't stand those things.)
Oh - and now that Novell has bought Evolution, let me say one thing: Mac OS X port, you Utah assmunches. (I lived there for 10 years - I've earned the right to say that.)
So, here's what I'm seeing so far:
1. If I type in the domain name and all the other good bits I put into the MS Outlook for OS 9 client - it doesn't connect.
2. So, I click "manual setup". It asks for the Exchange server address - I give it. It <i>then</i> tells me it needs an SMTP server address.
Uh-oh. See, I work at a security place (*please* don't ask why we use Exchange - it was *not* my idea) and we've pretty much disabled SMTP for everything so that, in theory, we won't get spam mail bombed and such.
So I put one in anyway, knowing the SMTP part won't work. And then it gives me the error that I saw coming a mile away:
IMAP folder error, blah, blah, blah.
See, it *looks* like to me that this isn't a 100% "hey, kids - let's talk to an Exchange server all nice and happy in the native way!". It's the "So - you Mac jackasses felt like you needed Keynote, huh? Well, here's your prescious Exchange support - we'll hook up the Calender and crap, but if you think we were going to use anything other than a basic auto-configured IMAP and SMTP service system - you were wrong! Bwahaha! Bwahahahahaha!"
I'm sure I'm wrong on some levels, but I am very dissapointed in this so-called Exchange Server compatibility. My old crappy Outlook for OS 9 works fine enough - so how hard would it have been to get Entourage to really, truly integrate with Exchange?
So - fine. I'll wait for Panther (it's version of Mail is suppose to be Exchange compatible - maybe I'll give it a shot) and push the company to use some other mail server in the future. (Anybody know if Lotus Domino has a Mac client? And no - not a web one, I can't stand those things.)
Oh - and now that Novell has bought Evolution, let me say one thing: Mac OS X port, you Utah assmunches. (I lived there for 10 years - I've earned the right to say that.)
We waited for THIS?????
This is just a lame lame update. If I was interested in using IMAP with Exchange I would stick with Mail.
This is just another pathetic atempt to calm the Mac user contingent. There's five minutes I'll never get back thanks to MS.
This is just a lame lame update. If I was interested in using IMAP with Exchange I would stick with Mail.
This is just another pathetic atempt to calm the Mac user contingent. There's five minutes I'll never get back thanks to MS.
Not true exchange
What we needed:
the ability for an adminstrative assistant to open and view the manager's schedule.
What we got:
I could do everthing that this update provides already. It is time to look into a different solution for our enterprise scheduling software.
neilt
What we needed:
the ability for an adminstrative assistant to open and view the manager's schedule.
What we got:
I could do everthing that this update provides already. It is time to look into a different solution for our enterprise scheduling software.
neilt
Hi JohnHummel
I can tell your for a fact that you're not going to like Domino - their Notes client for Mac OS X sucks even more than their Notes for Windows client.
For reasons I won't go into, I have to use both Notes and Exchange. Exchange with Outlook on Windows is great. I was looking forward to something similar on Mac OS X - it doesn't appear to be the case.
I'm having the same problem with Entourage not seeing our exchange server, even though it has service pack 3.
Hmm.
I can tell your for a fact that you're not going to like Domino - their Notes client for Mac OS X sucks even more than their Notes for Windows client.
For reasons I won't go into, I have to use both Notes and Exchange. Exchange with Outlook on Windows is great. I was looking forward to something similar on Mac OS X - it doesn't appear to be the case.
I'm having the same problem with Entourage not seeing our exchange server, even though it has service pack 3.
Hmm.
This really sucks. Just installed it, and configured and it's working fine, however, it's nothing different than the IMAP access as before. I was really hoping that I would have Tasks and Notes synchronizing up to the server and REAL exchange interaction. Having the Calendar synch up is the only real addition here.
Re: Not true exchange
What infuriates me the most is that MS proclaimed a "full Excahnge Solution" was coming way back in February. I told my fellow staff to be patient - soon our problems would be solved. And what did Microsoft deliver? - nothing!!! I could have spent the last few months researching a real solution!
What infuriates me the most is that MS proclaimed a "full Excahnge Solution" was coming way back in February. I told my fellow staff to be patient - soon our problems would be solved. And what did Microsoft deliver? - nothing!!! I could have spent the last few months researching a real solution!
Will not even INSTALL!
What the heck? I have never moved the Office X folder from my Apps folder and this is what I get:
What a useless "update." As you can see, the Office X folder is in my Apps folder. What the hell have the engineers at the Mac BU doing all these months?!!!
What the heck? I have never moved the Office X folder from my Apps folder and this is what I get:
What a useless "update." As you can see, the Office X folder is in my Apps folder. What the hell have the engineers at the Mac BU doing all these months?!!!
Re: Re: My JPG did not attach:
Yes, I do. I have installed the previous updates they have made available. I really have no use for Exchange (and if I do in the future I will use Panther's Mail) but I was hoping they had fixed crash-happy MS Word. Oh well.
Yes, I do. I have installed the previous updates they have made available. I really have no use for Exchange (and if I do in the future I will use Panther's Mail) but I was hoping they had fixed crash-happy MS Word. Oh well.
I could not get the update to install either: cannot find the application folder. Maybe because I've renamed Macintosh HD?
I checked to see what they did to update Word: they only fixed a bug importing nested tables. So it's not useful for me anyway.
I checked to see what they did to update Word: they only fixed a bug importing nested tables. So it's not useful for me anyway.
Trouble with updater
I'm having the same trouble here. I've followed MS's instructions to remove the Component Plugin file, but that didn't work.
When I try and point the installer to the Office X folder, the window that pops up is blank. My folder is in the default location.
I also tried downloading the updater file again.
What a disappointment.
I am confused about something though. Why do I need this for Exchange email? I already can do email on my company's Exchange server by setting it up as a POP account. Am I missing something here?
I'm having the same trouble here. I've followed MS's instructions to remove the Component Plugin file, but that didn't work.
When I try and point the installer to the Office X folder, the window that pops up is blank. My folder is in the default location.
I also tried downloading the updater file again.
What a disappointment.
I am confused about something though. Why do I need this for Exchange email? I already can do email on my company's Exchange server by setting it up as a POP account. Am I missing something here?
Why do you need this to read mail on Exchange?
Good question. Some Exchange servers are configured to do IMAP and/or POP, in addition to the native MAPI protocol.
So, if yours does IMAP or POP, you can probably get away with using just a regular old mail client. But, if it does MAPI only, then you need Outlook or some other Exchange-native client.
Finally, if yo uwant to do calendaring, POP isn't going to be good enough. You need a mail client that knows about Exchange calendaring.
Good question. Some Exchange servers are configured to do IMAP and/or POP, in addition to the native MAPI protocol.
So, if yours does IMAP or POP, you can probably get away with using just a regular old mail client. But, if it does MAPI only, then you need Outlook or some other Exchange-native client.
Finally, if yo uwant to do calendaring, POP isn't going to be good enough. You need a mail client that knows about Exchange calendaring.
Installer, other stuff
Allright:
The only way I was able to get the installer to work was to delete all remnants of Office X, restart for good measure, then install from the CD, run these updates in order: SR1, Update 10.1.2. THEN this installer worked. I did not bother with 10.1.3 because it has to do with Italian language support if I recall correctly.
I have to use Office because it in the default at my work place. They all use PC's there and I am the only one with a Mac. I told them Appleworks would work, but the idiot IT consultant convinced my employer that I HAD to run the Microsoft office suite or else our Windows Server 2000 machine might have "problems" handling appleworks back ups. Can you guys believe that? so I am required to use it on my iBook. Oh well, it updated to current version, and the first time I opened Word it promptly crashed when I tried to "save as." Oh well, same piece of caca.
Allright:
The only way I was able to get the installer to work was to delete all remnants of Office X, restart for good measure, then install from the CD, run these updates in order: SR1, Update 10.1.2. THEN this installer worked. I did not bother with 10.1.3 because it has to do with Italian language support if I recall correctly.
I have to use Office because it in the default at my work place. They all use PC's there and I am the only one with a Mac. I told them Appleworks would work, but the idiot IT consultant convinced my employer that I HAD to run the Microsoft office suite or else our Windows Server 2000 machine might have "problems" handling appleworks back ups. Can you guys believe that? so I am required to use it on my iBook. Oh well, it updated to current version, and the first time I opened Word it promptly crashed when I tried to "save as." Oh well, same piece of caca.
true, but if you could get your mail via pop before, entourage knew what to do with the calendar invites and it added them automatically to your calendar anyway. This doesn't really provide any new abilities other than how it gets the information.
neilt
Does not require IMAP support
I originally tried to set this up using the account wizard, but kept getting the IMAP server/port errors that other people mentioned. According to our admin, both IMAP and POP3 support are disabled on our Exchange server for security reasons. After tinkering with some of the settings, I discovered that the domain was set to the server address (which was incorrect). So...I set the domain field to the prefix of the search domain in the network system preferences. Now everything works fine. All of my mail is there, contacts, calendar, etc. Only my signatures seem to be lost in the conversion.
I originally tried to set this up using the account wizard, but kept getting the IMAP server/port errors that other people mentioned. According to our admin, both IMAP and POP3 support are disabled on our Exchange server for security reasons. After tinkering with some of the settings, I discovered that the domain was set to the server address (which was incorrect). So...I set the domain field to the prefix of the search domain in the network system preferences. Now everything works fine. All of my mail is there, contacts, calendar, etc. Only my signatures seem to be lost in the conversion.
And if someone could get me directions on how to do this with a default configured instalation of exchange 2000 I would really appreciate it.....