Within a couple minutes, the machines will start the local service and connect to the indexer. After group policy has converged the next reboot will install the package on our servers. I recommend a replicated DFS network location for deploying software packages.Īfter satisfactory testing, we can roll this package out to our servers. Then, under Modifications the MST is selected. In the group policy editor we create a new assigned application and select the MSI installer for Splunk Forwarder. The MST is generated by going to Transform > Generate Transform and saving the file.įrom here on out, we follow the usual methods for deploying software with GPO. Right click the table and click ‘Add Row’ then enter the key and value that will be added to the transform.Īfter all the parameters have been added to the transform, it’s time to export the finished patch file and get it ready for deployment. Now that the installer knows what to do with our parameters, we can actually add them. In this case, we need to add RECEIVING_INDEXER to the list. All we need to do here is make sure that all the new keys we will be adding are somewhere in the string. The list of parameters with default values is usually called AdminProperties and its value is a semicolon separated list of keys. Some of these aren’t configured by default, so we will need to make sure the installer will parse these parameters. Next we will add the indexer and the deployment server. The default value will be ‘No’ so we will change it to ‘Yes’ To add these configurations to the transform, we need to head back to Orca.įirst, locate the AGREETOLICENSE key in the Property table. Most packages that use MSI silent install switches will have a similar procedure.Īccording to the Splunk Documentation, we need to configure the following parameters: Of course, now is a great time to check the documentation for our specific product and needs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |