• 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 only explicitly installed the commandlet package for 'Quest One ActiveRoles Management Shell for Active Directory x64' 1.7.0.2949 ... yet, when we create a VA in ARS7, and run a get-qaduser username -includedproperties ars7VA ... the commandlet returns the ARS7-only virtual attribute... so I am seeing cross talk despite my best intention.

    The earlier feature set I mentioned - was how the output is formatted by default. ARS7 commandlets improved the information returned without having to weave a powershell script that formats it the way I want. easiest example is get-qarsoperation ... 6.9 concatentated the operationID unless piped to an appropriate format (by default) and 7 expanded it - as it should.
Reply
  • 0 over 7 years ago
    I only explicitly installed the commandlet package for 'Quest One ActiveRoles Management Shell for Active Directory x64' 1.7.0.2949 ... yet, when we create a VA in ARS7, and run a get-qaduser username -includedproperties ars7VA ... the commandlet returns the ARS7-only virtual attribute... so I am seeing cross talk despite my best intention.

    The earlier feature set I mentioned - was how the output is formatted by default. ARS7 commandlets improved the information returned without having to weave a powershell script that formats it the way I want. easiest example is get-qarsoperation ... 6.9 concatentated the operationID unless piped to an appropriate format (by default) and 7 expanded it - as it should.
Children
No Data