Bug ID 754541

Hello,

i guess i’ve a problem with Bug ID 754541:

though we are runnining version 14.1.2.7

there is statet:

"This issue is resolved in the following release candidates:

f5.microsoft_exchange_2016.v1.0.3rc5.tmpl

f5.microsoft_exchange_2016.v1.0.3rc6.tmpl"

but I can’t find this versions of the Template.

Any Ideas?

hello kgaigl,

Have you try on https://downloads.f5.com ?

→ iApp Templates

Regards

oh, i made a mistake in reading version mumber, sorry

no pb, please don’t forget to mark the answer as “Select as Best” in order to pass your post as resolved and help other people to find it.

The problem was: the package iapps-1.0.0.562.0 has changed:

when I first downloaded, it contained f5.microsoft_exchange_2016.v1.0.3rc4.tmpl

when I again downloaded maybe a few weeks or months later, it contained f5.microsoft_exchange_2016.v1.0.3rc6.tmpl.

But still, when I reconfigure the IAPP I can’t use the existing ssl-Profile, but with the new Template I can use the existing Cert & key

when you say “reconfigure the iApp” do you use this method correctly?

  1. Log in to the Configuration utility.
  2. Navigate to iApps > Application Services.
  3. Click the Name of iApp.
  4. Click the Reconfigure tab.
  5. Edit any iApp template fields as needed.
  6. Click Finished.
  7. The configuration modifications and are ready for use with the application.

that’s the way i did, yes

OK, did you changed the answer to the question “How should the BIG-IP system handle SSL traffic ?” (choose SSL Offload or SSL Bridging or SSL Pass-Through) in iApp f5.microsoft_exchange_2016.v1.0.3rc6 configuration ?

no, i didn’t

You talking about the steps in the workaround?

I didn’t want to do this because this means service-interruption

with …rc6 this should not be necessary anymore.

I only added 2 new Servers.

actually i wanted to “use an existing ssl-profile”, that didn’t work, then i selected “create a new ssl-profile” with existing Cer & key, and that worked without service interruption.

Yes indeed it’s not necessary with the iApp rc6, but I didn’t know if you were already using an old version (rc4) of the iApp or not.