As you may or may not know, this year I have two sessions on Windays 2010 conference. One is “Windows Server 2008 R2 AD Disaster Recovery” and another one is “Virtualization under control”. Make sure you visit one or both, since there will be shared more than just knowledge! 🙂
The easies thing for me to do, when preparing for a sessions, is to think up session concept and to create PowerPoint presentations to support my topic. It can all be done in a day or two, depending on how deep you want to go. Both of my session are level 300.
Level 100 – The technical level of introductory and overview material. Assumes little or no expertise with topic and covers topic concepts, functions, features, benefits.
Level 200 – The technical level of intermediate material. Assumes 100 level knowledge and provides specific drill down into topic.
Level 300 – The technical level of advanced material. Assumes 200-level knowledge and in-depth understanding of features in a real-world environment and strong coding skills. Provides a detailed technical overview of a subset of product/technology features, covering architecture, performance, migration, deployment, and development.
Level 400 – The technical level of expert material. Assumes a deep level of technical knowledge and experience and a detailed, thorough understanding of topic. Provides expert-to-expert interaction and coverage of specialized topics.
Now comes the hard part. Creating and configuring hardware and virtual machines. Since I want to show stuff that is very complex to implement, and for some of it I do not have appropriate hardware, I was forced to improvise. It will take me more than 4 or 5 days of work to put it all together. Right now, I am about 60% finished. Just to give you an idea, I will be using 4 physical computers and on them 3 virtual machines. 3 computers have Windows Server 2008 R2 Enterprise installed and one has Windows Server 2008 Storage Server installed. All of them are in the same domain (demo.local) and there is only one domain controller (Storage Server aka. SAN). Two of them are configured in Hyper-V failover cluster (NODE1 and NODE2) and one is just Hyper-V server (HV-R2-01). NODE1 has System Center Virtual Machine Manager 2008 R2 installed, which will be used to control all Hyper-V servers and one HA (Highly Available) virtual machine. Just to illustrate the whole thing, diagram of it looks like this:
And in real world, it looks like this (click to enlarge):
As I promised before, full “How to” text and video will be available after my Windays 2010 sessions.