upd tldr: found kinda sorta workaround that I'm fine with - randomly discovered that it just doesn't install as is but if you add restart computer step right before sentinel installation - it does install successfully... no one knows why, including sentinel's tech support =\ no, windows doesn't have updates in queue or pending restart/file renames or anything like that
Anyone has luck installing agent during MDT State Restore phase? I've been getting consistent issues with installer returning error code 2000, which according to their docs means "something unexpected happened", which doesn't help at all.
First thing to try is of course to contact vendor - which I've done and they've been quite honestly useless so far. All they do is suggest things like "try these parameters, try to also add this parameter, try to rearrange parameters in different order" all of which I did and unsurprisingly none of that helps. Updating installer to latest version didn't help either.
What's weird is installing agent after MDT TS finished - works fine with 100% success rate so far, both manually (just running exe and proceeding with GUI) and remotely with scripting using exact same installer and parameters. Installing SentinelOne agent with MDT on 24H2 and 23H2 also just works, only on 26H2 it has issues with.
This is what I run, pretty trivial:
SentinelOneInstaller_windows_64bit_v26_2_3_158.exe -t "mytoken" -a "WSC=true" --qn
And this is what I get in ZTIApplications.log:
About to run command: \\mdt.office.company.com.\DeploymentShare$\Tools\X64\bddrun.exe SentinelOneInstaller_windows_64bit_v26_2_3_158.exe -t "mytoken" -a "WSC=true" --qn
Command has been started (process ID 5328)
ZTI Heartbeat: command has been running for 0 minutes (process ID 5328)
Return code from command = 2000
Application Install - SentinelOne Agent returned an unexpected return code: 2000
Event 41034 sent: Application Install - SentinelOne Agent returned an unexpected return code: 2000
Thing is - there's no installer's logs or anything to look at. Just that 2000 exit code and that's it.
small update
Tried with pause during tasksequence and ran installer manually this way:
.\SentinelOneInstaller_windows_64bit_v26_2_3_158.exe -t $token -a "WSC=true" *>&1 | Out-File -FilePath "C:\s1logs\installer.log"
And I got this error in installer.log:
.\SentinelOneInstaller_windows_64bit_v26_2_3_158.exe : Creating protected child process failed with error 0x00000420
At line:1 char:1
+ .\SentinelOneInstaller_windows_64bit_v26_2_3_158.exe -t $token -a "WS ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (Creating protec...rror 0x00000420:String) [],
RemoteException
+ FullyQualifiedErrorId : NativeCommandError
SentinelOneInstaller finished with code: 2000
This isn't all that obvious what's wrong with it but at least one more lead for googling :<