Hey All,
Good or bad I've implemented years ago this KB:
https://documentation.meraki.com/SM/Device_Enrollment/Systems_Manager_Installation_using_Active_Dire...
Its been very nice and automated... it even installs the agent on my Servers (and VM's {Virtual Machines}). In some cases, this has actually been really helpful as an option to Remote In when other options were not available at the time.
In recent days we've been doing a lot of Server Host updates/upgrades. So sometimes we have to move a VM from one Host to the other. What happens in my SM world is that when we spin up the VM on a different Host I get a new notification that a "new" SM client has enrolled. However, its actually a duplicate. The original went offline and a new version of it now exsits in the list of SM Cleints.
Any thoughts as to why or a means in which to prevent it OR even "merge" the two within SM Clients?