E2K3 SP2 / W2K SP4 Domain I ran this tool a few minutes before the following and it worked fine. After running the 'adprep /forestprep' to add the W2K3 R2 schema changes, The Exchange Best Practices Analyzer Tool reports the following message: "No Exchange organization container found in domain" The schema changes were added to a W2K Domain directly to R2. All synchronization has occurred successfully. Any ideas?
This could indicate you do not have the necessary permissions to access the needed AD container, or it could indicate you are not pointed to a GC in the correct domain. "MR-KEN" wrote in message news:%23ZO8OncTGHA.4308@TK2MSFTNGP10.phx.gbl... > E2K3 SP2 / W2K SP4 Domain > > I ran this tool a few minutes before the following and it worked fine. > > After running the 'adprep /forestprep' to add the W2K3 R2 schema changes, > The Exchange Best Practices Analyzer Tool reports the following message: > > "No Exchange organization container found in domain" > > The schema changes were added to a W2K Domain directly to R2. All > synchronization has occurred successfully. > > Any ideas?
It worked just before I did the schema update and the same results are in another install. I can still run the Disaster Recovery Analyzer Tool and the Performance Troubleshooter Tool.
In my lab, I installed a W2K3-R2 DC. Once that was done, the tool worked when connecting to both the W2K3-R2 DC and the W2K SP4 DC. Therefore, I would say that there is something wrong about the tool when it comes to installing the schema changes to a W2K SP4 Domain.
Thanks for the info. We will investigate. "MR-KEN" wrote in message news:e1rp4aoTGHA.1672@tk2msftngp13.phx.gbl... > In my lab, I installed a W2K3-R2 DC. Once that was done, the tool worked > when connecting to both the W2K3-R2 DC and the W2K SP4 DC. > > Therefore, I would say that there is something wrong about the tool when > it > comes to installing the schema changes to a W2K SP4 Domain.