• State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 61 subscribers
  • Views 7060 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

Long winded but interesting outside the box question ..

dyannic
over 7 years ago

I've installed both ARS 6.9 and ARS 7 administration services on the same single VM (in our development environment)

This lets me test and easily compare between the two with the smallest virtual footprint.

Since both have different service names, they play well enough together my dev sandbox.

A question came up - about the ARS commandlets.   I didn't update the powershell commandlets - thinking that the newer would supercede or overwrite the 6.9 version.  

Question - When you run a connect-qadservice  - how does/would it know which running service to connect to on the one host?  Do the 6.9 commandlets only connect to 'arssvc', and the 7.0 commandlet versions only connect to 'ARAdminSvc' ?

 

Parents
  • 0 over 7 years ago
    (In my opinion) Strategic. Having two ARS (different versions) on the same server is very unpractical idea. No sure what was the reasoning of the product architect designed the feature. ARS is a *mission critical for compliance* app / HA, and to introduce dependency of change control on ARS 6.x because update of ARS 7.x, and vice versa downs the road from 6.x to 7.x - it is a very unrealistic and unpractical scenarios. All ARS upgrades I do is in-parallel, not in-place because of mission critical factor.
    Technical. ARS MMC can connect to the same version of Admin Service only. I expect this must be valid for cmdlets (as supported and tested scenario)
Reply
  • 0 over 7 years ago
    (In my opinion) Strategic. Having two ARS (different versions) on the same server is very unpractical idea. No sure what was the reasoning of the product architect designed the feature. ARS is a *mission critical for compliance* app / HA, and to introduce dependency of change control on ARS 6.x because update of ARS 7.x, and vice versa downs the road from 6.x to 7.x - it is a very unrealistic and unpractical scenarios. All ARS upgrades I do is in-parallel, not in-place because of mission critical factor.
    Technical. ARS MMC can connect to the same version of Admin Service only. I expect this must be valid for cmdlets (as supported and tested scenario)
Children
No Data