ESMX Exchange 2010 SP1 support

Discussion in 'Other ESET Home Products' started by DrFix, Sep 15, 2010.

Thread Status:
Not open for further replies.
  1. DrFix

    DrFix Registered Member

    Joined:
    Nov 11, 2009
    Posts:
    20
    When ESMX supporting Exchange 2010 SP1 will be available?
    Now .19 version only supports SP1 BETA and it doesn't recognizes released SP1 version...
     
  2. rockshox

    rockshox Registered Member

    Joined:
    Oct 23, 2009
    Posts:
    261
    We have been running SP1 with 4.2.10019 for about a week and haven't had any issues due to installing SP1 that we have noticed yet.
     
  3. DrFix

    DrFix Registered Member

    Joined:
    Nov 11, 2009
    Posts:
    20
    We have the previous version installed and it doesn't recognizes any mail server.
    Trying installing the .19 version it says that no exchange server is installed on setup startup...
     
  4. nonoise

    nonoise Registered Member

    Joined:
    Jun 6, 2008
    Posts:
    322
    Did you try this?
     
  5. DrFix

    DrFix Registered Member

    Joined:
    Nov 11, 2009
    Posts:
    20
    Yes, nothing changed...
     
  6. rockshox

    rockshox Registered Member

    Joined:
    Oct 23, 2009
    Posts:
    261
    We probably did not see that issue as 4.2.10019 was installed prior to us installing SP1. We had issues in the past with one of the rollups having the issue you are describing and halting the installer as it thought that Exchange was not installed.
     
  7. AJStevens

    AJStevens Registered Member

    Joined:
    Aug 27, 2008
    Posts:
    97
    Location:
    Surrey, UK
    Very likely Exchange 2010 SP1 is supported in next ESMX version which they're working on now I'm sure and will release once ready.
     
  8. Berserker

    Berserker Registered Member

    Joined:
    Jul 28, 2010
    Posts:
    7
    Just a heads up if anyone is running an older build of ESMX on Ex2010 SP1 and plans to upgrade to at least build 10020.

    You may run into the issue where the installer gives you the "no Exchange install found" message. If it does, don't attempt to force uninstall ESMX first because it will remove all your network adapters/config/drivers. If you're running a DAG, this is a pain to get going again.

    I have opened a case w/ESET support for a better solution so I'll post back once I know. Thanks goodness I did this on a passive node first.

    Summary of my issue:

    Was running Exchange 2010/Windows 2008 R2/ESET Mail Security 4.2 build 10016

    Upgraded to Exchange 2010 SP1

    Noticed that ESET Mail Security did not recognize Exchange any more, specifically under Mail Server Protection, no Exchange reference was listed.

    Attempted to install ESET Mail Security build 10020.

    Installer states no Exchange install was found.

    Tried ESET KB article 2411, however it did not work: http://kb.eset.eu/esetkb/index?page=content&id=SOLN2411

    Contacted ESET support. Support recommended I force uninstall ESET Mail Security build 10016 then install build 10020.

    Exported current ESET Mail Sec settings.

    Ran the force uninstall procedure here: http://kb.eset.eu/esetkb/index?page=content&id=SOLN2289

    This successfully removed my ESET Mail Sec product, however it removed all the network adapters, network configurations, and network adapter drivers. I noticed upon reboot that I had no network settings and going into Network and Sharing Center would hang. I discovered this by reading the Uninstall Log that the ESET uninstall tool created. It removed all NIC related info.

    Took some time to figure that out, re-add the adapters and drivers, and finally reconfigure network settings.

    So build 10020 is running now but not without a huge amount of hassle. Can't have an e-mail server without network adapters :(
     
  9. Berserker

    Berserker Registered Member

    Joined:
    Jul 28, 2010
    Posts:
    7
    Worked with ESET Support today and made some progress on this. My process above was on one node of the DAG. I hesitated doing the procedure again on my other node becuase of the NIC removal issue.

    They determined that my upgrading to Exchange 2010 SP1 prior to upgrading the Mail Security to an SP1 supported build is the cause of my issue.

    So then we took a closer look at the KB article for the reg key change:

    ESET KB article 2411: http://kb.eset.eu/esetkb/index?page=content&id=SOLN2411

    I asked the support tech to try it again as I may have done it incorrectly. However, he ran into the same issue as I did previously.

    When peforming the KB article instructions, the "NewestBuild" reg key was not existant in the path it stated and had to be made. This didn't work. However, when he was browsing around the registry, I noticed a different reg path that actually had the "NewestBuild" key there.

    That path is: HKLM\Software\Microsoft\ExchangeServer\v14\Setup

    This path had the "NewestBuild" key with a diff value. So we backed up that key, changed it to 0000298f as per the KB article, and that allowed us to uninstall Mail Security successfully. Don't reboot just yet, then re-import the original reg setting.

    The KB article also should specify that the key is a DWORD entry.

    At this point, we are waiting to:

    1. Reboot the mail server.
    2. Install the latest build of Mail Security.
    3. Import the config.
     
    Last edited: Mar 3, 2011
  10. JesusV

    JesusV Former ESET Support Rep

    Joined:
    Jan 21, 2010
    Posts:
    93
    Hey Berserker,

    If you double check the article, it has been updated with the necessary changes. Thanks for the heads up.

    Regards,

    Jesus
     
  11. Berserker

    Berserker Registered Member

    Joined:
    Jul 28, 2010
    Posts:
    7
    We rebooted the server last weekend and everything came up OK. The install for EMSX build 10020 went smoothly and the Exchange "awareness" is now visible again in the Advanced options of EMSX. So looks like this resolved it!

    Yes, I noticed the update to the KB as well, thanks for the heads up.
     
  12. DrFix

    DrFix Registered Member

    Joined:
    Nov 11, 2009
    Posts:
    20
    Yes, it worked for me too!! :)
    Really thanks a lot!!
     
Thread Status:
Not open for further replies.