Trend Micro Package won't keep server information

After installing the Trend Micro Security 3.0.1098 client, it will attempt to connect to the parent server(s) and typically will do a pattern update.

If it's not able to locate/connect to a parent server, the client Menu Bar will display that it hasn't registered with any parent. But your not seeing that error.

When you open the TMS application and click on the lower center box "Smart Scan Agent Patter", it should show the parent server path and the component version numbers.

Are the two other packages related to networking, DNS, proxy, or firewall settings?

I just did this a few weeks ago with the OfficeScan 3.0.1098 installer. To get it to work, I used Composer to make a .pkg file that installs the original tmsminstaller.pkg and the Resources directory (with plists, etc) to /var/tmp/Trend. Then, a simple bash script that runs

#!/bin/bash
installer -pkg /private/var/tmp/Trend30/tmsminstall.pkg -target / -verbose
rm -rf /private/var/tmp/Trend30
exit 0

+1 for @KSchroeder

We are doing the same thing here with our deployment. I was flummoxed too when i tried to deploy the pkg. If you look at the installer logs it actually says "could not find Resources/plist etc."

You or your Trend admin should be able to obtain the mass deployment "mpkg" for installing via Jamf Pro. (The server has an options for downloading single local installs via the pkg file or mass deployment via the mpkg file.)
Since the release of 3.0.x, I've switched to downloading the file from the console titled:

tmsminstall.mpkg.zip

I rename it

Trend_Micro_Security-3.0.1098-console005.mpkg.zip

and drop that into Casper Remote.
We've had good success with deploying via Casper Imaging and Casper Remote. They only issue we've seen is if the Trend Console Server isn't responding to new client connections. The result is that the clients will report that they have not successfully registered with a parent server. Restarting some of the services on the server will resolve that issue.

Hey @KSchroeder ,

Based on your example, is this how you structured your deployment:

When I try to open it locally on my machine, I get hit with the "The operation couldn’t be completed. (com.apple.installer.pagecontroller error -1.)" error.