JustWantingBasicHelp

Hhmmm ok interesting, we'll have to do some testing but the profiles sounds interesting, of course we like like to keep them monitored while they're away from Site 1 but as long as we know they'll still be getting updates directly from a second profile also works for us. Followup question, if a device doesn't check in with ESMC after a certain time period will it un-license itself or anything? E.g. if it was away from site 1 for 3 months would it no longer update itself? If so, can this time limit be defined in ESMC? Thanks for your help!

Would appreciate some guidance with this. Site 1: restricted network, small bandwidth. Has ESET appliance managing all machines in this site, by providing the ESMC again in this site allows the virus definition updates to be downloaded once and all machines update from this server as opposed to all machines going over the low bandwidth internet. Site 2: less restricted, decent bandwidth. Has separate ESET appliance managing machines Sometimes people in site 1 move to site 2 for a couple of months for work and therefore no longer receive updates to ESET as they can no longer connect to their usual ESMC server. To get around this, we thought it would be possible to use the same URL for machines to use. So matter where the machine was it would use the one URL and and always be able to connect and receive it's updates. E.g. Laptop A usually lives in Site 1 and ESET goes to eset.domain to contact the ESMC, then when Laptop A moves over to Site 2 (which also has eset.domain) it would just be able to connect in to Site 2's ESMC and receive all it's normal updates. We would then see the machine in ESMC in Site 2 and be able to manage it as needed until it moved back to Site 1 where it could also continue to work as normal - and be managed by the dedicated IT team there. What we actually find is that these machines from Site 1 are just unable to connect to Site 1 and 2 ESMCs and therefore do not receive any updates until they are back in Site 1 again. Our thoughts were this was due to the certificates not matching up and therefore ESMC denies ESET Endpoint being able to get updates from here. Let me know if this is unclear, appreciate any help with this Thanks!

Ah i see, i never fully tried the run task, i assumed it be Run a Task right now as opposed to apply it to the group. Thanks for the help!

We are running: ESET Security Management Center (Server), Version 7.0 (7.0.471.0) ESET Security Management Center (Web Console), Version 7.0 (7.0.429.0) And when i go to apply a task to a dynamic group i can only add a task by creating a new one, but the task im wanting to apply to the group is out the box with the appliance and i dont want to duplicate tasks, that feels pretty pointless. Can anyone help me just apply an already existing task to this group? Here is a screenshot of the menu i get, i can only run a task or create a task with 'New Task'