Monday, December 8th, 2008
From Friday 12th December 2008 until early January 2009, I m taking a break from everything. There will be no blog posts, no community forums participation, no website updates etc during this time. I hope to come back totally refocused and energised for the New Year. I already have plans for a few things in the new year and will announce them in 2009.
If you have anything waiting on me, then send me an email directly so I can attend to it before I go.
Hoping that everyone has a great Christmas / New Years break and gets to spend time with their loved ones just as I will be doing.
Saturday, December 6th, 2008
I learned something cool when I was in the USA last time. When you have an Exchange 2007 system connected to Exchange 2003, you get the following Exchange 2007 Administrative Group and the Exchange Routing Group to connect the systems together. You are also warned not to change the name of the Exchange Administrative Group (FYDIBOHF23SPDLT) or the Exchange Routing Group (DWBGZMFD01QNBJR)
What I didn t know is that these random characters are in fact codes.
A simple letter substitution reveals that FYDIBOHF23SPDLT is in fact EXCHANGE12ROCKS and that DWBGZMFD01QNBJR is in fact EXCHANGE12ROCKS
Cool huh right in front of you and you didn t even know it!
Saturday, December 6th, 2008
I ve not written about this before, but long story short, Microsoft Press and I have parted ways with my work on the SBS 2008 Administrators Pocket Consultant. I won t go into the details, but will say that it was due to a difference of opinion on things combined with some very personal factors in my private life that lead to the decision. I ve retained full ownership of the content I had done at that time (approximately half the book is completed).
I noticed this week that Amazon is listing the book with myself and Susan Bradley as authors and a release date of April 2009. This is incorrect. Neither Susan or I are involved in this title anymore. Susan did in fact write a few chapters for me which I will be using in other projects. I m not sure who the authors are but I know from working with MSPress that the book will certainly be worthwhile.
As for my own book plans, I ve been working on a few ideas but they too are on hold until I return from a long overdue family vacation which starts next week until early January 2009.
In late January 2009 I will announce the plans and I can assure you, that it will be worth the wait
Friday, December 5th, 2008
Today Microsoft released the latest revision of their SBS 2008 Migration documents. You can access them here
NOTE that this is only the ONLINE documentation that is updated. The downloadable copy of the document is NOT updated at this time.
6/1/2009 – UPDATE the downloadable documents were updated while I was on vacation see the post here
Thursday, December 4th, 2008
You go against all the good advice that Microsoft offer when they design the product and you don t even care enough for your clients well being to heed advice given by others. Such is the case of some people who believe that they can put the Hyper-V role ONTO the main SBS 2008 server and still make it work. Susan Bradley has a great blog post here on the issues that occur when you put the Hyper-V role on your SBS 2008 server. She is doing this as a demonstration of just what NOT to do. She is trying to document the brain dead things that people will try to do and fail in the hope that they might actually read.
However, I can t help but notice that one of the comments on her blog come from someone who seems hell bent on bending the SBS 2008 product beyond it s design constraints. Furthermore he not only wants to install Hyper-V ON the SBS 2008 server itself, but then wants to install ISA in one of the guest partitions. What kind of insanity is that? How will he get support from Microsoft when things go wrong? I sure hope he is joking and not doing this for real.
Furthermore I am seeing and hearing of people deploying SBS 2008 in live customer environments without even having installed it in a virtual test environment themselves. Stories of people doing LIVE migrations for the first time, also without doing any reading of the documentation before the start. These people all then point the finger at Microsoft for not having given them all the answers.
Why the hell would you do this for a clients server? Why would you do this for ANYTHING production quality and expect it to work? Why did you not do your homework and test it out first so you have an idea on what would go wrong?
Answer because you are an idiot. You have no concern for the clients business at all. You are the scum that makes the true IT Professional look bad. You are the used car salesman of the IT industry.
I am looking forward to the current economic woes of the world, because this in itself should weed out these types of people, force them out of business hopefully for good. These words sound harsh, yes. I m tired of hearing people blame the product, Microsoft and anything else that moves without taking responsibility for their own freaking actions.