![]() (Note: this is the same technology as the existing APNS cert in N-central’s MDM for iPads and iPhones – but it is being setup with a different back-end service.) Enrollment Helper can be enabled/disabled with each cert. N-central includes support for creating a push cert for only specific customers, or globally for all devices. Multi-tenant push certificates: To get started with Device Management, N-central admins must send a CSR from N-central to the Apple Push Certificate portal to get a push cert. This can be enabled/disabled across your entire fleet, or on a client by client basis, or one device at a time. This cannot be scripted.Įnrollment Helper: to assist with manual enrollment, N-central provides an app that presents your brand – or a friendly name of your choosing – to users and asks them to initiate the process of installing the Enrollment Profile. User-approved manual enrollment: To bring Mac workstations under management properly, Apple requires that enrollment into Device Management be approved by the user of the device. ![]() Here’s what Device Management for Apple includes in the 2022.7 release: The two services will co-exist for some time. The existing N-central MDM for iPhones and iPads is similar technology but a different back-end. This is a new service to N-central is for Mac workstations only. N-central 2022.7 is the first to include N-able’s Device Management for Apple solution. ![]() N-central 2022.7 is jam-packed with both fixes and new features! Please see below for more information on our new features, and the fixed items list for a list of bug fixes! Checklist for upgrading your N-able N-central Server to 2022.7 HF1. This list is still fully editable for individual devices and in the defaults if you desire to make changes afterward.įor new installations of N-central 2022.7 HF1, you will need to provide the FQDN for this N-central server on the initial login wizard page.īefore upgrading to 2022.7 HF1, we strongly recommend reviewing the following KB article to help prepare you for this upgrade. We are also adding the FQDN from the Network Setup page to the top of the Server Address list on the Communication Settings page. Agents and probes will not attempt to upgrade to 2022.7 HF1 and beyond unless the operating system of that device recognizes N-central’s certificate as valid. As a result, you can try the upgrade again without needing Support to remove a flag.Īgent and probe behavior is also part of the security enhancement in N-central 2022.7 HF1. We also have modified the upgrade process so that if you don’t have a valid certificate in place before attempting this upgrade, you will receive an error message before any database changes are made. To support these changes, there are updates to a few screens in the UI, such as the Network Setup page, as well as the Generate and Download certificate page. ![]() This will include any certificate where the whole chain is validated to a root CA within the system trust store. Now, the N-central server will require a valid SSL/TLS certificate to be applied. N-central 2022.7 HF1 provides a major security enhancement which requires additional attention to your N-central network and client environments. See the 2022.7 Release Notes for requirements and support details. ![]() If you had the code drop applied for this already or use EDR integrated with N-central, please contact Support before upgrading to this release. Please be aware that the known issue KUIP-4432 still exists in N-central 2022.7 HF1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |