Migration plan - install a second instance of ER and decommission the old one later (4311354)

Migration plan - install a second instance of ER and decommission the old one later

Old version of Quest running on Windows 2012 and SQL 2012 which needs decommissioning. Plan to install a new 3.22 version on a separate system and SQL database

Will installing a new version onto a new system cause an issue with the AD groups and current system.

As long as you deploy the new install in a new box in a new SQL or at least new database (different name if you using the same SQL server) then everything should be ok.

You cannot deploy nodes from two different versions of ER to the same Node system. The newer version will want to update or not even install because of the lower version. The ER 3.0.0 nodes will not work with a higher version of ER. Some thought needs to go into deploying the nodes, I would advise to use machines where there isn't nodes for the older version.

The groups are fine. There have been some changes in the groups over versions such as a new group added, but the 3.2.2 will only use the groups with are associated with it. If the groups already exist then nothing changes and the 3.2.2 version will use them. If a group is not there in AD then it will be added.

The only thing to be aware of is that discoveries should be managed closely. For example, you should not have an Active Discovery running from the two systems at the same time as this will make things very busy on the domain controllers and the network. If ER 3.0.0 is doing an Active Directory discovery then it would be better to do a Computer or SQL discovery with ER 3.2.2. You will still have high network traffic because of the two nodes are working at the same time, but the end point for the discovery is different. Careful planning of these items is the best advice.