F5 Sites
  • F5.com
  • F5 Labs
  • MyF5
  • NGINX
  • Partner Central
  • Education Services Portal (ESP)
Contact
  • Under Attack?
  • F5 Support
  • DevCentral Support
  • F5 Sales
  • NGINX Sales
  • F5 Professional Services
Skip to contentBrand Logo
Forums
CrowdSRC
Articles
GroupsEventsSuggestionsHow Do I...?
RegisterSign In
  1. DevCentral
  2. CrowdSRC
  3. CodeShare

Microsoft Exchange 2010 and 2013 iApp Template

Problem this snippet solves: Use the Exchange 2010/2013 template to provide additional security, performance, and availability for Exchange Server 2010 and Exchange Server 2013 Client Access Servers...
Published Mar 10, 2015
Version 1.0
f5.microsoft_exchange_2010_2013_cas.v1.5.0rc266 KB
BIG-IP Access Policy Manager (APM)
devops
iApps
LTM
security
Fred_Slater_856's avatar
Fred_Slater_856
Historic F5 Account
Joined May 02, 2012
View Profile
benjamin_gate's avatar
benjamin_gate
Icon for Altostratus rankAltostratus
May 02, 2019

Fred - nicely done here.

 

Need to pick your brain on this please kind sir!

 

We use this on our system for 6K mailboxes with 4 Exch2010 nodes in the backend. Strange problem came up the other day and below is the workaround I've found but do need a solution if you can explain what I'm missing please?

 

Symptom

 

Outlook (any version) is randomly prompting a few arbitrary users for Windows credentials.

 

Reproduction of issue & workaround

 

  • Outlook user using Outlook Anywhere is disconnected [for whatever reason, e.g. Hibernate, no network, etc].

     

  • Next time they connect, Outlook prompts for credentials; not every time though - happens randomly.

     

  • Searching APM logs for the user's AD username shows '...username@domainsuffix...WRONG PASSWORD...'

     

  • We know the password is valid because said user can then login on another machine (i.e. not their usual machine) and authenticate just fine through Outlook.

     

  • Any other user can log in to Windows on the affected user's usual machine and authenticate just fine through Outlook.

     

  • Delete the affected user's Windows profile on their usual machine and then create a new Windows profile on it.

     

  • Affected user can now login and authenticate just fine through Outlook.

     

Sledgehammer I know, but it works.

 

Questions

 

  1. Why does it work?

     

  2. What file can I delete to prevent having to delete the whole Windows profile?

     

  3. What's gone pearshaped with APM that's causing this?

     

Bit of historical context for you sir...

 

The last time this happened, we bounced the passive BIG-IP, then switched over to it - all good, and then bounced the active, then switched back - all good. F5 support had no explanation for why that resolved the symptoms.

 

Help guide the future of your DevCentral Community!

What tools do you use to collaborate? (1min - anonymous)

ABOUT DEVCENTRAL

DevCentral NewsTechnical ForumTechnical ArticlesTechnical CrowdSRCCommunity GuidelinesDevCentral EULAGet a Developer Lab LicenseBecome a DevCentral MVP

RESOURCES

Product DocumentationWhite PapersGlossaryCustomer StoriesWebinarsFree Online CoursesTraining & Certification

SUPPORT

Manage SubscriptionsProfessional ServicesCreate a Service RequestSoftware DownloadsSupport Portal

PARTNERS

Find a Reseller PartnerTechnology AlliancesBecome an F5 PartnerLogin to Partner Central

©2026 F5, Inc. All rights reserved.
TrademarksPoliciesPrivacyCalifornia PrivacyDo Not Sell My Personal Information