Red X Completed for Exchange 2007 Readiness Check
Maybe this is a "no brainer" but after installing Exchange 2007 roles on one server (MB, CS, HT), and then running the Exchange 2007 Readiness check thru the EMC\Toolbox, my Exchange 2003 server status is a "Green X Completed" but my Exchange 2007 server status ia a "Red X completed"?The only issues that show are informationaland all are basically just correct information.I performed a second complete installation on another server to validate the results and sure enough, same Red X. If I remember correctly, in the past whenI have installed each of the Exchange 2007 server roles on separate servers, and then run the Exchange 2007 readiness check, I do believethe result is a Green X for each of the servers?Any discernment would be appreciated. If this is just a "fluke result" or should I not include the Exchange 2007 server for a "readiness" check? I want to just move on!ThanksSteve
November 27th, 2009 1:24am

Please try to find any warining or Critical informaiton and then post here.http://msexchangeteam.com/archive/2006/07/28/428506.aspxRegards,Xiu
Free Windows Admin Tool Kit Click here and download it now
November 27th, 2009 12:02pm

We had the same issue...after we applied SP1 the error went away.
November 27th, 2009 12:32pm

No warnings or critical alerts are found. That was the first thing I checked.
Free Windows Admin Tool Kit Click here and download it now
November 27th, 2009 1:52pm

It is nice to know that I am not a single case. :)I iniitally found this after I just happened to perform the Exchange 2007 Readiness Check "after correctly installing Exchange Server 2007 SP2 on Windows Server 2008 with SP2". (Just FYI - this isNOT Windows Server 2008 R2)I decided to test by performing a second installation on a second server usingExchange 2007 with SP1 bits - same issueBoth in a production pilot and also in test, I do believe that if the roles are installed on separate servers, the issue is not seen?Thanks for both of your replies and I hope someone has also experienced this as well with another possible andswer why?Steve
November 27th, 2009 2:00pm

Please try to capture the screenshot and post here.Thanks.Xiu
Free Windows Admin Tool Kit Click here and download it now
November 30th, 2009 7:00am

I rebuilt the entire domain and made sure I did not do anything incorrectly.Same thing. Red X. Now I do see this issue recorded but I do not see it as an issue but just an informational - Simple Exchange Organization?I have the Screen shots but do not see anywhere that I can upload the screen shots?ThanksSteve
December 1st, 2009 4:55am

Hi,You can send the screenshot to me.Xiu
Free Windows Admin Tool Kit Click here and download it now
December 1st, 2009 5:27am

Hi,After you perform a Readiness check please select "View Best Practices Report",there we need to check all issues tab.From my lab, I also have Completed with red X. Then from the "All Issues" tab, I found "Transition documentation" "The Exchange 2007 transition readiness check has classified this Exchange Organization model as 'Standard'".It is a warning.Because I have all the roles instaled on the same machine. Messaging services needs grow beyond the resource limits of a single computer,separation of Exchange 2007 services onto multiple computers becomes the next topological division:the standard Exchange organization.So if it is the same as my lab.Then I think it is a true behavious. Regards,Xiu
December 1st, 2009 5:55am

HI Xiu Zhang, Your last post just answered my issue. Thank you very much for pursuing this through example and not just from a doco.I guess from years of working with past MS products, a "Red" X usually meant a "Red\White" severity warning alert and not a "Blue\White" severity Best Practices Informational. (or atleast that is how I am reading them when the actual report does not have either a "yellow or a red" icon next to the warning or issue statement. :):)Some interesting points gleaned from this:1. My original pilot build had each roleplaced on a unique and separate server (3 servers; MB, HT, and CA) A. This was why I did not see"my Red" X for a Simple Exchange Organization2. When I originally saw this issue and researched, I thought a way of correcting the Red X was to build 3 separate servers, each with a unique Exchange 2007 role (but keeping the original build of 3 roles on 1 server) A. After running an Exchange 2007 Readiness Check again, the Red X still appears (thought the additional Exchange Servers would negate the Simple Exchange Organization - it did not) B. My conclusion after rebuilding and applying different configurations is that if there are 3 roles on 1 server, one will get the Red X and theBest Practices informational.Your time and expert effort to test this issue is greatly appreciated!!Thank you againStevelsd
Free Windows Admin Tool Kit Click here and download it now
December 1st, 2009 8:21pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics