Skip to main content

system center orchestrator 2012 unleashed

i completely forgot to blog about this on its release. you’ve probably already seen all my hassling about it on linkedin or twitter already so this is old news anyway, right? :)

the orchestrator book is finally released. it’s available on amazon in both paperback and kindle edition. if you don’t know orchestrator yet, it’s time to learn. it’s pretty neat stuff. quite happy it’s finally out!

here’s a complete description:

Using System Center 2012 Orchestrator, you can capture and document processes across your entire IT organization, establishing the automation you need to deliver advanced cloud services and self-adjusting computing resources.

Authored by five leading System Center experts, this comprehensive reference and technical guide brings together all the knowledge you’ll need to architect, install, implement, integrate, and maximize the value of your own Orchestrator solutions. The authors introduce current best practices based on large-scale enterprise implementations they’ve personally led or participated in.

This up-to-date guide shows how to apply Orchestrator’s major improvements to implement IT process automation in any environment, including private clouds. You’ll start with context: what Orchestrator does, how it has evolved, how it works, and essential architecture and design techniques. Next, the authors help you make crucial up-front decisions about activities, runbooks, security, and administration. Finally, you’ll find expert guidance for integrating Orchestrator with the rest of System Center and with Windows Azure cloud services—including advanced automated workflows that encompass both data center and cloud.

Detailed information on how to…

  • Understand System Center 2012 Orchestrator’s capabilities, evolution, architecture, and design, including SP1 improvements and R2
  • Successfully install System Center 2012 Orchestrator and migrate smoothly from Opalis Integration Server 6.3
  • Take full advantage of Orchestrator’s advanced new runbook automation capabilities
    Configure activities associated with runbook control, systems, scheduling, monitoring, files, email, notification, and data handling
  • Design runbooks for fault tolerance and optimal performance
  • Enforce strong security using roles, permissions, and auditing
  • Deliver integration capabilities for Operations Manager, Service Manager, Configuration Manager, Virtual Machine Manager, and Data Protection Manager
  • Automate end-to-end data center/ cloud workflows with integration packs and PowerShell
    Create your own integration packs with Orchestrator Integration Toolkit (OIT.SDK)
  • Support Orchestrator 2012, troubleshoot problems, and discover the best web and third-party resources
Labels:

Comments

Post a Comment

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can
11 comments
more »

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off
3 comments
more »

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m
3 comments
more »