8:08 AM : Loopback Fix
I’ve been here for a while, catching up on some of my non-blog communication, MBA coursework, etc. About ten minutes ago, I started testing a probable fix for the validation error I had last night. Just as a reminder, that validation error looked like this:
The fix is recorded in Appendix D of the Office Communications Server 2007 Enterprise Edition and Communicator 2007 Deployment Guide. In a nutshell, you need to add a multi-string value to HKLM\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0. The MSV should be named BackConnectionHostNames and should have a value of your pool’s FQDN. What this does is allow IIS to validate certain FQDNs as being valid for loopback. You’ll want to remove this value when you’re not validating, and more detail is available by reading the referenced guide.
When I followed the instructions for the fix, the validation wizard for the remaining steps executed properly.
8:16 AM : Validation Wizards
(Yes, that’s a different validation wizard.)
(Yes again.)
8:23 AM : Validation Results
So the current state of our deployment is that there are two validation warnings, neither of which I care about because I haven’t deployed Enterprise Voice or edge access yet.
From the Validate Front End Server Configuration wizard, we have:
From the Validate Web Components Server Functionality wizard, we have:
8:27 AM : Internal Deployment Complete
Aside from the above validation warnings, it seems that internal deployment is complete. I do have one more warning in my Communicator client regarding Exchange Web Services, but the Exchange deployment on this domain isn’t complete yet, so it’s also expected. The ramification at this point is that Communicator can’t automatically set my status to “In a Meeting” if I have a meeting scheduled in Outlook.
Next step is external user access, meaning I’ll be bringing up a scaled single-site edge topology. I’ll try to explain that in more detail, but there will probably be some downtime here as I test Communicator internally and prep another couple of servers to be edge servers. (I have to install Server 2003 at least.)
1:53 PM : Enterprise Voice
1:56 PM : Activating Mediation Server
2:00 PM : Assigning Certificates
3:16 PM : Enterprise Voice Prep
I’ve been reading (and will continue to read through) the Microsoft Office Communications Server 2007 Enterprise Voice Planning and Deployment Guide. This will probably take the rest of the day and will ensure that I make minimal mistakes when deploying Enterprise Voice. I have a good idea of what it is that I need to do, but I want to be certain.
