You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: