This can be done by using the Generate XSight Agent functionality after upgrade.
| XS‑14343 | Upgrades of SOTI XSight from 4.3.2 to 2024.0.0 were failing when the SOTI XSight Database was not using the SQL_Latin1_General_CP1_CI_AS collation |
| XS‑14445 | External user groups were not inheriting SOTI XSight permissions based on role assignment from SOTI MobiControl |
| XS‑14535 | SOTI XSight Live View (Patent Pending) and Live Chat did not start if device did not have an Analysis Profile |
| XS‑16334 | SOTI XSight Live View not showing data when SOTI XSight Dashboard Service was running on a custom port |
| XS‑13116 | SOTI XSight Android Agent was crashing when the device had an incompatible XT Socket Plugin installed |
| XS‑15290 | Users were unable to update an existing report using the “Save As” functionality |
| XS‑15055 | Emails for Scheduled Reports contained CSVs for all dashboard charts but only device/application/battery lists should have been shown |
| XS‑16476 | When previewing device snapshots of Linux devices, the list of all installed apps was incomplete |
| XS‑14426 | Users with the “System Administrator” roles were unable be added as assignees to incidents |
| XS‑14407 | Command line installation would fail if SOTI MobiControl database name was not “MobiControlDB” |
| XS‑14406 | Users were unable to configure multiple IMAP accounts under the same hostname |
| XS‑16383 | After upgrade to 2024.0.1, previously created reports and scheduled reports do not function as expected and need to be resaved |
| XS‑16349 | On environments with multiple SOTI XSight Dashboard Services, batteries cannot be imported via CSVs |
| XS‑16594 | Device snapshots saved in an incident cannot be previewed when migrating from 4.2.1 to 4.3.2 or from 4.2.1 to 2024.0.0 or from 4.3.2 to 2024.0.0 |
| XS‑14730 XS‑9661 | On environments with multiple SOTI XSight Dashboard Services, the master SOTI XSight Dashboard Service can end up in a race condition that causes the Operational Intelligence dashboards to not show data |
| XS‑16663 | Private key for SOTI XSight Agent certificate is not being generated by the SOTI XSight Admin Utility |
| XS‑13939 | Users cannot select existing incidents when attaching it to a Standalone RC session |
| XS‑16828 | Incident raised via the self-service portal is shown as being reported from the phone |
| XS‑16991 | Users without the “Create/Edit Public Notes” or the “Create/Edit Private Note” permission can create/edit incidents |
| XS‑14476 | Sorting on the cellular data usage column is not correct for large deployments |
