Jump to content


Photo

Exchange 2016 compatibility


  • Please log in to reply
4 replies to this topic

#1 ej72

ej72

    Newbie

  • Members
  • Pip
  • 2 posts

Posted 21 October 2016 - 12:32 PM

We have been in a co-existence environment with Exchange 2010 and 2016 for a few months. ALE has been working perfectly.

Last night we removed Exchange 2010 from our domain.

I updated the Lockout Examiner Remote Control settings to point to the new 2016 Exchange server.

We still receive email notifications when accounts are locked out, however when we reply to the email with "unlock:password" nothing happens, the account is still locked out and we don't receive any email notification.

We are using ALE 4.1.417.0

 

Here is the relvant portion of the log file:

ALEService.exe Information: 0 : [TID: 34, Time: 10/21/2016 7:09:40 AM] REMOTE CONTROL: ADNServ.ExchangeServerVersion: Version 15.1 (Build 30466.34)
ALEService.exe Information: 0 : [TID: 34, Time: 10/21/2016 7:09:40 AM] REMOTE CONTROL: ADNServ.ExchangeServerSite: CN=XXXX,CN=Sites,CN=Configuration,DC=XXXX,DC=loc
ALEService.exe Information: 0 : [TID: 34, Time: 10/21/2016 7:09:40 AM] REMOTE CONTROL: Listed: CN=CASArray,CN=Arrays,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=XXXX,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=XXXX,DC=loc
ALEService.exe Information: 0 : [TID: 34, Time: 10/21/2016 7:09:40 AM] REMOTE CONTROL: FindFirstValidURL, try connect to the server: casarray.XXXX.loc
ALEService.exe Information: 0 : [TID: 34, Time: 10/21/2016 7:09:40 AM] REMOTE CONTROL: FindFirstValidURL, complite; server: casarray.XXXX.loc
ALEService.exe Warning: 0 : [TID: 34, Time: 10/21/2016 7:09:41 AM] REMOTE CONTROL: System.Web.Services.Protocols.SoapException: The specified server version is invalid.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at ESB2013.ExchangeServiceBinding.FindFolder(FindFolderType FindFolder1)
   at ALService.RemoteControl.Listeners.MSExchange.ExchSoap13MailBox.get_Folders()
   at ALService.RemoteControl.Listeners.ExchangeServerListener.GetMessages(RemoteControlSettings settings)
   at ALService.RemoteControl.Listeners.DefaultMessageListener`1.OnDoWork(DoWorkEventArgs e)

Thank you.



#2 jeffb

jeffb

    Advanced Member

  • Administrators
  • PipPipPip
  • 384 posts
  • Gender:Male

Posted 24 October 2016 - 01:52 PM

Hello,

 

This feature has not been tested against Exchange 2016 and from the looks of the error the remote calls we use do not work on this version of Exchange.  There are currently no plans to extend the products functionality to new Exchange versions however if more people use it then it will for sure be heavily considered.

 

-Jeff



#3 ej72

ej72

    Newbie

  • Members
  • Pip
  • 2 posts

Posted 24 October 2016 - 03:35 PM

Thank you for the reply.



#4 dg1

dg1

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 16 March 2017 - 08:20 PM

We have the same issue. We have really liked using Netwrix Account Lockout Examiner to unlock accounts on the fly, so it would really be great to have an update or a replacement tool that did the same thing...



#5 dls

dls

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 15 April 2018 - 07:27 AM

We have the same issue. We have really liked using Netwrix Account Lockout Examiner to unlock accounts on the fly, so it would really be great to have an update or a replacement tool that did the same thing...

 

We heavily rely on this tool to unlock users after hours (especially in the middle of the night).  I hope you will please fix this.  I have been using this tool for over 10 years.  It's a life saver.

 

-David






0 user(s) are reading this topic

0 members, guests, anonymous users