DRA Idea Exchange

Idea ID: 2790913

DRA PowerShell should mimic native AD poweshell

MigrationDeletedUser

Status: Accepted

Accepted

See status update history

over 6 years ago

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.

Tags:

Integrations

Jeff K over 4 years ago

We are currently scoping and planning to update the DRA PowerShell behavior and cmdlets in the next few updates in order to simplify using these cmdlets.
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel
Jeff K over 5 years ago

Bill, we are actively exploring where we can update our DRA PowerShell behavior and where it fits into our roadmap.
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel
billstewart over 5 years 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?
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel
Jeff K over 5 years ago

We are currently exploring this feature and determining where to place on an upcoming road map and release
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel
shocko over 6 years ago

I agree. Piping support a must. Also, being able to specify a default DRA/REST server with a profile variable would be nice.
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel

Resources

Learning Services

Partner Programs

Privacy

Compliance

Help

Company

Privacy Policy
Terms of Use
Cookies Preferences

Accessibility
Anti-Slavery Statement

Support
Contact Us

Careers
Code of Business Conduct and Ethics

The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.