/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Anyone been able to deploy the forticlient to windows machines with k1000.  I assume I have one of the options selected wrong.

I have Forticlent.msi as dependency
On success
Launch as Program
Directory: $(KACE_SYS_DIR)
file:  Forticlient.msi
parameters: msiexec /i FortiClient.msi /qn

Also, was anyone able to also add the configuration file to the install?
Answer Summary:
Cancel
2 Comments   [ - ] Hide Comments

Comments

  • Any specific reason you are using Scripting rather than Managed Install? I find it much easier to deploy MSI files using the Managed Installations module (located under "Distribution")
  • Hey,
    as far as we were told by our Fortigate representative you can't add any configuration File as parameter to the msi.
    There once was the Forticlient Configurator which required a license so you could customize the Client to what you want. But that one is not supported anymore and they want you to use the Forticlient EMS Server for this.
Please log in to comment

Answer Chosen by the Author


Answers

0
What I wanted to add on to my post was the advice that the other thing that you should always do is log the installation, which is a cinch to do with MSIs. If there's no log, how on Earth are you going to even begin trouble-shooting failed installations?
Answered 04/09/2018 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Answers

0
I know damn all about Kace but I suspect you're expecting the agent to find the MSI in the KACE_SYS_DIR.

I *always* use explicit paths for files, be they EXEs or "data". For deployment, where you might now know the final target folder name, use %~dp0 (along with relative pathing, if required).
Answered 04/09/2018 by: VBScab
Red Belt

Please log in to comment
This content is currently hidden from public view.
Reason: Removed by member request
For more information, visit our FAQ's.

0
I know damn all about Kace but I suspect you're expecting the agent to find the MSI in the KACE_SYS_DIR.


I *always* use explicit paths for files, be they EXEs or "data". For deployment, where you might now know the final target folder name, use %~dp0 (along with relative pathing, if required).
Answered 04/09/2018 by: VBScab
Red Belt

Please log in to comment
0
I know damn all about Kace but I suspect you're expecting the agent to find the MSI in the KACE_SYS_DIR.

I *always* use explicit paths for files, be they EXEs or "data". For deployment, where you might now know the final target folder name, use %~dp0 (along with relative pathing, if required).
Answered 04/09/2018 by: VBScab
Red Belt

Please log in to comment
0
Some awesome coding on display here.

The duplicate posts are NOT of my doing. They appeared after attempting to edit the first one. I have contacted Quest via the 'Contact Us' link about them.
Answered 04/09/2018 by: VBScab
Red Belt

Please log in to comment