Architecting Operations Manager in a Cloudy world

Size: px

Start display at page:

Download "Architecting Operations Manager in a Cloudy world"

Sandra Lamb
6 years ago
Views:

Architecting Operations Manager in a Cloudy world Cameron Fuller @CFullerMVP http://blogs.

1 Architecting Operations Manager in a Cloudy world Cameron Bob Cornelissen (AKA

2 Cameron Fuller Dallas TX, Principal Consultant Started with MOM 2000 #MMSMOA

3 Bob Cornelissen Netherlands and Managing Consultant Started with MOM 2000 #MMSMOA

4 Architecting OpsMgr in a Cloudy world Agenda: Architecting Operations Manager Microsoft OMS impacts Monitoring in a Cloudy World

5 Architecting Operations Manager While considering on-prem, Hybrid and Cloud configuration

6 Architecting Check your assumptions at the door:

7 Architecting High level architecting for the Cloud: What is still the same (Operations Manager) Where may be different Where impacts costs Where impacts capabilities How is vastly different

8 Architecture & Management Groups Management groups and Management group considerations Does not require any additional management groups Could benefit from a Cloud based management group

9 Architecture design considerations What underlying design considerations still apply? Management Servers still need to be in proximity to their database server and data warehouse server Consoles still need to be in proximity to their management server(s) The same port requirements exist 5723 to the management servers 1433 (or other port number) to the SQL Servers Etc.

10 Architecture & Management Servers Management Servers Need at least 2 Size & costing: 1 std A3 = $267.84/month/server 1 std A4 = $535.68/month/server Roles can still be consolidated Requirements at Sizing helper at

11 Architecture & database components combined Azure SQL is not currently supported for any of these roles DB/DW/Reporting: Size & costing: 1 std D3 = $416.64/month (may require additional disk space) 1 std D4 = $833.28/month (may require additional disk space)

12 Architecture & database components split Database server Size & costing: 1 std D3 = $535.68/month Datawarehouse server Size & costing: 1 std D3 = $535.68/month (may require additional disk space) Reporting Servers Size & costing: 1 std A2 = $133.92/month Licensing note: SC standard license versus gallery image

13 Architecture & OpsMgr Components Gateway Servers Size & costing: 1-2 std A2 = $133.92/month 1-2 std D2 = $208.32/month 1-2 std A3 = $267.84/month Consoles Size & costing: 1 std A2 = $133.92/month 1 std A3 = $267.84/month

14 Monitoring with resources in the Cloud Resources in Azure to your on-prem OpsMgr Resources in Azure to Gateways in Azure (AMGW) OpsMgr in Azure CHOICES!

15 Architecting ACS functionality What about Audit Collection Services (ACS)? ACS still exists in OpsMgr 2012 R2 and beyond ACS could benefit from a Cloud based approach Most likely a D4 configuration plus additional drive space Running ACS in the Cloud could benefit from Cloud based backup approaches (Azure IaaS backup) Removes the data from your site and moves it to the Cloud Consider OMS as a replacement option to ACS Built to gather data from a variety of sources Would need queries, dashboards and potentially reports

16 Architecting, Redundancy, High availability Azure Site Recovery For on-prem OpsMgr designs Consider Azure IaaS backup Quick and easy method to backup your Cloud resources Scheduled & Policy based Redundancy? High Availability?

17 Microsoft OMS impacts How does OMS change the equation? Visualizing a Cloudy world

18 OMS Overview Collect Correlate Visualize Act Automate manual and repeated tasks Protect and extend your datacenter Audit Breach Analysis Malware Assess Update Assess

19 OMS Highlights/Strengths Cloud based Excellent for data visualization: Don t hate it just because it s pretty Pre-built solutions not requiring configuring or any significant tuning Connects into existing OpsMgr environments or standalone systems Added Linux Server standalone systems

20 Key insights on OMS OMS is currently more analyzing than monitoring since it is lacking alerting, reporting, authoring, MP ecosystem. OMS is NOT OpsMgr in the Cloud Management of business services is still a core requirement OMS Conclusions: Learn OMS and use it together with SCOM SCOM Vendors start integrating with OMS Content above taken from the Is Operations Manager still relevant white paper and webinar

21 ACS vs OMS ACS = SCOM Audit Collection Services Centralize Security events Filter Report OMS = New solution for audit collection? Centralize Security events Query Dashboard PowerBi

22 OMS Security And Audit

23 Demo Let s just jump in and show what kind of alternative to ACS this is! Cameron demo time

24 Monitoring in a Cloudy world While considering on-prem, Hybrid and Cloud configuration

25 Monitoring Cloud based workloads Use Operations Manager for: AWS: Azure:

26 Monitoring Cloud based workloads Use OMS for: Automation Backup Site Recovery

27 URL References Designing OM when you have IaaS virtuals: The road to the cloud webinar highlights: Using an Azure Monitoring Gateway: Is Operations Manager still relevant?

28 SPONSORS Discuss Ask your questions-real world answers! Plenty of time to engage, share knowledge. Evaluations: Please provide session feedback by clicking the EVAL button in the scheduler app (also download slides). One lucky winner will receive a free ticket to the next MMS! Session Title: Architecting Operations Manager in a Cloudy world

OMS, ATA AND AZURE SECURITY CENTER MIXER

OMS, ATA AND AZURE SECURITY CENTER MIXER Bob Cornelissen BICTT Managing Consultant www.bictt.com/blogs bob@bictt.com Cameron Fuller Catapult Systems Solution Director - Launch blogs.catapultsystems.com