@mack525 they updated the client on the 18th. I installed it, on my Catalina test machine and it works but after trying to follow the setup processes here now it gave me that verification error. In theory if it's not verified wouldn't install manually correct?
UPDATE:
Today I re-packaged and changed the group permissions to: admin (80) it was set to wheel (0) flushed the Failed policy and it completed successfully this time. I am going to wipe the machine and re-do the Enrollment and hope it goes through without a hitch this time.
Executing Policy WFBS TrenMicro Installation
Downloading TrendMicro.pkg...
Downloading https://use1-jcds.services.jamfcloud.com//download/19727f945eb74fb797d9d257fa52498e/TrendMicro.pkg?token=mysecuretoken
Verifying package integrity...
Installing TrendMicro.pkg...
Successfully installed TrendMicro.pkg.
Running script TrendMicro Installation...
Script exit code: 0
Script result: mkdir: /var/tmp/TrendMicro: File exists
Running command installer -pkg /var/tmp/TrendMicro/WFBS-SVC_Agent_installer.pkg -target /...
Result of command:
installer: Package name is Trend Micro Security Agent
installer: Installing at base path /
installer: The install was successful.
Running Recon...
Retrieving inventory preferences from https://mycloud.jamfcloud.com/...
Locating accounts...
Locating package receipts...
Searching path: /System/Applications
Locating software updates...
Locating printers...
Searching path: /Applications
Locating hardware information (Mac OS X 10.15.1)...
Gathering application usage information...
@JarvisUno Sounds like you got it under control
I've restricted our org from 10.15. i am glad i did. This would've caused some issues with our VPN.
@mack525 Yea No one here has Catalina either, we had to restrict the update. I then had to scrabble for Apple's BOTCHED security update. All of this caused me, to prop up a NETSUS server and call it a day.
Howdy, all! I agree, TrendMicro's macOS deployment documentation is a bit outdated. I packaged things as described in the linked article--essentially following Steps 1-2 and then added the below postinstall.sh script using Jamf's Composer. This worked in my local testing. I haven't yet introduced this into a Jamf deployment (e.g. policy) but imagine that this would work just fine. As always, please test!
installer -pkg /private/var/tmp/TrendMicro/WFBS-SVC_Agent_Installer.pkg -target /
sleep 5
open -a /Applications/TrendMicroSecurity.app
@mack525 Did you have to make any adjustments to your PPPC for Catalina at all? I curious because now that I been testing Catalina I am noticing the I had to update my PPPC settings for Trend to work.
@CorpIT_eB I did use JAMF Composer to package this. What we found was Trend's documentation
for mass deployment needed a little T.L.C for JAMF. I'll break down the steps we took to get this working for us.
- Used Composer to package the WFBS Installer .pkg file i received from the web console and dropped it /var/tmp/TrendMicro directory. Make sure this is composed as .dmg with (FUT) & (FEU) selected

- Next, in order for Trend to register/update the correct virus patterns each machine to your web console, you will need to drop a .plist file. Take a look at this link
on how to get the that identifier. Identifier script should be set to run "After" 
- Lastly i added a "Files and Processes" Execute Command within that same policy

- Should be all you need. We have ours in Self Service and have not had any issues. if you have machines that had Trend installed, i would recommend adding an uninstall script in front of this. Heres how the final the policy looks.

Thank you so much for your solution... Out of curiosity, were you also able to resolve the PPPC prompts?

@mack525 they updated the client on the 18th. I installed it, on my Catalina test machine and it works but after trying to follow the setup processes here now it gave me that verification error. In theory if it's not verified wouldn't install manually correct?
UPDATE:
Today I re-packaged and changed the group permissions to: admin (80) it was set to wheel (0) flushed the Failed policy and it completed successfully this time. I am going to wipe the machine and re-do the Enrollment and hope it goes through without a hitch this time.
Executing Policy WFBS TrenMicro Installation
Downloading TrendMicro.pkg...
Downloading https://use1-jcds.services.jamfcloud.com//download/19727f945eb74fb797d9d257fa52498e/TrendMicro.pkg?token=mysecuretoken
Verifying package integrity...
Installing TrendMicro.pkg...
Successfully installed TrendMicro.pkg.
Running script TrendMicro Installation...
Script exit code: 0
Script result: mkdir: /var/tmp/TrendMicro: File exists
Running command installer -pkg /var/tmp/TrendMicro/WFBS-SVC_Agent_installer.pkg -target /...
Result of command:
installer: Package name is Trend Micro Security Agent
installer: Installing at base path /
installer: The install was successful.
Running Recon...
Retrieving inventory preferences from https://mycloud.jamfcloud.com/...
Locating accounts...
Locating package receipts...
Searching path: /System/Applications
Locating software updates...
Locating printers...
Searching path: /Applications
Locating hardware information (Mac OS X 10.15.1)...
Gathering application usage information...
Hello @Heavy_D
Am facing the same error where it says, Result of command: installer: Error - the package path specified was invalid: '/var/tmp/TrendMicro/WFBS-SVC_Agent_installer.pkg'.
Can you help me with this steps, where you were able to rectify the issue..?