sysadmin

So chances are, after reading my previous post on how to move Mailboxes via Organizational Unit you have migrated a couple hundred mailboxes.

I’ll admit, I do love Active Directory.

Whether you are lucky in love or still searching I hope February 14th brings you great joy and happiness.

The modern data centre or server farm looks very different from 5 years ago.

We’ve all been there…your company has just taken over or brought out another company and you have been given a list of new employees to receive network accounts or another example (and my reality) it is the start of a school year and you have a herd of new year 7 students that need network accounts.

So you have a Hyper V 08 R2 (or maybe 2012) Cluster with a couple of nodes and it is all going rather well.

Came across an interesting little bug which probably would have gone unnoticed if I never migrated my mailbox to our new Exchange 2010 mail server.

On Friday while I was preparing our new Exchange 2010 VM for coexistance with our current Exchange 2007 physical box (more on that later) I ran into a annoying snag.

Any any Windows domain environment one of the most overlooked but ultimately crippling when things are wrong component is time.

There will certainly be a few people out there who are either doing it already or investigating upgrading their Virtual Machine host from 2008 R2 with Hyper V (or Hyper V Server R2) to Server 2012 with Hyper V (or Hyper V Server 2012).