It’s a “feature”, not a bug. Since Mojave, Remote Desktop control applications have to be given explicit permissions to be allowed to control the desktop. We use Screenconnect. To get that to work with Mac Mojave, we have to go into System Preferences > Security > Accessibility and add the Screenconnect app to the list. You can probably do the same with remote control. After doing that we can then control the screen. There are two gotchas that we’ve come to expect, even after adding our Remote Desktop app to the list. One, if the Remote Desktop app changes even slightly, such as with an app update, you have to get the user to go back into System Preferences > Security > Accessibilty. Once there, they have to first uncheck the Remote Desktop app, then recheck it. That really  because it requires the user to have Admin privileges. Second, you know that “Allow” button you have to click in the Security Preferences panel whenever you need to install new software? Yeah, Apple has made it impossible to click it using any Remote Desktop software. You physically need to be in front of the Mac and click it with the attached mouse. There is no other way. That’s mildly irritating when you have to ask the user to do it for you. It’s a security risk to give them admin rights to do it for you. It’s a  straight up inconvenience when you have to drive to a site with a monitor, keyboard, and mouse to click that button on a normally headless Mac Pro Server sitting in the closet.       auto clicker ... View more

Checked all that - devices check in fine.   Got the same results with a device that is being used at home. ... View more

I dont think it can.   You can however set up email alerts (Systems Manager>Configure>Alets) to notify you if software is installed with a certain expression. ... View more

That would be excellent!   Haven't seen anything about it, may have to be a 'Make a wish' request. ... View more

Hi,   So we have a separate SSID for our casting devices which are accessible from the corp network, but the same principal could work for you.   This SSID is set to Bridge mode with Layer 2 isolation disabled and set to allow all traffic for wireless clients accessing LAN. Our Corp SSID is also in bridge mode.   You could possibly give each streaming device a static IP and set a Layer 3 firewall rule on the guest network to allow communication to the destinations you require (IPs of each streaming device) and block all communication with anything else on your network. and a rule on the corp network to also allow communication with the IPs of the devices on the guest network but block everything else - Not sure how this would look. Im not sure of the limitations of the walled garden but you could try allowing the IPs of the streaming devices? or have them in their own VLAN and allow connection to that IP range. not sure how well it would work as Ive never tried it.   Cheers Chris   ... View more

Doesn't seem to be an option at the moment.   May be worth submitting a feature request via the Make a wish button? ... View more