Can a Remote Desktop certificate be configured to issue a Subject Alternative Name in NetBIOS format in addition to the FQDN?

Folks -

Per the article linked to below, I have configured a certificate template on my internal PKI that is properly issuing certificates for use by the terminal services/remote desktop client in Windows 7.

http://blogs.msdn.com/b/rds/archive/2010/04/09/configuring-remote-desktop-certificates.aspx

However, I receive a certificate validation warning when I attempt to connect to the destination computer via its NetBIOS name rather than its FQDN.  The validation warning is complaining that the name the certificate was issued to does not match the name of the destination computer.  Well, that's because the template didn't place both "ComputerX" and "ComputerX.domain.lcl" on the cert.  It doesn't appear to issue the cert with a Subject Alternative Name that would allow connectivity with either name.

The template has some additional options for what to include in the certificate.  One of which are the Service Principal Names of the account.  I selected that but it made no difference to the behavior.  I would have assumed that since both HOST/ComputerX and HOST/ComputerX.domain.lcl are default SPNs on all computer accounts that both names would end up on the certificate - they don't.  Only the FQDN does, so I'm in the same boat.

Has anyone figured out a way around this?  Is it possible to get the template to issue a cert for the purposes of RDP with both the FQDN and NetBIOS names included?

This is purely for RDP console support purposes - general remote workstation administration by a help desk.  No RD gateways, brokers, VDI, etc. involved.  Simple P2P connectivity.

Thanks.
amendalaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

footechCommented:
To the best of my knowledge, there is no automatic way to do this.  I think you could manually create a cert with this info though, using the certificate service webpage on a standalone CA (don't think it will work on an Enterprise CA).
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
amendalaAuthor Commented:
Yeah, we are trying to accomplish this through auto-enrollment.  Given that we had thousands and thousands of workstations, obviously, manual issuance and renewal would be well - a headache to say the least.  :)

I'll keep the question open for a bit to see if anyone else knows.
0
amendalaAuthor Commented:
It doesn't seem this can be done based on conversations I've had with Microsoft PFE's.  Going to close the question out.
0
footechCommented:
I wish it was.  I looked into it some time ago as I figured it would be nice not to have the warning all the time when making RDP connections to various machines.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.