We are having a few initial teething issues with SM.
Macs cant be managed in SM if you have the "prevent an agent from running both patch management and software management at the same time" ticked. This is despite macs not being manageable in PM. The "filters" that check this function should not be excluding macs.
profiles - scan and analysis - select a profile, under machines assigned there is an add button - clicking add always displays an empty list.
most of the time but not always, when you save settings under configuration - settings, you receive a timeout error (but the settings are saved successfully).
The browser debugger console is logging thousands of errors in the SM page - usually "Error <tspan> attribute: x: expected length, "<nan>". and other similar errors - source being ext-all.js:18
profiles - Deploying is for applying windows updates
Profiles - 3rd-Party software is for applying third party updates
Why are you lumping the "scan" and "deploy" jobs under the same heading? It's badly worded. Scan jobs and deploy jobs needs to be under separate sections, or at least far more clearly labelled. It's confusing as heck as it stands, to lump everything together in one section.
Similarly, alerting should be under configuration, as it is in the Cloud Backup and Antivirus module -- surely all the modules should follow the same logical groupings of functions?
Also, most of our KB overrides didn't migrate from PM. We have around 40 PM KB overrides. Only 7 of these were migrated to SM. Why not the other 30+ ???
Craig, how do you have access to the SM module?
I'm on the Beta programme. However, SM is available to 188.8.131.52 users now - there was a webinar a few days ago announcing GA; apparently Kaseya will enable SM on everyone's licences over the next few weeks.
As usual, talk to your rep/success person if you want access faster.
Thanks Craig Hart
Seems that the module still need some adjustements even that the Beta phase is ended.