SecretServer User handling for Win2012R2

SecretServer User handling for Win2012R2

avatar

Hi,
I haev an issue with RDP to Windows 2012 R2 Machines with an Local User.

The problem is:
The Machine Name is not sent with the Username. So instead of a user "Server1/User1" it just sends "User1". which is not accepted by the Servers Terminal Services authentication.

Solution:
For Win2012 change the user handling to "Server1/User1"

Thanks!

All Comments (11)

avatar

Hi,
We have setting in the Advanced section of the Connection:

Force machine name as the domain name

Could you give it a try?

David Hervieux

avatar

Hi David,
Thank you, this is working (with Domain\Username format only! Not username@domain.com !)

I think i have found the reason for this:
It happens for machines running Windows Server 2012 R2 which are joined to a domain. When you try to connect using a local password it failes!

Could you try to maybe add this feature on the credental level instead of the session level? or let us choose what field to use for the domain field?

Thanks
Peter

avatar

Hi,
I will enter a feature request for that to change the username format in the credentials

David Hervieux

avatar

Do you have a status for this?

avatar

It's not done yet but it's should be done soon. It's on the top of my list.

David Hervieux

avatar

Hello Peter,

Sorry for the wait. The username format feature will be available on the credential level. When a connection's own username formatting is set to "Default", it will use the credential's formatting.

This will be available in the next beta version of RDM.

Regards,

Hubert Mireault

avatar

The REAL Problem is:
I have a machine in a domain everything fine.
I conntect to this (domain) machine via a Credential "Local Admin" (NOT Domain) -> the domain part on the connection is empty!

avatar

Hi Peter,
I think that we need few print screen to understand your issue.

David Hervieux

avatar

Hi David, i sent you the screenshots via pm.

avatar

Hi Peter,
I won't be available next week. I will send your message to Hubert.

Regards

David Hervieux

avatar

Hello Peter,

I think I found how to make this work in your scenario. In your credential (the one that doesn't have a domain), can you put the variable $MACHINE_DOMAIN$ in the domain field of that credential? It should take the domain of the connection that is using this credential at the time.

Regards,

Hubert Mireault