Exchange 2013 will not support any Outlook version under 2007 they cut off 2003 support in this version (its fine in Exchange 2010 though)
I am just starting to look into this my self. We might have a problem with our NetBios domain name as it has a underscore in it and you can not do a NetBios rename if you are running Exchange 2007.
Not exactly sure. It seems like an update did terrible things to it. It was fragile to begin with, the update from 2003 had issues and it had been limping along for about a year. It was best to do a clean install, I just wish it wouldn't have taken so long and gone so wrong!
------------------------- I'm not sick, but I'm not well
Ahh I see :D Exchange is a bastard sometimes. The first thing I was handed when I started in my new company was a fooked Exchange 2003 to 2007 migration that was started but never completed. All transport was going through 2007 but mail boxes, public folders and other services were still on 2003. It took me about 2 weeks in total to finish the migration and clean everything up. Now I get to tackle the jump to 2013 but I know my exchange environment is clean so it wont be too bad (fingers crossed)
It continues to be. I still have users who can't share calendars and I still have to figure out the problem with public folders and who knows what else will pop up. If I could go back I'd just go with 2010.
------------------------- I'm not sick, but I'm not well
I continue to find issues with XP and Outlook. Outlook 2007 can't share calendars now, MS knows about it. I really wish I'd just have went with 2010 but I was under pressure and figured if I was going to do it I might as well get up to date.
------------------------- I'm not sick, but I'm not well
On a different note, has anyone tried Sharepoint 2013? I'm looking at deploying a new server at work, but am torn between Sharepoint 2010 and Sharepoint 2013 (after finding out what a pig's breakfast Exchange 2013 has turned out to be!)
