Forum Discussion

TimGawne_92272's avatar
TimGawne_92272
Icon for Nimbostratus rankNimbostratus
Jun 06, 2011

Exchange 2010 Deployment Guide

I had documented all the configuration steps needed for our Exchange 2010 deployment from the previous deployment guide. Now that the guide has been updated, I noticed that it has removed several configurations. I'm trying to decide if it was found that these are no longer needed, or were they just left out?

 

 

I can't use the templates because our environment differs too much, so I'll be doing the configs manually. The appendix has the manual cofigs listed, but they are very basic compared to the previous deployment guide. The previous one had instructions on creating detailed HTTP profiles, with content compression entries (mostly for Office docs and pdfs). This new one doesn't even have the suggested load balancing method in the manual appendix. I notice the persistance iRule is quite a bit different as well.

 

 

The new guide has me questioning the configs i documented out of the previous guide, but is not complete enough for me to trust it.

 

 

Should I use the http profile detailed from the previous guide, where we're enabling compression and caching? Why does the new guide only have the basic http profile now?

 

2 Replies

  • Dayne_Miller_19's avatar
    Dayne_Miller_19
    Historic F5 Account
    Hi Tim-

     

     

    I'm sorry you're having difficulty with the new guide. We inadvertently left out a few things (some of which had been left out of the tables in previous versions as well). Thank you for bringing those to our notice; we'll have an update out shortly, probably in the next day or two, that corrects those ommissions.

     

     

    I am curious about your iRule comment, though. The iRule on pages 56-57 of the new guide is almost identical to that in the previous versions of the guide, with only a few small fixes or improvements. What are you seeing that's "quite a bit different"?

     

     

    And lastly, we're always looking to improve our templates. Can you let us know what is different enough about your environment that the current template can't be used? While not able to anticipate every topology, we'd like to make sure we cover as many as possible, or at least no lock customers into a small set of configurations by not providing flexibility.

     

     

    Thanks for your feedback!
  • Thanks Dayne. The main difference in our environment for the templates, is that we have to re-encrypt on the backend between the LTM and the servers. The templates seem to be focused on modifying Exchange to run on port 80, which we won't be doing.

     

     

    For the persistence iRule, I'm confused about which I should use. Th new one seems to have added a section for ActiveSync and Autodiscover traffic, disables caching for Outlook Anywhere, and adds specific pools. I guess I should use these new additions, but do I just remove all of those pool entries since I only have one pool?

     

     

    The previous version only had this configuration:

     

    when HTTP_REQUEST {

     

    switch -glob [HTTP::path] {

     

    "/rpc/rpcproxy.dll" {

     

    switch -glob [HTTP::header "User-Agent"] {

     

    "MSRPC" {

     

    if { [HTTP::cookie exists "OutlookSession"] } {

     

    persist uie [HTTP::header "OutlookSession"] 3600

     

    }

     

    else {

     

    persist uie [HTTP::header "Authorization"] 3600

     

    }

     

    }

     

    "*Microsoft Office*" {

     

    persist uie [HTTP::header "Authorization"] 3600

     

    }

     

    default {

     

    persist source_addr

     

    }

     

    }

     

    HTTP::disable

     

    COMPRESS::disable

     

    }

     

    default {

     

    persist cookie

     

    }

     

    }

     

    }