<dd class="wp-caption-dd zemanta-img-attribution" style="font-size: 0.8em;">
Image via <a href="http://www.crunchbase.com">CrunchBase</a>
</dd>
</dl>
Paul Thurrott posted a nice attaboy to the MSN folks today for releasing a wallpaper product that will check Microsoft for updates to your operating system.
(note: the following is a stream of consciousness post regarding some software requirements as i dream them up.  if you are a developer and actually take up these requirements as the design for a software project, please let me know.  if you are aware of a software product that accomplishes all of this, please do not bother to let me know about it.  i don’t care.  fact is, nothing on the market today does this well enough to make me care about it the way i want to care about it.)
Last week I had to do some serious debugging on storage copy replication.  We discovered that one of our SCC clusters had decided to quit replicating to the SCR node at the other site.  We’re not sure why (we think it’s because the SCR node was rebooted and replication was not cleanly suspended), but the ramifications of failed replication are interesting.
I’m all about negativity today. Sorry.
Anyway, I’ve had something nagging at me for a while now and I think I’ve just figured it out. Powershell is Microsoft‘s answer to having a dumb command line through the Win95 – Win2003 years and it’s quite powerful, as the name implies. Microsoft likes it so much that they makes most of the Exchange 2007 administration efforts in the Exchange Management Shell, a derivative of Powershell that contains Exchange-specific cmdlets.
One item you’ve probably learned by now if you’re an Exchange admin working on a 2007 deployment is that Microsoft has changed the behavior of the recipient update policy.  Most of you won’t care about this and that’s just fine.  You shouldn’t.  I would dare say that if your Exchange environment is engineered well and planned out the way Microsoft probably expects it to be, you should have almost no issues whatsoever.