We acquired a company that has very unusual setup. They have multiple tenants in Azure which have multiple firewalls to deal with because the government requires these to be protected and live in their own bubble. We bypassed the issue of attempting to install the BF client by using a configuration file during the setup which pointed to the relay in order to register the endpoints to the actual BF server. This works just great to push patches. I am having an issue where if I install software (Sentinel One) into either of the segmented tenants it states it failed but checking the server it actually installed. The following is my install action script:
waithidden "__Download\SentinelOneInstaller_windows_64bit_v25_1_4_434.exe" INSTALL Parameters
continue if {exit code of action = 0}
My Relevance is:
not (exists service "SentinelAgent" OR exists regapp "SentinelAgent.exe" OR exists key "HKLM\SOFTWARE\SentinelOne" of registry)
The failure according to BF is the "waithidden" line. with a None for the exit code.
This installs just fine in the other tenants it is just the segregated tenants. Can anyone give me an idea of where to start? The servers do show up in the Sentinel Once console.
I had similar issue. If the Sentinel One installer touches network drivers or forces a brief restart of management services during its setup in these specific environments, it might be causing the BESClient service to restart.
If the BES Client restarts while evaluating a waithidden command, it loses track of the execution. When it comes back online, it marks the action as failed with an exit code of None because the original thread is gone.
Best way is to wrap this in command shell and log the output use both exit codes as successful 3010 which is pending restart and exit code 0. Let us know if this solves
Good Morning,
I ran the task early this morning. When I logged in today, all of the servers had failed. I can look at the actionsite\download directory and can see the file there. BigFix has exit code 206 now. I had shortened the name because I read that exit code 206:
"Microsoft Exit Code 206 typically indicates a file path length limitation (exceeding 260 characters), or a network connection/server disruption blocking an update"
Completed action uses wow64 redirection false
Completed prefetch SentinelOnev25_1_4_434.exe sha1:B0F6DD8AA3A821A9EA1C3CB88EA2E56E65548295 size:64715016 http://BFServerName.bdo.com:52311/Uploads/SentinelOnev25_1_4_434.exe sha256:1719791E599B74A07FFB9EBF5D3428821AAC186759B1F1BE8FCC26D5EDF7684F
Completed //output a log
Completed waithidden "__Download\SentinelOnev25_1_4_434.exe" parameters > "C:\Windows\Temp\Sentinel_Install.log" 2>&1"
Failed continue if {exit code of action = 0 OR exit code of action = 3010}
I imagine you've done this already, but worth checking/confirming: if you run the installation executable with the specified parameters manually on a target device, does it work properly? A quick check on exit code 206 for SentinelOne (that's what is returning the exit code in question) seems to suggest an issue with the installation command or parameters.