Sophos 9.5 windows 7 64 bit

If you force it to comply and request an update afterwards it should then upgrade to 9. I have still no idea why it should affect only the Win7 machines though except that you say you did install them manually - did they have Sophos on them before?

Both the XP machines and Win 7 machines are reporting to EConsole that they are compliant with the updating policy even though they aren't! Note that both pcs are saying that they are compliant with updating policy, yet Win 7 machines primary update server is listed as CID S version 9.

Site Search User. On-Premise Endpoint. Thread Info. RSS More Cancel. This discussion has been locked. Windows 7 64bit and Sophos 9. Hi, Bit of a issue here which is baffling me. Set up a new Subcription to 9. I've manually installed 9. Both Win 7 and XP machines are sharing the same updating policy.

Any ideas? Hello Trevor, the difference is very likely the manual install. You should check the policy compliance on the Win7 clients and whether they realy use S If so, please specify. If not - do you notice some other different behaviour like part of an application unresponsive?

As you think you have disabled almost everything related to Sophos I think you better call support unless you want to wait if others speak up in this forum. I have not installed the firewall component, as I downloaded the version without it. Windows Firewall is disabled too. By "can not connect" I mean the tutor app runs, and scans the network based on their computer name, when you have selected your desired computers, the tutor app makes a connection to those machines and can perform tasks such as lock thier desktop, restart their machine, run tests, remote desktop etc.

I have not noticed any error messages and sophos doesn't log any errors. There is no different behaviour being displayed other than when it gets to the point where the tutor machine makes its connection to the clients, it fails. It can make a difference whether it is 7. But suppressed alerts shouldn't be the problem at all as you say you have disabled "everything" both tutor and student?

Check SAV. Wild guess: If Netsupport has some built-in security features it and SAV might step on each other's toes As I said, there's always Support for the really complicated cases :smileywink:. It's been a while. Since it uses a remote control protocol, Sophos stops it by default. Small apps are Sony specific apps on Sony devices that overlay existing apps. This applies to devices where Sophos Mobile is the device administrator.

If an Exchange email account is transferred to an Android work profile, the account stays with the profile even if the policy is removed. You can send a policy containing another Email configuration to the device. The latest Email configuration is always used. If the configured account is removed, you must remove the whole Android work profile from the device. For example a file manager app. The Apps from unknown sources compliance rule is ignored for devices running Android 8.

As a result, apps in the work profile that rely on the WebView app may stop working. Google resolved this issue by enabling the Chrome app, which enables the internal WebView app. However, you might not want to allow a browser app in the work profile. Normally when you enroll an Android Enterprise fully managed device that is unencrypted, the device is initially encrypted and then enrolled. On some devices including Samsung devices using Android 6.

Some devices e. Due to technical limitations of the Android platform, the App Protection and App Control features can only prevent direct interaction with an app through its user interface. Users might still be able to interact with a protected app through other apps like Google Assistant or through Android system functionality.

For details, see knowledge base article Installing a recommended or required app via an iTunes link on an iOS device requires the Safari web browser. The user can synchronize the app manually. This is a rare issue. Sophos Secure Workspace becomes unmanaged after upgrading. This is caused by a problem with the Apple iOS mechanism used for managing the app.

The managed settings are lost. Installing the profile again for the device in the Sophos Mobile admin console resolves the problem.

The Disable… options are updated correctly. All other options only work on the first installation of the profile. To change these settings you need to remove and reinstall the profile. This is an issue in Apple iOS. On some devices, users are able to uninstall apps even if the Allow app removal restriction is disabled in the iOS device policy. After upgrading to Sophos Mobile 9. Sophos Mobile 9.

For more information and a workaround, see knowledge base article This is an issue in Windows Phone and Windows 10 Mobile. When you forbid data roaming, a Windows 10 Mobile device with data roaming enabled is still reported as compliant. To correct this, clear your browser cache and reload the page. Android devices are automatically enabled through the EAS proxy if the device was enrolled through the Self Service Portal.

Internet Explorer may classify the Sophos Mobile Admin console as an intranet site. As a result, compatibility mode is activated by default which results in a corrupted view and erroneous behavior. To turn off this browser feature, clear the Display intranet sites in Compatibility View check box in the Compatibility View settings of Internet Explorer.