• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 63 subscribers
  • Views 5890 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Why is Exchange Server 2016 not supported until ActiveRoles Server version 7.2?

david_standish
over 6 years ago

We are working on a deployment/migration of Exchange Server 2016 and I'm surprised to find that ActiveRoles Server does not support this yet.

support.oneidentity.com/.../181755

Exchange Server 2016 will have been out for two years if the 7.2 release ETA of November is on track.

I'm wondering if other customers have proceeded with deployments already. Our deployment will be completely on-premises.

Any feedback appreciated.

  • 0 over 6 years ago
    The following Knowledge Base article contains info on planned release of support for Exchange 2016:

    support.oneidentity.com/.../181755
  • 0 over 6 years ago
    Why does it take soo long to implement this Exchange 2016 Support ? just to understand a possible reason why it's not coming sooner ?!

    Assume, Exchange 2016 has no really fundamental changes which may cause developing a complete new interface from ARS to Exchange ..

    thanks
  • 0 over 6 years ago
    Hey Schmihe1,

    Typically it's noted as not supported because it hasn't been fully tested and confirmed to work 100% with the product. It may very well not have any issues at all, it just can not be listed as a supported version until it has been properly put through it's paces.

    Hope this was helpful!
  • 0 over 6 years ago
    though ARS 7.x does not support EX2016 yet.
    I made a test on one of my customer: ARS 7.x had not problem in EX2010/2016 mixed mode organization to (a) read EX2010 and EX2016 mailboxes info (number of items, size) fro Exchange server side and (b) provision EX2016 mailboxes on EX2016 server using Exchange cmdlet called remotely. Customer was happy and was aware of not-supported situation.
  • 0 over 6 years ago
    hello Nick,
    I fully understand this at all ..
    but what is the point now that Quest is not “testing” it in an appropriate time frame ?
    So that for example 1/2 year after release of Exchange 2016, ARS with Exch 2016 support will/can follow .. !