30000 ms timeout waiting for FortiClient Install Service

[AEK]

Hi FortiClient EMS admins

FCT EMS 7.0.13.

When deploying client from EMS I get error 150 on the EMS logs.

Windows events on client show 30000 ms timeout waiting for FortiClient Install Service.

I checked all below prerequisites are ok.

https://community.fortinet.com/t5/FortiClient/Troubleshooting-Tip-FortiClient-Deployment-Error-150-f...

Any idea?

[ebilcari · Accepted solution]

Is this affecting only initial deployments or also the upgrade? Have you tested with different end hosts?

The 7.0 branch has reached end of engineering support and is not actively maintained. I searched internally and found out an engineering ticket to add support for upgrading to 7.0.13 without mentioning initial deployments. There is also a known issue #992045.

[Anthony_E]

Hello Abdelkrim :)!

Hope you are good.

Will try to find somebody ASAP :)!

Regards,

[AEK]

Thanks for your support Anthony!

[Anthony_E]

Hi Abdelkrim :)!,

Anytime.

Sorry it is taking some time but we are still investigating :)!

Regards,

[Anthony_E]

Hello @ziomeko,

Did you post in the wrong conversation?

Regards,

[AEK]

Thanks again Anthony. I appreciate.

Yes I think Ziomeko is in the wrong conversation.

[Anthony_E]

Yes apparently Ziomeko was not in the good discussion.

Did you find an answer Abdelkrim?

@MZBZ, @mithing, I can see you are EMS expert? Do you maybe have an idea to help Abdelkrim?

Regards,

[ebilcari · Accepted solution]

Is this affecting only initial deployments or also the upgrade? Have you tested with different end hosts?

The 7.0 branch has reached end of engineering support and is not actively maintained. I searched internally and found out an engineering ticket to add support for upgrading to 7.0.13 without mentioning initial deployments. There is also a known issue #992045.

[AEK]

Thanks for your feedback, Emirjon.

This is an initial deployment.

We opened a ticked few days ago and still working on it (escalated to dev team).

I see the known issue 992045, and I see it looks like my case. Any workaround for that issue?

[ebilcari]

Unfortunately there is no workaround available. I guess you will receive a proper feedback from the TAC team but since this product is already EOES and this feature is not affecting security, a fix may not be provided.