Video Screencast Help

Steps to configure Console access and during installation of CMS 7.1

Created: 14 Apr 2013 | 4 comments
snm1502's picture

Hi,

Last time when I developed a Test environment where CMS 7.1 was installed on a Win 2008 Server and there were 7 clients connected to it. However, I was unable to access console from client machines, instead access to console via local host was fine.

I had checked the security roles and permissions and everything was ok.

I know there is a step while installation where in we select if we would be using HTTP or HTTPS and I remember i selected HTTP (however, I am unsure of the exact difference with respect to Altiris in both).

I am again planning for a test lab build up tomorrow however, want to be sure that I am following correct path. Hence, requesting guidance:

What is that I missed while installation due to which console is not accessible?

What should be the steps to check?

Also, it would be great if we can share any other considerations we could keep in mind while performing an installation.

Thanks in advance.

Operating Systems:

Comments 4 CommentsJump to latest comment

SK's picture

If you chose HTTP then it should just work.  Its when you select HTTPS that you have to then install the cetificate on the clients before you can do things.

Please clarify your actual console access issue.  Can the page be displayed?  Do you get a login prompt? 

 

If the local browser works, then it is most likely an IIS and/or a remote browser configuration issue.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

snm1502's picture

Hello SK,

Thanks for the reply.

Console wasnt opening at all and was throwing an error (cant recollect the error message but was not Page cannot be displayed for sure). Also, there was no prompt for login. We did checked the IIS page which displayed fine so not very much positive if it was an IIS issue.

Issue has been resolved, though. Not sure if there was something incorrect in the configuration. However, when I reinstalled CMS following same steps it worked. The only difference was, in my previous install I changed the install folder to D:, however, while reinstalling I allowed it to install at the default location.

As it was a test environment installing at default location was fine. However, it would be great if you advise what should be modified if installation is done somewhere other than default location.

Thanks
snm1502

SK's picture

Most of our customers do not install to the C: drive, and as far as I am aware, there isn't any special configuration needed as SIM simply uses the path you specify.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

snm1502's picture

I remember vaguely, SIM was installed at default location however, while installing CMS i changed the drive.

Would that be a cause of issue SIM and CMS being on separate locations.