So I think I am running into a bigger issue here....When I try to apply the certs, I get "Invalid Private Key"...What I found out is that when the CSR was created, it was done through the backend with openssl. Does the CSR need to be created through the NetSUS GUI in order for the certs to apply?
I have four files that I was given by our Network team, who handles obtaining certs, and they are as follows: ServerCertificate.crt, ChainBundle.crt, .pem, and .csr.
I placed the .pem file contents in the "Private Key" field. The ServerCertificate.crt file contents were placed in the "Certificate field" and the ChainBundle.crt file contents were placed in the "CA Bundle" field.
Turns out that the private key was in the wrong format that NetSUS accepts, so converting it from .pem to .key was the solution.
I am however experiencing issues with our devices not being able to see updates from the SUS. I built it identical to our old NetSUS server but for some reason every computer that checks in for updates comes back with "0 updates found". If I switch it to Apple's server or our old NetSUS, it can see the updates just fine. Any ideas as to what may be preventing the updates from being found?