u/Lunde_Deluxe

Has anyone experienced this with the Rockneo Q105?

I've split my lawn into a front yard and a backyard (charging station is in the backyard). The two areas are connected by a passage that's about 1 meter wide.

During mapping, I manually drove the mower through the passage without any issues, so the map looks correct. But when it starts mowing automatically, it approaches the passage, turns around, and then says the mowing task is complete without ever entering the other zone.

The same thing happens in another narrow passage elsewhere in the garden.

Is there a setting I'm missing, or is there a minimum passage width required for the mower to navigate between zones?

Any advice would be appreciated!

Has anyone experienced this with the Rockneo Q105?

I've split my lawn into a front yard and a backyard (charging station is in the backyard). The two areas are connected by a passage that's about 1 meter wide.

During mapping, I manually drove the mower through the passage without any issues, so the map looks correct. But when it starts mowing automatically, it approaches the passage, turns around, and then says the mowing task is complete without ever entering the other zone.

The same thing happens in another narrow passage elsewhere in the garden.

Is there a setting I'm missing, or is there a minimum passage width required for the mower to navigate between zones?

Any advice would be appreciated!

Has anyone experienced this with the Rockneo Q105?

I've split my lawn into a front yard and a backyard (charging station is in the backyard). The two areas are connected by a passage that's about 1 meter wide.

During mapping, I manually drove the mower through the passage without any issues, so the map looks correct. But when it starts mowing automatically, it approaches the passage, turns around, and then says the mowing task is complete without ever entering the other zone.

The same thing happens in another narrow passage elsewhere in the garden.

Is there a setting I'm missing, or is there a minimum passage width required for the mower to navigate between zones?

Any advice would be appreciated!

Hey Reddit,

We're in the process of enforcing MFA for all users in our org using Microsoft Entra ID. We've got Conditional Access policies set up, but we're struggling to get a clean overview of who hasn't actually registered an MFA method yet.

At the moment I'm using Authentication Methods -> User Registration Details -> report, which shows MFA Capable: Yes/No. That seems to be the best source of truth so far.

A few things we're trying to figure out:

- How are you identifying users who haven't configured MFA?

- Are you using the User Registration Details report, something else, or a custom PowerShell/Graph script?

- I have tried creating a Dynamic Group, in Entra ID using user.strongAuthenticationMethods -eq "[]" but got a service error, seems like that attribute isn't supported. Anyone found a workaround for automatically maintaining a group of "not configured" users?

- How are you keeping that group up to date, manually, scheduled script, something else?

Worth mentioning: we're not only using Microsoft Authenticator, we also use OS2Factor as an MFA method. Because of this, we're not using the built-in, Registration Campaign feature, as it only nudges users to set up Microsoft Authenticator, not third-party providers like OS2Factor. So we're looking for alternative ways to identify and notify users who still need to register.

Would love to hear how others are handling this, especially in larger environments.

Cheers!

Hi all,

I’ve been troubleshooting an issue with Windows Autopilot profile assignment and wanted to hear if others have seen similar behavior.

We recently changed our setup from assigning the Autopilot profile to “All devices” to instead using a dedicated Autopilot dynamic group (similar to “All Autopilot Devices”).

Since that change, we’ve noticed some inconsistent behavior:

Devices without a GroupTag show as - “Assigned externally” and do not get an Autopilot deployment profile

These same devices, do appear within the Autopilot profile scope, since they are members of the group

New imports work fine and get assigned correctly (unless explicitly tagged for other profiles like Shared/Test)

Triggering a sync does not fix the assignment

The strange part:

If we manually update the GroupTag, the profile assignment is immediately recalculated and applied.

But:

- Only certain values seem to work (e.g. existing tags like `Region-Personal` or `FIX-Personal`)

- Simple/new values like `Fix`, `Temp`, etc. do not trigger reassignment

So right now it looks like:

- Assignment gets “stuck” after moving away from “All devices”

- A valid GroupTag change seems to be required to force reevaluation

- Group membership alone (dynamic Autopilot group) does not always trigger profile assignment refresh

So to the question:

1. Have you experienced similar issues after moving from “All devices” to scoped Autopilot groups?

2. Does GroupTag act as a hidden trigger for reassignment in your experience?

3. Are you assigning profiles via “All Autopilot Devices” or using more controlled/dedicated groups?

4. Any best practices to ensure consistent profile assignment without manual intervention?

I’m currently testing a script-based approach to reapply tags and force reassignment, but I’d prefer understanding the root cause.

Any input or experiences would be greatly appreciated!

Peace out tech