I'm posting this here for lack of a better place to whine. I have been less than impressed with Ex2007. For those of you considering it, you really need to investigate whether or not it is for you. It is a different beast than Ex2000/2003. I've been a walking billboard for 2000/2003 so when 2007 came out i jumped on board. Everything is different. I like change, but this change is a step backward. If you want to do any semi-advanced system change you have to do it via command line. That's great if you know the commands to issue, but if you're like me and just get in Exchange once in a while to make a change here or there, then you will absolutely hate it. I've spent 1 whole day on trying to figure out how to enable POP3 access for clients. You can do the exact same procedure on 2003 in 30 seconds or less. Microsoft's answer is that people shouldn't be using POP3 anymore so "we" removed POP3 settings from the GUI. We have application servers that utilize POP3, so not true. At any rate, this whole deployment has been a big burden and possible bad move. The product appears to be stable. However, any errors that you receive in the event viewer for 2007 have ZERO solutions on the internet. I'm guessing that is because it is relatively new. I really wanted to focus my time on showing all of our users how cool Exchange is since my current project is migrating from an ISP's POP3 service. It's hard to show people the features when you have to spend 8 hours on configuring a service. Well, that's my rant. My only advice on this product is: Make sure you know what you're getting into. If you don't want your email server to rule your life, then this product is NOT for you. If you're a CLI type of person and your only job is to make sure your people get email...then go for it.

I am with you on the pop3 thing. I have just installed the Eval to check it out and i have enabled the pop3 (I think) and when i try to authenticate it gives the password right back to me. Over and Over and Over and Over. You get the idea. Do you have any advice for me on what this might be. i know it is not the password or username. Here is the error i am getting. I would appriciate any help you could give me. Log onto incoming mail server (POP3): Your e-mail server rejected your login. Verify your user name and password in your account properties. Under Tools, click E-mail accounts. The server responded: -ERR Command is not valid in this state.

Hi Patrick, I agree that people didn't expect Microsoft to change the GUI. But, I think... we will get all we expect in the GUI in the coming days. I expect the GUI to be more enhanced in the service packs or resource kit for Exchange 2007. Until then, we have to live with the Command line.

Dear Patrick You posting, is the first post I am reading on Technet Forums, Well beleive me. I totally agree with you(although I did not use Exchange 2007,rather planning to). My way of doing the things is something based on many factors. When I plan to implement some technology, i read about that technology, then i compare its suitability, reliability and feasibility according to my requirements, then i collect conclusion about the technology from the ppl who are already dealing with that respective technology. Then finally I decide to implement it. From where I can hear about Exchange 2007, I mean How to Install, System Requirements, Fully Deployment. Can you tell me about these things and very important thing, about its compatibility with Windows Server 2003. Waiting for the response from experts Regards Adnan

i'm getting the same pop3 -err msg as well. I have tested the account using outlook 2007 and it works fine, but our helpdesk system with the same settings gets this error message.Hopefully someonecan tell us what is going on.

Wow... sorry for the 7 month delay in responding to you. Hopefully, you will read this. I will say that 2007 has been very stable. Suprisingly stable. Amazingly stable. However, I'm still stuck on the lack of administration control without being a command line junky. A perect example that arose last week was that i needed to give a person full control over another user's mailbox. Understand that they needed control over ONE mailbox, not the entire organization. Well, after googling and searching the MS site i found the three commands to give sendas rights. Nuts!! The programmers of Exchange might be a little heavy on the crazy. lol That's a lot of work to make a change that required mere seconds in 2003. Another caveat is hardware. I don't care what anyone says, you need 4 gig of ram and some serious hard drive performance to make administration tolerable. I get into the console a few times a day and it was taking anywhere from 30-60 secs to load. This was with 1.5 gig of RAM, 4 SAS drives in a RAID 10. It was UNBEARABLY slow. we dont have that many users either. We upgraded to 4 Gig of ram, 6 drives ( RAID 1 for OS raid 10 for DB) and now it works like a champ. ok, hope that helps and very sorry about the delay.