Skip to main content

introducing the long awaited operations manager 2007 r2!

i’m not sure if i’m bringing you any “news” since i’m usually the slowest blogger when it comes to release dates and such.  however, this is pretty monumental so it’s worth repeating.  for those of you who wish to espouse the market fluff to your boss, you can read that here.  it’s not worth repeating here as i could not compete with the geniuses that write that material for a living.

i started off with every intent of doing a full article on all the goodness of opsmgr 2007 r2.  however, when i started searching for material with actual figures, i noticed that apparently this is such big news that even “fire pants” mckenna wrote a blog post about it!  believe it or not, it’s pretty good.  quite entertaining.  i won’t do an injustice by trying to complete with it.

a lot has changed since 2007 when opsmgr first launched.  (good grief, i just realized how much time had passed.)  where i work, we were very slow to begin our rollout.  i mean we started when r2 beta came out.  still, it was fun to ask some of the other mvps how things were going for them.  i think one of my favorite conversations went something like …

“you haven’t upgraded yet?”

“nope, still waiting for funding.”

“consider yourself lucky.  don’t do it!”

(did i say upgrade?  -snicker-  there still is no upgrade from mom 2005.)  it’s gone through a service pack since then and now is on r2.  if you haven’t started, there’s a steep learning curve.  once you get beyond the concepts, though, the potential starts to open up.

i should warn you that when you open the console for the first time after upgrading to r2, you’re going to be presented with what appears to be the “black” theme in outlook.  :)  i guess black is the new black.  details are here at this link if you want to know more.

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 »