RemoteApp “Publisher Can’t Be Identified” Warning

Windows logo

Short answer: “The publisher of this RemoteApp program can’t be identified” means the RemoteApp shortcut (for example Dolphin Management on a Remote Desktop server) is not signed by a certificate your computer trusts. Clicking Connect is safe if you recognise the server. To stop the warning for good, your IT administrator signs the RemoteApp with the Remote Desktop publishing certificate and tells workstations to trust it through Group Policy.

An orthodontic practice contacted us because their practice manager could not get into Dolphin Management from a desk at one of their sites. Instead of Dolphin opening, a yellow RemoteApp security warning appeared saying the publisher could not be identified, and she was not sure whether it was safe to continue. The Remote Desktop server was online and every other desk was working. The problem was on that one workstation, which did not trust the certificate used to publish the Dolphin shortcut. Here is what the warning means and how to fix it.

Fixed by Dan Redman at GCIT. Written up by Elliot Munro, CISO.

Symptoms

When you open a program published from a Remote Desktop server, such as Dolphin Management or Dolphin Imaging, this window appears:

The publisher of this RemoteApp program can’t be identified. Do you want to connect to run the program anyway? This RemoteApp program could harm your local or remote computer. Do not connect to run this program unless you know where this program came from or have used it before.

The details show Publisher: Unknown publisher, the program name, the remote computer and the gateway server. Other signs:

  • It appears on one computer but not others that use the same shortcut.
  • It starts after a workstation is replaced or rebuilt, or after the server’s certificate is renewed.
  • Staff are blocked because they are unsure whether to click Connect.

RemoteApp security warning for Dolphin Management: The publisher of this RemoteApp program cannot be identified

Affected Software

  • Application: Any RemoteApp program, including Dolphin Management and Dolphin Imaging, practice management systems and accounting software published from a Remote Desktop server
  • Platform: Windows 10 and 11 workstations connecting to Windows Server Remote Desktop Services, often through an RD Gateway or RD Web Access

Cause

A RemoteApp shortcut is really a small .rdp file. Windows checks whether that file was signed by a publisher it trusts. If the file is not signed, or it is signed with a certificate this computer does not trust, Windows shows “Unknown publisher” and asks the user to confirm before connecting.

It usually appears on one workstation because that computer is missing the trust setting the others have, for example a newly built PC, a computer that has not received the latest Group Policy, or a computer outside the practice network. It can also appear for everyone after the server’s publishing certificate is renewed and the old thumbprint is still the one workstations trust.

Resolution

Step 1: For staff right now

  1. Check the Remote computer and Gateway server shown in the warning are your practice’s own server and web address.
  2. If they are, click Connect. The program opens normally.
  3. If anything looks unfamiliar, click Cancel and call your IT provider.

Step 2: Check the workstation (IT administrator)

  1. Confirm the computer is joined to the practice domain and has the latest Group Policy (gpupdate /force, then sign out and back in).
  2. Re-download or re-create the RemoteApp shortcut from RD Web Access so it carries the current signature.
  3. Check the certificate used by RD Web Access and the RD Gateway is valid, not expired and trusted by the workstation.

Step 3: Sign the RemoteApps and trust the publisher

  1. On the RD Connection Broker, open Server Manager > Remote Desktop Services > Overview, choose Tasks > Edit Deployment Properties, open Certificates and make sure RD Connection Broker - Publishing has a valid certificate. This is the certificate that signs RemoteApp .rdp files.
  2. Copy that certificate’s SHA1 thumbprint.
  3. In Group Policy, edit Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client > Specify SHA1 thumbprints of certificates representing trusted .rdp publishers. Enable it and paste the thumbprint.
  4. Apply the policy to every workstation that uses the RemoteApps. Signed shortcuts from that publisher then open without the warning.
  5. When the publishing certificate is renewed, update the thumbprint in the policy at the same time.

Important Notes

  • Do not train staff to click through every warning. The warning exists to catch fake .rdp files sent by attackers. Fix the trust setting so genuine shortcuts open cleanly, and any warning that does appear is worth stopping for.
  • “Don’t ask me again” only fixes that one computer. Ticking it on the warning stores the choice for that user on that computer. Group Policy fixes every workstation.
  • Dolphin still not loading after Connect? If Dolphin freezes, will not book patients or cannot print reports once it opens, the problem is more likely the Remote Desktop server or the Dolphin database. Ask your IT provider to check the server and Remote Desktop sessions.

If you need help keeping your practice software running on Remote Desktop, get in touch with our team.

Was this article helpful?
Ready to secure and simplify your IT? Talk to a GCIT expert today.