KaceSMA
KaceSMA copied to clipboard
A module for interacting with a Quest Kace Systems Management Appliance API via Powershell.
Starting with KACE SMA 12.0, the headers `x-dell-api-version` becomes `x-kace-api-version`, and `x-dell-csrf-token` becomes `x-kace-csrf-token` https://support.quest.com/kb/276970/verifying-api-connection-with-postman I'm guessing that some logic should also be added that can support the old and...
I want to update the owner field on an asset. When I run Get-SMAAsset I get this: ``` id : 7341 asset_type_id : 10202 name : Polycom VVX 411 (PoE)...
Having issues creating a new asset and a barcode with it. From the documentation barcodeData schema, it looks like the monitor asset has to be created before the barcode can...
With 10.x now supporting SAML Authentication, it would be great if this module supported servers where SSO was utilized for logins.
The canned error message from Connect-Server does not give any information that could be useful for troubleshooting. If I was put in the wrong org, I should receive: (500) Internal...
Each cmdlet sets the TLS negotiation at a minimum of TLS 1.2. Obviously trying to connect over HTTP would not work in this case. There have been a few reports...
This might be a documentation bug or a problem with the endpoint itself. This should not be exposed until it has been fixed upstream or the docs are updated with...
I can successfully retrieve the archival status of an asset with Get-SmaAsset, using `-QueryParameters "?filtering=asset.archive eq completed,asset.id eq 1234"`, however, running `Get-SmaArchiveAsset` against the same AssetID returns a 500 error....
If the ORG feature is not licensed, the module can authenticate but possibly returns 401 un-authorized for all subsequent POST requests