Up to this point, Hyper-V 2012 Failover Clustering was unusable because backing up any virtual machines would cause IO timeouts and/or virtual machines to enter a paused state due to these delays. At best, backing up virtual machines would cause the clustering logs to be riddled with critical errors. Fortunately there is finally good news after more than a month of waiting for Microsoft to fix this.
I ran into a problem today with our Lync on-premise environment being unable to federate with Microsoft Messenger contacts (hotmail.com, passport.net, passport.com, live.com, and vanity domains; outlook.com still isn’t supported and likely won’t be until sometime in 2013 when it comes out of beta). I searched but came up empty-handed with results regarding similar problems so I’m guessing that I’ve discovered this one before the general public. As a result, I hope my solution helps fellow sysadmins; please leave a comment if it does (and give credit if shared, thank you!).
During my latest work transitioning a client’s Exchange environment from 2007 to 2010 I stumbled across an issue I had not ran in to previously. This issue involved running different versions of (2007 and 2010) Outlook Anywhere (OA) in one environment simultaneously. I couldn’t find good documentation on this process from Microsoft so I figured I’d hopefully help someone else out by documenting the process I went through.
First off, getting your Client Access Servers (CAS) up and running with the proper hostnames and associated SAN certificate is essential. The initial plan was to bring up the 2010 Outlook Anywhere (OA a.k.a. RPC over HTTP) and then disable the 2007 OA due to Microsoft’s recommendation to transition the CAS fully before proceeding with the migration. With this latest transition, I needed to keep both the Exchange 2007 and 2010 OA proxies running side-by-side. This was necessary due to having numerous domains that were hosted on this Exchange environment that wouldn’t be able to have their external DNS edited in time for the beginning of the migration (for a variety of reasons that are outside the scope of this post).
I have been using Apple laptops since about 2002 when I bought my first 1GHz Titanium PowerBook G4. At the time, my needs were very small and I fell in love with Mac OS X 10.2 Jaguar. Following my TiBook, I had a couple different Aluminum PowerBook G4s and finally got my first C2D (Core 2 Duo) MBP (MacBook Pro) in November of 2006. That C2D MBP treated me very well for the last 2 years and my only real complaints with it were:
As an IT admin it will happen to all of us at some point; there will be that problem that seems like you are 10 minutes away from fixing that quickly turns into 10 hours and then 2, 3, even 5+ days. Before you know it, you have spent a week with nearly zero sleep and a lot of caffeine and then you finally realize that you are not any further along than when you started. I spent the last week banging my head up against a wall trying to get a clients new Windows Server 2008 and Exchange 2007 SP1 environment up and running, only to find out that Microsoft has a crippling bug in Windows Server 2008 that won’t allow Outlook Anywhere (a.k.a. RPC over HTTP) to run in its default configuration.
The most unfortunate part about this is that Microsoft is still yet to release any information publicly about this problem, which is really sad because they generally do such a great job of at least posting limitations of their products on many of their wonderful blogs. I had to search the Internet and eventually found articles that led me in the right direction but I was never able to find a blog/article that outlined the exact steps that I used to fix/diagnose Outlook Anywhere which is why I really felt the need to write this post.
Well, I’ve been swamped with work for the last 10 months and haven’t even come close to having a chance to sit down and write any well thought out blog entries. I was compelled though a couple weeks ago to write a new entry about the coolest new feature that I stumbled across in Apple’s still relatively new OS X 10.5.2 Server.