BigIP LTM, APM and Exchange 2010 design question for multiple AD DS instances

Do you want to authenticate user on both AD servers, or depending on the username or domain you want to choose the AD to request ?

yes I presume you mean if I have multiple AAA Active Directory Servers in their own pools, one for each domain?

Yes I would think this is how it would work. But then, based on the NTLM credentials it would forward the authentication request to the appropriate Active Directory authentication pool.

Don't know if it's what you want, but you can have this :

                                   -> NTLM to server 1
Authentication -> domain condition
                                   -> NTML to server 2

It's only based on VPE creation. Let me know if it's good for you and I'll tell more about it.

that sounds like it could certainly work.

Here are steps you have to do :

1. Create Logon Page with Username, Password and Domain
2. Add a SSO Credential Mapping
3. Add an empty box with 2 branches

    

   1 fallback and the other with the condition : mcget {session.logon.last.domain} == your_domain_name
4. Then you can make your AD authentication
5. And finally make your Resource Assignment

Does this mean the user will be presented with a form he needs to authenticate against?

I may have a confusion, I've just read from the begining your request.

I thinked you it was Outlook Web Access question, but it's Outlook Anywhere...

You will find informations on this here

If you want to check the domain on ntlm informations, the condition is :

I may have a confusion, I've just read from the begining your request.

I thinked you it was Outlook Web Access question, but it's Outlook Anywhere...

You will find informations on this here

If you want to check the domain on ntlm informations, the condition is :

I have managed to get this to work for both domains. Manually editing the krb5.conf file to include a mapping for the domain name worked. LEGACYNAME = LEGACYNAME.ROOT.LOCAL

I can now pre-authenticate users from any domain.

Sure - one thing down, now it's to figure out what to do with OWA with multiple domains :)