Upgrading SentinelOne on macOS Clients is not done the same way as it's initial deployment. We have edited the Installation script to identify if the client already has SentinelOne installed and run the following command to upgrade instead of going the normal install route: *sentinelctl upgrade-pkg PKG\_pathname* To deploy the upgraded SentinelOne Client to devices, simply create a new revision, upload the new PKG to the Fileset, and change the file name references in the install script.
## Ingredients - FileWave Central - [SentinelOne\_Fileset&Profiles.zip](https://kb.filewave.com/attachments/514) - SentinelOne PKG installer - SentinelOne Group/Site Token ## Directions #### Editing the Fileset: ``` sentinelctl upgrade-pkg PKG_pathname ``` 1. Download and import the SentinelOne Fileset into FileWave Central (we'll handle the Profiles later) 2. In a text editor, create a plain text file named com.sentinelone.registration-token that contains only your Site/Group Token [](https://kb.filewave.com/uploads/images/gallery/2025-01/zO0RfwdcsB8oM0mh-screenshot-2025-01-15-at-11-22-14-am.png) 3. Open the imported Fileset and replace the files under /usr/local/etc/FileWaveInstallers/SentinelOne with your registration token file and SentinelOne PKG.Make sure the token file ownership is set to root:staff. You can change the ownership by selecting the file > Get Info > Ownership
The "com.sentinelone.registration-token" plaintext file must also be extension-less in the fileset and will not work if the file has a .txt extension at the end of the file name. If your filename ends in a ".txt" this can be removed/edited by right-clicking on the file in the fileset > "Rename".
| Before: | After: |
| [](https://kb.filewave.com/uploads/images/gallery/2025-04/VCKEbybJ5HCdfPhw-screenshot-2025-04-09-at-3-15-42-pm.png) | [](https://kb.filewave.com/uploads/images/gallery/2025-04/UGAxPK1sBhSGnPz3-screenshot-2025-04-09-at-3-19-27-pm.png) |
| Before: | After: ***Your installer's name will be different*** |
| [](https://kb.filewave.com/uploads/images/gallery/2025-04/WnwvrDlfSnw2Yv3S-screenshot-2025-04-09-at-4-27-11-pm.png) | [](https://kb.filewave.com/uploads/images/gallery/2025-04/FsMGMPmftV7xTvJB-screenshot-2025-04-09-at-4-19-44-pm.png) |
Profile Metadata shown below
##### We're all set! Now create a Deployment with the Fileset and four Profiles. ##### The Fileset contains a script that will only allow the Installation once all four Profiles have been installed. It is normal to see a Fileset failure the first try. It will keep trying until profiles have installed.The check\_profile script logs each attempt and why it either failed or succeeded. You can see this log by right-clicking on the script in Client Info>Fileset Status. Select the Fileset in the list and the script status will show on the right. Right-click to see script output.[](https://kb.filewave.com/uploads/images/gallery/2025-04/6ASwNv6RQjlHOx3g-screenshot-2025-04-09-at-3-30-03-pm.png) [](https://kb.filewave.com/uploads/images/gallery/2025-04/4IH618E3VdFuH2fs-screenshot-2025-04-09-at-3-34-09-pm.png) You'll notice that the script exited successfully (exit 0) once all the Profiles were found. The profiles are identified by their Profile ID. You can find this by double-clicking on the Profile in the Filesets view.
## Profile Metadata #### Service Management Profile