If you choose to install the OpsMgr 2012 RC Web Console on a stand-alone, non-management server (MS), and you don’t want to get prompted for credentials when logging in, the easiest fix is to use SSL. But what if you’ve already configured the Web Console to not use SSL but decide later to use it? Hopefully this will help you ensure that you successfully deploy the web console with SSL or re-configure it to use SSL.
- First things first, configure IIS and SSL on your remote server (instructions here)
- Ensure that your web console is working PRIOR to attempting this. This means that you’ve at least got a web console that does prompt for windows credentials and then successfully loads after authentication.
So, at this point you have either 1) have already installed the SCOM 2012 Web Console on a stand-alone server and you wish to enable it to use SSL. or 2) want to install the web console and get it right the first time!
Scenario 1) if you already have the web console working and want to enable it to use SSL do the following
- Configure SSL using Marnix Wolf’s method (here)
- Uninstall the web console from Add/Remove programs
- Reinstall the web console from Add/Remove programs
- At the Specify the web site for use with the Web Console screen, check the ENABLE SSL box and then complete the installation > screen shot below < (yeah, that easy)
Scenario 2) you want to install the web console on a clean stand-alone system and want to use SSL
- Install IIS and configure it according to the documentation from Microsoft
- Configure SSL using Marinx Wolf’s method (here)
- Install the web console, select MIXED AUTHENTICATION
- At the Specify the web site for use with the Web Console screen, check the ENABLE SSL box and then complete the installation.
Note: this topic covers Microsoft System Center Operations Manager 2012 Release Candidate; your experience may differ as other versions are released.