This sounds awfully familiar ;-)
John Bowles ________________________________ From: Michael B. Smith [mich...@smithcons.com] Sent: Tuesday, May 04, 2010 1:47 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 to 2010 issues You will have to edit the ExternalURLs on all the Exchange virtual directories. Personally, I find this easier to do via EMS; but most of them can be edited on the Server Configuration -> Client Access tabs. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Tuesday, May 04, 2010 1:45 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 to 2010 issues I’ve just discovered that I made a mistake during the installation process. In the install wizard when it asks for the Internet facing name for the server I put in smtp.acadiau.ca instead of exchange.acadiau.ca. I’m not exactly sure what issues this mistake will cause, but it definitely messes up the certificate installation process. I’ve looked though the various dialogs to find out where I can change that setting but it doesn’t appear anywhere obvious. Is there a quick solution to this mistake? From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: May-03-10 2:52 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 to 2010 issues Mail delivery seems to be working properly now, so I think I’ve got the various connectors configured properly. The 2003 server does not have a certificate and I haven’t installed a UC cert on 2010 yet. I’m reading everything I can find on the topic before tackling the certificate install. After the way things went today I doubt that things will go problem free… From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: May-03-10 2:09 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 to 2010 issues How have you configured namespace sharing, i.e., namespaces vs. SSL certificates on the two servers? Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Monday, May 03, 2010 1:07 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 to 2010 issues That might be it. I had sort of wanted to keep Exchange 2010 out of the picture after this first phase since all the mail boxes are still on Exchange 2003. I want to get backups, certificates, and other misc stuff working on Exchange 2010 before moving mailboxes. One weird problem that has surfaced since the 2010 install is a problem with Public folders. When I try to look at the folder in System Manager on Exch2003, I get the error “The HTTP service used by Public Folders is not available, possible causes are that Public stores are not mounted and the Information Store service is not running.” I’m getting lots of google hits for this error but none specifically relating to an Exchange 2010 upgrade. The folders show up fine in Outlook, but not in OWA or System Manager. This issue did not come up in our test lab. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: May-03-10 1:49 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 to 2010 issues That would tend to indicate that the mail is being routed through the Exchange 2003 server and you don’t have a properly scoped send-connector on the 2010 side. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Monday, May 03, 2010 12:47 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 to 2010 issues Yes, I had already done that. I’m a bit confused now though. I stopped/started the SMTP virtual host (on the EXCH2003 side), and that seemed to solve the problem. Things seem to be working so I guess whatever was broken/stuck is ok. At least it’s working… From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: May-03-10 12:40 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 to 2010 issues Did you create a send-connector to forward the scoped domain to the Unix host? Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Monday, May 03, 2010 11:37 AM To: MS-Exchange Admin Issues Subject: Exchange 2003 to 2010 issues We did as much testing as we could in our test lab, so we moved ahead and installed our production Exchange 2010 server. The installation went fine without any errors, but we’re have delivery problems. We’ve been preparing for a transition from Exchange 2003 to Exchange 2010. We’ve done various test installs in our lab and thought we had everything figured out. Unfortunately we’re having mail delivery problems after completing the install. The actual installation went without problems. We have a shared address space, with some users on our Exchange server and some on a Unix host. The biggest issue we’re having is sending to users who are not on our Exchange server. We’ve set the Accepted Domains for “acadiau.ca” to Internal Relay, but when we try to send to usern...@acadiau.ca<mailto:usern...@acadiau.ca> that does not exist in the Exchange name space, the message bounces (it never makes it to our Unix smart host). We’ve compared things with our test servers and everything looks correct. At this point we’ve very confused what we’re doing wrong. If anyone has a suggestion what to look for we really appreciate it.
