• State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 61 subscribers
  • Views 7056 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
    I have upgraded environments and dealt with the challenge of multiple cmdlet versions.

    If you are not using the '-proxy' switch, you can continue to use the "old" cmdlets if you like.

    I'm not sure what you mean by the "earlier version feature set" as functionality-wise (6.9 service compatibility notwithstanding), you don't lose anything going with the 7.x cmdlets?
Reply
  • 0 over 7 years ago
    I have upgraded environments and dealt with the challenge of multiple cmdlet versions.

    If you are not using the '-proxy' switch, you can continue to use the "old" cmdlets if you like.

    I'm not sure what you mean by the "earlier version feature set" as functionality-wise (6.9 service compatibility notwithstanding), you don't lose anything going with the 7.x cmdlets?
Children
No Data