SCCM-Migrating form HTTP to HTTPS

SCCM-Migrating form HTTP to HTTPS
4.4 (88%) 5 votes

Hi All,

have you ever needed to migrate a SCCM 2012 (or Current Branch) environment from HTTP to HTTPS? if you have, you know that it is quite easy, but there are some challenges, when things go wrong, off course :)…

The steps I normally take (and I hope I haven’t forgotten any :)) are:
1- Create the certificate Template (ConfigMgr Clients (if the workstation is not already in place), ConfigMgr IIS Servers and ConfigMgr DP Servers)
2- Request the certificates
3- on the IIS servers, change the bind to allow HTTPS port (default 443) and select the certificate
4- Export the Root CA (and any other CA) certificate and import it into SCCM. Note, do not force the SCCM to use PKI, instead, allow it to use HTTP or HTTPS..
5- for each client, confirm that the Client Certificate is set to PKI (you can easily check the HKLM\Software\Microsoft\CCM\HttpsState and HKLM\Software\Microsoft\CCM\PKICertReady). or you can check the Report Clients incapable of HTTPS communication
6- Confirm that you can navigate to HTTPS://
7- From the server, confirm that you can navigate to the CRL for the certificate selected
8- From the client, confirm that you can navigate to the CRL for the certificate
9- on the console, add the column “Client Certificate” and confirm that it is set to PKI” for all clients (this may take couple of days/week to be completed)
10- once all machines are ready to use HTTPS, migrate the MP and check the logs: MPSetup, MPMSI & MPControl
11- on the client side, check the ccmmessaging log

now it is time to start migrate and test all other roles and once all roles have been migrated successfully

For DP:
– Import the new DP Certificate and set it to use HTTPS

For Application Catalog:
– Set the IIS Bindings to use a IIS Certificate
– You can easily change the app catalog website from HTTP to HTTPS, however, you cannot do it for the app catalog webservice. in this case, you’ll need to uninstall and install it again.

For SUP:
– Set the IIS Binding to use a IIS Certificate
– run the WSUSUtil.exe configuressl (check ServerCertificateName and PortNumber under HKLM\Software\Microsoft\Update Services\Server\Setup).
– Change the SUP to use SSL and confirm it is working
– force APIRemoting30, ClientWebService, DSSAuthWebService, ServerSyncWebService and SimpleAuthWebService to use SSL only

if everything goes well, migrate the site to HTTS only 🙂

if something goes wrong, you’ll see your mpcontrol saying problem connecting, forbiden, etc…
11- Check this: http://blogs.technet.com/b/configurationmgr/archive/2013/08/13/support-tip-a-configmgr-2012-management-point-enabled-for-ssl-fails-with-403-forbidden.aspx
12- Check this: http://blogs.technet.com/b/windowsserver/archive/2013/01/12/fix-available-for-root-certificate-update-issue-on-windows-server.aspx
13- check this: http://blogs.msdn.com/b/kaushal/archive/2012/10/15/disable-client-certificate-revocation-check-on-iis.aspx
14- check this: http://wibier.me/wsus-and-configmgr-2012-https-communication/

remember, this is only 1 part of the security on the SCCM, you should also have a console security strategy in place (I mean, have a good RBAC settings that only allow people to do what they supposed to do, and nothing else), a security for the server, sql, etc.

Tags:

Recent Posts

Comments are closed.
%d bloggers like this: