Symantec Management Platform (Notification Server)

 View Only
  • 1.  SSL and Software Delivery (CMS7)

    Posted Mar 03, 2009 02:34 PM

    I know this is a little early but here goes:Our Test CMS7 server has SSL enabled on the default website.  Because of this, I set Altiris Agent Settings - Targeted > Advanced to define the URL of the server as https://NSNAME/Altiris under the "Alternate URL for Accessing NS" setting.  The client agents are checking in fine but they are unable to download packages because it is trying to do it over HTTP, not HTTPS.  There are no sites defined, so no package servers.

     

    I also tried running AeXAgentutil with the /server and /web switches on a client but still it won't download the package via HTTPS.  The URL just shows up as HTTP.

    Does anyone know why this might be happening?



  • 2.  RE: SSL and Software Delivery (CMS7)

    Posted Sep 29, 2009 12:47 AM

    If you go to the websites properties (Default Web Site, or a custom one) > Directory Security > Server Communications > Edit, is the "Require secure channel (SSL)" option enabled?

    If it isn't, then please enable it, and then restart IIS. 



  • 3.  RE: SSL and Software Delivery (CMS7)

    Posted Jan 05, 2010 04:57 PM
    It is enabled and I have restarted IIS multiple times.  The agent is pointing to HTTP and I can browse out to the package path using HTTPS, so it is not a Web server issue.

    This issue is still affecting me on our new system.  Any ideas on how to rectify this?


  • 4.  RE: SSL and Software Delivery (CMS7)
    Best Answer

    Posted Jan 05, 2010 07:37 PM
    (configuration of IIS, redirecting the clients, getting and accepting a certificate, etc) the only thing that seems to apply is that the package codebases are not coming down over HTTPS (rather http). Is this correct?

    If so, did you try restarting the NS Package Refresh scheduled task? See Altiris KB34101 for confirmation.


  • 5.  RE: SSL and Software Delivery (CMS7)

    Posted Jan 06, 2010 09:56 AM
    Thanks for pointing me in this direction, It has addressed the issue. I think I may have had the fix going already but was impatient as the changes are not immediate.  Thanks very much Jim.

    Bryan