/build/static/layout/Breadcrumb_cap_w.png

Forticlent Deployment

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?

2 Comments   [ + ] Show 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") - JasonEgg 5 years ago
  • 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. - Alex_ 5 years ago

Answers (5)

Answer Summary:
Posted by: anonymous_9363 6 years ago
Red Belt
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).
Posted by: anonymous_9363 6 years ago
Red Belt
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).
Posted by: anonymous_9363 6 years ago
Red Belt
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).
Posted by: anonymous_9363 6 years ago
Red Belt
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.
Posted by: anonymous_9363 6 years ago
Red Belt
0

Top Answer

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?

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ