WSE 2012 R2 workstion remote web access

A workstation on the Essentials 2012 R2 server had Windows reinstalled to solve a Windows update issues. Everything functioning except the computer was grayed out in Remote Web Access, Uninstalled and reinstalled the connector and the computer is no longer grayed out, however any attempt to connect to it results in the standard message - remote access to the computer is not enabled, the remote computer is turned off or the remote computer is not available on the network. Firewall settings are correct, I can ping it, the computer is being backed up, all other functions work. I can't remote desktop to it from the server. The server has the error below when trying to connect to this computer. There are several revoked certificates for this computer, including the original one. The current Issued certificate is 47, the error displays different certificate number each time including the revoked certificates.
Is there a way to fix the certificate or install on the computer? If not, uninstall the connector again, remove from the server, rename it and run the connector again?

Log Name:      Application
Source:        Microsoft-Windows-CertificationAuthority
Date:          5/26/2015 8:16:54 AM
Event ID:      53
Task Category: None
Level:         Warning
User:          SYSTEM
Computer:      SERVER.Domain.local
Active Directory Certificate Services denied request 46 because The permissions on the certificate template do not allow the current user to enroll for this type of certificate. 0x80094012 (-2146877422 CERTSRV_E_TEMPLATE_DENIED).  The request was for CN=WINDOWS-PC.  Additional information: Denied by Policy Module
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.

Cliff GaliherCommented:
A certificate issue would throw a different error. Since this was a rebuilt machine, look for duplicate stale DNS records. RDGateway is far more sensitive to them than ping, which is not a good DNS test tool.
dpachecoAuthor Commented:
I did look for stale DNS, deleted this workstations record from DNS and DHCP and restarted it. The record was recreated.
I cannot RDP either from the server nor from inside the network either by computer name nor by IP address.

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
dpachecoAuthor Commented:
This was not resolved, I reformatted the computer and re-connected to the domain.
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 Server 2012

From novice to tech pro — start learning today.