the DRA PowerShell cmdlets should mimic AD powershell in usage and return. The Identifier should allow ALL of the same value types as the native AD cmdlets, and should be called Identity rather than Identifier. When you execute Find-DRA... cmdlets they should return a subset of the object properties rather than a set of items that has to be parsed through, even if there is a single results. These cmdlets should also be able to be piped to additional cmdlets to actually work with the objects that are found. They should mimic the ability in native AD cmdlets to specify the DC/Server that will run the operation by using a single -Server parameter to specify a single DRA REST/Host server using default ports rather than using full syntax of DRARESTServer and DRAHostServer and ports.

by: Scott H. | over a year ago | Integrations

Comments

• This is a valid enhancement request. We will evaluate this as a possible enhancement for a future release.

  by: Dennis P. | over a year ago

• I agree. Piping support a must. Also, being able to specify a default DRA/REST server with a profile variable would be nice.

  by: Darragh O. | over a year ago

• We are currently exploring this feature and determining where to place on an upcoming road map and release

  by: Jeff K. | over a year ago

• Automatic discovery of DRA REST server is there in 9.2.1, which is good. However it seems odd that we still have to specify -Domain - why not default -Domain to the current domain?

  by: Bill S. | over a year ago

• Bill, we are actively exploring where we can update our DRA PowerShell behavior and where it fits into our roadmap.

  by: Jeff K. | over a year ago