Exchange 2010 Update Rollup 17 EMC version mismatch RRS feed

  • Question

  • After installing UR 17 on our Exchange servers (4 servers), and then installing UR 17 on our workstations (Running the console only), we can no longer connect to exchange.

    There is a version discrepancy - it seems the client computers are running version 14.3.352.0, and Exchange is running 14.3.351.0, and thus all our supporters cannot connect to Exchange through the management console.

    We are installing the same patch on all computers (KB4011326).

    Has anyone experienced anything like this and is there a solution?


    Friday, May 5, 2017 6:32 AM

All replies

  • Same issue here but on CAS Servers, which causes OWA Proxy Problems between CAS Servers.
    I have 10 Standard Server, all with Ex2010SP3RU17, only one has 14.3.352.0 all others 14.3.351.0...

    Saturday, May 6, 2017 7:37 AM
  • Hello

    Check for these 2 kbs are installed on exchange or dc.

    If it's installed then uninstalled it.



    • Edited by 201SAM201 Sunday, May 7, 2017 7:47 AM
    Sunday, May 7, 2017 7:46 AM
  • Hi,

    What's the result of the following command against that four Exchange Servers?

    Get-ExchangeServer | FL Name,*admin*

    Open ADSIEdit, go to CN=ServerName,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=com

    Check serialNumber attribute for all servers.

    Let me know the results.

    Best Regards,

    TechNet Community Support

    Please remember to mark the replies as answers.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, May 8, 2017 3:13 AM
  • This all shows Version 14.3 (Build 123.4). But that Version number does not matter!

    "Get-Command ExSetup | ForEach {$_.FileVersionInfo}"
    ProductVersion   FileVersion      FileName
    --------------   -----------      --------
    14.03.0351.000   14.03.0351.000   C:\Program Files\Microsoft\Exchange Server\V14\bin\ExSetup.exe

    should be:

    ProductVersion   FileVersion      FileName
    --------------   -----------      --------
    14.03.0352.000   14.03.0352.000   C:\Program Files\Microsoft\Exchange Server\V14\bin\ExSetup.exe

    All Folders under the OWA and ECP Folder are Version 14.03.0351 too, which causes Proxy Problems. Normally copying the Files to the CAS Server works, but here not which is really sh**!
    Monday, May 8, 2017 6:29 AM
  • Hi there,

    same here with Exchange 2010.

    "Get-Command ExSetup | ForEach {$_.FileVersionInfo}" is responding with Product- & FileVersion 14.03.0351.000

    According to https://technet.microsoft.com/en-us/library/hh135098.aspx, this version doesn't exist!

    Best regards,


    • Edited by Gahmuret Thursday, May 18, 2017 10:41 AM
    Thursday, May 18, 2017 10:41 AM
  • Hi,

    Has there been an update/fix for this?

    I have just installed update rollup 17 for Exchange 2010, product and file version both displaying 14.03.0351.000.

    This is causing problems connecting with the remote management tools as there is a version mismatch:

    "Due to potential compatibility problems, can't connect to version 14.3.351.0 server using version 14.3.352.0..."

    Again, 14.03.0351.000 is not listed as a version, it should be 14.3.352.0??

    Any help, advice or update on this would be appreciated.

    Thanks in advance.

    • Edited by Ando2017 Monday, May 22, 2017 4:07 PM
    Monday, May 22, 2017 2:32 PM
  • Same issue here.  We have multiple CAS servers but one of the servers (where we installed the patch manually to test - the rest were installed via WSUS) has 14.3.352.0 the rest have 14.3.351.0.  We've had to power the server off as it was causing issues with OWA access.

    Any ideas what the fix is?

    Tuesday, May 23, 2017 8:16 AM
  • The windows update one seems bad! Download from the microsoft download center and re-install.  Exchange 2010 SP3 rollup 17 build number should now be correct at 352 instead of 351.


    Saturday, May 27, 2017 9:19 PM