Skip to main content
Question

Injecting "Domain\account" credentials through Remote RDP

  • June 5, 2026
  • 4 replies
  • 32 views

Forum|alt.badge.img+4

Hi everybody, hope y’all having a great friday so far.

Even though we know Windows 2003 are out of support, we still have a couple running precious services, and we’re on track to upgrading them.  There are accounts on our Password Safe that go through PRA ECM integration for injecting credentials. That works for 99% of the newer Windows machines except these. We realized that whenever we jump to these, the main issue is the “format” of the credentials are wrong (even it says in the login menu of the machine).

Is there a workaround or any ideas that might worth a try?

 

Thanks!

 

 

 

 

 

4 replies

  • BeyondTrust Employee
  • June 8, 2026

Hello ​@NectarNinja 

Please have a look at this KB.

https://beyondtrustcorp.service-now.com/csm?id=kb_article_view&sysparm_article=KB0017307

You can use the OptionalIncludes file to change the Account Name Format used on Windows RDP, Client and Launcher Jump Item Types.

A sample entry to use domain\Username when connecting to Server01

  {
    "PlatformName": "Windows",
    "CredentialType":"domainlinked",
    "JumpItemType": "rdp",
    "AccountNameFormat": "DownLevel",
    "TargetSystems": [
    "Server01"
    ]

Regards,

John


Forum|alt.badge.img+4
  • Author
  • Rising Star
  • June 9, 2026

Thanks so much ​@jchandler , I appreciate the knowledge. However, this is Both SaaS deployments (PAssword safe and PRA) for the customer, I’m not sure how to proceed. Also: Will this affect All Jump Items? We have some newer windows where the current state of the credential injection works flawlessly.

Cheers!


Forum|alt.badge.img+4
  • Author
  • Rising Star
  • June 9, 2026

Would these changes still apply? On the Resource Broker or Jump Server? side?


  • BeyondTrust Employee
  • June 9, 2026

If you are running the SaaS Password Safe you would need to deploy the standalone ECM server which could be deployed on your Resource Broker. 

Then you configure  OptionalIncludes config file in the ECM install directory.

 

Here is our doc on setting up the ECM

Password Safe and Endpoint Credential Manager | PRA 

And this doc for configuring the optional includes

https://beyondtrustcorp.service-now.com/csm?id=kb_article_view&sysparm_article=KB0017307

 

This is a sample entry 

DownLevel set the format to domain\username for the systems listed under Targetsystems

A sample entry to use domain\Username when connecting to Server01 and Server02

  {
    "PlatformName": "Windows",
    "CredentialType":"domainlinked",
    "JumpItemType": "rdp",
    "AccountNameFormat": "DownLevel",
    "TargetSystems": [
    "Server01",

     Server02
    ]

 

The AccountNameFormat can be modified to use one of the following:

  • "DownLevel" - hostname\username or domain\username
  • "OriginalName" - unedited value directly from Password Safe
  • "UPN" - username@domain
  • "UsernameOnly" - username only