I wanted to share this little tidbit of information with you for a while, but I haven't had the time to write / publish this post. When I finally decided to put my mind to it - I wrote this series of posts while en route to Vancouver BC for my one Western stop of the TechNet Winter Tour 2005, and decided it was about time to get this done!
I am passionate about Active Directory!!! (is case you didn't know from talking with me before) It is the foundation for identity and authentication for Microsoft products. I've personally worked on over 36 Active Directory projects and migrations ranging from 200 users in a single site to 27000 spread nationally in 90+ sites. I created the "Migration Strategy and AD Practice" at my previous Gold Certified Microsoft Partner who uses it for the bulk of its engagements. To put it simply - I love this stuff! I want YOU to get into AD 2003 and I will do almost anything to help.
One of the things that I found VERY frustrating over the last 5 or 6 years was the lack of clear documentation on in-place upgrades or single domain designs from the "white paper" engine that Microsoft has created. Let’s face it - are you a large multi-national organization with tons of physical sites? If you are reading this post - probably not. The proliferation of large white papers around AD design for these large organizations resulted in a lot of discussion and perception issues with my Canadian customers who didn't really need to undergo a more complex and lengthy multiple domain and Pristine domain migration which required 3rd party tools to streamline. That being said - I recently came across a nice little document in the Exchange 5.5 to 2003 migration kit for Small Business that outlines an approach to in-place migrations - Way To Go!
If you still have one or more NT4 domains that you manage and haven’t gotten around to performing your upgrade because of various reasons, this article and subsequent posts in this 8 part series are for you!
First off - my approach to AD design. This series of posts are about migration, not design. That will be the topic of future posts. But - because you have to have your "end point" AD design completed before you can start a migration - you have to have a vision on where you want to be before you get started, right? Let me give you a couple of words of advice on AD design - they have served me well. I was influenced by two main principles in my design projects.
- KISS (Keep It Simple S{insert your term here). The simpler the design you have with fewer domains, the easier it will be to implement and maintain on an ongoing basis.
- Design for Nirvana (I stole that one from Stuart Kwan a while back from an interview he had about AD design). You want pie in the sky and are tired of working with your "old inherited and expand as you go" NT4 domain? Go Long - Go Deep! Design for what your business needs with all the technology bells and whistles that will make it easier to manage and free your time.
The fewer domains you have (and obviously, the fewer forests) the easier your life as an IT pro will be. That being said - why would you design for multiple domains and un-needed complexity? This was another discussion I had a lot with customers who were going through a design project. They'd present this multiple domain forest that looks a lot like their old NT4 environment and didn't really have any sound business reasons or technical reasons as to why they thought they needed it that way. I've done the single domain and domain consolidation thing many times and let me tell you - its well worth it. Even if you have one of those "complete trust" spider webs of NT 4 - one of your larger user account domains could be a candidate for a hybrid in-place migration.
To wrap up this post - Are you (like SO many other Canadian companies) a Candidate for an in-place Migration? Are you interested in streamlining and accelerating you migration while reducing and mitigating you risk? What makes a good candidate? Here's my perspective of a good candidate:
- A domain with concentrated User accounts and computer accounts
- the ability to "touch" all your BDCs in a short period of time in order to minimize the use of Mixed Mode
- a migration team that has a clear vision of where they want to go and are willing to work at getting there
- your target design will have a single forest and as few domains as possible (preferably 1 if you haven't caught on yet)
If you answered YES to these questions - you might want to consider reviewing my approach to in-place migrations. Stay tuned for the next post.
WHAT DO YOU THINK? Please feel free to click on the Feedback/Comments link at the end of this post to voice your opinions or thoughts on the process as we go along. I am looking forward to hearing from you. Do you like the idea of a series? Do you have any suggestions? Sound off and be heard!