RE: Exchange 2010 install w/coexisting E2K3 Organization
That's only actually required if you have multiple paths between the E2K3 and E2K10 routing groups. In the original post, only a single E2K3 server and a single E2K10 server was quoted, so I personally wouldn't bother with this. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: 26 March 2010 18:23 To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Yessir. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 2:11 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization One question I have for you though.. should I suppress link state routing prior to performing this? From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 1:49 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Sure have. It was very common in 2007 migrations and only slightly less so in 2010 migrations. Just create the Interop-RGC. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 1:47 PM To: MS-Exchange Admin Issues Subject: Exchange 2010 install w/coexisting E2K3 Organization All- I installed an Exchange 2010 server into an Exchange 2003 organization(1 E2K3 server, 1 E2k10 server). All the pre-req's passed with no problems, exchange installed fine. One issue is that when Exchange 2K10 was installed it didn't create RGC between to the two servers, also the E2K10 server doesn't show up in the created admin group during installation. So no, I cannot replicate PF's or send mail between servers. Has anyone seen this behavior before? Thank you, John Bowles
RE: Exchange 2010 install w/coexisting E2K3 Organization
I know it SAYS that in the documentation (what Neil said), but I've run into the classic link state bounce issue at two clients during migrations. Disabling it is now part of my standard process for all migrations. (As is installing KB 922817 and KB 937031.) It only takes a minute and it can possibly save a good bit of hassle. Now, I've got suspicions about why those two clients had issues - I think it had to do with improperly cleaned up old servers (i.e., servers that had simply been cut off and never properly removed from the Exchange organization) and still-active connection objects for those servers. But PROVING that would be a lot more difficult than simply suppressing link-state updates. IMHO. YMMV. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Neil Hobson [mailto:nhob...@gmail.com] Sent: Monday, March 29, 2010 4:50 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization That's only actually required if you have multiple paths between the E2K3 and E2K10 routing groups. In the original post, only a single E2K3 server and a single E2K10 server was quoted, so I personally wouldn't bother with this. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: 26 March 2010 18:23 To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Yessir. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 2:11 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization One question I have for you though.. should I suppress link state routing prior to performing this? From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 1:49 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Sure have. It was very common in 2007 migrations and only slightly less so in 2010 migrations. Just create the Interop-RGC. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 1:47 PM To: MS-Exchange Admin Issues Subject: Exchange 2010 install w/coexisting E2K3 Organization All- I installed an Exchange 2010 server into an Exchange 2003 organization(1 E2K3 server, 1 E2k10 server). All the pre-req's passed with no problems, exchange installed fine. One issue is that when Exchange 2K10 was installed it didn't create RGC between to the two servers, also the E2K10 server doesn't show up in the created admin group during installation. So no, I cannot replicate PF's or send mail between servers. Has anyone seen this behavior before? Thank you, John Bowles
RE: Exchange 2010 install w/coexisting E2K3 Organization
I can't say that I've had that personally and it's another bunch of service restarts on the production E2K3 servers that I could probably do without - but I take your point. Perhaps another E2K10 gotcha? ;) From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: 29 March 2010 12:13 To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization I know it SAYS that in the documentation (what Neil said), but I've run into the classic link state bounce issue at two clients during migrations. Disabling it is now part of my standard process for all migrations. (As is installing KB 922817 and KB 937031.) It only takes a minute and it can possibly save a good bit of hassle. Now, I've got suspicions about why those two clients had issues - I think it had to do with improperly cleaned up old servers (i.e., servers that had simply been cut off and never properly removed from the Exchange organization) and still-active connection objects for those servers. But PROVING that would be a lot more difficult than simply suppressing link-state updates. IMHO. YMMV. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Neil Hobson [mailto:nhob...@gmail.com] Sent: Monday, March 29, 2010 4:50 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization That's only actually required if you have multiple paths between the E2K3 and E2K10 routing groups. In the original post, only a single E2K3 server and a single E2K10 server was quoted, so I personally wouldn't bother with this. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: 26 March 2010 18:23 To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Yessir. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 2:11 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization One question I have for you though.. should I suppress link state routing prior to performing this? From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 1:49 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Sure have. It was very common in 2007 migrations and only slightly less so in 2010 migrations. Just create the Interop-RGC. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 1:47 PM To: MS-Exchange Admin Issues Subject: Exchange 2010 install w/coexisting E2K3 Organization All- I installed an Exchange 2010 server into an Exchange 2003 organization(1 E2K3 server, 1 E2k10 server). All the pre-req's passed with no problems, exchange installed fine. One issue is that when Exchange 2K10 was installed it didn't create RGC between to the two servers, also the E2K10 server doesn't show up in the created admin group during installation. So no, I cannot replicate PF's or send mail between servers. Has anyone seen this behavior before? Thank you, John Bowles
RE: Exchange 2010 install w/coexisting E2K3 Organization
I've got a list of about 20 gotchas now, some big, some small. If I have a maintenance window ALREADY, I don't mind taking the restart hit(s) all very quickly one after the other. But, again, I'm old, gnarly, and set in my ways. :) Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Neil Hobson [mailto:nhob...@gmail.com] Sent: Monday, March 29, 2010 11:59 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization I can't say that I've had that personally and it's another bunch of service restarts on the production E2K3 servers that I could probably do without - but I take your point. Perhaps another E2K10 gotcha? ;) From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: 29 March 2010 12:13 To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization I know it SAYS that in the documentation (what Neil said), but I've run into the classic link state bounce issue at two clients during migrations. Disabling it is now part of my standard process for all migrations. (As is installing KB 922817 and KB 937031.) It only takes a minute and it can possibly save a good bit of hassle. Now, I've got suspicions about why those two clients had issues - I think it had to do with improperly cleaned up old servers (i.e., servers that had simply been cut off and never properly removed from the Exchange organization) and still-active connection objects for those servers. But PROVING that would be a lot more difficult than simply suppressing link-state updates. IMHO. YMMV. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Neil Hobson [mailto:nhob...@gmail.com] Sent: Monday, March 29, 2010 4:50 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization That's only actually required if you have multiple paths between the E2K3 and E2K10 routing groups. In the original post, only a single E2K3 server and a single E2K10 server was quoted, so I personally wouldn't bother with this. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: 26 March 2010 18:23 To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Yessir. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 2:11 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization One question I have for you though.. should I suppress link state routing prior to performing this? From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 1:49 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Sure have. It was very common in 2007 migrations and only slightly less so in 2010 migrations. Just create the Interop-RGC. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 1:47 PM To: MS-Exchange Admin Issues Subject: Exchange 2010 install w/coexisting E2K3 Organization All- I installed an Exchange 2010 server into an Exchange 2003 organization(1 E2K3 server, 1 E2k10 server). All the pre-req's passed with no problems, exchange installed fine. One issue is that when Exchange 2K10 was installed it didn't create RGC between to the two servers, also the E2K10 server doesn't show up in the created admin group during installation. So no, I cannot replicate PF's or send mail between servers. Has anyone seen this behavior before? Thank you, John Bowles
RE: Exchange 2010 install w/coexisting E2K3 Organization
check your redirect on the OWA directory, if you did the http redirect at the default website it probably propogated down the the owa putting it in loop Jean-Paul Natola From: mich...@smithcons.com To: exchangelist@lyris.sunbelt-software.com Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Date: Fri, 26 Mar 2010 19:37:29 + No. I doubt highly that they are related. In both cases, you should be getting event log entries providing clues. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 2:50 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Crap! As I solve one issue, another arises. I’m trying to log into my test account via owa (https://server.company.com/owa) I get the login page.. but when I submit my credentials it times out on me. Even when I try and access it from IIS Mgmt Console it gives me the same issue. Another issue is when I restart my server the DB’s never mount. I have to manually mount them each time. I’m wondering if the above issue is directly related to this. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 2:25 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization I filed a bug, and they fixed one instance of the issue, but apparently the larger issue is that setup creates objects that may not be replicated in AD by the time setup goes back to try to use them. This is a common issue. And some of the problems cause fatal setup errors, this one doesn’t happen to be a fatal issue. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 2:06 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Really? It blows my mind by just running a typical installation that is guided by MS would create issues like that. Thanks again Mike for your help… you’ve been very insightful on many occasions for me. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 1:49 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Sure have. It was very common in 2007 migrations and only slightly less so in 2010 migrations. Just create the Interop-RGC. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 1:47 PM To: MS-Exchange Admin Issues Subject: Exchange 2010 install w/coexisting E2K3 Organization All- I installed an Exchange 2010 server into an Exchange 2003 organization(1 E2K3 server, 1 E2k10 server). All the pre-req’s passed with no problems, exchange installed fine. One issue is that when Exchange 2K10 was installed it didn’t create RGC between to the two servers, also the E2K10 server doesn’t show up in the created admin group during installation. So no, I cannot replicate PF’s or send mail between servers. Has anyone seen this behavior before? Thank you, John Bowles _ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID27925::T:WLMTAGL:ON:WL:en-US:WM_HMP:032010_3
RE: Exchange 2010 install w/coexisting E2K3 Organization
Sure have. It was very common in 2007 migrations and only slightly less so in 2010 migrations. Just create the Interop-RGC. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 1:47 PM To: MS-Exchange Admin Issues Subject: Exchange 2010 install w/coexisting E2K3 Organization All- I installed an Exchange 2010 server into an Exchange 2003 organization(1 E2K3 server, 1 E2k10 server). All the pre-req's passed with no problems, exchange installed fine. One issue is that when Exchange 2K10 was installed it didn't create RGC between to the two servers, also the E2K10 server doesn't show up in the created admin group during installation. So no, I cannot replicate PF's or send mail between servers. Has anyone seen this behavior before? Thank you, John Bowles
RE: Exchange 2010 install w/coexisting E2K3 Organization
Really? It blows my mind by just running a typical installation that is guided by MS would create issues like that. Thanks again Mike for your help... you've been very insightful on many occasions for me. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 1:49 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Sure have. It was very common in 2007 migrations and only slightly less so in 2010 migrations. Just create the Interop-RGC. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 1:47 PM To: MS-Exchange Admin Issues Subject: Exchange 2010 install w/coexisting E2K3 Organization All- I installed an Exchange 2010 server into an Exchange 2003 organization(1 E2K3 server, 1 E2k10 server). All the pre-req's passed with no problems, exchange installed fine. One issue is that when Exchange 2K10 was installed it didn't create RGC between to the two servers, also the E2K10 server doesn't show up in the created admin group during installation. So no, I cannot replicate PF's or send mail between servers. Has anyone seen this behavior before? Thank you, John Bowles
RE: Exchange 2010 install w/coexisting E2K3 Organization
One question I have for you though.. should I suppress link state routing prior to performing this? From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 1:49 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Sure have. It was very common in 2007 migrations and only slightly less so in 2010 migrations. Just create the Interop-RGC. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 1:47 PM To: MS-Exchange Admin Issues Subject: Exchange 2010 install w/coexisting E2K3 Organization All- I installed an Exchange 2010 server into an Exchange 2003 organization(1 E2K3 server, 1 E2k10 server). All the pre-req's passed with no problems, exchange installed fine. One issue is that when Exchange 2K10 was installed it didn't create RGC between to the two servers, also the E2K10 server doesn't show up in the created admin group during installation. So no, I cannot replicate PF's or send mail between servers. Has anyone seen this behavior before? Thank you, John Bowles
RE: Exchange 2010 install w/coexisting E2K3 Organization
Yessir. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 2:11 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization One question I have for you though.. should I suppress link state routing prior to performing this? From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 1:49 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Sure have. It was very common in 2007 migrations and only slightly less so in 2010 migrations. Just create the Interop-RGC. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 1:47 PM To: MS-Exchange Admin Issues Subject: Exchange 2010 install w/coexisting E2K3 Organization All- I installed an Exchange 2010 server into an Exchange 2003 organization(1 E2K3 server, 1 E2k10 server). All the pre-req's passed with no problems, exchange installed fine. One issue is that when Exchange 2K10 was installed it didn't create RGC between to the two servers, also the E2K10 server doesn't show up in the created admin group during installation. So no, I cannot replicate PF's or send mail between servers. Has anyone seen this behavior before? Thank you, John Bowles
RE: Exchange 2010 install w/coexisting E2K3 Organization
I filed a bug, and they fixed one instance of the issue, but apparently the larger issue is that setup creates objects that may not be replicated in AD by the time setup goes back to try to use them. This is a common issue. And some of the problems cause fatal setup errors, this one doesn't happen to be a fatal issue. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 2:06 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Really? It blows my mind by just running a typical installation that is guided by MS would create issues like that. Thanks again Mike for your help... you've been very insightful on many occasions for me. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 1:49 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Sure have. It was very common in 2007 migrations and only slightly less so in 2010 migrations. Just create the Interop-RGC. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 1:47 PM To: MS-Exchange Admin Issues Subject: Exchange 2010 install w/coexisting E2K3 Organization All- I installed an Exchange 2010 server into an Exchange 2003 organization(1 E2K3 server, 1 E2k10 server). All the pre-req's passed with no problems, exchange installed fine. One issue is that when Exchange 2K10 was installed it didn't create RGC between to the two servers, also the E2K10 server doesn't show up in the created admin group during installation. So no, I cannot replicate PF's or send mail between servers. Has anyone seen this behavior before? Thank you, John Bowles
RE: Exchange 2010 install w/coexisting E2K3 Organization
Crap! As I solve one issue, another arises. I'm trying to log into my test account via owa (https://server.company.com/owa) I get the login page.. but when I submit my credentials it times out on me. Even when I try and access it from IIS Mgmt Console it gives me the same issue. Another issue is when I restart my server the DB's never mount. I have to manually mount them each time. I'm wondering if the above issue is directly related to this. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 2:25 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization I filed a bug, and they fixed one instance of the issue, but apparently the larger issue is that setup creates objects that may not be replicated in AD by the time setup goes back to try to use them. This is a common issue. And some of the problems cause fatal setup errors, this one doesn't happen to be a fatal issue. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 2:06 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Really? It blows my mind by just running a typical installation that is guided by MS would create issues like that. Thanks again Mike for your help... you've been very insightful on many occasions for me. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 1:49 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Sure have. It was very common in 2007 migrations and only slightly less so in 2010 migrations. Just create the Interop-RGC. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 1:47 PM To: MS-Exchange Admin Issues Subject: Exchange 2010 install w/coexisting E2K3 Organization All- I installed an Exchange 2010 server into an Exchange 2003 organization(1 E2K3 server, 1 E2k10 server). All the pre-req's passed with no problems, exchange installed fine. One issue is that when Exchange 2K10 was installed it didn't create RGC between to the two servers, also the E2K10 server doesn't show up in the created admin group during installation. So no, I cannot replicate PF's or send mail between servers. Has anyone seen this behavior before? Thank you, John Bowles
RE: Exchange 2010 install w/coexisting E2K3 Organization
No. I doubt highly that they are related. In both cases, you should be getting event log entries providing clues. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 2:50 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Crap! As I solve one issue, another arises. I'm trying to log into my test account via owa (https://server.company.com/owa) I get the login page.. but when I submit my credentials it times out on me. Even when I try and access it from IIS Mgmt Console it gives me the same issue. Another issue is when I restart my server the DB's never mount. I have to manually mount them each time. I'm wondering if the above issue is directly related to this. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 2:25 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization I filed a bug, and they fixed one instance of the issue, but apparently the larger issue is that setup creates objects that may not be replicated in AD by the time setup goes back to try to use them. This is a common issue. And some of the problems cause fatal setup errors, this one doesn't happen to be a fatal issue. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 2:06 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Really? It blows my mind by just running a typical installation that is guided by MS would create issues like that. Thanks again Mike for your help... you've been very insightful on many occasions for me. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 1:49 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Sure have. It was very common in 2007 migrations and only slightly less so in 2010 migrations. Just create the Interop-RGC. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 1:47 PM To: MS-Exchange Admin Issues Subject: Exchange 2010 install w/coexisting E2K3 Organization All- I installed an Exchange 2010 server into an Exchange 2003 organization(1 E2K3 server, 1 E2k10 server). All the pre-req's passed with no problems, exchange installed fine. One issue is that when Exchange 2K10 was installed it didn't create RGC between to the two servers, also the E2K10 server doesn't show up in the created admin group during installation. So no, I cannot replicate PF's or send mail between servers. Has anyone seen this behavior before? Thank you, John Bowles
RE: Exchange 2010 install w/coexisting E2K3 Organization
Which AV for Exchange are you running? I had a similar issue with an earlier build of Forefront (was my fault though as I had downloaded a version that wasn't quite 2010 compatible). -Greg From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 12:37 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization No. I doubt highly that they are related. In both cases, you should be getting event log entries providing clues. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 2:50 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Crap! As I solve one issue, another arises. I'm trying to log into my test account via owa (https://server.company.com/owa) I get the login page.. but when I submit my credentials it times out on me. Even when I try and access it from IIS Mgmt Console it gives me the same issue. Another issue is when I restart my server the DB's never mount. I have to manually mount them each time. I'm wondering if the above issue is directly related to this. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 2:25 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization I filed a bug, and they fixed one instance of the issue, but apparently the larger issue is that setup creates objects that may not be replicated in AD by the time setup goes back to try to use them. This is a common issue. And some of the problems cause fatal setup errors, this one doesn't happen to be a fatal issue. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 2:06 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Really? It blows my mind by just running a typical installation that is guided by MS would create issues like that. Thanks again Mike for your help... you've been very insightful on many occasions for me. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, March 26, 2010 1:49 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 install w/coexisting E2K3 Organization Sure have. It was very common in 2007 migrations and only slightly less so in 2010 migrations. Just create the Interop-RGC. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 1:47 PM To: MS-Exchange Admin Issues Subject: Exchange 2010 install w/coexisting E2K3 Organization All- I installed an Exchange 2010 server into an Exchange 2003 organization(1 E2K3 server, 1 E2k10 server). All the pre-req's passed with no problems, exchange installed fine. One issue is that when Exchange 2K10 was installed it didn't create RGC between to the two servers, also the E2K10 server doesn't show up in the created admin group during installation. So no, I cannot replicate PF's or send mail between servers. Has anyone seen this behavior before? Thank you, John Bowles
