This Knowledge Base article provides awareness and updates on Trellix rebranding efforts. Subscribe to this article for the latest status of our rebranding efforts and continued updates. Most services and components in the Trellix portfolio will implement rebranding with minimal to no action needed by Trellix customers. When action is needed, advance notice and guidance will be provided as to what steps customers need to take.
What will the rebranding include?
The rebranding will include the following:
- Trellix domain and URL updates
- Rebranded product releases
The following table describes the latest status of our rebranding efforts.
Trellix domain and URL updates
The changes listed in this section require action to be taken by customers. Carefully review and take action before the date specified in the "New URL Effective Date" column.
| Component | Customer Data Center Location | Current URL | New URL | Action / Impact | New URL Effective Date | Deadline / URL Redirect Ends |
| Mobile console | United States | Action: Allow access to the console URL by March 31, 2023. Impact: Users will be unable to access the Trellix Mobile Console. |
March 29, 2023 | March 31, 2023 | ||
| EMEA | ||||||
| API Server URL | United States | Action: Allow access to the updated URLs from your proxy/firewall by March 31, 2023. Impact: ePO SaaS may fail to synchronize data from the Mobile console. |
||||
| EMEA | ||||||
| Token Domain (Syslog integration) | US and EMEA | Action: Allow access to the updated URL from your proxy/firewall. Update scripts to include the updated URL by March 31, 2023. Impact: Syslog will fail to fetch device information. |
||||
| Default Channel | US and EMEA | acceptor.mobile.security.trellix.com/srx | Action: Allow the new URL through your firewall, proxy, or MDM solution by March 31, 2023. Impact: The MDM solution will fail to configure applications. |
By April 3, 2023, Trellix Mobile Security will be available as an update on iOS and Android devices. This update will rebrand the App from McAfee MVISION Mobile to Trellix Mobile Security. We recommend that users upgrade to this rebranded version and open the application after it's installed, to make sure that communication to the Trellix Mobile console isn't lost.
NOTE: Update your MDM solution to include the Trellix Mobile Security application and "Default Channel" URL listed above to avoid any interruptions on new provisioning.
Refer to the integration guide for instructions on how to update the Default Channel on your MDM solution:
- Microsoft Endpoint Management (InTune) can continue to use the McAfee MVISION Mobile threat connector.
- Non-MDM managed devices will need to have the activation link or QR code regenerated to use the Trellix URLs for new provisioning.
NOTE: Non-MDM managed iOS devices might lose their logon token and require the user to log back into the Trellix Mobile application. Re-generate a new activation URL or QR code to provision the device back to the Trellix Mobile console to prevent the device from reporting as inactive.