Freshservice Agent install with json file.

Running into the same issue over here. It says that it is able to successfully install the package and looks like it is going to work, but never reports back to FreshService.

Thanks for the response I will try this out and see if I can get it going.

Smiliek Thanks so much for your recommendation I followed what you did and it worked perfectly!

Hi, where did you get the FreshserviceAgent.pkg? I only received the other 2 files.

You create it once you build that PKG, do the file copy to the directory then you drag the freshly created FreshserviceAgent.pkg into Composer and drop it in the folder structure. Then you hit build as PKG again and that is your final package. I was confused at first too till I tried that, never would have thought about doing something like that.

That works. Thanks.

This is my first time using composer trying to accomplish this. Can you provide some additional steps to get this going?

Start out by creating a Normal Snapshot, Name it what you like I named it similar to what SmilieK did. After the the snapshot copy the files to a folder easily accessible. I actually put it in /Users/Shared/tmp Once you have the files copied click Create Package Source. When it is finished you will see the file structure. Drag your newly created package into Composer so it adds it to folder structure. Then click Build as PKG. The create your script which actually installs the agent based on SmilieK's example script. Obviously you want to edit the file path if you aren't using what he did. It worked perfectly for me.

what can i do if I want to prioritize the files? I want json file to be placed in specific location before running the installer

You just need to follow your order of operations when using Composer.  

I've tried that solution, it work when it's a fresh install, but when it's to replace a previous version, it doesn't sync with Freshservice, someone have a solution for that ? 

Any updates on this? Desperately trying but the agents don't check in to FS backend. -___-

Finally this way have work, I don't know why, but only my Mac doesn't work, all the rest in the company have work

What I've done, I've created a folder in the /Library/Application Support/[Business Name]/Fresh Service/ and I've dropped the FS-Agent folder inside it with the json and pkg

Drag the FS-Agent folder in composer, and Apply the permission of the Application Folder to all subfolder

Create the package, that I called FreshServiceAgent.pkg, that package will cache the installer

When the package is done, drag the package in /Library/Application Support/[Business Name]/Fresh Service folder in repackage it. 

I've used this script to perform the installation that I run after

I hope it will help you

Hey there, I'm new to using composer. Where did you input the script?

I created the script in Jamf Pro console under All Setting => Computer Management => Scripts.  Then when creating the policy add that script to run after.  It will then exicute after it downloads the package.

Thanks for the response! I  was able to package the script in composer without having to enter it in the Jamf Pro console. Regardless, your step by step instructions were very helpful and concise. I was able to get it up and running! Thanks!

Hi all,

We have an issue of deploying the Fresh Service Agent over MAC machines. We have followed the suggested steps as above, but it is not working as expected. The steps were follow to use the Composer and to set up the file as supposed to be. Seeing the following log from JAMF:

Can you advise what could be perform to resolve the issue? 

We are seeing it as a report to be Completed, but the file is not deployed

We are starting to use the Asset Management module in Freshservice and used the Jamf app/integration to get all our Macs and iPads into FS. This way the assets don't count against the limit. What is the advantage of using the agent instead of the free integration?

We need to be Jamf Cloud to use the asset management module. So if we are on-prem, we need another solution like the one in this post

Hey iradev,

I know this is waaaayyy old but I had to package this recently and figure this all out. I don't think "wait" is supported anymore use "sleep" instead as the command in the script.

Thank You!

Paul Fye

ok thanks for that. 

I don't use it anymore, we've connect the Jamf Connector and removed the FS-Agent from our Mac, that way some information that we want stay as we expect when the Agent was always changing the Mac name for exemple

Hey Jynotte,

Of course no problem! We had to switch just this week from the Jamf Connector application within FreshService as there is a known bug right now in FreshService with setting up Client Credentials. FreshService support said it would not be fixed until Oct 29th and we could not have assets sitting over a month not getting enrolled into our system which is why we switched!

Thank You!

oh didn't know about that one

i'm trying to install the fershservice agent same method mentioned and tried other methods but it keeps failing ... it started happening in Sequoia, any idea what is it going? does it work for you guys?