Got it. Installing on both and using the 2nd should the first one get dorked up :)
Thanks mate! From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Holman Sent: Mittwoch, 30. Juli 2014 22:55 To: [email protected] Subject: RE: [msmom] Web Console hosted where Having web consoles on both MS makes most sense for load balancing, but customers often do this so if one gets dorked up, they have another to use. It is rather quick to install so usually not a big deal unless they have to go through change control to get another one installed, or IIS added, etc. Yes, dorked up is a technical term. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Wednesday, July 30, 2014 2:53 PM To: [email protected] <mailto:[email protected]> Subject: RE: [msmom] Web Console hosted where That was my thinking: yet another server for a rather small environment. One system more to pay for and to possibly fail. And basically all reasons mentioned below to do it, doesn't apply for us. We should be fine with having the Web Console on one MS. What about having them on both. Only making sense with load balancing right? And I think I put SSRS on the WH-SQL box, although reporting could be heavy, couldn't it? -Roland From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kevin Holman Sent: Mittwoch, 30. Juli 2014 21:21 To: [email protected] <mailto:[email protected]> Subject: RE: [msmom] Web Console hosted where It isn't a terrible idea, but there is no need to add an additional server in this design, for a management group of this size. Additional servers cost money. I like to advise what will be the lowest total cost of ownership, and still meet customer needs. Web consoles installed on a non-management server can have authentication issues, that require additional configuration, which is another negative. Splitting out SSRS is not really that advantageous for an environment this small, unless you have memory limits per VM, but can have multiple VM's. The only time I split out SSRS from the Warehouse SQL server is when the warehouse SQL instance will be clustered, in which case SSRS is not supported on a node of a failover cluster, as SSRS is not cluster aware. Just opinions though. There aren't any hard and fast rules here, just guidance based on the sizer as a starting point. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sarbjit Singh Sent: Wednesday, July 30, 2014 1:24 PM To: [email protected] <mailto:[email protected]> Subject: RE: [msmom] Web Console hosted where Why not have another server just for the Web Console, Ops Console and maybe even SSRS? Sarbjit From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Wednesday, July 30, 2014 11:58 PM To: [email protected] <mailto:[email protected]> Subject: [msmom] Web Console hosted where I'm new to OpsMgr and so far I plan to do this: 2 MS (only windows systems, maybe 500, no network monitoring yet) Ops-DB and DW on separate boxes. That makes 4. All VMs. Where should I put the web console? Adding IIS and the additional load is what worries me. It's using the DW as source affair, so is the DW server the best choice? -Roland
