This can occur if the ERDisk.mdb file get virtualized due to UAC Data Redirection:
WORKAROUD:
Check to see if the ERDisk.mdb file exists under the following location:
C:\Users\<accountRunningTheCmdlets>\AppData\Local\VirtualStore\
If the ERDisk.mdb file is present in the VirtualStore the file was virtualized and each time the cmdlets are run using invoke-command the updates are made to the virtualized mdb file and not the one the console uses (C:\ProgramData\Quest Software\RMAD or C:\ProgramData\Dell\RMAD)
To prevent the file from getting virtualized, always run the powershell session using elevated credentials and disable UAC.
STATUS:
Enhancement request PT73386814 has been submitted to Development for consideration in a future release of Recovery Manager for AD.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center