Client Management Suite

 View Only

  • 1.  Altiris 7.1 console HTTPS inaccessable

    Posted Nov 20, 2014 04:53 AM

    Hi Guys,

    Came into the office this morning and for some reason noone can access the CMS 7.1 console through HTTPS. HTTP is fine.

    First I restarted IIS - Then restarted the NS. However navigating to HTTPS://Altiris/Console brings up

     

    Internet Explorer cannot display the webpage


  • 2.  RE: Altiris 7.1 console HTTPS inaccessable

    Posted Nov 20, 2014 05:02 AM

    Can you please share the screen shot of error, Because that URL is not opening which you have shared in above comment.



  • 3.  RE: Altiris 7.1 console HTTPS inaccessable
    Best Answer

    Posted Nov 20, 2014 05:21 AM

    Have you configure altiris console on SSL ?

    Configuring the Symantec Management Platform 7.1 to use SSL.

    Article:HOWTO53002 | Created: 2011-05-16 | Updated: 2012-12-19 | Article URL http://www.symantec.com/docs/HOWTO53002


  • 4.  RE: Altiris 7.1 console HTTPS inaccessable

    Posted Nov 20, 2014 05:24 AM

    That's the internal DNS name for our console

    Our server is called Altiris

    For example http://10.0.0.10/altiris will take me to my CMS console

    httpS://10.0.0.10/altiris will show "Internet explorer cannot display this page" as if the IIS site wasn't there.

     

    If you would really like a screen shot..here: https://www.google.co.uk/search?q=internet+explorer+cannot+display+this+page&safe=active&rls=com.microsoft:en-gb:IE-Address&source=lnms&tbm=isch&sa=X&ei=qMBtVKaxKcWrgwTO4YLACg&ved=0CAgQ_AUoAQ&biw=1862&bih=972



  • 5.  RE: Altiris 7.1 console HTTPS inaccessable

    Posted Nov 20, 2014 05:49 AM

    Can you please confirm the service is start or not

    Unable to access Symantec Management Console - Screen is blank

    Article:TECH188550  |  Created: 2012-05-11  |  Updated: 2012-08-16  |  Article URL http://www.symantec.com/docs/TECH188550


  • 6.  RE: Altiris 7.1 console HTTPS inaccessable

    Posted Nov 21, 2014 03:50 AM

    Thanks for the link to the how to. It obvisouly was configured before otherwise I wouldn't have expected it to work. But following the HOWTO enabled me to spot where the process had broken down.