--- title: Mcore not working in BYOD mode description: Mcore not working in BYOD --- [Skip to content](https://service.spor-group.com/sportal/mcore-not-working-in-byod-mode-#main-content) English - United Kingdom Show submenu for translations [More support](https://service.spor-group.com/sportal/kb-tickets/new?hsLang=en-gb) [Customer Portal](https://service.spor-group.com/tickets?hsLang=en-gb) [![Untitled design (1)](https://service.spor-group.com/hs-fs/hubfs/Untitled%20design%20(1).png?width=80&height=80&name=Untitled%20design%20(1).png)](https://www.wearespor.com/) Open main navigation Close main navigation - English - United Kingdom Show submenu for translations - [More support](https://service.spor-group.com/sportal/kb-tickets/new) - [Customer Portal](https://service.spor-group.com/tickets) - [See Our Pricing](https://app.priceguide.ai/estimator/recGXDMSCiHBft2hE) [See Our Pricing](https://app.priceguide.ai/estimator/recGXDMSCiHBft2hE) How can we help you? - There are no suggestions because the search field is empty. 1. [SPOR Group Knowledge Base](https://service.spor-group.com/sportal?hsLang=en-gb) 2. [Troubleshooting](https://service.spor-group.com/sportal/troubleshooting?hsLang=en-gb) # Mcore not working in BYOD mode 01 Verify device eligibility and prerequisites Mcore BYOD mode has strict baseline requirements. Confirm all of the following before proceeding. ### Required checks - **Operating system version**Windows 10 22H2+ / macOS 13+ / iOS 16+ / Android 12+. Older versions are blocked at enrollment. - **Disk encryption enabled**BitLocker (Windows), FileVault (macOS), or device encryption (mobile) must be active. Mcore will not load on unencrypted devices. - **Screen lock / PIN set**A passcode or biometric lock must be configured in device settings. - **No jailbreak / root detected**Rooted or jailbroken devices are blocked by policy. Mcore will exit silently without error. - **Device registered in the IT portal**Log in at**portal.company.com/byod**and confirm your device UDID/serial appears under "My Devices". ℹIf any check fails, resolve it first. Skipping prerequisites is the most common cause of BYOD failures. 02 Check MDM enrollment status Mcore requires a valid MDM (Mobile Device Management) profile to operate in BYOD mode. A missing or expired profile is a common root cause. ### Windows 1. Open**Settings → Accounts → Access work or school**. 2. Confirm your work account appears and shows*Connected to \[Company\] MDM*. 3. If missing, click**Connect**and follow the enrollment flow. 4. If present but showing an error, click the account →**Info**→**Sync**. Wait 60 seconds and retry Mcore. ### macOS 1. Go to**System Settings → Privacy & Security → Profiles**. 2. A profile named*Mcore BYOD Profile*(or your company name) must be listed. 3. If absent, re-download the enrollment package from the IT portal and run it. 4. If present and marked*Not Verified*, remove it and re-enroll. ### iOS / Android 1. Open your MDM app (e.g., Intune Company Portal, Workspace ONE). 2. Check that device status showsCompliant. 3. If status isPendingorNon-compliant, tap**Check Status**or**Sync Device**. ⚠MDM profiles expire after 365 days of inactivity. If you have not used Mcore BYOD in over a year, you must fully re-enroll. 03 Confirm network and VPN connectivity Mcore BYOD requires access to specific internal endpoints. Connectivity issues are often masked by generic "service unavailable" errors. ### Required endpoints | Endpoint | Port | Protocol | Purpose | | --- | --- | --- | --- | | `mcore-auth.company.com` | 443 | HTTPS | Authentication | | `mcore-api.company.com` | 443 | HTTPS | Core API | | `mcore-update.company.com` | 443 | HTTPS | Agent updates | | `ntp.company.com` | 123 | UDP | Time sync (required for cert validation) | ### Test connectivity Run in Terminal / Command Prompt `curl -v https://mcore-auth.company.com/health curl -v https://mcore-api.company.com/health` A healthy response returns `HTTP 200`. Any other response (timeout, SSL error, 503) indicates a network or certificate issue — not an Mcore application fault. ### VPN requirements - **Split-tunnel VPN enabled**Mcore BYOD traffic must route through the corporate VPN. Confirm the VPN profile includes mcore-\*.company.com in its included routes. - **VPN connected before launching Mcore**Mcore reads network configuration at startup. Connecting VPN after launch will not work — fully close and reopen Mcore. - **No conflicting personal VPN or proxy**Disable any personal VPN or browser proxy before connecting. Conflicts cause certificate validation failures. 04 Validate Mcore agent installation A corrupted or outdated Mcore agent installation can cause intermittent failures in BYOD mode that are hard to reproduce. ### Check running agent version Windows (PowerShell) `Get-ItemProperty HKLM:\Software\Mcore | Select-Object Version, InstallDate` macOS / Linux `mcore --version # Expected: mcore/4.x.x (byod-enabled)` If the output does not include `byod-enabled`, the agent was installed without BYOD support. Uninstall and reinstall using the BYOD-specific package from the IT portal. ### Verify agent service is running Windows `Get-Service -Name "McoreAgent" | Select-Object Status, StartType` macOS `launchctl list | grep mcore` The service must show as `Running`. If stopped, restart it: Windows (run as Administrator) `Restart-Service McoreAgent` macOS `sudo launchctl kickstart -k system/com.mcore.agent` ℹAfter a macOS major version upgrade, Mcore's system extensions require re-approval under **System Settings → Privacy & Security → Security**. Look for a blocked extension banner. 05 Resolve authentication and certificate errors BYOD mode uses certificate-based authentication alongside your SSO credentials. Expired or missing certificates cause login failures even when credentials are correct. ### Check certificate validity macOS `security find-certificate -a -c "Mcore BYOD" ~/Library/Keychains/login.keychain-db` Windows (PowerShell) `Get-ChildItem Cert:\CurrentUser\My | Where-Object {$_.Subject -like "*Mcore*"} | Select-Object Subject, NotAfter` If the `NotAfter` date has passed, or no certificate is found, request a new one from the IT portal under **My Devices → Renew Certificate**. ### SSO / MFA issues - **Confirm SSO session is valid**Sign in to your SSO portal (e.g., Okta, Entra ID) in a browser first. If that fails, resolve SSO access before troubleshooting Mcore. - **MFA method is up to date**If you recently changed your phone or authenticator app, re-register your MFA device in the identity portal. - **Device clock is accurate**Certificate validation requires correct system time. Enable automatic time synchronisation and ensure timezone is correct. 06 Clear cache and re-register the device If steps 1–5 have not resolved the issue, a stale local state or corrupted registration token is likely the cause. This step resets Mcore's BYOD identity on the device. ⚠Re-registering will log you out of any active Mcore sessions and clear locally cached data. Save your work before proceeding. ### Full reset procedure 1. Quit Mcore completely (confirm it is not running in the system tray / menu bar). 2. Stop the Mcore agent service (see Step 4 commands above). 3. Delete the local BYOD token store: Windows `Remove-Item "$env:APPDATA\Mcore\byod-token" -Recurse -Force Remove-Item "$env:LOCALAPPDATA\Mcore\cache" -Recurse -Force` macOS `rm -rf ~/Library/Application\ Support/Mcore/byod-token rm -rf ~/Library/Caches/com.mcore.agent` 1. Restart the Mcore agent service. 2. Launch Mcore and sign in. The agent will automatically re-register the device. 3. If prompted by MDM for device approval, check your IT portal for a pending approval notification. ✓Most BYOD issues are resolved at this step. If Mcore is still not working after a full reset and re-registration, proceed to escalation.       How do I manage devices remotely so that I don't need to escalate issues as they happen? Our SPORTrack platform gives you the ability to remotely monitor and manage all of your devices, across the globe. [Check out the SPORTrack platform here.](https://www.spor-group.net/sportrack)     - [Setting Up Your Video Conference Rooms](https://service.spor-group.com/sportal/setting-up-your-video-conference-rooms?hsLang=en-gb) - [Troubleshooting](https://service.spor-group.com/sportal/troubleshooting?hsLang=en-gb) - [Podcasts](https://service.spor-group.com/sportal/podcasts?hsLang=en-gb) - [The Problem With AV](https://service.spor-group.com/sportal/the-problem-with-av?hsLang=en-gb) - [Reviews](https://service.spor-group.com/sportal/reviews?hsLang=en-gb) - [How Much Does AV Cost](https://service.spor-group.com/sportal/how-much-does-av-cost?hsLang=en-gb) - [Comparisons](https://service.spor-group.com/sportal/comparisons?hsLang=en-gb) - [Support](https://service.spor-group.com/sportal/support?hsLang=en-gb) - [Room Guides](https://service.spor-group.com/sportal/room-guides?hsLang=en-gb) [![Untitled design (1)](https://service.spor-group.com/hs-fs/hubfs/Untitled%20design%20(1).png?width=100&height=100&name=Untitled%20design%20(1).png "Untitled design (1)")](http://wearespor.com) 2nd Floor Right Suite, Burlington House, Maidenhead, United Kingdom, SL6 1SQ Copyright © 2025, SPOR Group