Exchange 2007 and Exchange 2010 on Windows 2008 or Windows 2008 R2 – Updated TCP Chimney and RSS settings experience

See info below, and let me know what you think: 



Comments (2)

  1. SammyKrosoft says:

    @Exchange Queries: yes indeed, TCP/Chimney is part of the Windows Network Scalability Pack and the Windows team tell us that it should be enabled. But if the NIC drivers are not properly configured or have not been updated, there may be network issues
    and odd Exchange behavior, just like I had one in a 25,000 Mailbox site with 10 Exchange servers (mails getting stuck in the MAPI Submission queue – which is the Queue of a HUB Transport server that is transferring messages directly to the destination Exchange
    Database where the final recipient is located). Deactivating TCP Chimney and RSS was the solution for that as we saw in the dumps that the Transport server was not able to connect to the destination store, it was just waiting for a connection; deactivating
    TCP Chimney and RSS solved this issue, which never ever occurred again. We tried to re-activate TCP Chimney and RSS just to check what would happen then, and after a few minutes we got a couple of messages stuck in the queue again. Then we de-activated these,
    and almost immediately the messages were released from the "MAPI Submission queue".


  2. Is it a good practice always to disable to TCP/Chimney for Exchange 2013 SP1 in Windows Sever 2008 R2 Sp1..And the KB951037 article talks for Windows Server 2008 not for 2008 R2 or 2008 R2 Sp1…Found it should be enabled as best praticse ….can you suggest
    on it..

Skip to main content