Hello dear all,
We want to make the Windows local scan accounts manageable by onboarding them into Password Safe using a Managed Account Smart Rule. However, for this to work, the local account must appear under the Advanced Details of the asset before it can be automatically onboarded.
The issue is that, for some managed systems (MS) where we want to onboard the local scan account, these accounts do not show up in the asset’s Advanced Details.
To resolve this, I understand that we need to perform a new scan on those systems using the previous local scan credential, so the system can retrieve and display the local account information. But this process is quite painful, especially considering there are over 30 managed systems, and we’d have to reconfigure all scheduled scans afterward to use the new Managed Account scan credential. As you know, you can’t change the scan credential to a managed account after the scan is created — it must be set during the initial scan setup.
Do you have any suggestions to make the local accounts appear without having to redo all the scans? Or perhaps an alternative approach to achieve the same result with less overhead?
