Washington DC Endpoint Management User Group

During the installation of 7.1 I had IIS both accept HTTP and HTTPS traffic. I have since configured all the agent settings to talk over HTTPS and configured IIS to only accept HTTPS trafffic. However, my existing software packages are still trying to use the HTTP url to download. How do I force this change? My Package Service Settings page already has Publish HTTPS codebase set. In 7.0 you just had to require HTTPS and then kick off the package refresh task and the software download sources would update. However, this doesn't seem to be the case in 7.1. The NS is still publishing HTTP urls along with the UNC.

I'm so glad you asked!  This was a pain in my side at a particular customer.

The first step would be to follow this KB:
http://www.symantec.com/docs/HOWTO10091

Set PreferredNSHost in the registry to the FQDN/SSL name of the server, restart services, and run a package refresh.

If that's not successful, check out this KB:
http://www.symantec.com/docs/TECH171971

Regarding the "in isolated cases" in TECH171971, I'm the "isolated case."  So if all else fails, run TRUNCATE TABLE SWDPackageCodebase as specified, then run the refresh to repopulate it.

Does this help?

Very helpful mclemson. The truncate step did the trick for me.

Thanks!

I'm having the same problem but the configuration of my environment is as follows: The common name of the certificate I'm using is different from the FQDN of the server, and configured PreferredNSHost the certificate name, but when it set up the server agent NS can not connect with the Task Server to resolve this in Target Agent Settings, set up a policy for only the NS server use her own name without FQDN https to communicate and the rest of the environment used the alias of the certificate, but when I set the package server, it is only over HTTP.

Does anyone have any ideas?