![]() ![]() There should be one package that asks the user its OU based on a database that IT sets up. EVERY ONE OF THEM must be updated every time there is a new Kaseya client release (about four times a year). If you have more than about a dozen OUs, you will see what I mean: you must create a new install package for each OU. The way installation packages are created is terrible. "View" is powerful to *use* but clumsy and unwieldy to *manage/administer* misleading word choices in scheduling boxes Then apply the Manage Variables to those Machine Groups under the Agent Procedures.Cons: Persistent, unfixed, obvious GUI issues spanning years and years after being reported: Or if you need Intercept X only installed create a Machine Group called intercept only To provide different Variable Options for a Customer, you can create Machine Groups and then group those systems under that Machine Group.įor Example, if we have certain workstations or servers that don't get Sophos installed Create a Machine Group for no sophos So on the Manage Variables set the Deploy, Customer Token, Location (Management Server), and Products So for this Customer: sophoslab the workstations are in the root group. Taking a look at the Agent below, we can see that the Win10Kaseya workstation belong to the root.sophoslab ![]() ![]() The Customer Name, Customer Token, and Management Server (Location variable).Īpplying the Customer CSV Values to the correct Customer or Group In the Custom CSV File, there will be three columns that are needed. ***Use a Comma not a Semi-colon to separate the products***įor the Next Step, you will need to download the Customer CSV File. ***For Termed licenses, all will only install the components available on the License ID*** all - This indicates that you want to install all three components.deviceencryption - This indicates that you want Device Encryption.intercept - This indicates that you want Intercept X.antivirus - This indicates that you want Endpoint Advanced or Standard depending on the license selected under Licensing.This is important because it will direct the Agent on which components need to be installed. There are a few different options for this field. Set Variable Value to antivirus,intercept.On the right side under Rename/Create Variable enter Sophos-Central-Products.Next, the Sophos-Central-Products variable. On the right side under Rename/Create Variable enter Sophos-Central-Location.Next, the Sophos-Central-Location variable. On the right side under Rename/Create Variable enter Sophos-Central-Token.On the right side under Rename/Create Variable enter Sophos-Central-Deploy.We'll start with the Sophos-Central-Deploy variable Next, we need to manually create the New Variables and Apply a few Place Holder Variables In this next section please ensure that you copy the Managed Variables exactly or else the Script won't work. Upload the SophosSetup.exe, which will then appear under the Current Folder Contents. Next, you'll go into Kaseya and Agent Procedures - Schedule/Create Save the SophosSetup.exe to your desktop. Upload the SophosSetup.exe Thin Installerįrom the Sophos Partner Dashboard, Click Deployment and then Click on the Endpoint Installer Then Right Click on the Sophos Central Folder and Click Import Folder/ProcedureĬlick on the Camera Search Button to the right, select the Sophos Central Thin Installer.xml and Click SaveĪt this point you have the Agent Procedure Installed ![]() Right Click on Shared and Click New Folder - Folder Name: Sophos Central (You can put it where ever you want) Start by going to Agent Procedures - Schedule / Create The first step is to import the XML Agent Procedure into Kaseya. 5621.Procedure Sophos Central Thin Installer.xml ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |