Do they not know their own product? Perhaps not.Ī quick glance, the initial download gives you "FortiClient_5.0.3.105_Installer.dmg" which only contains a 400K "FortiClientUpdate.app" application that downloads the REAL installer. On a side note, its amazing they can't give you even some guidance on what gets configured. ![]() In some cases you might need to script it with something like defaults or PlistBuddy. Even monitoring file system changes for a few seconds can pull in dozens of files not related to what you're configuring, so just be careful to examine everything carefully afterwards. ![]() ![]() I recommend doing it on as clean a system as you possibly can, maybe even one not joined to your domain for example, to prevent all kinds of extra stuff getting picked up. I sometimes use Composer snapshots or the "Monitor File System Changes" method just to figure out what's being dropped on the system during a manual configuration and take things from there. Not necessarily that you'd want to just wrap up whatever Composer sees, but you can use it as a basis of what files and preferences, etc to examine. The post registration and config part is the only place I would use a snapshot method in Composer to at least figure out what files it may be adding as the client gets configured.
0 Comments
Leave a Reply. |