# Automating Certificate Imports on Microsoft Systems - Certificate Imported but Not Applied

**URL:** <https://community.letsencrypt.org/t/automating-certificate-imports-on-microsoft-systems-certificate-imported-but-not-applied/34980>\
**Category:** Help\
**Created:** [May 26, 2017, 1:34pm UTC](https://community.letsencrypt.org/t/automating-certificate-imports-on-microsoft-systems-certificate-imported-but-not-applied/34980 "2017-05-26T13:34:44Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ahaw021](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/ahaw021/32/14882_2.png) [@ahaw021](https://community.letsencrypt.org/u/ahaw021)\
**Post date:** [May 27, 2017, 12:07pm UTC](https://community.letsencrypt.org/t/automating-certificate-imports-on-microsoft-systems-certificate-imported-but-not-applied/34980/2 "2017-05-27T12:07:18Z")

</div>

hi @mobamoba

You should really use a Windows Library to do this.

You are missing an important point. Importing a certificate (thumbprint xx:xx:xx) is not the same as applying it to a service.

If you want to for example apply a certificate to an IIS site you have to use the the thumpbrint.

Lets say you have a binding for domain test.xyz and two certificates for that domain (yy:yyy:yy) IIS will not start using (xx:xx:xx) until you tell it to

review: [https://docs.microsoft.com/en-us/iis/manage/powershell/powershell-snap-in-configuring-ssl-with-the-iis-powershell-snap-in](https://docs.microsoft.com/en-us/iis/manage/powershell/powershell-snap-in-configuring-ssl-with-the-iis-powershell-snap-in)

Also review this article which shows some of the automation you can do: [Using Let's Encrypt to secure Windows Remote Desktop connections](https://community.letsencrypt.org/t/using-lets-encrypt-to-secure-windows-remote-desktop-connections/29964/4)

Andrei

---

_[View the full topic](https://community.letsencrypt.org/t/automating-certificate-imports-on-microsoft-systems-certificate-imported-but-not-applied/34980)._
