Hi everyone,I’d like to clarify something regarding the Intune deployment using the official bash script as it seems to be a bit problematic.I was following during configuration → Deploying FortiClient using a shell script | FortiClient 7.4.0 | Fortinet Document Library We are updating from 7.4.2 to a higher version. Issue I encountered are the following: *If the EMS is connected, the service does not run at all. No errors are show shown in the Intune portal. Which leaves me with the impression that the devices are not being reached. *Some newer OS versions -> macOS 26.5.2, assigned to the same group are not added to the list of “pending” (invisible, not in the list). And I don’t understand why. I am unsure if the script is even reaching them. The person in question had the older version, we removed it manually, and then we were waiting for the script to be executed. The person’s device was synced a few times (and restarted once) - no changes. *In some occasions, the script does not identify whether a FortiClient is installed or not; however, if I install the older version manually, 7.4.2 it recognises it and pushes the newer one almost immediately (once the EMS is disconnected). *What’s the recommended way in that case? Should we keep the older version or just disconnect the EMS? ***We use Azure BLOB storage and devices HAVE access to it. The download does not seem to be the problem but the execution. ****Also, I noticed that the system “feedback” seems to be a bit slow. Perhaps, it’s an Intune problem.Our organisation does not rely on MAC and we can do the installation on-demand (for those who need it if the script fails), but the behaviour is confusing and it’s bugging me.Have you seen something like that? What would you suggest?Kind regards,Sami

Visitor III

Question

FortiClient Intune Bash Script Update

Forum|Forum|10 days ago
July 31, 2026
6 replies
71 views

Hi everyone,

I’d like to clarify something regarding the Intune deployment using the official bash script as it seems to be a bit problematic.

I was following during configuration → Deploying FortiClient using a shell script | FortiClient 7.4.0 | Fortinet Document Library
We are updating from 7.4.2 to a higher version.
Issue I encountered are the following:
*If the EMS is connected, the service does not run at all. No errors are show shown in the Intune portal. Which leaves me with the impression that the devices are not being reached.
*Some newer OS versions -> macOS 26.5.2, assigned to the same group are not added to the list of “pending” (invisible, not in the list). And I don’t understand why. I am unsure if the script is even reaching them. The person in question had the older version, we removed it manually, and then we were waiting for the script to be executed. The person’s device was synced a few times (and restarted once) - no changes.
*In some occasions, the script does not identify whether a FortiClient is installed or not; however, if I install the older version manually, 7.4.2 it recognises it and pushes the newer one almost immediately (once the EMS is disconnected).
*What’s the recommended way in that case? Should we keep the older version or just disconnect the EMS?
***We use Azure BLOB storage and devices HAVE access to it. The download does not seem to be the problem but the execution.
****Also, I noticed that the system “feedback” seems to be a bit slow. Perhaps, it’s an Intune problem.

Our organisation does not rely on MAC and we can do the installation on-demand (for those who need it if the script fails), but the behaviour is confusing and it’s bugging me.

Have you seen something like that? What would you suggest?

Kind regards,
Sami

Jean-Philippe_P

Staff & Editor

Hello Sami,

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.

Regards,

Jean-Philippe - Fortinet Community Team

Jean-Philippe_P

Staff & Editor

Hello,

We are still looking for an answer to your question.

We will come back to you ASAP.

Regards,

Jean-Philippe - Fortinet Community Team

B

Buster_BladerAuthor

Visitor III

Good evening, Jean.

Yes, that's no problem at all.

As far as I heard from our Infrastructure engineer, there has been a problem with the previous versioun, too.

So, there is no rush. If you team finds anything and decides to share it with us, that’d be nice.

But, yeah, seems like it does not properly recognise whether the FortiClient is installed on a newly joined machine (to Intune). If you have the older version, as long as the EMS is disconnected, the script has higher probabylity to execute.

:)

Kind regards,
Sami