![]()
The agent version control feature provides the ability to control what agents are returned when any URL request is made to Deep Security to download the agent. Using agent version control to define which agent version is returned ![]() If the path ends at / (because both and were not specified), the manager will return the agent download for that platform as described in the table above. If no is provided after ///, the manager will return the agent download for that platform as described in the previous table. software/agent/AIX_7.1/powerpc/ĪIX 6.1, 7.1, 7.2 (Deep Security Agent 12 and up) software/agent/RedHat_EL8/x86_64/agent.rpm software/agent/RedHat_EL7/x86_64/agent.rpm software/agent/RedHat_EL6/i386/agent.rpm software/agent/RedHat_EL6/x86_64/agent.rpm software/agent/Oracle_OL7/x86_64/agent.rpm software/agent/Oracle_OL6/i386/agent.rpm software/agent/Oracle_OL6/x86_64/agent.rpm software/agent/CloudLinux_7/x86_64/agent.rpm software/agent/CloudLinux_6/x86_64/agent.rpm The, , and parameters should be replaced with the strings listed in the table below. #TREND MICRO DOWNLOAD AMAZON HOW TO#More detail on agent version control and how to leverage this feature from your scripts can be found at Using agent version control to define which agent version is returned. If using the latest agent in the manager's local inventory meets your requirements, this is the most straightforward option to use.Īgent version control provides the ability for the Deep Security administrator to select on a per-platform basis exactly what agent version is returned from the manager. Simply use scripts that omit the component from the path.If you have many internal application teams, the process to request changes to each one of these scripts in use can be significant.ĭeep Security provides two options to deal with this challenge: #TREND MICRO DOWNLOAD AMAZON UPDATE#If the is hardcoded in each script you distribute, this will require that each of these scripts requires an update to start using the new agent version. When deploying agents at scale, it should be noted that adding the agent version in the URL (which hardcodes this agent version into every script you distribute) can create challenges for security operations teams that will be distributing scripts to many applications teams.Ĭonsider the process that will be needed when the time arrives to use a newer version of the agent. ![]() If your intent is to only use a specific version of the agent in a controlled environment, then explicitly adding the agent version to the URL will accomplish this goal. Should I include the explicitly in my scripts? When this parameter is specified, this represents the agent version string. When this parameter is not specified, the latest agent in the manager's local inventory for the target platform is returned. If any other file name is specified, the file name returned by the manager will always be one of the names provided in the table above. The manager does not validate the file name itself however when a file name is specified, the extension must be one of. Red Hat Enterprise Linux, CentOS, Oracle, CloudLinux, Amazon Linux, SUSE The file name is dependent on the installation process used by each platform: Platform The parameter is the file name of the agent installer file. The parameter is the fully-qualified domain name of the manager, including the listening port number. All the parameters that comprise the URL format are described below. The URL format used to download the agent is: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |