- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Autopilot and NAC integration
What is the best procedure for OOBE Autopilot devices and NAC integration? We have MDM Connector configured. When ever a new device is connected it is moved to isolation and cannot continue with OOBE.
Currently our windows devices registered as a host if persistent agent is on the machine.
Current MDM Connector Configs.
- Labels:
-
FortiNAC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When you say the device is moved to isolation, do you mean registration, authentication, or other?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Its is Registration but we currently do not allow users to actually Registration/authentication via Captive Portal.
Here is an example of where we get stuck at in the OOBE process.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Since this type of setup "OOBE Autopilot" is a Microsoft feature I guess you are using InTune as MDM, is this correct? What version of FNAC are you currently running?
Due to Microsoft changes the option "Enable On Demand Registration" may not work, the issue is fixed and will be included in next releases (reference #919953).
As a workaround you can lower the "Automatic Registration Polling Interval" to 30 minutes. This option will try to register new hosts found in Intune before they are connected in network devices managed by FNAC.
If you have found a solution, please like and accept it to make it easily accessible for others.