Exchange 2010

[leco]

I've successfully installed Exchange 2010 onto a new server. It's co-existing with Exchange 2003. Question: Do I need to stop both Exchange servers in order to move mailboxes from 2003 to 2010? If so how do I do that?

[glennda]

I've successfully installed Exchange 2010 onto a new server. It's co-existing with Exchange 2003. Question: Do I need to stop both Exchange servers in order to move mailboxes from 2003 to 2010? If so how do I do that?

 

I havn't done it from exchange 2003-2010 but you can just select the mailboxes in System manager and then transfer them while they are online. The client is then just asked to restart outlook and it auto-updates the outlook profile.

 

As i say this i don't know if this will work from 2003-2010 like it did in 2003 -2003 or 2003 -2007 etc.

[leco]

Apparently 2003 Exchange System Manager can't be used I have to use 2010 Exchange Management Console. It's just that I've used the interface to move a mailbox but it's still showing as a legacy one. This means that if I try to remotely (web access) access it the server is still looking for my legacy.server. I just wondered if Exchange needed to be off before it would actually move the mailbox.

[glennda]

sorry not a clue only used 2003/2007! will be looking to exchange 2010 later this year.

[leco]

That's OK thanks for suggesting anyway.

[mb2k01]

Hi Leco. No, you don't need to stop either Exchange Server, the move should be seemless for the user (apart from a message advising an Outlook reboot). I'm not near the server to check, but I am fairly sure e2010 lists a legacy mailbox as one which was created on an earlier version - even when it has been moved?

 

I didn't understand the post about web acces really.

Once the mailbox has been moved that user can't access owa 2003 and needs to access owa 2010 in order to connect to their mail. If that option isn't available yet then they can still access via Outlook on a desktop etc.

 

I have been very slack finishing off my 2010 project and have been co-existing 2003 + 2010 for several months now. If I can help with anything give me a shout!

[leco]

Thanks for the reassurance - it's quite scary working in Exchange since email is so important. Not sure on the web access front either since we didn't use it in 2003. Maybe the installation shouldn't have a legacy.server at all? I think I'll have to set up a new mailbox in 2010 and test that instead.

[mb2k01]

If you aren't too worried about having OWA then you could save yourself a headache for a bit.

Outlook Anywhere allows users to use Oulook via port 80 or ideally 443 with a UC certificate and works perfectly well.

 

If you fancy using OWA the things to check are probably IIS permission / Certificate related - this was a huge learning curve for me!

Also make sure that your test user is accessing via the URL specified on the properties of the Client Access section of the Server Configuration section of the management console.

[leco]

What's the difference between OWA and Outlook Anywhere? I'm only using OWA because I thought that's what I should be. I do know the URLs though as I've just set all those up in the Commander. Another thing - I know absolutely zilch about Certificates.

[mb2k01]

What's the difference between OWA and Outlook Anywhere? I'm only using OWA because I thought that's what I should be. I do know the URLs though as I've just set all those up in the Commander. Another thing - I know absolutely zilch about Certificates.

 

OWA is the web-based interface for connecting to a mailbox on Exchange.

Outlook Anywhere is a feature of Exchange which lets users connect to their mailbox from Microsoft Oulook when they are away from the site. I think I am right in saying that all traffic is sent/recieved by port 80 or ideally 443. From their point of view, they won't see much difference between their classroom/office PC and their home laptop/pc.

 

With all that said, Outlook Anywhere still requires the server to be setup for external access and have certificates / permissions in place, so it might as well be looked at during the same time as configuring OWA!

[mb2k01]

I've just dug up my old thread which I started at the beginning of my project. There might be some info on there that can help you out on other things too http://www.edugeek.net/forums/windows-server-2008-r2/46887-exchange-2003-2010-transition-co-existence.html

 

I should be in the office for most of tomorrow so will try and glance here to see of theres anything I can help with!

[leco]

Ah I see, so with Outlook Anywhere users have to have Outlook as their email client. Which is obviously ok if they are using a school laptop (at home for instance) but they might not have it on their home PC. I'd have to check on that with staff.

 

Learning time again - off I go to find out about permissions and certificates. Well I will tomorrow, need to give my brain a rest for now. Thanks, no doubt I'll be back with more questions.

 

Edit: Thanks for the link, most helpful. I do now remember reading it before. I think most of my issues are to do with OWA as it's not been there before.

Edited May 10, 2010 by leco
Additional thanks

[mb2k01]

I'll post some bullet points tomorrow when I'm more awake - the ones that I wish I had read somewhere before I started having to troubleshoot e2010. (Some might be patronising depending on your knowledge of Exchange, but they're all ones I didn't know and had to go off and learn the hard way!)

[leco]

Just an update on this thread - I have moved a mailbox to the 2010 server but it now cannot receive mail on either 2003 or 2010! I can telnet into the Exchange server to send mail to the mailbox but I get a no authorisation error. Anyone got any suggestions for resolution please?

[EduTech]

what settings do you have set on the receive connector?

 

James.

[leco]

what settings do you have set on the receive connector?

 

James.

Considering I've been staring at this all day - I can't honestly say:( I can say that I've checked all of the settings against the upgrade paperwork - they are all as they should be. My external support has also checked all the settings. Currently trawling blogs/support sites/forums etc to find clues.

[EduTech]

Guessing you can send email internally no problem, is the firewall rule setup correctly since the change? do you get any bouncebacks when you attempt to send email to the server from an external address?

 

James.

[leco]

Internal mail is OK. Firewall is off. Exchange Administrator gets non-delivery messages - external sender gets 4 delay messages then a failure message.

[EduTech]

Can't remember what the delay messages say now, but is there any information on them?

 

you said that you have managed to telnet, did you do that externally?

 

On the receive connector make sure there are no IP Restrictions, and also on other think on the permissions tab have you selected Anonymous users and then does that work?

 

James.

[leco]

Very little information on the non-delivery messages unfortunately. Telnet was internal and external (though by the time I'd got home I couldn't remember the exact command for mailing but I got into the Exchange bit of the server. There are no IP restrictions and Anonymous is turned on.

[EduTech]

Erm, lol! *think*

 

https://www.testexchangeconnectivity.com/

 

What does the Inbound / Outbound test tell you if you run it?

 

James.

[leco]

I don't have OWA set up yet as we didn't use it in 2003. But I think I've tried the tests that are in the Tools menu on the .local address. From memory, which is by now suspect as I seem to have tried every test I can find, I think the message was that no such server could be found.

[EduTech]

I don't have OWA set up yet as we didn't use it in 2003. But I think I've tried the tests that are in the Tools menu on the .local address. From memory, which is by now suspect as I seem to have tried every test I can find, I think the message was that no such server could be found.

 

Hmm, Interesting.. do you know what server it is looking for?

[leco]

The one I specified in the .local address I assume - that's the machine that Exchange is running on as in servername.schoolname.local. I also tried owa.schoolname.local/owa as that's the namespace I set up, but that didn't work either.