Best Practices: Building Your Strategy for a Private Cloud

Posted on June 6, 2013by OpsConfig

Fantastic talk from TechEd this week given by Eduardo Kassner:

Building a Private Cloud Eduardo Kassner TechEd 2013

Leave a Reply

Your email address will not be published. Required fields are marked *

Post navigation

Previous post Troubleshooting: Product Evaluation is expiring in 60 days (SCOM 2012)

Next post Troubleshooting: SCOM Agent Healthy, but availability report for server shows monitoring unavailable

The contents of this site are provided “AS IS” with no warranties, or rights conferred. Example code could harm your environment, and is not intended for production use. Content represents point in time snapshots of information and may no longer be accurate. (I work @ MSFT. Thoughts and opinions are my own.)

Recent Posts

Intro to Azure Monitor – Application Insights -Availability Monitoring
Intro to Azure Monitor – Application Insights with ASP.NET Core
Intro to Azure Monitor – Application Insights for SCOM Admins Part II
Intro to Azure Monitor – Application Insights for SCOM Admins
Comic Relief: Graph

Recent Comments

Mark MacLachlan on How do I: Create a Wildcard SCOM Service Monitor and Recovery
OpsConfig on Intro to Azure Monitor – Application Insights for SCOM Admins Part II
Manoj Mathew on Intro to Azure Monitor – Application Insights for SCOM Admins Part II
OpsConfig on Intro to Azure Monitor – Application Insights for SCOM Admins
George on Intro to Azure Monitor – Application Insights for SCOM Admins

Archives

Categories

Azure Monitor – Application Insights
Best Practices
Book Review
Comic Relief
Exchange 2010
How do I
Management Packs
OpsMgr Blogs
Sidenote/Tangent
Talks
Tools
Troubleshooting
Uncategorized

Disclaimer:

The content of this blog is intended to demonstrate concepts and potential partial solutions. The use of the code as-is in the blog may actually harm your environment if not modified to fit your specific needs. Each posts represent a snapshot of a point in time and may no longer be correct as patches, rollups, or service packs are released. (Provided as-is with no warranties or guarantees.| Use at your own risk. |Not intended for production use| As always, test, test, test and then test some more.)