Hey folks,
Running into something odd. One of our macOS devices is now flagged non-compliant because SentinelOne refuses to install.
Deployment keeps failing with error 1603, and after adding the SITE_TOKEN (twice… just in case), it still fails.
Hexnode just says “missing required app,” SentinelOne says “1603,” and I’m somewhere in the middle staring at logs like they’re horoscopes.
Anyone cracked this one before?
90 Views
Oh wow, 1603 error is the installation equivalent of a shrug emoji.
That one’s usually thrown when something in the install parameters is off, but macOS won’t tell you what. Classic.
For SentinelOne specifically, I’d check these:
Jumping in, we had a nearly identical issue last week.
Everything looked perfect… until we noticed something tiny like a single space around the equal sign in the SITE_TOKEN parameter.
I’m not kidding; that was the entire issue.
If it looks like this: SITE_TOKEN = abc123
It will fail. Every. Single. Time.
It must look like this: SITE_TOKEN=abc123
No space. No formatting freedom. Installation parameters are allergic to whitespace.
We fixed that one character, pushed again, and the install went through instantly. Compliance cleared up right after. I felt both relieved and slightly betrayed.
Okay… I’m embarrassed to admit this, but yeah there was a tiny space in my parameters.
Removed it, synced the device, and SentinelOne installed like nothing ever happened. Compliance is happy, I’m happy, and I’m never trusting my eyeballs with install parameters again.
Don't have an account? Sign up
