local login credentials appears to be ignoring domain field.
i'm surprised i cannot find any info on this, so admitted defeat and come to ask...
I've used RDM for years. both in a team environment and more recently as the "free" teir offering.
Some of our servers have been removed from the old domain and are now workgroup servers, thus need to use the .\USERNAME method to login.
My laptop with RDM installed is on our new domain.
I've created a new username&password credential entry with the following details. I want to be prompted for the password every login, so the password remains empty.
name = LocalAdmin username = localadmin domain = . password = EMPTY
in the RDP connection, i've updated the 'credential' field to 'Linked (vault)' type, and referenced this LocalAdmin credential entry.
save & attempt to login.
RDM correctly prompts for the password.
The server then fails to accept the credentials and comes back as localadmin@newdomain.tld, and not .\localadmin as expected.
it appears to be ignoring the '.' domain in the credential entry.
whats the secret to getting this to work with a local login?
All Comments (3)
Hello,
Thanks for your post!
Typically, if you leave the domain field blank, RDM should default to using a local login—unless a domain is specified elsewhere. You might also try entering the username directly with the .\ prefix in the username field, like this (keeping the Domain field empty):
Username: .\localadmin
This should ensure that RDM correctly interprets it as a local account.
Let me know if this works for you or if we need to dig deeper! 😊
thanks for that info, after a bit more testing it was actually quite simple.
in the saved credential entry, username only (no .\ prefix), empty domain, and 'always ask for password' (it cannot just be left empty).
RDM will then prompt for the password, and not hand it off to mstsc/windows auth prompt.
Hello,
It's great to hear it's working for you now.
The next troubleshooting step would have been changing the username Format in the Advanced section of the RDP entry, where you can choose a specific format.
If you are experiencing similar issues, this would be worth the try!