 boognishPremium
join:2001-09-26
Baton Rouge, LA
kudos:6 | reply to lorennerol
Re: Exchange 2003 to 2013 said by lorennerol:Exchange 2003 supports all those devices via ActiveSync; that's nothing new or added with 2007-2013.
What we did get in 2007 was larger and more databases in the Standard edition of Exchange. Hard to believe the original limit in Exchange 2003 was 16GB and one store for all mailboxes.
When we had 5.5 we hit the database limit and upgraded to 2003 enterprise to avoid hitting it again. I actually had gotten the software assurance with 2003, but they didn't come out with another exchange fast enough for us to use it.
--
don't get 2 close 2 my fantasy |
|
 DarkLogixTexan and ProudPremium
join:2008-10-23
Baytown, TX
kudos:3 | That's why you renew it. |
|
AsherN
join:2010-08-23
Thornhill, ON | reply to boognish
said by boognish:said by AsherN:You buy server software and CALs to allow clients to access it. That client can be anything you want. If you want native connectivity, you require Outlook. With Exchange 2013, MS decided to no longer support RPC, so Outlook has to be 2007 or newer.
You are welcome to use any open source software if you access Exchange through ActiveSync, POP3 or IMAP.
I realize the obvious. I was ranting because MS included outlook with your CALS at one time and I hadn't realized it changed. I will adapt, throw more money, and time at this so I can get back to my main objective or I may just upgrade as far as 2010. Still looking at my options. The last version of Exchange to include Outlook was 2003. It's not new. |
|
boognishPremium
join:2001-09-26
Baton Rouge, LA
kudos:6 | reply to lorennerol
The move to exchange 2010 wasn't that bad. I set it up on a virtual machine. I had to use pfdavadmin to fix some permission problems I had before I could move mailboxes. It took me about a day to get the initially set up, a couple of days to move users, and then another day to finalize the setup. I have had exchange 2003 offline for a day little over a day now with no problems. Now to get the hardware and software setup to start moving over to exchange 2013.
--
don't get 2 close 2 my fantasy |
|
|
|
DarkLogixTexan and ProudPremium
join:2008-10-23
Baytown, TX
kudos:3 | BTW make sure that no AD accounts with mailboxes have admincount=1
This happens if the user is a member of any protected group (or a member of a member group)
And somethings won't work properly if admincount is 1 for the user, and you can't just set it to 0 there's a few more steps.
--
»www.change.org/petitions/create-···imcity-4 |
|
jdrwhoPremium
join:2003-11-03
Baltimore, MD
1 edit | reply to boognish
There is not a migration path or co-existance yet to go from any prior version of Exchange to 2013. That will be added in Exchange 2013 CU1 which is scheduled for Q1 2013 release but still has not been released yet. We have 2 client upgrades waiting for CU1 to come out before we can move forward with the projects. |
|
