Question: I'm trying without any luck to use [**NTSysLog**](http://troy.jdmz.net/syslogwin/) in order to grab my network computers *Security Logs* and send them into a Log Service ([**Loggly**](http://loggly.com/) in this case).

I can install and run NTSysLog from a Windows 7 Professional machine 

![enter image description here](https://i.stack.imgur.com/riiCI.png)

from Loggly I only have Unix related setup help and they specify:

```
:: Syslog ::

For UDP, put this in /etc/syslog.conf:
     *.*    @logs.loggly.com:46031

To restart:
     /etc/init.d/syslogd restart

:: rsyslog ::

For UDP, put this in rsyslog.conf:
    *.*    @logs.loggly.com:46031

```

From this, **How can I setup a Windows machine** correctly without the need of setting up a Linux machine to be the SysLog server from then I would send the messages to the Log Service?

Setting the **Primary Syslog Daemon** as it shows in the image above, does not log it.

Answer: 
You can't install a certificate on a machine unless the corresponding private key is already installed. Even if you could, what would the point be? A certificate binds a key to an identity. Without the key, the certificate is useless. (The certificate is public. The key is private.)

Likely the server it worked on has the private key already, possibly because the private key was generated on that machine. The instructions in the support blog you link assume the private key is already installed on the machine.

You need to export the private key from the machine that generated the CSR. Then you can import that private key on other machines so that they can use the certificate to identify themselves.
mmc is not very user friendly with the snap in module etc. If you going to do operations like exporting and reimporting certs on IIS like David suggested you may want to look at other more user friendly tools like [SSLTools Manager](http://www.ssltools.com/manager)