Hi all,

we have a Lync 2013 deployment and everything is working fine.

Only issue is that when mobile clints sign in from internal network,it fails since no window shows up to accept internal signed certificate.

Sometime this is working,but after a while it fails.For some users it works if we reinstall the client.

Iphone users doesnt have this issue.

My question is,can we assign 3rd part certificate on all front end pools?

Does Pool name need to be in the subject ?

I talked to our network guy to put on internal/external certificate on the KEMP (since its here internal client hits first),but he refuses.....

T

>can we assign 3rd part certificate on all front end pools?

Yes, you can install 3rd party certificate on front end pools and subject name should be pool name.

Hi Off2work,

If you use public certificate for your FE servers , you should also use public certificate for your Edge internal interface.

Best regards,

Eric

Hi all thanks for reply,

we are using public cert on edge servers,its only FE servers we are using internally signed.

Issue we are having is when mobile clients sign in from internal WIFI.Usually mobile clients should pop up and ask if you want to accept the certificate.We can choose yes and never show again.

This will work for a while,then suddenly it says cannot connect to server.If we reinstall the 2013 mobile client,then it will work again for a while before same error occurs.

If we have to use frontendpool as Subject name,then dont think it is a good way to go.

We still think this is a mobile client bug,since it works fine on Iphone devices.Just Android and Windows Phone are having this issue.

Will have to force networkguy to install the cert on KEMP,then i guess we avoid this error.