Strange result when using Get-RDMRepository
Hi,
I would like to use the PS script to export a Hub Personnal Vault
I used this doc
But when I launch the script I have this message :
"WARNING: Vault does not exist.
Do you want to open the default vault?"
So, I tested commands step-by-step :
Get-RDMDataSource -Name "XXX XXXX"
ID : dfd5e88d-xxxxx
IsConnected : True
IsOffline : False
Name : XXX XXXX
Type : HubPersonal
Set-RDMCurrentDataSource "dfd5e88d-xxxxxxxxxx"
Update-RDMUI
Get-RDMRepository
Description :
ID : ffffffff-ffff-ffff-ffff-ffffffffffff
IsAllowedOffline : True
IsPasswordProtected : False
Name : None
I think that the problem is here, the ID "ffffffff-ffff-ffff-ffff-ffffffffffff"
Why the Get-RDMRepository return this ID "ffffffff-ffff-ffff-ffff-ffffffffffff" ?
Thanks
All Comments (3)
Hello lbaster.
Thank you for contacting the Devolutions support team.
I did some tests around it, and when I tried to connect to the database, it asked me to create an account.
Also, by the web interface, the only export option available is with a JSON file.
https://docs.devolutions.net/hub/web-interface/tools/import-export/#json-export-type
I will follow up with the dev team, but I don't think this is supported at this time.
Also, note that you still can export your vault using right-click on the root folder and select export all as a .RDM file.
Best regards,
Patrick Ouimet
Hi,
Thanks for your answer but the doc about export explain how to export as a .rdm
So if it's not supported why put it in the official documentation and develop a powershell module ?
I think it's just a bug
I know I can export it with right click but I want to automate the export
Thanks
Hello,
A small follow-up on this case.
My version of PowerShell and the module was not up to date.
The script you are using is the proper one, but you don't have to mention the vault since Hub Personal only has one.
The export cmdlet should work as intended.
Best regards,
Patrick Ouimet