none
2010 ExBPA?

Answers

  • I just received feedback from the ExBPA team, this is a known issue now and will be fixed in SP1 for Exchange 2010.
    With kind regards / Met vriendelijke groet, Jetze Mellema | http://jetzemellema.blogspot.com/
    • Proposed as answer by Jetze Mellema Tuesday, January 19, 2010 12:35 PM
    • Marked as answer by chrislehr Thursday, January 21, 2010 1:09 AM
    Tuesday, January 19, 2010 12:35 PM

All replies

  • When will there be an update for the BPA tool?


    Bump?

    Every Exchange 2010 BPA I've run has an error accessing the web.
    Wednesday, November 18, 2009 7:48 PM
  • I can confirm that, i get the error as well, seems pretty bad for a final /rtm release if you ask me...
    blabla
    Thursday, November 19, 2009 11:55 AM
  • I dropped a line to one of (if not _the_) gentleman who crafts ExBPA. Hopefully he's around to take a quick look. :)
    Brian Day, Overall Exchange & AD Geek
    MCSA 2000/2003, CCNA
    MCTS: Microsoft Exchange Server 2010 Configuration
    LMNOP
    • Marked as answer by chrislehr Thursday, November 19, 2009 9:00 PM
    • Unmarked as answer by chrislehr Thursday, November 19, 2009 9:11 PM
    Thursday, November 19, 2009 2:50 PM
  • Try it now, worked for me.
    Brian Day, Overall Exchange & AD Geek
    MCSA 2000/2003, CCNA
    MCTS: Microsoft Exchange Server 2010 Configuration
    LMNOP
    Thursday, November 19, 2009 6:59 PM
  • I no longer have warnings connecting or that my schema is an unknown version, yay.

    Little leery that the fix is "i know a guy"

    Sigh.

    Thursday, November 19, 2009 9:00 PM
  • Scratch that - still getting

    "Active Directory domain has an unrecognized Exchange signature.  Current DomainPrep version: 12639"

    Which is correct according to:
    http://technet.microsoft.com/en-us/library/bb125224(EXCHG.140).aspx

    Thursday, November 19, 2009 9:11 PM
  • I no longer have warnings connecting or that my schema is an unknown version, yay.

    Little leery that the fix is "i know a guy"

    Sigh.


    The problem you first mentioned was that it wasn't connecting to the internet at all, which is what I tried to help get fixed. Does that part at least work for you now?
    Brian Day, Overall Exchange & AD Geek
    MCSA 2000/2003, CCNA
    MCTS: Microsoft Exchange Server 2010 Configuration
    LMNOP
    Thursday, November 19, 2009 9:22 PM
  • Same error message here. Schema version reported by BPA is 12639, which is the correct one.

    Strange that Exchange 2010 BPA doesn't even know it's own version. It does recognize that it's running on exchange 2010, since when you select an exchange 2007 server to scan it reports it can't do that because it's designed for Exchange 2010.

    Franc.
    Sunday, November 22, 2009 9:50 PM
  • also still getting the error...sad that Exchange 2010 shipped in this state...fresh install and event log is crammed with errors and basic troubleshooting tools don't work...nice QA, Microsoft
    Friday, November 27, 2009 6:10 PM
  • Same error. ExBPA no find any new update. When MS make new defenition for ExBPA?
    Truly, Valery Tyurin
    Monday, December 14, 2009 4:07 PM
  • Get this in our ExBPA report, W2K8 SP2 + EXG 2KX

    Active Directory domain 'XXXX' has an unrecognized Exchange signature. Current DomainPrep version: 12639.

    Would like it to go away, or at least know if there is an underlying issue associated to it.

    Wednesday, December 23, 2009 6:56 PM
  • After almost 2 months this is still not fixed.

    Franc.
    Sunday, January 10, 2010 11:35 PM
  • Unfortunately I can't give you a solution, but you can use the feedback button in ExBPA to submit your feedback to the team. Feedback goes to exbpafb@microsoft.com.
    With kind regards / Met vriendelijke groet, Jetze Mellema | http://jetzemellema.blogspot.com/
    Thursday, January 14, 2010 7:42 AM
  • I just received feedback from the ExBPA team, this is a known issue now and will be fixed in SP1 for Exchange 2010.
    With kind regards / Met vriendelijke groet, Jetze Mellema | http://jetzemellema.blogspot.com/
    • Proposed as answer by Jetze Mellema Tuesday, January 19, 2010 12:35 PM
    • Marked as answer by chrislehr Thursday, January 21, 2010 1:09 AM
    Tuesday, January 19, 2010 12:35 PM
  • Thank you - I certainly wish Microsoft would have been transparent about this issue.  It has annoyed the daylights out of me.

    Any idea when SP1 will be released :-)

    _______________________________________

    Vegemeister
    Wednesday, January 20, 2010 10:43 PM
  • I just received feedback from the ExBPA team, this is a known issue now and will be fixed in SP1 for Exchange 2010.
    With kind regards / Met vriendelijke groet, Jetze Mellema | http://jetzemellema.blogspot.com/

    Thanks Jetze!  Marking as answer for now.   I haven't liked showing people the BPA tool because it errors with a critical unknown error!
    Thursday, January 21, 2010 1:10 AM
  • Has anyone built any PowerShell scripts to scan an Exchange 2003 organization for prerequisites to install Exchange 2010 since the ExBPA doesn't seem like an option. I tried to cheat and install the Ex2010 tools in an Exchange 2003 org in my lab but the Ex 2010 install program will run /prepareAD if you install the tools. Once they are installed, it will not function without an Ex2010 server in the environment.

    If anyone has a script to check for environment prerequisites, I would like to see a copy.

    Thanks.


    Ivor
    Sunday, February 21, 2010 9:56 PM
  • Has anyone built any PowerShell scripts to scan an Exchange 2003 organization for prerequisites to install Exchange 2010 since the ExBPA doesn't seem like an option. I tried to cheat and install the Ex2010 tools in an Exchange 2003 org in my lab but the Ex 2010 install program will run /prepareAD if you install the tools. Once they are installed, it will not function without an Ex2010 server in the environment.

    If anyone has a script to check for environment prerequisites, I would like to see a copy.

    Thanks.


    Ivor
    Hi Ivor,

    Not sure what you're looking for, but the environment requirements or pretty straight forward. Have a look at http://technet.microsoft.com/en-us/library/aa996719.aspx Probably you don't need to script anything because I asume you already know if you have an DC/GC/Schema Master running Server 2003 SP1 or higer. And Domain and Forest Functional level are easy to check manually.

    With kind regards / Met vriendelijke groet, Jetze Mellema | http://jetzemellema.blogspot.com/
    Monday, February 22, 2010 1:19 PM
  • Has anyone built any PowerShell scripts to scan an Exchange 2003 organization for prerequisites to install Exchange 2010 since the ExBPA doesn't seem like an option. I tried to cheat and install the Ex2010 tools in an Exchange 2003 org in my lab but the Ex 2010 install program will run /prepareAD if you install the tools. Once they are installed, it will not function without an Ex2010 server in the environment.

    If anyone has a script to check for environment prerequisites, I would like to see a copy.

    Thanks.


    Ivor

    Have a look at the Exchange Server Pre-Deployment Analyzer: http://msexchangeteam.com/archive/2010/02/24/454083.aspx I think this does exacly what you're looking for.
    With kind regards / Met vriendelijke groet, Jetze Mellema | http://jetzemellema.blogspot.com/
    • Proposed as answer by Jetze Mellema Thursday, February 25, 2010 8:47 AM
    Thursday, February 25, 2010 8:47 AM
  • But it's an ExBPA Problem or an Exchange Problem? I think it's not acceptable that a tool that verifies "EXCHANGE 2010 BEST PRACTICES" doesn't even know that it is running in a "Exchange 2010 Extended Forest". How can i trust it for all the other references?
    Please MSFT release an ExBPA Update that fixes this issue.
    Tuesday, March 2, 2010 6:13 PM
  • yeah really, "known issue". That's almost as good as when the other products have that "unexpected error" response.
    Tuesday, June 22, 2010 2:12 PM
  • yeah really, "known issue". That's almost as good as when the other products have that "unexpected error" response.


    I understand your reaction, and I fully agree with what Corrado Mollic write in the posting above yours. But in this case 'known issue' means that the issues is in the picture and a solution will arrive. Based on your feedback here and on other forums, the ExBPA people made a fix which will be there before SP1.

    For now I would ask you to slam Update Rollup 4 to your server and start the BPA, allow it to check for updates on the web. The BPA should detect an update within a couple of days, which fixes the 'unrecognized Exchange signature' error.


    With kind regards / Met vriendelijke groet, Jetze Mellema | http://jetzemellema.blogspot.com/
    Thursday, June 24, 2010 5:52 PM
  • Its funny to see this thread. It just goes to show that sometimes waiting for SP1 for any Microsoft Server product is the thing to do. I mean it really doesn't hold true like it used to.... but this reminds me :)
    Saturday, July 10, 2010 9:54 PM
  • Hi all,

            so far, whit SP1 (whit the Beta) this issue was solved.

    Regards,

    Leonardo Artese

    MCSE - MCTS: Exchange 2007 - MCITP: EMA 2010 - MCITP: EA

     

    Sunday, July 11, 2010 6:20 PM
  • yep we are having the same issue too

    Y doesnt MS release an update for BPA to fix this since before you run BPA it checks for updates automatically.

    instead of waiting for a SP1 any ideas when this will be released?

    im glad i did a google search before following the line of fixing this error in BPA as stated of running domainprep again, who knows what that would have done to our environment.

    Wednesday, July 14, 2010 10:26 PM
  • Hi I have just deployed Exchange 2010 SP1 and am still getting the same error on the ExchBPA. Has it been confirmed that this was resolved with SP1? Our environment was a fresh install of Exchange 2010 SP1 into an existing Exchange 2003 environment. Thanks
    Wednesday, November 10, 2010 9:12 AM
  • Hi,

       Have also just deployed an Exchange 2010 in /hosting mode. Receive the same error. The builds reported are Schema version: 14726 & DomainPrep version 13040 which correlate to those defined here: http://eightwone.com/references/schema-versions/

    There are a number of posts suggesting that this was fixed with SP1, though evidently it is not, or there is still an issue with the BPA tool?

    Anyone have an update?

    Cheers.

     

     

    Wednesday, November 24, 2010 6:04 AM
  • You ain't the only one "Active Directory domain 'Domain' has an unrecognized Exchange signature. Current DomainPrep version: 12639."

     

    December 2010 Merry X-Mas...

    Saturday, December 18, 2010 11:27 PM