Learned the hard way: "Unattended" access isn’t 100% silent out of the boxSolved

Participant
Discussion
3 weeks ago Jan 27, 2026

I just wanted to save someone else from the headache I’m dealing with this morning.

We just rolled out a batch of Samsung tablets to our warehouse floor. They are mounted high on forklifts, so they are effectively “unattended” devices. I pushed the Unattended Remote Access policy in Hexnode, assuming I could just remote in whenever I needed to fix issues.

The Gotcha: I tried to remotely view/control into a device today, and the connection just hung on “Waiting for user permission.”

Turns out, Android security requires the user to grant permission physically, one time before the “Unattended” policy kicks in. Since nobody at the warehouse knows these tablets exist yet, I had to walk a floor manager through climbing up a forklift just to tap “Allow” on a screen.

Learn from my mistake: Pre-stage your permissions before you mount the hardware!

Replies (4)

Marked SolutionPending Review
Participant
3 weeks ago Jan 26, 2026
Marked SolutionPending Review

Oh man, I feel your pain. The “First-Time Prompt” is a classic Android security feature. It prevents creepy admins from spying on people without at least one initial consent.

Did you also make sure you had the Hexnode Remote View app installed? I know on non-Samsung devices the main agent is enough, but Samsung usually needs the helper app to handle the Knox API calls.

Marked SolutionPending Review
Participant
3 weeks ago Jan 27, 2026
Marked SolutionPending Review

Yeah, thankfully I caught that part in the docs. The Remote View app was there; I just assumed the policy would override the OS prompt immediately.

So just to confirm my sanity, once that manager clicked “Allow” today, it should never ask again, right? Or do I need to keep the guy on speed dial?

Marked SolutionPending Review
Participant
3 weeks ago Jan 27, 2026
Marked SolutionPending Review

You’re good now!

As long as that Unattended Remote Access policy stays active in your Hexnode portal, the permission is “sticky.”

  1. First attempt: Prompts the user (or during staging).
  2. Every attempt after: Silence. You just drop right into the session.

Ideally, you want your staging team to initiate a remote session while the device is still on the IT bench to clear that prompt before it ever goes into a box.

Marked SolutionPending Review
Participant
3 weeks ago Jan 27, 2026
Marked SolutionPending Review

“While it’s on the bench.” Adding that to my checklist for next time. Thanks guys.

Save