Slashdot Mirror


First Look at Microsoft Exchange Server 2010 Beta

snydeq writes "InfoWorld's Martin Heller takes a first look at Microsoft's Exchange Server 2010 Beta, noting several usability, reliability, and compliance improvements over Exchange 2007. Top among Exchange 2010's new features are OWA support for Firefox 3 and Safari 3; improved storage reliability; conversation views; mail federation between trusted companies; and MailTips, a sort of Google Mail Goggles for the corporate environment. 'Database availability groups give you redundant mail stores with continuous replication; database-level failover gives you automatic recovery. I/O optimizations make Exchange less "bursty" and better suited to desktop-class SATA drives; JBOD support lets you concatenate disks rather than stripe them into a redundant array.' Exchange 2010 will, however, require shops to upgrade to Windows Server 2008, as support for Windows Server 2003 has been dropped. Microsoft will release technical previews of other products in the suite, including Office 2010, SharePoint Server 2010, Visio 2010, and Project 2010, in the third calendar quarter."

274 comments

  1. Now Let's Talk Pricing by eldavojohn · · Score: 5, Funny
    I found this part of the review especially helpful:

    The invoice for this baby is pretty small compared to your normal MS Exchange Server, it's only 1. But that's not in dollars, that's in first born children. So I'm going to throw out a few strategies for coping with this.

    • Just squeeze one out with your wife/prostitute to get it out of the way. ProTip: don't waste money on shots or clothing, a transport blanket will do. Usually you you can convince your wife that the first one is like a test run anyway.
    • Order one of those adopted kids from some other country. Throw some cheap makeup on them to match your ethnicity, pick up some false documents and practice watering up your eyes for when you have to push the kid across a long empty room to Steve Ballmer waiting with a pair of handcuffs. They'll be slightly better off indentured to Microsoft than whatever country they came from anyway.
    • Shaft them and never have kids. This is probably the option that will come naturally to most software folks. Get a vasectomy, abstain, do whatever it takes. There's no clause against this in the licensing agreement I read--yet.

    So, like pretending you're a college student, starving African or university staff to get cheap editions of Exchange 2007, there are ways to acquired 2010 at a relatively low cost and I hope this helps you cope with the extreme cost of owning Microsoft Exchange Server 2010 for your enterprise business.

    Sure the costs don't stop there, you need to upgrade to Windows Server 2008 to use it and there are a few more things you'll need to upgrade if you want to keep the same functionality you have now ... but that's just the unspoken rule.

    --
    My work here is dung.
    1. Re:Now Let's Talk Pricing by just_another_sean · · Score: 4, Funny

      Great. Thanks. Now I have to RTFA to find out if your serious or not.

      Why do you hate /.?

      --
      Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
    2. Re:Now Let's Talk Pricing by weber · · Score: 0, Flamebait

      OMG how can the parent be modded insightful? Are you drunk?!? :-D

    3. Re:Now Let's Talk Pricing by jonbryce · · Score: 5, Insightful

      Exchange is pretty cheap compared to the competition. That's probably one of the reasons why it is so popular.

    4. Re:Now Let's Talk Pricing by ukyoCE · · Score: 2, Informative

      Well...that depends on what you consider competition. If you're talking Exchange-look-a-likes, sure. But if your company is OK with a Good Reliable mail server with a separate calendaring app that integrates well with the mail app your company uses, you can get solutions dirt cheap or free.

      I've configured a heck of a lot of unix mail servers, and I can't pretend any are as easy to setup and configure as Exchange. But every Exchange+Outlook solution I've used at a half dozen companies has been painfully slow and unreliable with piss-poor webmail. For how important mail is to most companies, I'm surprised they put up with Exchange.

    5. Re:Now Let's Talk Pricing by Zonnald · · Score: 1

      Did you realize that you are the Parents first born?

    6. Re:Now Let's Talk Pricing by weber · · Score: 1

      I see that now he's modded Funny which makes more sense!

    7. Re:Now Let's Talk Pricing by vegiVamp · · Score: 2, Interesting

      I'm sure you mean "compared to the competition on wintel" ?

      --
      What a depressingly stupid machine.
    8. Re:Now Let's Talk Pricing by Anonymous Coward · · Score: 0

      No, he means "compared to comparable solutions".

      Of course, they're 'comparable' even though the drop-in exchange server replacements aren't actually feature-equivalent. Or even close. Or nearly as fast (And that's saying something, since Exchange is not exactly a speed demon). Or as reliable. Or as easy to get working with any smartphone other than blackberry (Screw you, RIM!). Or as easy to setup and maintain...

  2. And all the admins ask... by mbourgon · · Score: 2, Interesting

    What database engine is it using, and can we access it via SQL?

    --
    "Sometimes a woman is a kind of religion, she can save your soul & set you free from all your sins" - Bad Examples
    1. Re:And all the admins ask... by David+Gerard · · Score: 1

      dBase II. HAHAHAHAno.

      --
      http://rocknerd.co.uk
    2. Re:And all the admins ask... by Lumpy · · Score: 3, Funny

      Nope.

      MSFT is still retarded that way.

      i would KILL to be able to data-mine the email in the company with a SQL script.

      "here you are sir, 23 people in the office are boinking your Executive assistant."

      --
      Do not look at laser with remaining good eye.
    3. Re:And all the admins ask... by sakdoctor · · Score: 3, Informative

      I've never used Microsoft Exchange Server in my life. Mostly because I'm more from a hippy FOSS type company.

      Having read the Microsoft marketing crap, then the wikipedia article for a more neutral POV, I don't get it.
      What is special about "electronic mail, calendaring, contacts and tasks; support for mobile and web-based access to information; and support for data storage."

      I often hear exchange server quoted as THE reason why some companies can't diversify their software from Microsoft, but that lot doesn't sound too compelling to me.

    4. Re:And all the admins ask... by Amouth · · Score: 4, Informative

      http://msdn.microsoft.com/en-us/library/aa142634(EXCHG.65).aspx

      it isn't exactly normal SQL but it is alot closer than most things - and it does work.

      --
      '...if only "Jumping to a Conclusion" was an event in the Olympics.'
    5. Re:And all the admins ask... by Lumpy · · Score: 5, Insightful

      Because most companies dont want to hire competent EMail admins. Any of the MCSE monkeys can administer the Exchange server. No they cant administer it correctly but they can administer it. You really do need a competent email admin staoff to use exchange, but it's not as daunting as the FOSS or other options out there to windows It staff.

      I also dont understand the love affair with outlook, It's simply that some PHB's hate change and they used Exchange as the killing point to stop OSS infiltration.

      --
      Do not look at laser with remaining good eye.
    6. Re:And all the admins ask... by Anonymous Coward · · Score: 0
      Mostly because the user base is familiar with it, and Exchange connectors for mobile devices are plentiful and frequently "just work".

      Don't underestimate the power of a C-level asking "why don't we use Exchange like everyone else?"

    7. Re:And all the admins ask... by Anonymous Coward · · Score: 0, Funny

      Ease of use, integration, and scaling.

      The funny part is, most hippies I've dealt with are hippies because all it requires is the ability to spout off at the mouth and a life long lust for lethargy. Well, I should explain: it's funny because hippies would normally take the easiest way out thus providing them with more quality time in which to express laziness, and in this case, Exchange Server is by far the easiest way out. Well, maybe I should explain further: it's funny because hippies are communists (though they often present themselves under false pretenses as soclialists) and FOSS vs. commercial is analogous to communism vs. capitalism.

      So, much like I envision the Soviets' as having an inability to grasp the concepts of capitalism, I envision the same for you hippy FOSS types.

    8. Re:And all the admins ask... by alen · · Score: 5, Insightful

      if you have an iphone or winmo you can point your phone to a corporate email server and it will download all your email into the phone as long as you have a signal. and the IT department can manage all the phones remotely.

      say your hippy marketing exec loses his or her iphone and it has all kinds of data on it. the IT people can just wipe it remotely not caring where it is.

      say you have to keep all email for at least 7 years but you don't want it in anyone's mailbox. right now you have to buy a third party product. Exchange 2010 integrates it.

      say you want failover to another city with all your company's email there. Exchange 2007 and later.

      Even the FOSS Exhcange clones don't come close. For a medium to large business it's cheaper to buy Exchange with all the features than pay for add on software and more people to admin it

    9. Re:And all the admins ask... by somersault · · Score: 4, Funny

      "here you are sir, 23 people in the office are boinking your Executive assistant."

      "Don't worry - I've already told the cleaners to give special attention to your desk, chair, phone, scanner, shredder, and your little wooden dinosaur sculptures with the very long necks."

      --
      which is totally what she said
    10. Re:And all the admins ask... by somersault · · Score: 4, Insightful

      support for mobile .. access

      Bingo. This is the reason that we haven't moved away from Exchange. Windows Mobile connected to Exchange with DirectPUSH is a great combination for mobile users.. you can synchronise all your contacts, calendar, tasks and email with Exchange remotely. Email actually arrives on the mobiles a second or two before showing up in Outlook. Our Exchange server would be replaceable if it weren't for this. I almost replaced it with OpenExchange until I found out about this feature, which has now become essential to a lot of our sales team. If the blackberry network (and devices) weren't so shit then maybe I'd reconsider (the number of times I used to have our blackberry users blaming me for email not working when in fact it was the blackberry network, something which I have no control over.. eurghh..). There is a lot of room for a nice FOSS email client/server product on an open mobile platform..

      --
      which is totally what she said
    11. Re:And all the admins ask... by Sandbags · · Score: 4, Insightful

      Yea, it would be REALLY NICE if MSFT would put Exchange inside of something other than a Jet engine database... Then maybe I could have a high performance database that wasn't capped at 200GB for performance reasons, and I could have one big database per server cluster instead of 12-16... and I could front end that with a half a dozen exchange servers and have all 20,000 users inside of a single database and eliminate all the wasted space from single indexing!

      For Chrsits sake, can't the Exchange people and the SQL people work together, and combine the log shipping asynchronous non-cluster replciation features of exchange with a REAL F*ING DATABASE ENGINE!?!?!?!

      --
      There is no contest in life for which the unprepared have the advantage.
    12. Re:And all the admins ask... by Nicholas+Evans · · Score: 1

      Email and calendaring are hard when you get down to the nitty-gritty.

    13. Re:And all the admins ask... by CastrTroy · · Score: 1

      I've always wondered why email servers don't use database servers to store the email. It seems like an obvious idea. Personally, I think that even personal email clients should employ this type of technology. If everything was indexed, it would make search the email so much easier. Also, with SQL access, the could be many plugins for your mail client that would increase the value of the product.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    14. Re:And all the admins ask... by Anonymous Coward · · Score: 4, Insightful

      I agree with your point, but must say that your abrasive tone makes this AC understand why IT folks get such a bad rap. It's similar to why people dislike police so much. I consider myself a "competent" e-mail admin, but the several Exchange servers I administer only constitute about 3% of the servers I am responsible for, so I don't really have time to focus on them as much as I would like.

    15. Re:And all the admins ask... by Kamokazi · · Score: 5, Interesting

      I was able to set up a working Exchange 2007 server in 2 days. I had never configured an e-mail server before. I'm not even an MCSA (well MCTS woudl be the new name for it)....really only about halfway to it.

      So it's even easier than you say it is :-) But you are absolutely correct...you need a competent admin to do it right (I know I sure as hell didn't do it right...it was just a test box)...they don't necessarily have to be an "E-mail Admin" to do it right, they just need to be competent enough to follow best practice guidelines (and obviously have a basic understanding of how e-mail works...any of your 'MCSE monkeys' should have that).

      And that is a big part of why Exchange predominates...it's easily administered, and it has features that nothing else offers on an equivalent level.

      Also keep in mind that it's not just the PHB's being resistant to change that stops OSS...it's the fact that Microsoft does a good job of making sure that their stuff integrates with eachother very well (and they don't exactly go out of their way to make sure other stuff can integrate with their products). The reason Exchange was so easy to get up and running for me is due in large part to Active Directory integration, and ISA Server 2006 is basically preconfigured to allow an Exchange server the proper access just by telling it the IP address.

      --
      As our way of thanking you for your positive contributions to Slashdot, you are eligible to disable Slashdot 2.0.
    16. Re:And all the admins ask... by Anonymous Coward · · Score: 0

      Mostly because I'm more from a hippy FOSS type company.

      Don't worry, we all make mistakes in life. ;-)

    17. Re:And all the admins ask... by Anonymous Coward · · Score: 1, Interesting

      MSFT has tried moving Exchange to SQL Server several times and have never even reached performance parity. SQL Server is great, but the Exchange engine is faster at e-mail type workloads.

      Also, don't confuse the Exchange database engine with Jet, which was part of Access/Office.

    18. Re:And all the admins ask... by Anonymous Coward · · Score: 1, Interesting

      Any of the MCSE monkeys can administer the Exchange server. No they cant administer it correctly but they can administer it.

      Let's hear it for backscatter where the return path is an exchange server on a company intranet.

      I also dont understand the love affair with outlook

      Business people have funny ideas. In my experience they want everything integrated and everyone using the same software. They think it's cool that someone that mailed once 6 months ago is in their address book.

      I'm under instruction to produce some stationary for outlook because the CFO wants a logo in his emails. I've explained to him that it's stupid. I've shown him base64 encoded binary attachments on the mail spool. I explained the increase in message size and storage requirements for sent email. Futile. Like the bit in American Psyhco where they're all flashing business cards, his peer group are impressed by recieving email with a company logo. I suppose I'm going to be asked to append a disclaimer next, then he and his CxO chums can have a little competition over who has the most obnoxious and unenforcable email disclaimer. Such is the mentality of outlook users!

      /rant

    19. Re:And all the admins ask... by Bill,+Shooter+of+Bul · · Score: 1

      So I guess the moral of the story is : Don't use SQL Server for email like workloads. Unfortunately, I think this is where most of the growth in the db industry is right now smallish, high concurrent reads/writes.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    20. Re:And all the admins ask... by drsmithy · · Score: 3, Insightful

      What is special about "electronic mail, calendaring, contacts and tasks; support for mobile and web-based access to information; and support for data storage."

      Not having to run a dozen different, barely interoperable end-user applications to achieve it.

    21. Re:And all the admins ask... by Anonymous Coward · · Score: 0

      What is special about "electronic mail, calendaring, contacts and tasks; support for mobile and web-based access to information; and support for data storage."

      Well, from the POV of a small business try to find me a FOSS solution that lets users easily:

      - Use email
      - Set appointments for themselves and others, send appointment requests to others, and view all other users' calendars
      - Sync to their wireless devices

      Six years ago, when we looked to move beyond simple POP3 mail, that solution was Exchange. At that time, I looked hard for a FOSS solution, but it wasn't there. Just today I bought a new server running SBS 2008; the licenses were about $2k for 30 users. If you're running Outlook (which the users love, and actually works very well), it's really a no brainer. There may be something out there on the server side (Zimbra?) that would work for us, but then we'd have to pay for Outlook connectors so we wouldn't really save much if anything.

    22. Re:And all the admins ask... by cayenne8 · · Score: 1
      "Yea, it would be REALLY NICE if MSFT would put Exchange inside of something other than a Jet engine database... Then maybe I could have a high performance database that wasn't capped at 200GB for performance reasons, and I could have one big database per server cluster instead of 12-16... and I could front end that with a half a dozen exchange servers and have all 20,000 users inside of a single database and eliminate all the wasted space from single indexing!"

      Well, I supposed they could use PostgreSQL. It wouldn't cost them a penny.

      :)

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    23. Re:And all the admins ask... by knghtrider · · Score: 2, Informative

      Not only that, but they make is so dirt cheap for the not for profit entities to buy, that it gets more entrenched there. I have numerous friends who are employed as admins in the Non-Profit Sector; and while most of them can get some FOSS in their enviroments; email isn't one of them.

      Actually, one of the best things to have happened is Google Mail and Google Apps. I know that several large churches have moved all of their staff from Exchange to Google Mail; and more of them are coming. I also know several medium sized churches that have moved to both Google Mail and Google Apps. I've been using gmail for several years now, and under IMAP, it's pretty good. Granted, they have outages, but as of yet, I haven't lost any mail. I'm sure it will happen. but the important items are hard copies and filed anyway--mostly e-receipts from online bill payments; and I delete those from e-mail anyway.

      Less headaches for the already overworked IT staff that also happens to work with the AV gear as well. And, with Google Apps--less to break at the desktop level.

      --
      In America today you can murder land for private profit. You can leave the corpse for all to see, and nobody calls the c
    24. Re:And all the admins ask... by shutdown+-p+now · · Score: 5, Informative

      Exchange database engine is also called "Jet", but it's a different kind of Jet: Access is Jet Red, Exchange is Jet Blue. The difference is explained here.

    25. Re:And all the admins ask... by vux984 · · Score: 1

      Actually, one of the best things to have happened is Google Mail and Google Apps. I know that several large churches have moved all of their staff from Exchange to Google Mail; and more of them are coming.

      Why is that so great? How about hotmail? Would you endorse that?

      Why or why not?

    26. Re:And all the admins ask... by Jinjuku · · Score: 0

      I admin our Exchange servers (2003) w/o issue. RBL's are integrated, SPF is setup and working. AV is scanning everything in/out. Never been hacked, never have experienced any downtime. Host over 1200 accounts. Integrated Calenders, Public Folders, vendor and client contact lists etc... You find me an integrated FOSS solution that doesn't absolutely eat up my precious time doing everything that Exchange does for our organization (I gave Zimbra a whirl and wasn't impressed. Maybe it has improved by now...).

    27. Re:And all the admins ask... by CarpetShark · · Score: 1

      i would KILL to be able to data-mine the email in the company with a SQL script.

      apt-get install dbmail imapsync

    28. Re:And all the admins ask... by DigDuality · · Score: 2, Informative

      zimbra does this.

    29. Re:And all the admins ask... by nine-times · · Score: 4, Insightful

      Sorry, but really, you're wrong. I'd love to believe you, because then we could all just drop Exchange and everything would be good. What you're saying may contribute to Exchange's place in the corporate world, but it's not the complete answer.

      But show me another email package that provides all the same things. Integrated email, contacts, calendar, the ability to send/receive meeting invites, role delegation, public folders, support for mobile devices (w/push and remote wipe), single sign-on, advanced AJAX web client as well as desktop client... I'm missing some things. Those are just the major features off the top of my head.

      Oh, right, you're going to tell me about Zimbra and Scalix, except those don't seem to work as well as FOSS people claim, and besides not all of the components are FOSS. Or you're going to post something about some package that no one has ever heard of, but you'll swear it's great. When I investigate, it'll turn out to be some not-really FOSS package that doesn't work at all and has only been in development for 2 months. Or you'll tell me, "I don't care about your features," in which case, great, that's why you can use a FOSS alternative and the rest of us can't.

      Sorry, I need a trustworthy and functioning alternative from a major vendor (who I can safely assume will exist in 2 years). Maybe Apple will be a contender once Snow Leopard comes out, but your IMAP/POP3 server isn't really in the same class of product.

    30. Re:And all the admins ask... by Acer500 · · Score: 5, Insightful

      Business people have funny ideas. In my experience they want everything integrated and everyone using the same software. They think it's cool that someone that mailed once 6 months ago is in their address book.

      I might be too far along the "Dark Side" (TM)... but why exactly is that a bad idea? I think it's a nifty feature, myself.

      I'm under instruction to produce some stationary for outlook because the CFO wants a logo in his emails. I've explained to him that it's stupid. I've shown him base64 encoded binary attachments on the mail spool. I explained the increase in message size and storage requirements for sent email. Futile. Like the bit in American Psyhco where they're all flashing business cards, his peer group are impressed by recieving email with a company logo.

      Are you stupid yourself??? Why would your CFO care about how many bytes an encoded binary attachment takes, or how it looks in base64 of all things !!! Just tell him "Yes sir, it will cost U$ XXXX in added storage costs, do you still want to go ahead sir?", that's all he wants to understand or care about.

      Much like some of us don't care how exactly your car works as long as it takes you there (even though it's not a bad idea to know a bit), your CFO doesn't want to or cares to know how his logo goes.

      Even further, if he thinks a company logo on his emails will result in more business opportunities, I think he's right to implement that. YOU are not the target of those logoed emails, it's other people like him !!!

      /anti-rant + rant (sorry for the flamebaitish name-calling)

      --
      There are three kinds of lies: lies, damned lies, and statistics.
    31. Re:And all the admins ask... by rufus+t+firefly · · Score: 1

      Why is that so great? How about hotmail? Would you endorse that?

      Google Mail, etc, is a bit more palatable since it allows standard IMAP, SMTP, etc. I wasn't aware of hotmail supporting client access via standard protocols (although apparently they do support POP3 now).

      --
      "He may look like an idiot, and talk like an idiot, but don't let that fool you. He really is an idiot." - Duck Soup
    32. Re:And all the admins ask... by knghtrider · · Score: 1

      Actually, I'm talking about the commercial form of Google Mail, not the freebie..

      I have no experience with the 'Windows Live' versions, but since the parent company of 'Windows Live' doesn't support FOSS as much as Google does; then in terms of the discussion, Google would be weighted heavier because of their FOSS support.

      --
      In America today you can murder land for private profit. You can leave the corpse for all to see, and nobody calls the c
    33. Re:And all the admins ask... by rufus+t+firefly · · Score: 1

      As does Google Sync, for the most part. And definitely across more platforms than Exchange does.

      Funambol also supports some pretty aggressive syncing as well.

      --
      "He may look like an idiot, and talk like an idiot, but don't let that fool you. He really is an idiot." - Duck Soup
    34. Re:And all the admins ask... by Khorniszon · · Score: 0

      the IT people can just wipe it remotely not caring where it is.

      I already love how they can remotely install sh*t on my box. No, thanks.

      keep all email for at least 7 years but you don't want it in anyone's mailbox. right now you have to buy a third party product.

      failover to another city with all your company's email there.

      Like, say, *any* database backup utility? As for failovers, even bloody sendmail could do that.

      Exchange is pure evil. The only thing worse is the MTA from Lotus Notes.

      --
      My whole being exists in a formless void.
    35. Re:And all the admins ask... by Anonymous Coward · · Score: 1, Insightful

      Because most companies dont want to hire competent EMail admins. Any of the MCSE monkeys can administer the Exchange server. No they cant administer it correctly but they can administer it. You really do need a competent email admin staoff to use exchange, but it's not as daunting as the FOSS or other options out there to windows It staff.

      Correct, businesses want all the benefit of in-house mail servers that do everything Exchange does (which is to say, unparalleled feature set) without having to hire a person JUST to deal with the mail server. I'm not a great mail server admin, but I can keep Exchange running across two sites, no problem. I provide my users with a ridiculous amount of functionality with a minimum amount of management time on my part. None-the-less, most *nix options scare the daylights out of me.

      Poor argument to make if you're supporting OSS.


      I also dont understand the love affair with outlook, It's simply that some PHB's hate change and they used Exchange as the killing point to stop OSS infiltration.

      Outlook makes use of those 80,000 quirky little features that Exchange supports... and the interface, IMHO, is fantastic. I have my own problems with it, but I've yet to find anything close. But this is just personal preference.

    36. Re:And all the admins ask... by knghtrider · · Score: 1

      Yup..no IMAP, just POP3.

      here

      --
      In America today you can murder land for private profit. You can leave the corpse for all to see, and nobody calls the c
    37. Re:And all the admins ask... by guruevi · · Score: 0, Troll

      The time tables here kill me. 2 days for a freakin' e-mail server? Get any decent Linux distro and you can do it in 2 hours including spam and antivirus checking. You want calendaring: Darwin Calendar Server, another 2 hours (if that long).

      On the other hand, mail stores can be huge without even crashing anything. I have currently in the proximity of 500GB but I know of installations with several terabytes all administered by 1 or 2 admins.

      The place I work at has several departments each doing their own thing. I currently manage a Postfix and Calendaring install on a single box for about 150 users by myself while also doing everything else for the rest of the department. The functionality is identical to the Exchange setup and it's down maybe 10 minutes a month for updates and patches.

      Another department has a huge Exchange cluster (a rack of blades) to manage maybe 1500 users (only 10 times as much), they need a freaking appliance for spam/virus filtering and 5 full-time Exchange admins. That thing (although being a cluster) is every month at least 2 hours down (patching and updating) and every week there is some type of notice e-mail about some data store being down or migrated or moved and x-number of users being unable to use it during that maintenance.

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    38. Re:And all the admins ask... by jonbryce · · Score: 2, Interesting

      With Darwin Calendar Server, can I enter appointments on Outlook or similar on the desktop, and have them automatically update on my phone?

      Can I get push email on my phone, or do I have to have the added bandwidth and battery overhead of polling an IMAP server every few minutes?

      As for setup time, from my perspective, I installed Small Business Server, and Exchange and Sharepoint came already set up. That was a lot less than two days. Windows 2003 itself is slightly more difficult to install than Ubuntu, but not much.

    39. Re:And all the admins ask... by mcmonkey · · Score: 2, Informative

      I've always wondered why email servers don't use database servers to store the email.

      They do. They just don't expose their inner database.

      Also, with SQL access, the could be many plugins for your mail client that would increase the value of the product.

      And this is why. Your email server vendor does not want to hear from you when your 3rd party plugin has made your email database FUBAR. Or when some hotshot admin unleashes a cascade of table scans and no one can get their email.

      Seriously. Have you even known off-the-shelf app with a database where the vendor said, "don't go in to the database, do all your work through the app" and customers actually listened and did not go in to the database?

    40. Re:And all the admins ask... by jonbryce · · Score: 1

      Apple's not going to be a contender, because they have taken the decision to support Exchange in their products.

      The latest iPhone already supports it, and Snow Leopard will as well. You can already get very decent support by installing Entourage.

    41. Re:And all the admins ask... by nine-times · · Score: 1

      Apple's client software supports Exchange, but they're also working on the server side of things to offer a replacement for Exchange that their client software will also support.

    42. Re:And all the admins ask... by V!NCENT · · Score: 3, Interesting

      The problem with Microsoft products is that everybody can set it up, but almost no-one that does that knows how to configure it the right way. Defaults? Rofl...

      --
      Here be signatures
    43. Re:And all the admins ask... by Anonymous Coward · · Score: 0

      I hope you know that a program provides an OLEDB access interface, doesn't mean it is a jet engine database. Postgres also has OLEDB interface, if I remember it correctly. Is Postgres also jet engine based?

    44. Re:And all the admins ask... by atamido · · Score: 0

      I suspect they may have been doing things 'wrong', ie the "everything in one giant database" approach. It is impossible to tune a database to deal with all sizes of data efficiently, so the easiest thing to do is break the bits apart.

      Have a database that stores the various important parts of the email header viewed by users. Extract the text from the emails and attachments and store it in a different database for performing text searches. Finally, store the full email header and email body in two different databases (or just the file system), indexed by a hash on their contents (this gets you single instance storage for when an email is sent to several people).

      Doing this you can use different database systems on different servers that are carefully tuned to their specific workloads.

      I recently had to build an online archive to display years worth of emails stored in PST files. I couldn't find anything simple so I just imported the emails into an IMAP account, and then wrote some PHP that queried and broke up the messages into pieces for storage. Granted, it's not serving gigabytes of emails to thousands of users simultaneously, but it's fast. It really makes me wonder how people get this wrong.

      *I broke up the emails into their individual MIME attachments and stored those individually after compressing them with GZIP. This meant that broken emails might end up with missing pieces, but in my testing email clients never showed the broken pieces anyway. Also, most people just want the important parts of the header and the text, so the various MIME attachments are rarely retrieved so compressing them made a lot of sense.

    45. Re:And all the admins ask... by ukyoCE · · Score: 1

      I'm a little afraid to read the OP you're responding to, but you're absolutely right. I cringe thinking of an admin showing a CFO a base64 mail spool. It took me a while to learn this too, but costs and results are all that matter to the people above you at most companies. This isn't really a bad thing either.

      Not to mention, you could use an html image link to the company logo on the website if you're so scared to death of adding a tiny compressed logo to every e-mail...

    46. Re:And all the admins ask... by Anonymous Coward · · Score: 0

      I might be too far along the "Dark Side" (TM)... but why exactly is that a bad idea? I think it's a nifty feature, myself.

      The problem isn't the feature itself, the problem is that neither email addresses or accounts are permanent. If changing email address policy company wide didn't convice you as to the un-nifty-ness, then I'm sure a couple of years explaining DSN's to irate users would.

      if he thinks a company logo on his emails will result in more business opportunities

      Then he's deluded. He's the CFO, not a sales exec. I probably wasn't clear, he doesn't just want the logo on his own emails, he's pushing to have the stationary mandatory throughout the company. While HTML emails may be fine for his department, we have staff who contribute to mailing lists where HTML is considered rude. There's many reasons to call me stupid, explaining HTML email to the CFO isn't one of them ;-)

    47. Re:And all the admins ask... by The+Snowman · · Score: 2, Insightful

      Microsoft? Delivering a quality product? Mod be troll all you want (and frankly I don't care because after many unfair troll ratings my karma is still excellent), but seriously, if you disagree, name one product that Microsoft ever made that is quality software.

      Personally, I like SQL Server 2005. It may not have the scalability or performance that Oracle has, but it makes up for it in simplicity and ease of use. I have several customers with SQL Server databases in the 40-60 GB range accessed almost constantly via Java web services and rarely do we see so much as a hiccup. The tools are fairly easy to use and intuitive, and I like how the system tables/views are laid out: between standard SQL, the information schema, and TSQL, I have found only one task I could not accomplish. However, given that SQL is not NP-complete, I simply offloaded that logic (recursive lookup) to the application, not the SQL or stored procedures. Oracle could have done it, but it still would have been slower than just grabbing the data and processing it in a language better suited to it anyway.

      Visual Studio is an excellent development environment. Recent versions are about as C/C++ standards-compliant as any open source offering, and the debugger is probably the best on the planet. Between the rock-solid and intuitive IDE, the strong compiler/standard library, I have no complaints there. I am talking standard C/C++ however, not .NET.

      Other than that, I have to agree, much of the rest of their software is junk. Windows is a resource hog. Outlook+Exchange makes me cry every day at work: poor performance, lost connections, slow searching, and worst of all, it encourages top-posting. Office uses those awful ribbons that make me want to throw my monitor through the cubical wall.

      --
      24 beers in a case, 24 hours in a day. Coincidence? I think not!
    48. Re:And all the admins ask... by Omniscientist · · Score: 1

      The message store in Exchange can be simplified by viewing it as being a bunch of MAPI tables.

      A read-only view of a table is provided by the IMAPITable : IUnknown interface.

      If you have an initialized IMAPIContainer, then you can get a MAPITable by calling either its contents or hierarchy table retrieval methods.

      Regardless of how you get the table, you have something you can work with in terms of querying, but as far as I know there is no outright support for straight up SQL query syntax with MAPI and Exchange. I'd recommend instead using the ExecSQL method found on the MAPITable object exposed by Redemption.

    49. Re:And all the admins ask... by sr180 · · Score: 2, Informative

      Z-push will connect to almost any IMAP mail server and provide pushmail for all supported devices.

      --
      In Soviet Russia the insensitive clod is YOU!
    50. Re:And all the admins ask... by Anonymous Coward · · Score: 0

      also integration of Live Meeting and IM into Outlook/Exchange. About 1 extra click an I have SALESMEN setting up meetings with groups of people to share docs/presentations on a video / audio conference call. SALESMEN. Outlook gives a meeting reminder, everyone clicks 'Join the Meeting' and I just sit back and do nothing but watch the line usage. Nice.

    51. Re:And all the admins ask... by trawg · · Score: 2, Interesting

      You are spot on. We recently evaluated Zimbra; it's good, but a) it's not all OSS (the fucking Outlook connector, dammit, is a must have) and b) it's a bit fiddly sometimes.

      I've tested a stack of different calendaring apps and have found them all inferior to Outlook in almost every respect. It's just so easy to use. I'm trying really, really hard to prevent us going to Exchange, but I'm running out of reasons.

      I'm really, really hoping Thunderbird 3.0 / Sunbird 1.0 will make an impact here. If there's one market that OSS will really make a difference in its the groupware market.

    52. Re:And all the admins ask... by ill1cit · · Score: 1

      I think you missed the point. Someone without any mail experience set this up in a couple of days. I doubt it was 2 full days either. There is no way that someone without any FOSS experience could set up a FOSS mail server in 2 hours. You are deluded if you think they could. Quite simply, Exchange and Outlook are the best solution for the vast majority of environments because of their ease of installation and administration. Almost anyone one with half decent Windows server experience can be trained up quickly to admin an exchange server. The same can't be said for most FOSS systems out there. If you don't understand that then you are a one eye FOSS fanboi.

    53. Re:And all the admins ask... by guruevi · · Score: 3, Informative

      Yes, with Calendar Server you can enter appointments somewhere and it will automatically update on every device you got connected to the calendar. There are also implementations that keep Calendars in IMAP folders although you would have to use the same (or at least compatible) software on desktop and mobile devices.

      You can get push e-mail with IMAP, it's called IMAP IDLE. A lot of "push" services work in a similar way. Somehow the connection is kept open and the server sends a small packet when there's new mail. Bandwidth usage is minimal and implementation cheap and simple. I wouldn't be surprised if Exchange uses the same protocol but somehow encapsulates it into a proprietary layer (like they do with Kerberos and LDAP for AD)

      Windows SBS is not the same as a dedicated Exchange box. Although the implementation depends largely on the administrator I think. Either way it can be done, Ubuntu doesn't have to pay CAL's though.

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    54. Re:And all the admins ask... by guruevi · · Score: 1

      Well, a lot of "FOSS" distro's have tools for that built-in and they are quite good (eg. RedHat distro or Webmin). I have FOSS experience but not specifically with Postfix or Cyrus. However the frontend tools were very simple for me to use.

      If you want really simple and you can afford it, get a Mac OS X Server, those tools (although on the simplistic side) are very, very easy. I would say easier than anything else I've ever seen. However you might want to install webmin or go under the hood for the more advanced stuff.

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    55. Re:And all the admins ask... by ill1cit · · Score: 1

      the IT people can just wipe it remotely not caring where it is.

      I already love how they can remotely install sh*t on my box. No, thanks.

      In most cases you are using a company phone if you have it linked to your company exchange server (not all of course), and unless you live in fantasy land I don't think it is outrageous to allow the IT admins to remotely wipe your company phone if you lose it or it gets stolen. And for the record you can even wipe it yourself from OWA.

    56. Re:And all the admins ask... by arth1 · · Score: 1

      The problem with the kitchen sink approach is that when one of the functions is down, all of them are down.

      The toolbox approach of Unix has proven itself over time to be far more reliable, and you can replace unreliable/obsolete/underperforming components at will.

    57. Re:And all the admins ask... by Darby · · Score: 2, Insightful

      There is no way that someone without any FOSS experience could set up a FOSS mail server in 2 hours. You are deluded if you think they could.

      yum install postfix
      emerge postfix
      apt-get install postfix
      /etc/init.d/postfix start

      Hell I just did it in at least 3 different distros with what would have only taken a quick google search.

      So, it's actually a very simple and obvious fact, rather than a delusion. So that's 5 minutes out of my 2 hours gone and I have a working mail server. Plenty of time from my 2 hours left over for learning how to configure 20 or more different features.

      Almost anyone one with half decent Windows server experience can be trained up quickly to admin an exchange server. The same can't be said for most FOSS systems out there. If you don't understand that then you are a one eye FOSS fanboi.

      If you don't understand that most of this shit really isn't all that complicated in most instances and that any reasonable intelligent person can quickly learn to admin a new application given that they already have good general admin skills, then it is you who are obviously the sad and deluded fanboy.

    58. Re:And all the admins ask... by oatworm · · Score: 1, Insightful

      That's nice. There's just one problem: Exchange isn't just e-mail. Now, let's say for a sec that you have your standard-issue MCSE-aspirant staring at a bunch of Windows XP or Vista boxes and they need to get e-mail, calendaring, and webmail. Better yet, they've been told that it needs to work with existing in-house logins. On Windows, this is fairly simple, albeit expensive - take one Windows 200(3/8) server, install some version of Exchange (2003 would probably be simpler for this purpose, but you can muddle through 2007 if you're patient), and you're done. Assuming you made your new server a member of the domain, the installation process for Exchange should take care of whatever schema changes that might be necessary. Even with Exchange 2007, which seems to have been explicitly designed to prevent setting up a single-server Exchange setup, you'll probably have something that works internally in a couple of hours and will send e-mail to the outside world by the end of the day. Exchange 2003 is almost point-and-click. Exchange 2010... I don't know yet. I downloaded the beta, though, so I'll hopefully find out by the end of the week. :-)

      Meanwhile, following your example... okay, we need to integrate with Active Directory, so that means setting up Samba, pam, winbind, and Kerberos. If you're lucky, you have Likewise installed and can work it in that way. Then, we can get Postfix installed... but that's just e-mail. Okay, now we need calendaring... erm... iCal? Wait, we also need webmail, so that means setting up Apache (Exchange sets up IIS automatically) and then getting whatever e-mail/calendaring solution you have talking to it... right. Of course, there is Zimbra and its ilk, but it really doesn't take long for the subscriptions to cost more than Exchange in the long run.

      Now, just so I'm not misunderstood, do I think that doing things the "long way" will work out better in the long run? Sure, probably. If you're setting up e-mail for a few thousand people or so, you're going to need to spend some time planning it and, if you happen to have the experience and knowledge to pull off a custom solution, more power to you. On the other hand, if you're taking care of e-mail for a few hundred people, Exchange really isn't half bad, especially if you really don't have the time (or the resources) to sit down and try every conceivable e-mail/calendaring/web access solution. Like most things Microsoft, it's not great, but it's "good enough".

      Last but not least, Exchange 2007 did a fine job of pooching that. I know I took a much more serious look at other groupware systems after dealing with that beast. Exchange 2003 was quirky and a little unreliable, but at least it installed cleanly and didn't have a bunch of silly "roles". For single server environments, Exchange 2007 was a HUGE step backwards. Mind you, I'm sure the clear subdivision of roles made life easier in multi-server environments, but if FOSS can come up with a similarly priced and slightly easier to administer alternative (getting close!), they'll eat MS alive.

    59. Re:And all the admins ask... by vegiVamp · · Score: 1

      Apparently, Jet Blue is an ISAM database, dixit WikiPedia.

      Maybe they should try MySQL as Exchange backend.

      --
      What a depressingly stupid machine.
    60. Re:And all the admins ask... by Anonymous Coward · · Score: 0

      Here's an email server using SQL written by someone that used to work at AT&T Labs:

      http://decimail.org/server/

    61. Re:And all the admins ask... by AlXtreme · · Score: 1

      Of course, there is Zimbra and its ilk, but it really doesn't take long for the subscriptions to cost more than Exchange in the long run.

      It's clear you don't know what you're talking about on this front. Zimbra (with outlook connector) is a _lot_ cheaper compared to Exchange.

      I recently did a Zimbra-conversion for a client, it went remarkably well. The price is reasonable if you want outlook-interactivity and support, and given that Zimbra uses FOSS under the hood and has a great admin-interface it's easy to administer and extend. The open source version is perfect if you are in a situation where Outlook has not reared its head.

      Then again, for your average business reliability/stability is much more important than price. That is the biggest win Zimbra and FOSS have over Exchange. Webmail users don't mind switching, as long as they get a better, more dependable solution.

      The only thing keeping Exchange in place are the PHBs.

      --
      This sig is intentionally left blank
    62. Re:And all the admins ask... by abelb · · Score: 0

      IBM Lotus Notes and Domino Server. Domino server can run on Linux and I think they either have, or are working on a native Notes client for Linux.

    63. Re:And all the admins ask... by UbuntuLinux · · Score: 0, Informative

      As someone who has moved from a company that uses Exchange to a company that uses Lotus Notes, I can say for absolute certain that I would do almost *anything* to be using Exchange again. Without exception, everyone fucking hates Lotus Notes here.

    64. Re:And all the admins ask... by ericrost · · Score: 1

      Roger that for the same reasons above!

    65. Re:And all the admins ask... by Darby · · Score: 1

      That's nice. There's just one problem: Exchange isn't just e-mail.

      That's completely irrelevant.

      The comment I responded to said:

      There is no way that someone without any FOSS experience could set up a FOSS mail server in 2 hours. You are deluded if you think they could.

      I demonstrated absolutely that that is an ignorant statement at best and a bald faced lie at worst.

      Put your strawman away, you've only proven your incompetence at basic reading comprehension skills.

    66. Re:And all the admins ask... by vux984 · · Score: 1

      Google Mail, etc, is a bit more palatable since it allows standard IMAP, SMTP, etc

      True.

      But your average church really doesn't care about stuff like IMAP. And if you did need IMAP while hotmail might not do it, yahoo, for example, does.

    67. Re:And all the admins ask... by vux984 · · Score: 1

      but since the parent company of 'Windows Live' doesn't support FOSS as much as Google does; then in terms of the discussion,

      What terms of the discussion were those?

      Google would be weighted heavier because of their FOSS support.

      So, you prefer the proprietary data mining advertising company seeking to access and index all your information both private and public in order to build advertising profiles on you over the sometimes monopolistic proprietary software developer that's seeking to lock you into buying their products.

      I fear google more than microsft. The worst microsoft ever aspired to was charging me too much for software. Google wants to be the gatekeepers to all information.

      But "google would be weighted heavier because of their FOSS support"?

      You've been bought too cheap.

      Not that I'm saying I'd go with Microsoft for this. The reality is that if you are prepared to pay for email hosting, there are LOTS of very excellent 3rd party options to choose from. Ones that aren't busy trying to harvest your data or lock you into their products.

    68. Re:And all the admins ask... by oatworm · · Score: 1

      I've looked at this before. Let's run through the numbers:

      Exchange 2007 pricing boils down to $699/server for Standard with $67/CAL, which gives you five storage groups and five databases per Mailbox server role. In my experience, one database on a reasonably well equipped server can handle 100 mailboxes without any serious effort; it would take each user pulling in a 500 MB mailbox before you run into the artificial 50 GB database limit, which is easily circumvented with a well-documented registry change. Obviously, this being Microsoft, you get an "Outlook connector" for free, as well as mobile support. With a single tweak to the registry, a single server should be able to handle hundreds of large mailboxes.

      Looking at Zimbra's feature matrix, meanwhile, the only version that comes with the Outlook connector is the Professional Edition, which "starts" at $28/user/year.

      Let's do the math.

      Assume that, whether you get Exchange or Zimbra, you'll be able to run it for about three years before you have to upgrade to the latest and greatest version. This is probably a bit fast for most corporations, but it'll give us an idea of what we can do. Assuming this is the case, we're looking at an equation that resembles:

      699+67x = 3(28x)

      Solving for x, we find that, for x > 42, Exchange is actually cheaper if we amortize the up-front licensing costs for Exchange over a three year period. This gets even worse for Zimbra if we push it farther than that. Now, that said, this is only true if we ignore Windows 2008 licensing, which does push things into Zimbra's favor, provided we're installing Zimbra on a free-as-in-beer OS of some sort. On the other hand, we didn't even include Zimbra mobile pricing, which isn't even included with Zimbra Professional.

      In short, if you install Zimbra on a free-as-in-beer system, yes, it will come in slightly cheaper than Exchange. If you don't, though, Exchange pricing is actually comparably affordable.

    69. Re:And all the admins ask... by nine-times · · Score: 1

      Yeah, let me be clear about this: I would LOVE to be able to use Thunderbird and Sunbird and never have to deal with Outlook and Exchange again.

      But!

      I need to replace all the functionality on the server side and client side, including mobile devices. When one of my users (which includes my bosses) ask me, "How do I do [whatever] in this new system?" I can't say, "You can't, but that's ok because it's FOSS!" I have to be able to say, at worst, "You can't do that exactly, but you can do this other thing which really is just as good." At worst.

    70. Re:And all the admins ask... by Sandbags · · Score: 1

      Well, honestly most of the Suck behind Microsoft is not Microsoft at all, but poorly designed infrastructures; lack of professional admins who understand monitoring, tweaking, and sizing tools; lack of proper application design; a complete failure to code for effiency ("oh, that massive library has one code sequence I need, instead of making my own subset of code for this problem, I'll just link the whole library in!"); Lack of understanding from the bean counters that more money on quality systems instead of low end Dell Crap servers is actually CHEAPER in the long run; Lack of Admins customizing the Windows install for their specific needs (uh, hello, of the 3+ GB of bloat in 2003R2, you can cut it back to about 600MB and not loose a bit of functionality, and by trimming the applications and services loaded, you can more than half it;s boot time and double it's response time.

      The REAL problem with Microsoft is the people who adminster it, and the people who budget it. People who are given underfunded, underdesigned, undertested hardware and simply slap the OS and an AV program on it and put it into production without running it through 2-3 months of load testing, tweaking, and hardware adjustments are destined to have tier app crash on them sooner rather than later, and then they blame it on the OS Vendor.

      There are litterally TENS of THOUSANDS of pages of microsoft documentation just covering Exchange 2007 server... I'VE READ THEM, and we've recently deployed a true Tier 0 infrastructure for it. Yes, it took 9 months to develop and deploy. yes it cost over a million dollars including 28 servers, 2 load balancers, and all the licences, and a new DR solution (and that's not including support infrastructure like AD, DNS, switches, etc, nor the CALs for outlook). We have 16,000 users on this. It's overdesigned, overpowered, and complex. It's also never going to loose connectiv ity unless we loose the physical connection to the world (and even then the MX record is in the cloud and we deployed a failover site using Geo-clusters)

      Ya know what? Our exchange team has learned so much through this process that this level of attention is being focused on our other 2000+ x86/64 servers. We expect to save this company over 15 million this year by analyzing our hardware and software infrastructure, combining this type of focus to reduce our systems into VMWare and z/VM linux, cut our storage dependency by about 100TB, shrink our DR system, and in the end, have a more resilient, better performing, less crashing solution that costs less to operate and takes up 1/6th the amount of floor space in our datacenters. This is not the first project to get this level of attention. Our Sharepoint infrastructure, IP phone system, Citrix farms, have all gone through this in the last 2 years. We have had appreciably 0 downtime since they've gone through review (this excludes PLANNED downtime).

      Yes, M$ solutions take more resources to do the same job. Hardware is cheap, skilled unix admins are not. (we have about 300 AIX servers and 12 mainframes, so we're quite familiar...) ...and no, M$ is NOT the right solution for every job. In fact, we thing it's right for less than half our server needs. That said, there are MANY things it can do better, simpler, and with higher compatability than anything else we've deployed.

      Is it the best desktop OS? no, I'd place it 3rd behind Apple and Linux. Is it the best server OS? not even close. Are their apps the best? no, actually office kind of sucks. however, the ability to tie that together, and have universal vendor support is workth a lot more...

      --
      There is no contest in life for which the unprepared have the advantage.
  3. striped? by dj245 · · Score: 1

    JBOD support lets you concatenate disks rather than stripe them into a redundant array.'

    Both of these options seem like terrible ideas to me if you care at all about your data.

    --
    Even those who arrange and design shrubberies are under considerable economic stress at this period in history.
    1. Re:striped? by RightSaidFred99 · · Score: 1

      Not if you're using DB level replication.

    2. Re:striped? by fuzzyfuzzyfungus · · Score: 1

      What I find curious about that statement is that it seems to imply that JBOD support is an application level feature, rather than being handled by the OS or disk controller hardware. Am I missing something, or has Exchange started to gobble up OS functions now?

    3. Re:striped? by Scott+Scott · · Score: 3, Funny

      Frankly, nearly every option I have ever heard containing the phrase "with Windows Server" has been a terrible idea.

    4. Re:striped? by Amouth · · Score: 1

      since exchange 2000 - it has replaced part of the file system i/o handeling in windows (for preformance reasons) i can only assume it is getting worse.

      --
      '...if only "Jumping to a Conclusion" was an event in the Olympics.'
    5. Re:striped? by ConceptJunkie · · Score: 3, Funny

      Am I missing something, or has Exchange started to gobble up OS functions now?

      You must be new to Microsoft products.

      --
      You are in a maze of twisty little passages, all alike.
    6. Re:striped? by h4rr4r · · Score: 0, Troll

      DB level replication does nothing about discs failing. Great you can go to another box, that probably has replicated the errors that failing drive introduced on its way out.

    7. Re:striped? by atamido · · Score: 1

      Database replication happens on write, not read.

    8. Re:striped? by meadowsoft · · Score: 2, Insightful

      This is not unique to Microsoft products. Databases have been doing this for a long time. Oracle Database has options for RAW devices and disk access, where redundancy is handled in the application layer by throwing more disks at the problem. You can also stack your layers of redundancy by using Oracle automated storage management to have multiple logical disks while at the same time using an array controller to provide a level of RAID redundancy at the physical layer.

      And a point about JBOD being useful for Exchange. In most Exchange environments I have worked with, replication happens at the appication layer, with huge portions of the data store being replicated amongst members of the Exchange Cluster, each with their own copy of the data. While expensive RAID/physical redundancy is a good idea, it is not critical as exact copies of the data store are available elsewhere in the cluster, and mailboxes can be failed over to those members.

      And for the people that want a full RDBMS or SQL Server under the hood of Exchange - this is primarily a performance concern. Exchange access to data stores has such a unique profile that ca be modeled to show specific performance profiles that would benefit from a customized data access layer, overall Exchange performance would be hampered by the inclusion of an RDBMS that was designed to respond to a multitude of performance profiles. When you have the luxury of understanding how your application accesses data, it is best to choose (or develop) the data storage subsystem that will reap you the best performance. Here is where I believe Microsoft has the right approach.

    9. Re:striped? by shutdown+-p+now · · Score: 1

      Am I missing something, or has Exchange started to gobble up OS functions now?

      You must be new to Microsoft products.

      A philosophical question, then: what's coming first - Exchange running in Emacs, or Emacs running in Exchange?

    10. Re:striped? by ConceptJunkie · · Score: 1

      For a serious and hard-core server product I don't think it's a problem either. I would see the Exchange product as being a server rather than something you install on the server. It's going to be on a dedicated system and it makes sense for MS to restrict to one version of Windows for the highest robustness. This isn't just some commodity component that is installed on your desktop.

      However, the initial comment is ironic given that practically every non-trivial Microsoft app ever written hooks into the OS at a level most people would consider unreasonable. In fact, that's how Microsoft gained and maintained their edge in the first place as has been well documented.

      --
      You are in a maze of twisty little passages, all alike.
    11. Re:striped? by David+Gerard · · Score: 1

      Microsoft: "We want all open source innovation to happen on Windows. In practice, Windows is too slow, and just putting Linux underneath the same software stack triples performance. So we're running the Windows versions of the software on Linux using Wine. We'll also be funding the Wine on Windows initiative."

      --
      http://rocknerd.co.uk
    12. Re:striped? by ConceptJunkie · · Score: 4, Funny

      A philosophical question, then: what's coming first - Exchange running in Emacs, or Emacs running in Exchange?

      My money would be on Emacs running a virtual machine on which you could install Exchange.

      --
      You are in a maze of twisty little passages, all alike.
    13. Re:striped? by fuzzyfuzzyfungus · · Score: 1

      Are you postulating the future existence of lisp.NET?

    14. Re:striped? by micheas · · Score: 1

      unfortunately firefox.exe under wine is faster than native firefox under linux.

    15. Re:striped? by Achromatic1978 · · Score: 1
      No other vendor would do such a thing. I mean every App Developer for the iPhone is able to background their app. It's not an Apple-only API, right?

      Oh.

    16. Re:striped? by ConceptJunkie · · Score: 1

      That hadn't occurred to me, but I bet it would be better than Java.

      --
      You are in a maze of twisty little passages, all alike.
  4. Blah by slaker · · Score: 2, Insightful

    I kind of like it when my mail server is, you know, just a mail server. Call me a nut but SMTP + IMAP do everything I need.

    --
    -- I wanna decide who lives and who dies - Crow T. Robot, MST3K
    1. Re:Blah by alen · · Score: 5, Informative

      there are these entities called corporations/companies. they are required to follow a lot of laws and in some cases retain all communications for many years. Exchange makes this easy because it centralizes everything for easier management.

      2010 looks more like 2007 R2. Same engine but more features and support for it's new ActiveSync partners, Google and Apple.

      the archiving and legal features look nice. right now you have to buy add on products from EMC and other companies. Integrating the SOX features into Exchange will save customers a lot of money.

    2. Re:Blah by RightSaidFred99 · · Score: 4, Insightful

      Yeah, but you're not a large corporation. Exchange does all kinds of crazy shit that's nice to have in a very large environment. Calendaring, extreme scalability, integration with other systems, mobile messaging integration, spam filtering, encryption support, voicemail integration, auditing compliance. etc... and etc... and etc...

      Exchange does a _whole_ lot of shit and integrates with other products that do a whole lot of other shit.

      So if you have 50 employees and 40 computers, Exchange might be overkill. If you have 40,000 employees, it might be exactly what you need.

    3. Re:Blah by ender81b · · Score: 2, Interesting

      The archiving feature alone really fixes a gap in Exchange server. Say what you will, but it's ridiculous that it doesn't have any archiving abilities (and no, localto workstation archiving doesn't count) that even remotely compare to notes.

    4. Re:Blah by adarn · · Score: 4, Insightful

      People underestimate how important Exchange is.

      The argument is always how Office is the real lynchpin and that if only a compatible document suite like Google docs or OpenOffice got a foothold Microsoft would be crushed but Outlook/Exchange is the REAL barrier to entry.

      I work at a call center. EVERY corporate employee who calls me is using Outlook except the 1% of poor souls stuck with Lotus Notes and Domino.

      Business relies on Outlook/Exchange.

    5. Re:Blah by drinkypoo · · Score: 2, Interesting

      there are these entities called corporations/companies. they are required to follow a lot of laws and in some cases retain all communications for many years. Exchange makes this easy because it centralizes everything for easier management.

      So does a server with SMTP+POP+IMAP+Jabber.

      SOX requires you to disclose certain things, and to have policies in place to allow you to disclose certain other things on demand. In terms of SOX compliance, there are no serious barriers in your way when rolling a solution from FoSS; indeed, such a solution is provided for you turnkey if you like, by purchasing it from Red Hat or perhaps from IBM.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:Blah by alen · · Score: 1

      do the FOSS solutions include failover, replication, archiving, integration with your company's telephone system and a long list of other features?

      say you are a 5000 person company and NYC loses electricity again and you have 3000 people in other states that still need to work. with exchange 2007 and later you replicate your mail to a standby server.

      It's like the IPhone. the basic parts of a phone are mature like calling, address book, voice mail, etc. it's the apps that make the iphone a killer phone

      same thing with exchange. email, calendar and other features are mature. it's features like replicating your email to another city for failover that are killer features now. along with archiving and other legal requirements that are built into the box

      if there is a disaster than POP and IMAP are useless and can result in lost data. today if you have a failover you can just check your email on your phone if your PC loses power

    7. Re:Blah by drinkypoo · · Score: 1

      do the FOSS solutions include failover, replication, archiving, integration with your company's telephone system and a long list of other features?

      Yes.

      if there is a disaster than POP and IMAP are useless and can result in lost data.

      If there is a disaster, you're fucked, because you're stupid. POP and IMAP are protocols. Bad implementations lead to lost data.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    8. Re:Blah by alen · · Score: 1

      so which FOSS solution includes all the legal features, DR, and mobile functionality? with Exchange you just point your phone or blackberry to your mailbox and you've got mail. someone loses his phone, you just wipe it remotely over the cell phone network

    9. Re:Blah by Super_Z · · Score: 1

      As an aside, Companies that want extreme scalability go for products like Sun JES, CriticalPath Memova or simply Postfix/Cyrus/Apache/WebDAV. When you pass 500.000 users, you dont want a server that does "all kinds of crazy shit" - you want something that is rugged and easy to debug :-)

    10. Re:Blah by TheCabal · · Score: 3, Informative

      Exchange has had support for mailbox journaling for a while now. It's not a new feature. Maybe in 2010, they just prettied up the process.

    11. Re:Blah by mweather · · Score: 1

      What cell phon that supports exchange doesn't include a web browser to get to a webmail account?

    12. Re:Blah by ender81b · · Score: 2, Informative

      Mailbox journaling is not archiving.

      Here is what most people mean by archiving. On notes (and now exchange) there's a server side policy/program that runs and moves mail that meets a defined criteria (say.. mail that is over 6 months old) and copies them to a new mail file. The user's can then access their archive from inside the client or via the web by clicking on a link or something and it takes them right to it.

      It's really nice from a system administration perspective as it keeps mail file sizes down (increasing performance) on your main servers and you can use a series of low cost/lots of disk space servers as archiving servers as most people will only go into their archive once or twice a year so the load is very low.

    13. Re:Blah by Super_Z · · Score: 1

      OSS solutions like Zimbra, eGroupware, Open-Xchange, SOGo and Citadel all do most of the stuff Exchange does (except the MAPI part). AFAIK none of them has built-in site failover functionality but most of them support a HA setup.

    14. Re:Blah by ender81b · · Score: 1

      Because using the web on a cell phone is SO EASY compared to a built in messaging/calendaring application.

    15. Re:Blah by Anonymous Coward · · Score: 5, Insightful

      This kind of misses the point. In many cases of Microsoft products, you could weave and configure together a bunch of FOSS applications to do the same thing. But then you'd have a custom solution that only your now-very-valuable admin understands. On the other hand, Exchange is a one stop shop for all this stuff, and the admins are pretty much interchangeable, since the product is the same.

      Mail servers for large corporations are not just, well, mail servers. For a 200 person shop, full Exchange is definitely overkill (which is why there's multiple versions you can buy). For a 300K person company, it worth the cost.

    16. Re:Blah by TheOtherChimeraTwin · · Score: 1

      do the FOSS solutions include failover, replication, archiving, integration with your company's telephone system and a long list of other features?

      Exchange doesn't do those things. At best, it has features that you would find useful in creating a complete solution. Just like FOSS. Either way, it takes a lot of hard work and expense to create a solid system that includes comprehensive DR.

    17. Re:Blah by Anonymous Coward · · Score: 0

      A nice 64 bit Ubuntu-server, with fast raid array of WD green disks, Getmail for pop3s, Dovcot as IMAP server, and Bacula for on and off-line backups, Thunderbird on the clients and the freedom to scale, extend or upgrade now and far into the future without being restricted by software cost or license agreements.
      A wonderful company email server is easy when you factor out Outlook and only use software that is intended to actually inter-operate well with other software.

    18. Re:Blah by Anonymous Coward · · Score: 0

      A nice 64 bit Ubuntu-server, with fast raid array of WD green disks, Getmail for pop3s, Dovcot as IMAP server, and Bacula for on and off-line backups, Thunderbird on the clients and the freedom to scale, extend or upgrade now and far into the future without being restricted by software cost or license agreements.

      I will quote a fellow AC who responded nicely to this sentiment:

      "This kind of misses the point. In many cases of Microsoft products, you could weave and configure together a bunch of FOSS applications to do the same thing. But then you'd have a custom solution that only your now-very-valuable admin understands. On the other hand, Exchange is a one stop shop for all this stuff, and the admins are pretty much interchangeable, since the product is the same."

    19. Re:Blah by cayenne8 · · Score: 1
      "Integrating the SOX features into Exchange will save customers a lot of money."

      I hear about SOX this and that, but, I don't know exactly what it requires of what types of companies.

      Can you tell me what SOX features are that Exchange will have and will help to do what?

      TIA

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    20. Re:Blah by alen · · Score: 1

      or i can just set up an iphone or winmo cell phone to use the integrated mail app to make life easier.

      the iphone allows access to the GAL over the cell network. and mobile safari works nicely with OWA since it's a full web browser.

      blackberry has BES which does not work with any of the FOSS solutions

      Google also licensed activesync so expect new android phones to have exchange integration as well.

    21. Re:Blah by alen · · Score: 1

      quick check shows they cost close to what exchange costs when you factor in migration and other costs. and they don't support all the features of exchange

    22. Re:Blah by Bill,+Shooter+of+Bul · · Score: 1

      As long as your FOSS solution was just properly configured well known applications, then I fail to see what the problem is. If they are writing their own solution in Erlang, then you have a point.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    23. Re:Blah by alen · · Score: 1

      the failover and replication in Exchange 2007. SOX auditors want to know what your business continuity plans are.

      for Exchange 2010 it will be the integrated legal and archiving features. part of SOX is having procedures in place to follow mail retention laws, deletion of email to prevent discovery in a lawsuit, etc.

      it's mostly processes that have to be followed so your auditors, CEO and CFO can go to jail if there is fraud in the financial statements. a lot of products have come out to help you be compliant, and MS is now integrating their features into Exchange 2010 instead of you buying separate products

    24. Re:Blah by cayenne8 · · Score: 1
      "deletion of email to prevent discovery in a lawsuit,"

      Ok, I can understand if you are deleting to prevent discovery, but, does it mandate how long or how you store email if you are NOT involved in a lawsuit?

      I'll go look it up myself some more, but, if you could give a quick answer. Or, does sox just say you have to have a policy and stick by it, but, doesn't mandate how long or how you keep emails?

      Again, thanks in advance

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    25. Re:Blah by atamido · · Score: 1

      If you have over half a million users, Microsoft is going to have a team ready to fly out if there is a problem.

    26. Re:Blah by David+Gerard · · Score: 1

      Yeah, Microsoft came up with Exchange's most important feature during the antitrust trials:

      "Oh, those emails? They got eaten when Exchange ate its entire database. Yes, again. So very sorry."

      --
      http://rocknerd.co.uk
    27. Re:Blah by adarn · · Score: 2, Insightful

      Umm....

      Collaborative calendaring? Ability to delegate rights for your calendar and inbox to other employees? (Admin assistants) Ability to book physical resources for your appointments?

      These are all mission-critical features for most medium to large businesses and as far as I've seen no open source solution comes close offering all the features of Outlook/Exchange. I'm sure some enterprising young lad might be able to hobble all the technology together but that is entirely different from having 1 product that just does the job - a hobbled together solution isn't going to take the enterprise by storm.

      Again, this is the stumbling block for Linux adoption in the enterprise. Word, Excel, Power Point interoperability means nothing without an Exchange replacement.

    28. Re:Blah by jonbryce · · Score: 1

      The webmail solution doesn't beep at me when an email arrives. I have to visit the site and check my mail. Outlook Mobile does, or I can look at the Today Screen and see how many unread mails I have.

    29. Re:Blah by BiAthlon · · Score: 1

      I think what you meant to say is that "If you have over half a million users, you're paying Microsoft enough money that they have people there fixing problems already."

    30. Re:Blah by jonbryce · · Score: 1

      When I last priced these solutions, they worked out a lot more expensive than Small Business Server for a comparable feature set.

    31. Re:Blah by atamido · · Score: 1

      Well, that's what I meant to imply. You're paying enough money that you don't debug the product, the vendor does. It's that way with most products at very large corporations.

    32. Re:Blah by jambox · · Score: 1

      Exchange may be great for managers and admins (I'm a developer so I couldn't say) but Outlook is sucky for users. For one thing it can reduce even a newish mid-spec PC to a dreadful crawl. Just switching windows to it can take several whole seconds. Also, if I know I've got an email from somebody a while ago but can't remember when, how long does it take to search or sort a gigabyte of emails? Much too long. I have to go off and make a coffee. Now I'm not necessarily suggesting it as a direct replacement but if I could only use my Google Mail for business then I'd save all sorts of time.

      --
      You thought you could break the laws of physics without paying the PRICE?
    33. Re:Blah by parityodd · · Score: 1

      Exhcange 2003/2007 could only Journel per database, i belive that exchange 2010 can journel per mailbox.

    34. Re:Blah by scurlaruntings · · Score: 1

      Yeah, but you're not a large corporation. Exchange does all kinds of crazy shit that's nice to have in a very large environment. Calendaring, extreme scalability, integration with other systems, mobile messaging integration, spam filtering, encryption support, voicemail integration, auditing compliance. etc... and etc... and etc...

      Exchange does a _whole_ lot of shit and integrates with other products that do a whole lot of other shit.

      So if you have 50 employees and 40 computers, Exchange might be overkill. If you have 40,000 employees, it might be exactly what you need.

      Exchange isnt even overkill for 5 users. If it was SBS wouldnt exist. There is no MTA that is even comparable or as easy to set up. That being said the world of an Email admin is entirely diffrent to pressing next next next on a wizard. There are very few SME's out there running dovecot/fetchmail/sendmail or Citadel Zimbra or Axigen over Exchange. The reason for this is support and ease of use. Its all well and good using OSS products but if your not up to speed on them nor have the skills in house its a nightmare. There is nothing wonderful about configuring .cf files manually or even recompiling Webmin to make your life easier.Exchange does an absolute excellent job and is by far the most versatile MTA out there. Wether 2010 is required just yet is debatable as there are massive diffrences between 2003 R2 and 2007. 2007 is the most complete MS MTA to date. Its a marvelous product that requires very little in the way of 3rd party bolt ons. Wether geeks here want to admit it everything has its place. MS may seem an expensive alternative but good consultancy ensures the company has the right product at the right price and with the right support and skills to manage it.

  5. But does it run... by rodrigoandrade · · Score: 2, Funny

    Oh nevermind :-)

    1. Re:But does it run... by Anonymous Coward · · Score: 0

      Let me guess... Windows? :)

    2. Re:But does it run... by sharkey · · Score: 1

      No, it does not run, it limps. It IS Exchange, after all.

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
  6. Spam To Be Canned By 2006 by gregg · · Score: 2, Funny

    No mention of junk mail in the article. I'm still waiting for Bill to deliver on his promise of a 'spam free world.'

    1. Re:Spam To Be Canned By 2006 by theSpitzer · · Score: 2, Interesting

      Get yourself a barracuda or two. I know our College's barracudas blocked 12 million emails last year and only let 2.5 million (ideally, legit ones) through. And we STILL get spam in our inboxefrom time-to-time. Awfully hard to catch when they embed their garbage in images as opposed to text.

    2. Re:Spam To Be Canned By 2006 by TheRaven64 · · Score: 1

      Yup, they're great. Email to my editor with my latest article? Clearly spam - in the bin with it. Another email from a journal telling me a paper had been accepted? Spam, throw it away.

      If your recipient is using Barracuda, send them an IM to let them know you've got an email, just to be on the safe side.

      --
      I am TheRaven on Soylent News
    3. Re:Spam To Be Canned By 2006 by theSpitzer · · Score: 1

      Its unfortunate that your experience has been so sour, to my knowledge it is EXTREMELY rare that our setup blocks legitimate emails. Sounds like poor implementation/administration. It's only going to perform as well as it is configured. There's quite the balancing act between "block everything" and "let everything though" Like I said, we still receive some spam. If we tightened our filters more we would probably start blocking more legit traffic as well. It will never be perfect.... but a couple million less spam emails is a good thing IMHO. -J

    4. Re:Spam To Be Canned By 2006 by TheRaven64 · · Score: 1

      This is on two separate installs (one on the incoming server for one of my email accounts, on at my editor's company), with two different sets of admins in two different countries. Having to clean a spam email out of my inbox every few days is inconvenient. Having important emails lost is much, much, worse. Having legitimate emails which have the same structure as other, legitimate, emails, which are not blocked, is completely unacceptable.

      --
      I am TheRaven on Soylent News
    5. Re:Spam To Be Canned By 2006 by atamido · · Score: 1

      A properly set up Barracuda spam filter will let users log in and see any emails to their address that have been blocked. You can then deliver the mail, and set up whitelisting options.

      I would rank our experience with Barracuda as "excellent". Your mileage may vary though as blocking conditions can depend a lot on how the administrator sets it up.

    6. Re:Spam To Be Canned By 2006 by aaron.axvig · · Score: 1

      I took 5 minutes and set up Exchange 2007 with Spamhaus's block list, zen.spamhaus.org I believe. Blocks 95%+ of spam, and I don't even try to hide my e-mail address. Went from ~90/day to 2 or 3.

  7. Worthless review... by iamhigh · · Score: 2, Insightful

    His first point is you can use it with FF and Safari. Nice, but not a really big deal to most admins.

    Then his second favorite feature is that you can do database level real time replication - you know, without having to know about all that REALLY hard stuff, like RAID, or what this SCSI crap is, or backups.

    --
    No comprende? Let me type that a little slower for you...
    1. Re:Worthless review... by rob1980 · · Score: 5, Insightful

      His first point is you can use it with FF and Safari. Nice, but not a really big deal to most admins.

      For sysadmins who want their users to stick with Firefox or something else not named Internet Explorer, an improvement to OWA may not be a huge deal but it's still nice. OWA on alternative browsers blows pretty hard. It works, but it blows.

    2. Re:Worthless review... by EvanED · · Score: 1

      RAID isn't replication, and it isn't backups. SCSI is just an interface for talking to disks. You really need something at a higher level to be able to get true replication. Backups can be it, but you need to be sure that you get a consistent image of the DB. If you just naively copy bytes, it's very easy to not get this. If you just naively lock the file while you back up, you kill Exchange. Doing something that isn't one of those things either needs COW support from the OS or it needs cooperation from the actual application (Exchange).

    3. Re:Worthless review... by omfglearntoplay · · Score: 1

      It's a big deal. I've been trying to get my users off IE without completely killing it, and this will be one good way to do so.

    4. Re:Worthless review... by drsmithy · · Score: 1

      Then his second favorite feature is that you can do database level real time replication - you know, without having to know about all that REALLY hard stuff, like RAID, or what this SCSI crap is, or backups.

      DB replication solves a completely different problem to "RAID", "SCSI crap" or "backups".

    5. Re:Worthless review... by lordandmaker · · Score: 1

      I've had more issues with people using FF or Safari from home, and asking me why they can't search their emails in OWA - it worked when I showed them on their desktop in the office (in IE).

    6. Re:Worthless review... by aaron.axvig · · Score: 1

      It was a source of quite a bit of complaining that OWA did not have a decent interface on other than IE6+.

  8. Exmerge by Kyn · · Score: 1

    But does it have Exmerge? Command lines are nice and all, but the biggest feature we miss as a small/medium sized business is the Exmerge utility.

    1. Re:Exmerge by nmb3000 · · Score: 2, Informative

      Exmerge has been depreciated for years, primarily due to it not supporting the new PST formats.

      In keeping with Exchange 2007's newfound love of PowerShell, you should use the Export-Mailbox and Import-Mailbox cmdlets to replace Exmerge.

      --
      "What do you despise? By this are you truly known." --Princess Irulan, Manual of Muad'Dib
      /)
    2. Re:Exmerge by Kyn · · Score: 1

      Yeah, that's what we do. However, we really miss the Exmerge GUI which let us see folder sizes and easily only export certain date ranges.

    3. Re:Exmerge by turbine216 · · Score: 2, Informative
      You really should read up on Exchange Powershell: export-mailbox -identity username -startdate MMDDYYYY -enddate MMDDYYYY -targetfolder foo -targetmailbox username (or if you're daring, you can specify a PST file). and for mailbox sizes:

      get-mailboxstatistics -identity username | select identity,totalitemsize

      You could even script the two together, to identify mailboxes larger than, say, 1 GB and then export items older than 180 days...

      $enddate = (get-date).AddDays(-180)
      get-mailboxstatistics -resultsize unlimited | where-object{$_.totalitemsize -gt 1GB} | export-mailbox $_.alias -enddate $enddate -targetmailbox foo -targetfolder bar

      Seriously, RTFM.

    4. Re:Exmerge by Poohsticks · · Score: 1
      Microsoft has committed to updating the Exmerge.exe tool specifically to support the Unicode PST format (20 GB limit) and should be releasing it this year.

      It's low on their priority list, but since most Exchange admins love this utility - they finally agreed to update it.

      http://msexchangeteam.com/archive/2006/11/28/431669.aspx

      --
      "The story so far: In the beginning the Universe was created. This has made a lot of people very angry and has been wide
    5. Re:Exmerge by Alioth · · Score: 1

      How is the date format in PSH determined? By the system's locale? It would have been nice if they settled on ISO format dates for all command line use...

    6. Re:Exmerge by turbine216 · · Score: 1

      powershell uses UTC with an offset for the locale; however, you can remove the offeset if you wish and retrieve UTC only; you can even apply unix-style formatting if you want.

      Powershell is pretty friggin awesome once you scratch the surface...

  9. non-outbreak client support? by Anonymous Coward · · Score: 1, Insightful

    Wake me when they release some kind of server-end support for clients like thunderbird/sunbird, evolution, etc. It shouldnt be the job of a major project like that to reverse-engineer MS's garbage.

    Or just publish the specs and comply to the related standards... but let's not ask for the moon AND the stars, eh?

    1. Re:non-outbreak client support? by bunratty · · Score: 3, Informative

      Just enable IMAP support on the Exchange server, and it will work with any IMAP email client.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    2. Re:non-outbreak client support? by ender- · · Score: 1

      Just enable IMAP support on the Exchange server, and it will work with any IMAP email client.

      Until you get a couple thousand emails in your mailbox. Then Exchange's IMAP server gets ugly and useless. At least that's been my experience.

    3. Re:non-outbreak client support? by mhall119 · · Score: 1

      They did publish the MAPI specs, which is why Evolution now supports Exchange without going through OWA.

      --
      http://www.mhall119.com
  10. so we're by nimbius · · Score: 2, Insightful

    bundling the operating system? thats what it sounds like if the OS is a requirement....bad move on the part of redmond to make this mandatory in a recession.

    this is the part where customers ask the question: if linux users dont have to install a new OS to get the latest mailserver/groupware...why the hell do i???

    --
    Good people go to bed earlier.
    1. Re:so we're by ConceptJunkie · · Score: 2, Insightful

      If you want what Microsoft offers, you have to play by their rules. If the product is good and the rules are not onerous, then there's no problem. Proprietary software, despite its drawbacks, has been a useful and successful means for delivering value for over 50 years.

      On the other hand, if the product is lacking and/or the rules are onerous, then you need to go with another vendor.

      As much as I love a chance to bash Microsoft, I really don't see this as being an "onerous" requirement, especially since it probably helps the poor schmoes who have to write and maintain the code (although that would certainly have been much more compelling when the likes of Windows 9x was the OS no longer being supported), which hopefully means more stable and robust software.

      If you are looking at the expense and effort to use Exchange, I imagine dropping another thousand (or whatever a Windows Server license costs these days) to upgrade the OS is pocket change in comparison to the Exchange licensing and dedicated hardware and support personnel you need to run the thing. We're not talking Office or IE here... or even SQL Server.

      --
      You are in a maze of twisty little passages, all alike.
    2. Re:so we're by mweather · · Score: 1

      I imagine dropping another thousand (or whatever a Windows Server license costs these days) to upgrade the OS is pocket change in comparison to the Exchange licensing and dedicated hardware and support personnel you need to run the thing.

      Sure, if training your employees on the new OS were free.

    3. Re:so we're by shutdown+-p+now · · Score: 1

      if linux users dont have to install a new OS to get the latest mailserver/groupware...why the hell do i???

      Try to install the most recent version of Postfix on, say, a Linux distro with 2.0 kernel, and get back to us when you manage to do that.

    4. Re:so we're by ConceptJunkie · · Score: 1

      Given the level of employee you would need to administer Exchange do you really think that's an issue? We're not talking about regular IT guys who can only successfully replace a mouse two falls out of three. You're already looking at training for the new Exchange. How much different can Server 2008 be from Server 2003? Anything relevant to the OS required to run Exchange 2010 would logically be covered by the training for Exchange 2010 itself.

      --
      You are in a maze of twisty little passages, all alike.
    5. Re:so we're by fat_mike · · Score: 1

      How many companies do you know (not counting Fortune 500) that actually follow Microsoft's upgrade path? We just adopted Server 2003 last year along with Exchange 2007.

      Wanna know why? Because we don't have the resources or pull with Microsoft to have been testing the betas years ago. We have to test once its released. Microsoft knows this, and they know that the majority of companies won't upgrade for a while because they know they'll get the software cheaper because Server 20XX and Exchange 20XX will be available.

      Fortune 500 companies upgrade to this new cutting edge software because they have to keep up the appearance of being ahead of the competitor. We've received a grand total of 57 email attachments that were of the Office 2007 format since it came out.

      I seriously think most of the posters on here are Linux Fanboys and/or level 1 helpdesk techs who have no clue what goes on above them.

    6. Re:so we're by Achromatic1978 · · Score: 1

      Wanna know why? Because we don't have the resources or pull with Microsoft to have been testing the betas years ago.

      You couldn't afford the $375 for the MSDN Empower program, which provides all that software, including betas? Hmm.

  11. OWA Support for Firefox and Safari by Knara · · Score: 1

    Finally. Sheesh. No reason why this couldn't have been implemented years ago instead of relegating them to OWA Lite.

    1. Re:OWA Support for Firefox and Safari by truthsearch · · Score: 1

      I saw OWA when it first came out. It was built with ActiveX. So there couldn't be FF or Safari support until it was completely rewritten. And then I'm sure there were compatibility issues as they focused on IE 6 support and less on standards.

    2. Re:OWA Support for Firefox and Safari by drinkypoo · · Score: 2, Insightful

      Finally. Sheesh. No reason why this couldn't have been implemented years ago instead of relegating them to OWA Lite.

      Yeah, no reason except that it's just one more reason why your desktops don't have to run Windows...

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:OWA Support for Firefox and Safari by FunkyELF · · Score: 2, Insightful

      I use OWA with FireFox on Linux.
      Its not all that rich but it works just fine. Don't know what this is all about.
      Are they going to make the experience the same for both IE and FireFox?

    4. Re:OWA Support for Firefox and Safari by JCSoRocks · · Score: 2, Informative

      The FF experience sucks in comparison to IE. The OWA experience is almost exactly like the application itself when you're using IE. In FF it's more like a bad version of Gmail. Sadly I'm forced to use IE for my banking and for OWA. That's it. I'm actually excited to see FF support coming down the road.

      --
      You are using English. Please learn the difference between loose and lose; they're, there, and their; your and you're.
    5. Re:OWA Support for Firefox and Safari by Knara · · Score: 1

      That was my point. FF and what not always worked, just in a way that was a significantly degraded workspace experience.

    6. Re:OWA Support for Firefox and Safari by Knara · · Score: 1

      Your corporate desktops typically don't use OWA, they use the full client. OWA is more for a quick remote solution to email that doesn't require additional corporate hardware. I guess you could use OWA as a primary, but it does lack somewhat in that capability.

    7. Re:OWA Support for Firefox and Safari by drinkypoo · · Score: 1

      I've definitely used both, and most people could get away using OWA. They might not be very happy about it, but it would do what they need to do. Of course, it's also true that most people could get away using one of the completely-FoSS solutions with a web interface, so I'm not sure what that proves except that Windows is becoming less relevant all the time.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    8. Re:OWA Support for Firefox and Safari by Anonymous Coward · · Score: 0

      I dunno, maybe from a strict technology-comparison viewpoint they're less relevant... but from a mind share and corporate implementation viewpoint, I think the fact that we continue to regularly license, and install, Outlook on every machine in just about every Fortune 1000 company means Microsoft is just as relevant as ever (if less sexy than it may have been in the past).

    9. Re:OWA Support for Firefox and Safari by Poohsticks · · Score: 1
      Yes - Microsoft has committed to updating OWA to provide equivalent functionality to IE with ActiveX (the full OWA experience) for both Safari and Firefox.

      http://msexchangeteam.com/archive/2006/09/13/428901.aspx

      There are a few differences listed in the article, but it is more uniform.

      --
      "The story so far: In the beginning the Universe was created. This has made a lot of people very angry and has been wide
    10. Re:OWA Support for Firefox and Safari by IDIIAMOTS · · Score: 1

      Exchange 2010 fully supports premium OWA experience in Firefox 3.x and Safari 3.x (on Mac). That includes HTML mail compose, drag & drop support and flashy UI.

    11. Re:OWA Support for Firefox and Safari by lordandmaker · · Score: 1

      I'm sure OWA from Exchange 03 in FF3.x was HTML?

  12. Decent OWA?! by nine-times · · Score: 3, Interesting

    Wow, it's kind of hard to believe, but there's actually something in this update that sounds like it'd be helpful. I think it's the first update to a Microsoft product in... I don't know... about 8-9 years where the update actually offers me something new that would actually be useful for me.

    For those who don't already know, the webmail that is built in to Exchange is actually fairly good, and is one of the early web applications to actually use something like AJAX to give you the feeling of using a desktop application. The only problem is that it has only ever really supported IE, and if you use any other browser, it reverted to a crappy version which was... ok. Not really very good, but yes, it worked.

    Anyway, it's possible that I may consider buying an upgrade someday!

    1. Re:Decent OWA?! by Anonymous Coward · · Score: 0

      IETab plugin in firefox filled that gap for me. I *hate* the crappy OWA version that non IE browser are forced to use. Luckly IEtab makes it so you can use IE inside firefox for specific webpages.

      It works great for the two pages I like better in IE (sharepoint and OWA)

    2. Re:Decent OWA?! by et764 · · Score: 2, Informative

      For those who don't already know, the webmail that is built in to Exchange is actually fairly good, and is one of the early web applications to actually use something like AJAX to give you the feeling of using a desktop application.

      I think OWA (or whatever it was called at the time) was actually the first AJAX application. A while back, I was talking with someone from the Exchange team, and he said the team developed the XmlHttpRequest object that makes AJAX possible for the purposes of making OWA.

      Unfortunately for Microsoft, no one really noticed until Google made GMail.

    3. Re:Decent OWA?! by nine-times · · Score: 1

      I believe that's true, but I wasn't sure, so I just said "one of the early web applications".

    4. Re:Decent OWA?! by benjymouse · · Score: 4, Informative

      ..., and is one of the early web applications to actually use something like AJAX to give you the feeling of using a desktop application.

      More aptly, is was THE first AJAX application. It doesn't get earlier than that.

      This was years before it got its spiffy name. XmlHttpRequest (the linchpin in AJAX) was invented by Microsofts email client team to support Outlook Web Access. Being invented for IE it was (and still is AFAIK) a COM object which could be created from JavaScript in the browser. Mozilla later copied the idea and made XmlHttpRequest a first class citizen, but kept the name. The rest is history.

      --
      Reading slashdot one-liner: (irm http://rss.slashdot.org/Slashdot/slashdot).rdf.item | fl title,desc*
    5. Re:Decent OWA?! by Anonymous Coward · · Score: 0

      Bullshit.
      It may have been the first /mainstream/ AJAX application, but it wasn't the first.

      The "ajaxified" version of OWA was included with Exchange Server 2000, released November 29, 2000.

      http://webfx.eae.net/webboard/images/webboard.gif

      Erik and Emil were pioneers when it came to DHTML and pre-AJAX AJAX.

  13. Will it work nicely with Thunderbird? by jkrise · · Score: 2, Insightful

    Exchange Server 2007 gave the bird to Thunderbird. Will Server 2010 support Thunderbird or Seamonkey? Or will Linux desktops be second class citizens in an Exchange Server corporate setup?

    That's the only feature of interest to me...

    --
    If you keep throwing chairs, one day you'll break windows....
    1. Re:Will it work nicely with Thunderbird? by ejdmoo · · Score: 2, Informative

      Exchange works great with IMAP, even if it doesn't exactly follow the delete/expunge model of deletion (but then again, neither does Gmail).

      I've used Thunderbird with Exchange 2007 with no problems.

    2. Re:Will it work nicely with Thunderbird? by bunratty · · Score: 3, Insightful

      Exchange works with any IMAP email client, but the email admins need to manually enable IMAP on the Exchange server. The question I ask is, "Will Thunderbird 4 or SeaMonkey 3 support Exchange's default MAPI protocol?" That way, Mozilla email clients can work with any Exchange server. Then individual users can easily migrate away from Outlook without the prior consent of the email admins.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    3. Re:Will it work nicely with Thunderbird? by jkrise · · Score: 1

      I've used Thunderbird with Exchange 2007 with no problems.

      I don't believe this. With Thunderbird, Exchange 2007 simply refuses to work at all. The reason I tried using Thunderbird was to compose HTML mail on Linux desktops, and it was a miserable failure. OWA Lite is a very poor buggy cousin of OWA which works even on IE6, but not on FF3!

      --
      If you keep throwing chairs, one day you'll break windows....
    4. Re:Will it work nicely with Thunderbird? by h4rr4r · · Score: 1

      When MS publishes the whole MAPI spec in a useful way they will.

    5. Re:Will it work nicely with Thunderbird? by alen · · Score: 1

      maybe the old MAPI versions. every product cycle MS improves MAPI and adds more features

    6. Re:Will it work nicely with Thunderbird? by ejdmoo · · Score: 3, Insightful

      Perhaps IMAP was not enabled in that Exchange setup...it definitely works, though.

      However, to answer your original problem (Firefox and HTML mail), Exchange 2010 does support Firefox (and Safari) using all the features of OWA that IE does, including HTML mail compose.

    7. Re:Will it work nicely with Thunderbird? by jkrise · · Score: 0

      Exchange works with any IMAP email client, but the email admins need to manually enable IMAP on the Exchange server.

      This has to be done on a per-mailbox basis and cannot be done system-wide. But even if IMAP is enabled, Exchange 2007 breaks with Thunderbird, but works well with Outlook Express however. It does indeed appear that Thunderbird was broken beyond repair with 2007.

      The question I ask is, "Will Thunderbird 4 or SeaMonkey 3 support Exchange's default MAPI protocol?" That way, Mozilla email clients can work with any Exchange server.

      MAPI is a proprietary API and it is nonsensical to expect Mozilla to support MAPI. It is like asking Blender to move away from OGL to work with the Direct X 10 quicksand. Working with proprietary protocols has never benefitted the users, and keeps them fragmented and divided for ever. It will soon resemble the messy multiple .doc and .docx saga we are seeing with Office. Which MAPI will Mozilla support? What if the API changes without notice, in a Service Pack, breaking it yet again.... the worls is better off supoporting IMAP than MAPI.

      --
      If you keep throwing chairs, one day you'll break windows....
    8. Re:Will it work nicely with Thunderbird? by bunratty · · Score: 1

      Evolution supports MAPI. I suppose you can be an idealist and say that FOSS should not support proprietary protocols, but in my opinion that policy just drives users away from FOSS products. I also think it's good that OpenOffice can open .docx documents. It would be the death of OpenOffice if it couldn't.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    9. Re:Will it work nicely with Thunderbird? by turbine216 · · Score: 3, Insightful

      Who is modding this guy up?

      IMAP is enabled on ALL MAILBOXES in Exchange 2007 by default. You just have to configure a few settings and enable the service. You can also disable IMAP globally.

      To answer your previous assertion that Thunderbird doesn't work - you're wrong again. Our user base uses Thunderbird extensively. Like many universities, we used to push Eudora, waaaay back before we moved to Exchange 5.5, and a lot of professors liked Eudora enough that they will never use Outlook. Thunderbird is the most suitable replacement for Eudora that we've been able to identify. It works great with or without SSL encryption, using POP or IMAP.

      So seriously, you very obviously don't have a clue. Please stop with the misinformation.

    10. Re:Will it work nicely with Thunderbird? by turbine216 · · Score: 1

      To further address your concerns about client compatibility...

      Instead of using MAPI, which is admittedly a flawed and convoluted protocol, many mail clients are being developed to take advantaged of Exchange Web Services. The Mail app that ships with most versions of OS X uses IMAP to fetch mail from Exchange, and Exchange Web Services to work with the calendar. I believe that Evolution does something similar.

      In the future, you'll see these same clients start to use EWS for mail as well. The newest version of Entourage will use EWS exclusively when dealing with Exchange servers (until recently, it used a MAPI implementation).

    11. Re:Will it work nicely with Thunderbird? by Dan+Ost · · Score: 1

      Evolution supports MAPI.

      Really? I thought it scraped the webmail interface.

      --

      *sigh* back to work...
    12. Re:Will it work nicely with Thunderbird? by turbine216 · · Score: 1

      You're both correct, sort of.

      Evolution uses Exchange Web Services to gather calendar data, and IMAP for messages.

      There is, however, a MAPI add-on available, but the last time i checked it only worked with Exchange 2003. The IMAP+EWS combination works well, and is implemented in other mail applications - for example, the Mail app that comes with OS X.

    13. Re:Will it work nicely with Thunderbird? by prefect42 · · Score: 1

      No, Exchange 2007 does not work with any IMAP email client. For that, it'd have to properly implement the IMAP spec.

      You know, little things like reporting the correct RFC822.SIZE, returning useful content encodings for rfc822/message attachments, doing searches on email addresses on more than just the display name component, searching across multiple mailboxes properly, not crashing in a huge heap when users with slightly odd AD accounts connect...

      Mmm what other things is it crap at. It doesn't supported the "Forwarded" flag for messages, which is impressively crap.

      --

      jh

    14. Re:Will it work nicely with Thunderbird? by Anonymous Coward · · Score: 0

      The question I ask is, "Will Thunderbird 4 or SeaMonkey 3 support Exchange's default MAPI protocol?"

      No, the question is: Will Microsoft ever make an open protocol with published standards that others could then easily use besides OUTLOOK? And then don't BREAK that protocol with different versions of Exchange...

    15. Re:Will it work nicely with Thunderbird? by homesnatch · · Score: 1

      I've definitely used Thunderbird IMAP with Exchange 2007... Had to muck with the secure connection settings in TB to make it work.

    16. Re:Will it work nicely with Thunderbird? by dotancohen · · Score: 1

      Exchange Server 2007 gave the bird to Thunderbird. Will Server 2010 support Thunderbird or Seamonkey?

      One could only assume that it will give the monkey to Seamonkey.

      --
      It is dangerous to be right when the government is wrong.
    17. Re:Will it work nicely with Thunderbird? by Anonymous Coward · · Score: 0

      That's a stupid question. They have no reason to care. After all, the only thing that seems to make a specification "open" is that some organization other than Microsoft came up with it. Totally arbitrary hippie bullshit.

    18. Re:Will it work nicely with Thunderbird? by Anonymous Coward · · Score: 0

      Thunderbird, no. Thunderbird is designed as predominiately an email client using IMAP/POP3 and does not have the calendar/task or other folder features.

      Evolution on the other hand has a new MAPI connector (currently in the Fedora 11 Rawhide Beta) which enables full compatibility with all exchange features.

    19. Re:Will it work nicely with Thunderbird? by TheSkyIsPurple · · Score: 1

      > The question I ask is, "Will Thunderbird 4 or SeaMonkey 3 support Exchange's default MAPI protocol?" No they won't... and they really don't need to. Use Web Services (EWS), like the new Beta Entourage client is doing, and like the new window clients are using (for OCS, etc)

  14. Concatenation a feature?!?! by Fishbulb · · Score: 1

    JBOD support lets you concatenate disks rather than stripe them into a redundant array

    Uh, WHAT!? Seriously, Microsoft? You're selling concatenation as a feature?

    Anyone who thinks concatenation is a good thing, much less better than striping, needs to have whatever certifications they bought revoked.

    1. Re:Concatenation a feature?!?! by TopSpin · · Score: 2, Interesting

      Anyone who thinks concatenation is a good thing, much less better than striping...

      Concatenation, by itself, would certainly be unwise. I'll give Exchange admins the benefit of the doubt and assume this "concatenation" is in addition to whatever redundancy features are provided.

      From the story:

      JBOD support lets you concatenate disks rather than stripe them into a redundant array

      I find that statement confusing. Why is Exchange, a mail server/collaboration platform/etc., managing storage devices? Is the story conflating Windows Server 2008 features with Exchange, or is Exchange directly responsible for storage devices (like Oracle ASM)?

      --
      Lurking at the bottom of the gravity well, getting old
    2. Re:Concatenation a feature?!?! by Scott+Scott · · Score: 1

      Uh, WHAT!? Seriously, Microsoft? You're selling concatenation as a feature?.

      You seem surprised. Did you entirely miss the release of Vista or something?

    3. Re:Concatenation a feature?!?! by Sandbags · · Score: 3, Insightful

      You misread... That's for the REPLICATED copy. i.e. You keep your live database on RAID 1/0, but you keep the realtime replicated copy on JBOD. With EXCH 2007 microsoft began (for very good reasons) recomending DAS instead of SAN (due to application and database high availablility features of Exchange 2007). Now, half of your DAS modular array units don't require expensive controllers, further reducing your costs without detracting from availability. Since the server fron end no longer needs to be a microsoft Cluster as well, Enterprise Server is no longer a requirement either.

      We recently deployed a 20K user solution under Exch2007. We lobied for a modular extensible DAS storage solution, but instead upper management insisted on big iron SAN chassis (2 of them). We spent $450K on disks where we could have spent less than 100K and had the same performance and reliability simply because upper management (and apparently you) have not read or do not understand the new database architecture proposed in Exchange 2007. 2010 improves upon that by removing some server side hurdles while maintaining the same data reliablity.

      You're keeping 2-3 local, active, asynchronously replicated (with real time log rollback) copies of your exchange system, with 30 second or less automatic failover that does not disconnect users in the process. Why keep them all on RAID 10 if you can simply fail from one over to the other? The only reason to keep any 1 of them on RAID 10 is simply to keep from failing over the first time! (and you'll recover and be back on the RAID 10 in 24-48 hours and you still have redundancy in log shipping, offsite server replication, and traditional backups to supplement that, all without clusters!

      --
      There is no contest in life for which the unprepared have the advantage.
    4. Re:Concatenation a feature?!?! by drsmithy · · Score: 1

      With EXCH 2007 microsoft began (for very good reasons) recomending DAS instead of SAN (due to application and database high availablility features of Exchange 2007). Now, half of your DAS modular array units don't require expensive controllers, further reducing your costs without detracting from availability.

      If your "backup" (/disaster recovery) server doesn't have the same IO capabilities as your primary (which, presumably, it has because it needs them to support your userbase), then it is inadequate as an alternative server.

    5. Re:Concatenation a feature?!?! by ill1cit · · Score: 1

      Err only if management has mandated that the DR solution has to provide the same performance as the production server. In reality only big corps with lots of money to burn mandate this. Most companies will accept continuity at reduced performance in a DR situation. So you inadequate line is quite simply a load of crap (it might be true for the company you work in, but assuming that your companies policies are how the entire business world works is just a little retarded).

  15. Cool feature: Phone call rules by Com2Kid · · Score: 3, Funny

    You can setup rules for phone calls. Freaking awesome.


    if (Status == b0rking_hot_secretary)
    {
        if (caller.phonenumber == contacts.wife.phonenumber)
            call.redirect("/dev/null");
        else if (caller.phonenumber == contacts.otherHotSecretary.phoneumber)
            Send3WayInvite(caller);
    }

    But in all seriousness, it'll be nice to have a rule that auto-directs calls to my cell when I'm out of the office.

       

  16. Horrible Application Platform by Doc+Ruby · · Score: 2, Interesting

    I joined an MS consultancy in 1998 because they were supposedly the foremost developers in NYC of MS Exchange applications. Once I settled in, they told me they were expert enough in Exchange as a platform to know never to develop any apps on it, because it was so awful to develop for and to support. A piece of crap. I've never seen any evidence since then that Exchange got any better as an app platform.

    Any clue as to whether the 2010 version will be any better? If it were, I'd expect Outlook/Exchange to take over the Internet. But that was possible over a decade ago, and MS totally blew it since then.

    --

    --
    make install -not war

    1. Re:Horrible Application Platform by TheCabal · · Score: 2, Informative

      Big difference between Exchange 5 and Exchange of today. I've had issues with Exchange 5.5 servers and their quirkiness. I've also been running Exchange 2003 clusters that have been absolutely rock solid and almost completely bulletproof.

    2. Re:Horrible Application Platform by Doc+Ruby · · Score: 1

      I'm not talking about their stability in their "out of the box" featureset operation. I'm talking about APIs, programmability, etc, as an app platform. I don't see many Exchange apps built on an Exchange platform, so I'm guessing everyone realized it wasn't really an app platform, despite MS pitching it to developers that way.

      --

      --
      make install -not war

    3. Re:Horrible Application Platform by Anonymous Coward · · Score: 0

      ... almost completely bulletproof.

      This represents a level of penetration testing above and beyond anything we do at our outfit.

    4. Re:Horrible Application Platform by turbine216 · · Score: 1

      Exchange isn't an applications platform, and isn't billed as such. It's Groupware, period, full stop.

      That's not to say that Exchange 5.5 wasn't billed as an apps platform, but that was 10 years ago. Things change, and your anecdote from 1998 can't possibly be expected to reflect the current state of affairs.

      For what it's worth, Exchange can interact with external applications through the use of the Exchange Web Services API, which is a little difficult to grasp at times, but it's well documented on MSDN. We've developed several custom applications around the calendar interface in very short periods of time.

    5. Re:Horrible Application Platform by atamido · · Score: 1

      I'm not sure I follow what you're talking about. What kind of "app" would one build on the Exchange platform? As far as I knew, it was a database for storing emails, contacts, and calendar information.

    6. Re:Horrible Application Platform by Doc+Ruby · · Score: 1

      It's a collaboration server. And the messaging/DB infrastructure is exactly what all kinds of productivity apps are built in, usually from scratch instead of in a server. Exchange is supposed to be like a webserver for PIM data among org populations. But instead it functions more like what you said, a messaging DB, because MS failed to deliver its app platform in a way usable by developers.

      --

      --
      make install -not war

    7. Re:Horrible Application Platform by Doc+Ruby · · Score: 1

      "Groupware" is a class of applications. Evidently MS just stopped promoting Exchange as an app platform, rather than make it work, and everyone's given up on the original architecture. Too bad, because groupware servers are good places to run apps, just as webservers are with their own native data and transaction/session model.

      --

      --
      make install -not war

    8. Re:Horrible Application Platform by Thumper_SVX · · Score: 1

      For client-side API dev, you've got WebDAV in the OWA. To all intents and purposes the Outlook client is really just a WebDAV client that happens to cache stuff locally.

      For server-side, you have Powershell, which actually gives you a very effective command line / API into the back end. As I understand it, the Exchange Management Console is in fact just sending Powershell commands behind the scenes... it just puts everything in a pretty (????) interface.

      Basically in other words, yes... you could replace every admin tool and front end with your own quite simply, just maintaining Exchange on the back end. I've done some basic tool creation for administration since that's my work focus... but I know plenty of people who've written stuff using WebDAV to Exchange backends.

      The only thing I find a true negative is that although you can program WebDAV from a non-Windows client, so far Powershell for Linux / BSD does not appear to be forthcoming. :)

  17. MAPI/CDO by wandazulu · · Score: 2, Interesting

    These were depreciated in Exchange07, and I'm presuming that they're still depreciated, but not altogether gone (in 07 you had to install them manually).

    There's still a lot (okay, well, some) that depends on MAPI and CDO being available in Exchange.

    1. Re:MAPI/CDO by will_die · · Score: 1

      Just because you have to manually install does not mean Microsoft has deprecated it.
      Starting with recent products they are now taking the stance of just installing the very basic items by default and if you want anything else you have to install it.

    2. Re:MAPI/CDO by turbine216 · · Score: 3, Informative

      I think you've muddled the MAPI client and MAPI protocol together, so i'll clarify for you: MAPI as a client access method (ie the MAPI protocol) is built-in, and turned on by default. For Outlook clients who are on the same network as your Mailbox server(s), this is the default connection method. The MAPI client bits, however, are not included in Exchange server anymore. Really the only thing that i've found that this affects is the ability to export mail to a PST when working directly on a mailbox server. It's been replaced by a number of powershell commands (export-mailbox, import-mailbox), and can still be done on workstations with Outlook installed (because the MAPI client bits are part of Outlook).

    3. Re:MAPI/CDO by danomac · · Score: 1

      Some backup suites are also dependent on these client bits... Backup Exec comes to mind.

    4. Re:MAPI/CDO by turbine216 · · Score: 1

      Agreed, but the MAPI/CDO client package is available as a free download. It's generally listed as a prerequisite for any application that requires it.

      Not that much of an inconvenience, really.

  18. ever used a calender? by spectrokid · · Score: 1

    I get an invite for a meeting and click "accept". (first and only mouseclick) It auto-syncs to my phone and 15 mins before the meeting, I get reminded of topic and room number. Ever tried that with SMTP?
    Most big corporations will pump their outgoing mail through a real SMTP server before letting it loose on the net, and use a real SMTP to filter the incomming turdstream before it is allowed to hit Exchange though. And as far as standard complience goes, well I can send and receive VCards and VCals in Outlook/Exchange, try THAT in GMAIL...

    --

    10 ?"Hello World" life was simple then

    1. Re:ever used a calender? by TheRaven64 · · Score: 3, Interesting

      I'm fairly sure OpenGroupware.org (or, SOGO, at least) supports everything you've described, and does so via open protocols like CalDAV, IMAP, SMTP, LDAP, and so on.

      --
      I am TheRaven on Soylent News
    2. Re:ever used a calender? by mlts · · Score: 2, Insightful

      Exchange has evolved a lot. Take Exchange 2007 for example. On an internet-facing server, it is quite easy to enable anti-spam rules. Even better, they get updated weekly directly from MS. You can also add your favorite antivirus utility (you will end up paying "enterprise prices for it) to scan incoming and outgoing mail for CYA reasons. You also can add server to server connectors between companies so E-mail between your company and a customer never touches the Internet in the clear.

      There is one thing I do wish Exchange 2007 had built in, and that would be some sort of application level backup mechanism for mailboxes. As of now, if you want to back up users, you will need to spring for a third party utility such as Backup Exec, Retrospect, or Microsoft's own Data Protection Manager.

      Maybe the suggestion of making the backend of Exchange a SQL Server database is a good one. This way, mailboxes can be handled with the ton of DB tools available.

    3. Re:ever used a calender? by mhall119 · · Score: 1

      If you point your desktop and phone to the same CalDAV calendar, then you get exactly the same functionality as you described.

      And VCard and VCal are very well supported in FOSS products, have been for quite some time. I'd be surprised if GMail didn't know how to handle them.

      --
      http://www.mhall119.com
    4. Re:ever used a calender? by ion.simon.c · · Score: 1

      Is this what you mean by VCal?
      http://en.wikipedia.org/wiki/VCalendar#vCalendar_1.0

      IIUC, GPG public keys have all of the features of VCards. There's also a global distribution network that's dedicated to hosting them... say bye-bye to requests to "email me your credentials", or getting someone's VCard as an attachment to every damn email that they send. :D

    5. Re:ever used a calender? by alen · · Score: 1

      looking at the website it doesn't

      no mobile phone support with the ability to manage devices over the air. seems they only offer Palm support.

      for the rest of the features don't see anything about replication or failover ability to a DR site. and nothing about archiving policies or any of the new legal features Exchange now supports. sure you can hire an admin to do it manually, but that is extra money. Around $100,000 per year if you include salary, taxes and benefits. and is there a backup agent for it? Every major backup software has Exchange agents for online backups, restores, etc.

    6. Re:ever used a calender? by vux984 · · Score: 1

      I'm fairly sure OpenGroupware.org (or, SOGO, at least) supports everything you've described, and does so via open protocols like CalDAV, IMAP, SMTP, LDAP, and so on.

      Sure, but Exchange actually works.

      Seriously. As bad as exchange is, its miles ahead of the competition if you go beyond the most basic features.

      So if you want to say something snarky like "exchange actually works, for small values of 'works'" I'd agree... but sadly the open options work for even smaller values of 'work'.

  19. This is why I love slashdot! by Anonymous Coward · · Score: 0

    Man Exchange is AWESOME! The only thing I love more is Lotus Notes.

    Thanks, slashdot, for bringing this important and interesting update to my attention. Truly, news for nerds, stuff that matters.

  20. Get off my lawn! by Anonymous Coward · · Score: 0

    Everyone should use PINE to read email and lynx to browse the web.

    Of course, real men just telnet to the port and issue commands directly, then base64 decode the results in their head.

    In all seriousness though, if all you want is e-mail and you're not managing thousands of users then exchange is overkill.
    Exchange only gets sexy when you team it with outlook and use the more advanced features.

  21. Re:It Figures by Anonymous Coward · · Score: 0

    ...

    Good idea. Blame the company making the server you're favorite client can't keep up with. ...or you could just create an OSS version of exchange server.

    Isn't that one of the major benefits of OSS? (or is it just another excuse for you to whine about commercial software?)

  22. Re:Cool feature: Phone call rules by Windowser · · Score: 1

    But in all seriousness, it'll be nice to have a rule that auto-directs calls to my cell when I'm out of the office.

    You can do that with Asterisk and some imagination

    --
    Avoid the MS tax, always buy I.B.M. PC's (I Built-it Myself)
  23. Depreciation by Petersko · · Score: 2, Funny

    "These were depreciated in Exchange07, and I'm presuming that they're still depreciated...i>

    Yeah, I hear MAPI and CDO lose 40% of their value the first time you use them. Never treat them as an investment.

  24. db has changed by Cr0t · · Score: 0

    the DB has changed, which means you have to upgrade your Backup software.... if it's even supported yet.

  25. Really MS?? How about fixing 2007 first? by Electric+Eye · · Score: 3, Informative

    Honestly. The adoption rate of Exchange 2007 was LOW and slow. Even when SP1 was released (after almost a year delay, btw), we're still stuck with this shitty command line interface that USED to be GUI to do all sorts of fun admin things in. It's a royal PITA to administer. How about an SP2 that will fix seemingly dead issues like OWA support for other browsers, etc? If MS thinks we and other companies that just spent thousands of dollars on the "bleeding edge" 2007 are going to pony up for 2010, they've got a surprise waiting. This is incrtedibly insulting.

    I guess Ballmer realized how shitty everything was the company has done over the past 2-3 years since he took over and decided to move on.

    1. Re:Really MS?? How about fixing 2007 first? by h4rr4r · · Score: 2, Informative

      Moving to command line sounds like doing it right, someone at MS must have wised up. Try automating stuff like real admins do.

    2. Re:Really MS?? How about fixing 2007 first? by Spad · · Score: 1

      Adding command line functionality for automation and scripting = Good

      Removing existing functionality from the GUI, adding it to the command line and making it *horrible* to work with = Bad

      Message Tracking in Exchange 2003 was very good & GUI based, especially if you had a lot of servers. Message Tracking in Exchange 2007 is virtually a lost cause if you have a lot of servers unless you want to write Powershell essays to gather, filter, process and output the tracking logs from disparate servers in a usable format.

    3. Re:Really MS?? How about fixing 2007 first? by Thumper_SVX · · Score: 1

      As I understand it, the Exchange Management Console (the GUI) was a bit of an afterthought with Exchange 2007. Everything was intended to be done with Exchange Management Shell (Powershell). I think the only reason we didn't see more GUI functionality was because the Devs built the entire GUI on the Powershell, but I suspect ran out of time since they were coding to a deadline. That's why we've seen constant, incremental improvements in EMC since release.

      Me? I architected, built and now do some maintenance on an Exchange 2007 system that supports all of our North American users... and I like it. It's a far cry from Exchange 2003, which I hated working with beyond VERY basic management. With 2007 I do most of my stuff through EMS instead of EMC because I'm comfortable with a command line. What can I say? I'm a UNIX geek. I've created a bunch of scripts that I can run any time to do just about anything I would need to do on a daily basis. And when I encounter something I've never done before... I create a script for that too just in case it comes up again.

      Using EMS I was able to create a pretty quick and dirty web page in ASP for my users so they could do their own message tracking. I took away the necessity for them to call Helpdesk because they can just hit the Intranet, click a link and then provide it basic information about the email. It collates all that info from our numerous Hub Transport servers and then returns the results, allowing them to drill down further and (if it's queued) find out why.

      No, Exchange 2007 is not made for the single-server environment. In fact I've recommended at least one friend of mine that they wait for 2010 because 2007 is really designed with the enterprise in mind.

      Now, having said that I might also point out that generally those companies that HAVE migrated to 2007 are on ELA's (Enterprise License Agreements). We have an ELA for all of our software, and when 2010 is released we just go to our fulfillment site and download the ISO's. It costs us nothing more than we already pay... and we don't pay for the server... we pay per user. So it doesn't matter if we have one Exchange server per user, it'll still cost us the same (though mail routing would be a nightmare :) ) We won't pay for Exchange 2010 any more than most Enterprises will... we'll pay our user CAL as we've always done and just stand up the instances we need to support our user community.

      The only cost to the ELA is that every few years I have to run reports on the licenses / CALs we've used... but having a good SCCM (SMS) infrastructure makes that a simple matter of dumping those reports to an Excel file and emailing it back to our rep.

      YMMV... but I suspect I'll be asked to start testing Exchange 2010 sometime later this year with a prod rollout probably mid 2010.

    4. Re:Really MS?? How about fixing 2007 first? by Thumper_SVX · · Score: 1

      Message Tracking in Exchange 2007 is virtually a lost cause if you have a lot of servers unless you want to write Powershell essays to gather, filter, process and output the tracking logs from disparate servers in a usable format.

      Heh... and if you're a halfway decent ASP coder, then it's easy to do that. Just have it parse out the Exchange HT servers found in Active Directory, collate those logs in RAM (or temporary file, your pick) and then process with some basic text manipulation tools. Voila :) I did it in an afternoon and put a nice (?!?!?) web front end on it for my user community.

      And if you want it to be faster at the collection and collation, then an earlier version of my program did "log shipping" in that it would take a copy of the latest log files once every 30 minutes and keep them on the reporting server. This turned out to be unnecessary because the time it took to collect the log files was actually pretty short since most of our Hub Transport servers were in our collo facility that forms the hub of our network, and I could just put the reporting server there.

  26. Re:Cool feature: Phone call rules by Com2Kid · · Score: 1

    Not at my workplace from within Outlook. :)

  27. Backup, Replication and Archiving by flaky2 · · Score: 1

    I work at a company with 2000 employees, many using mobile clients, with a pretty high turnover rate and a need for long term archiving. We rely on email for almost all of our communication, handling an average of 1,000 messages per hour, peaking at 15k per hour, pushing an average of about 250 kbits per second.
    We use a combination of qmail, squirrelmail and Courier IMAP for mail, with our users trained to store older messages locally if they need them past one year.

    What benefits (aside from calendaring) would we see from Exchange?

    Messages older than a year are stored zipped on a disk array and tape. Since they use Maildir, they are easy as pie to view or restore.

    We don't have a geographically different replicant in place, but it wouldn't be difficult to do this at all. We've switched from server to server and archive to archive with a tiny bit of a delay in service.

    1. Re:Backup, Replication and Archiving by jjn1056 · · Score: 2, Insightful

      When all your salesforce wants Their blackberry email and calenders seamlessly synchronized with multiple desktops or notebooks, and when you need to be able to wipe a blackberry remotely when it's lost or stolen, then exchange starts to buy something for you.

      Particularly the mobile support and the ability to create meeting notices with people not even on your network is very valuable

      --
      Peace, or Not?
    2. Re:Backup, Replication and Archiving by alen · · Score: 2, Informative

      with exchange all email is in the database

      for Exchange 2003 you had to restore the db and there were ontrack powertools you bought to search the database file.

      with 2007 and with 2010 they either have the ability to do this or it's coming in 2010. you just restore the database and search it. want to find all the emails that joe sent to jeff, just put in the search parameters and it will find it all.

      no need for imap for mobile clients. if you don't have BES than winmo and iphones just sync the mailbox over the air. no need for a browser, you just use the integrated mail client.

      exchange supports online backup so no downtime during backups. log backups mean you can do point in time restores. if you think someone got an email and deleted it right away, just do a point in time restore and search the db for it.

    3. Re:Backup, Replication and Archiving by Ash-Fox · · Score: 1

      When all your salesforce wants Their blackberry email and calenders seamlessly synchronized with multiple desktops or notebooks, and when you need to be able to wipe a blackberry remotely when it's lost or stolen, then exchange starts to buy something for you.

      Unfortunately Exchange is pretty bad at doing that. I remember having to deal with stupid timezone issues with the devices and the exchange server. They had appointments wrong and many other things - a lot easier just having a webbased calendar system that supports ics import/export - since most software has support for that (including addons for Microsoft Outlook).

      --
      Change is certain; progress is not obligatory.
  28. Wait a second by Anonymous Coward · · Score: 0

    I get OWA from Firefox and Chrome all the time already on 2007, granted it's not quite as fancy as the IE one, but am I missing something there?

    1. Re:Wait a second by Anonymous Coward · · Score: 0

      I think the fanciness is what you are missing. Only the simple version of OWA is supported on firefox and chrome in 2007 which is vastly inferior to the version you get when you use IE.

      OWA is probably the only reason why I use IE (via IEtabs) anymore.

    2. Re:Wait a second by lordandmaker · · Score: 1

      All I noticed when I visited with IE was the appearence of a search button. Exactly which bit of IE this is dependent on, I've no idea.

  29. Been there, tried that... by Suzuran · · Score: 1

    ... and went right back to Outlook and Exchange when the owner and sales team complained that they didn't understand how to work Evolution, how the interface looked like it came from 1998, and how their calendars didn't work like Outlook calendars.

  30. All I want is text/plain by greed · · Score: 1

    All I want from Exchange is for text/plain message to go into it and come out the other side without being scrambled. I don't want them to suddenly turn into multipart/alternative, with the text/plain alternative complete re-flowed and a text/html alternative created from nothing.

    Our IT group managed to get that to stop, and every other kind of message (from outside Exchange) stopped working properly. (Of course, from MAPI and Outlook, this isn't an issue 'cause none of our UNIX servers can talk to MAPI.)

    Or, if it's already possible, I want a big shiny button put in the control panel that says "leave text/plain SMTP messages alone".

  31. If an email was an object in an object database... by master_p · · Score: 1

    ...would we need a separate application for managing emails?

    My gut feeling says no.

  32. Message to save shrank! by janwedekind · · Score: 1

    What about fixing the message size bug? And what about proper negotiation of authentication methods? ...
    I'm looking forward to Microsoft's new innovations in de-commoditisation of internet protocols and services.

  33. Message store size limits? by IGnatius+T+Foobar · · Score: 2, Informative

    One of the most wonderful things about Exchange is how they artificially limit the size of the message store in order to get you to buy the "enterprise" version.

    Why pay megabucks for that limitation when others give you 256 TB or more?

    --
    Tired of FB/Google censorship? Visit UNCENSORED!
  34. Re:Cool feature: Phone call rules by Anonymous Coward · · Score: 0

    But in all seriousness, it'll be nice to have a rule that auto-directs calls to my cell when I'm out of the office.

     

    Avaya has a product called EC500. If you're running Avaya Communications Manager 3.0 or higher, you can utilize EC500. What it does is when a call comes into your extension, it will call your cell phone simultaneously. If you don't pick up your cell phone, it rolls back into your company's voicemail system.

    Since our voicemail system uses Exchange as the message store, the voicemail pops up in my email, which I see on my cell phone because I'm using Exchange ActiveSync.

    Cool part about EC500 is that you can turn it on and off. A button on your phone will turn it on and off while you're in the office, and your telecom admin can set up a special set of phone numbers to call from your cell phone to turn it on and off remotely. The good thing about being able to turn it on and off is that you're contacted on your cell phone whenever you want to be called on your cell phone. No more handing out your cell phone number; just your office number!

  35. Focusing... by Anonymous Coward · · Score: 0

    ...the several Exchange servers I administer only constitute about 3% of the servers I am responsible for, so I don't really have time to focus on them as much as I would like.

    You see, that's where you are going wrong. If you would just put in those five little minutes it takes to teach your sharks to calibrate the lasers on their heads properly so that they can focus them on those pesky Exchange servers the problem would soon go away.

  36. Re:Cool feature: Phone call rules by Anonymous Coward · · Score: 0

    Yes, exchange 2010 supports that as well.

  37. OWA Lite by KingAlanI · · Score: 1

    Me too (Also used OWA Lite in FF for Windows); I've never found problems with OWA Lite.
    Heck, I've seen "full" OWA (in those few times I've touched IE lately), and I'd say the full OWA interface is too cluttered, especially if you don't have a bazillion-inch monitor

    --
    I listen to both RIAA and non-RIAA stuff if I like the music, tangential business/politics nonwithstanding.
  38. Now let's talk licensing by SL+Baur · · Score: 4, Funny

    Not only the pricing, but this part is intriguing too:

    Outlook protection rules

    Automatically triggers Outlook to apply an RMS template to a message before it is sent

    I suppose that means that a GPL V3 notice is attached whenever it notices that a user is attempting to email source code.

    Take that! you GNU/Linux weenies!

  39. Ask and ye shall receive by Gazzonyx · · Score: 1
    I just found this the other day (I've got a mail server, ipod touch and blackberry storm - this is the only solution that looks like it might harmonize the three), and I think it might do what you want... icing on the cake, FOSS.

    funambol server

    Teaser:
    Learn About Funambol
    Many people want quick and easy access to their email, contacts, calendars, tasks and notes, regardless of where that information is stored. Funambol syncs this data with 1.5 billion mobile devices and with thousands of applications and online services. It doesn't matter if you use Gmail, Yahoo!, AOL, Hotmail, Outlook or Thunderbird, with Funambol, you can sync your email & PIM on many mobile handsets.

    Funambol is the leading provider of mobile 2.0 messaging, powered by open source. Funambol solutions include push email for the mass market, mobile backup & PIM sync, device management and a mobile open source platform to mobilize applications and data.

    for the impatient, link to download page

    --

    If I mod you up, it doesn't necessarily mean I agree with what you've said, sorry.

    1. Re:Ask and ye shall receive by Achromatic1978 · · Score: 1
      FOSS. Unless you want tools for mass deployment (can't imagine why a company would want that), or the ability to use it in clustered or HA environments (after all, business email would never need HA)...

      No mention of what the price is there, but I'd guess "not cheap".

      Is not cheap a problem? Of course not. But let's not claim it's a FOSS panacea.

    2. Re:Ask and ye shall receive by somersault · · Score: 1

      Thanks, that looks interesting :)

      --
      which is totally what she said
  40. Zimbra instead by Anonymous Coward · · Score: 0

    We switched to Zimbra CE last summer. The Outlook users weren't happy initially since the calendar connector doesn't work. Heck, Thunderbird's is a read-only solution, IME. The web GUI is nice and works perfectly in most browsers. The only thing that didn't work in I.E. is moving the IM window around. IM works perfectly, just the drag and drop relocation of that pseudo-window didn't work in the version we have.

    If Outlook compatibility is mandatory, the paid version, Zimbra NE, should make them happy. No experience with that here. Sorry.

    OTOH, FREE - $0 is good. Runs on Linux. Uses lots of proven FOSS, but there are some limitations that are important to understand. My company is about to release a white paper on the subject.

    Of course, MS-Exchange has some nice functionality that is hard to beat if you are an MS shop. Zimbra isn't the end-all, best value solution for everyone.

  41. Re:If an email was an object in an object database by hey! · · Score: 1

    Well, look at Lotus Note/Domino. The original, pre-Internet application was essentially a document management and distribution engine. The E-mail bit was just a pre-built template you got with it. There was nothing special about that. An experienced administrator could cobble together other kinds of document distribution applications of equal sophistication for tasks like document approval or content management (although we didn't call it that).

    Despite it's stylistic faults, I think this approach was conceptually sound. The problem was that so many of the really useful concepts, such as public key cryptographic message authentication and key management, were way beyond the average admin of the day. I attended a class once, and people just couldn't get their brains around the process of signing keys, which really isn't that conceptually challenging. I think once they got over that hump, they never wanted to learn anything else about the product.

    The problem was rather than accept this made Notes a niche product, IBM tried to compete with Exchange. They didn't address the faults of Notes so much as try to copy Exchange, and then only superficially. The best part of Exchange is the ease of integrating calendar and e-mail. Since many people use e-mail anyway as a to-do list, integrating PIM and email is a must-do. The underlying document model of Notes should work very well with something like CalDAV, where calendars are basically collections of documents describing events. That shows the architecture is basically sound and they could have carved out a solid, high end niche. IBM just never put together a compelling "value proposition". They tried to chase Microsoft's taillights and lost.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  42. Re:Cool feature: Phone call rules by Anonymous Coward · · Score: 0

    You can setup rooles for phone corls. Freeekeeng awesome.

    if (Status == borking_hot_secretary)

    Fixed... err, cooked that for ya' :)