Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get-ePORecoveryKey - binary key file #34

Open
ttmme opened this issue Oct 11, 2021 · 0 comments
Open

Get-ePORecoveryKey - binary key file #34

ttmme opened this issue Oct 11, 2021 · 0 comments

Comments

@ttmme
Copy link

ttmme commented Oct 11, 2021

In the cmdlet Get-ePORecoveryKey, if the endpoint have a Recovery Key that is a "binary key file" the export process stops with "Recovery key type is not currently supported" and do not export any key from that endpoint.
Is possible to continue the process and export the renaming supported keys?

In debug mode last step before process stops:

VERBOSE: GET https://abcd:8443/remote/mne.recoverMachine?:output=json&serialNumber=25AD28EFAXXXXXXX with 0-byte payload
VERBOSE: received 58-byte response of content type text/plain;charset=UTF-8
DEBUG: Response:
StatusCode        : 200
StatusDescription : OK
Content           : Error 0 :
                    Recovery key type is not currently supported.
RawContent        : HTTP/1.1 200 OK
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant