Jump to content

jamiehall

Members
  • Posts

    5
  • Joined

  • Last visited

Reputation

0 Neutral

About jamiehall

Personal Information

  • Occupation
    Technical Engineer
  • Location
    Swindon
  1. Yeah still having the same issues, still need to whitelist any of the installer files - primarily "Exploit Mitigation And Activity Monitoring".
  2. So I had stupidly skimmed over the exclusion for "Exploit Mitigation And Activity Monitoring" which has rectified the issue. I skipped it as I couldn't see it as an option and presumed it was for a different license type. Turns out this isn't available for Sophos Central Enterprise top level and therefor has to be carried out for each and every sub-estate with a new policy so you can't use policy templates! Have queried with Sophos as I don't personally fancy cloning then editing workstation and server policies for 25 sub estates...
  3. Even with the exclusions, we're now having issues with the installer processes hanging after they finish which then eventually times out in SOLUS3 - it is eventually logging it as successful as the setup does run, but means ~30 minute timeout delay between each part of the deployment. This also happens when installing manually from extracted packages (you can see the processes continue to run in task manager). This appears to being caused by the Sophos "Malicious Behaviour Detection" module which Sophos has started turning on. We've got a case open with Sophos at the moment to troubleshoot further.
  4. jamiehall

    Help - MacOs Issues

    Have you got any custom scripts with any wait timers on? Found that the previous configurators of our scripts decided to put 20/30 second waits in scripts which massively slowed logons... Otherwise I'd say get a test device and start turning profiles off until you find which one was causing it?
  5. jamiehall

    SMB Drives

    Hi Guys, Using Mosyle MDM to manage a bunch of macs and all is working rather well. Using "Login Items" profile in Mosyle to assign the users mounted SMB drives at logon - however this has an issue of exactly that. If a user logs on offsite/at home/off the network, then they never get their drives unless they log off and on again. Looking at various scripts that we could run regularly to ensure the drives are mapped however they all prompt the user for login credentials. The Mosyle method doesn’t require this as presumably it uses the login/AD credentials it already has. Has anyone got any recommendations and ideas for me to test out? Thanks
×
×
  • Create New...