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

Can Active Roles version 6.9 coexist with version 7.3.1

We are planing to install a new version of ARS version 7.3.1 to run along side current version 6.9.  The installation will be performed using new servers.

Current infrastructure:

2 ARS servers and 2 Web interface servers with database pointing to SQL cluster for HA.

New infrastructure:

2 ARS servers and 2 Web interface servers with database pointing to same SQL cluster as version 6.9 for HA.

  • I would recommend two different ways to look at the situation proposed:

    #1. Technical. Correct, two/more AND different/same version *independent* AR deployments (here legacy AR69, new AR73) can coexist in (point to) the same AD domain. It is supported.

    #2. AD Workflow Architecture. It is not recommended to have two/more *independent* AR deployments (two *independent* Automated Workflows) to hit the *same* AD scope: it is very risky and dangerous situation for many reasons.

    Note, #2 can be used during in-parallel side-by-side Upgrade (73 from 69, here) - there are few tricks PSO might do to leverage the risks associated with #2. 

    In general, your direction with side-by-side Upgrade seems to me correct.

    AR documentation explains the Upgrade pretty well (in general terms). If you need details and logistical risk leverage/backup/roll back/smooth cutover during Upgrade of AR Enterprise Level Frond End Application and Change Controls associated with the upgrade, I would recommend engage Quest PSO for Upgrade Best Practices guidance. Let us (Quest) know if you need a help here.

  • Thank you for your answer that helps quite a bit.