Exchange 2007 SP1 and Server 2008 information

LMrcxx2E3F

v class="googleright">I wanted to share some of my findings with running Exchange 2007 SP1 on Server 2008. I've noticed and heard of several issues and information that I believe folk should be cognizant approximately.
Here are the issues and general information I have listened of and capable by far that seems to be valuable to share. If you differ with everything I am sharing, have found it works in a different course for you, and/or want to include your findings and anybody tidbits of information you may have, amuse feel free to comment.
* Hub Transport Server Role fails when IPv6 is disabled on that server
o If IPv6 is disabled prior to the installation of Exchange Server 2007, when installing the Hub Transport Server role, your Hub Transport Server character will fail to install
o If IPv6 is disabled afterward the installation of Exchange Server 2007, you may experience some Exchange services shortcoming to start
* Outlook Anywhere is broken beneath certain conditions
o Outlook Anywhere is not working for Outlook 2007 with IPv6 enabled (More information can be found from the Microsoft site. I'm not sure if this too happens with before editions of Outlook. The 1st link refers to Outlook 2007 when the second link refers to Outlook. I would figure this would be for all Outlook editions since RPC over /pagead/show_ads.js">
o This bug consists of the truth namely IPv6 is no hearing on the loopback port 6004 (RPC//?p=65.
* There is an HP Document (/ERC/downloads/4AA1-5675ENW.pdf) which goes over some testing with altering network latencies using CCR over an OC3 link with a network latency simulator. I wanted to give an overall summary of their discoveries.
o 20 ms latency - All the record files were shipped over properly and all CCR databases auto-mounted properly
o 30-40 ms latency - Some manual mounting ambition be necessitated to mount all your databases for the latency will discourage all logs to be shipped over quick enough for automatic mounting
o 50+ ms latency - Log shipping mechanism was out of control
* In regards to SCR and the web latency heading. SCR is a handbook failover machinery. Because of this, CCR is a lot more dependent on web latency deserving to its automatic failover machinery. Microsoft does provide recommendations on how to tune SCR because latency on the Exchange Technet Library which tin be found here. The problem here is the article is geared for Server 2003 Networking. As because real earth SCR scenarios, I have been told that a mailbox server that contains ~6,000 mailboxes has been successfully failed over to one SCR target along the globe over a 200 ms correlate.
Update 1: There has been an update in regards to NTLM Authentication issues from the Microsoft Exchange Team Blog here.
Sid quoted the following:
As promised, here's an update on the reprompting issue that many of you have encountered.
The core of the issue is that IIS7 uses kernel mode windows authentication by default. Turning this off will nail reprompting. I will post a careful update once I dig through some more and talk to the IIS PD, merely for immediately I ambitioned to provide this update so you can give
it a shot and let me understand if (no, "that") it works for you.
Here's the bid that absences to be run on the CAS boxes ->
%Windows%inetsrvappcmd.exe set config /section:system.webServ
er/security/authentication/windowsAuthentication /useKernelMode:false
Update 2: From the same blog article in Update 1 her