[evanelias]

Worse still, the SafeNet software that my cert vendor recommends using (to interact with the hardware key) doesn't even allow use of Remote Desktop sessions!

It somehow detects if you're in an RDP session, and shows that there are no hardware tokens attached if that's the case. No message or warning whatsoever. My only Windows PC is headless and I lost several hours trying to debug this.

The entire EV cert process is such an outrage. My cert vendor advertised that the validation process would take 2-3 business days if all docs were in order, DUNS info correct, etc. I spent a lot of time ahead of the order ensuring the docs were indeed in order, and the process still inexplicably took 9 business days.

[cjensen]

One way around SafeNet is to run the builder in a VM, then RDP into the host.

[vb6sp6]

or use vnc, teamviewer, etc

[josephcsible]

Can you use a VNC server instead as a workaround, or does it detect that too?

[rstupek]

Oh man I totally got hit by that and never did figure out being in rdp was the reason!

[geitir]

Maybe try something like TeamViewer since rdp virtualizes the display adapter and likely other things

[viraptor]

It's not about virtualisation. RDP sessions are actually marked as remote login sessions. The login source can be checked easily in each app. (or just run `net session`)

If TeamViewer acts on an already logged-in local session, it should work well.