Vermyndax vermyndax

  <dd class="wp-caption-dd zemanta-img-attribution" style="font-size: 0.8em;">
    Image via <a href="http://en.wikipedia.org/wiki/Image:Apple-logo.png">Wikipedia</a>
  </dd>
</dl>

Did anyone catch the memo?  The one that said Apple is done with Macworld after this year because they want to announce products on their own timeline?  Yeah that one.  I thought you saw that one.

Abit’s Death Date Reportedly Set: 31st of December, 2008 – X-bit labs.

Even though I don’t care too much about building PCs anymore, this is sad, sad news.  ABIT is shutting down completely at the end of this year.

However, on a positive note – at least that narrows down motherboard selections for enthusiasts.

If you were subscribed to my Twitter feed, you would have known in near real time that today I had one seriously exciting treat. I managed to squeeze my way into a tour group being led by the incredible Jack Garman here at Johnson Space Center. Think I would turn down such a chance? Absolutely not. Not only is Jack Garman a wonderful friend and professional mentor to me… today I learned much, much more about him… and I’m in simple awe. (Read the Wikipedia entry).

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.

I’m seeing screenshots on the web about Windows 7. In particular, the Paint and Wordpad applications are showing up on Paul Thurrott’s blog site.

I still have yet to find anyone who thinks the Office 2007 ribbon was a good idea. I mean anyone outside of Microsoft, that is. Well, and other than Paul Thurrott. Real-world users that I work with every day hate the bloody thing and I’m consistently asked how to turn it off.

As the parent of two children (soon to be three) and knowing the types of films that I would produce if I could – a question came to my mind while doing the dishes tonight.

Earlier I had been engaged in working on a script for an online short that I think will just be fan-damn-tastic, but admittedly would garner quite the R rating if it were to be shown in a movie theatre.  Knowing that, it makes me wonder how far it’s going to get around Youtube before someone finds it offensive.

Continuing my recent tradition of expressing what are likely to be fairly unpopular opinions with my peers, tonight I’m going to rag on Google‘s “Chrome” project and tell you why this is a Bad Idea ™.  I’ll try to keep this short (update: I failed).  This is considered to be a discussion starter, not a final statement.  I’ll probably elaborate on these discussion points on the next NO CARRIER, so be sure and give me some feedback here.

This video is way too good not to share:

This video is quite funny through most of it, but when it reaches the little boy I practically burst into tears.  Sometimes I think my job and this industry just does not lend itself to parenting at all.  I guess others agree.

This post is focused on those of you who have decided to deploy Exchange in a resource forest.  You’re in for tears.  While the resource forest is technically a supported deployment method for Exchange, I’m going to point out what can go wrong in your Exchange world that will keep your admins up at night.

Let’s start with the definition of a resource forest, just in case you’re not sure.  The resource forest approach means that you have one Active Directory forest where your user accounts live and another Active Directory forest where your application (Exchange, in this case) lives.  You have user accounts in the resource forest that are disabled and then externally associated with the users in the user forest.  This of course, requires a trust between the two forests, which you likely have anyway, right?  Right.