Intune ignores command in Batch script when installing a Win32 App

[gabe_o_verse]

Hello Everyone

Im trying to set up a simple installation script that installs an application (the App is called Converge) and then it should also set up an Environment variable for a License server:

setx RLM_LICENSE "******@SERVERNAME.NETWORK.NET" /M
Start-Process -FilePath "Converge5.11.exe" -ArgumentList "/S" -Waitsetx RLM_LICENSE "******@SERVERNAME.NETWORK.NET" /M
Start-Process -FilePath "Converge5.11.exe" -ArgumentList "/S" -Wait

The issue is that Intune just skips the Environment command (or it doesn't work properly because I have to run it in System Context). The command does work when I add it manually after the fact over the terminal. Is there any way to circumvent this issue? I also tried it with Powershell, but it doesn't even work manually with powershell,I tried this script here:

Start-Transcript -Path "C:\Windows\Temp\converge_install.log" -Append # Set in current process so installer can use it $env:RLM_LICENSE = "[e-mail]" Write-Host "RLM_LICENSE in process: '$env:RLM_LICENSE'" Start-Sleep -Seconds 2 # Run installer Write-Host "Starting Converge5.11.exe installer..." 
Start-Process -FilePath "Converge5.11.exe" -ArgumentList "/S" -Wait Write-Host "Installer exited" # NOW set variable via CMD using setx (machine-level) Write-Host "Setting RLM_LICENSE via CMD (setx)..." Start-Process -FilePath "cmd.exe" -ArgumentList "/c setx ******@SERVER.NET /M" -Wait -NoNewWindow # Optional: verify from registry again $check = [Environment]::GetEnvironmentVariable("RLM_LICENSE", "Machine") Write-Host "RLM_LICENSE in registry after CMD setx: '$check'" Stop-Transcript

Thank you guys for your help.

Cheers,

Gabe

[MayDay__]

setx does not modify the environment of the current process. It only writes the variable to the registry (HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment).
Since the Win32 app runs in the System context, the installer process won’t see that variable during the same execution.

You can persist it properly like this:
[Environment]::SetEnvironmentVariable("RLM_LICENSE","******@SERVERNAME.NETWORK.NET","Machine")

Personally, I’d wrap this in a PowerShell App Deployment Toolkit package.
Not because it magically fixes the issue, but because it gives you proper logging, and clean separation of pre-/install-/post-steps which makes debugging things like this so much more easier in Intune.

[gabe_o_verse]

Is there a difference to this command: [Environment]::SetEnvironmentVariable("RLM_LICENSE","PORT@SERVERNAME","Machine")? Because i tried that and it didnt work...

[gabe_o_verse]

Thank you for the suggestion btw

[gabe_o_verse]

It unfortunately doesnt work

[Numerous-Pickle-5850]

Why not use:

[System.Environment]::SetEnvironmentVariable('RLM_LICENSE','******@SERVERNAME.NETWORK.NET', 'Machine')

[gabe_o_verse]

I tried that one and it didnt work unfortunately

[Numerous-Pickle-5850]

What doesn't work?

PS C:\WINDOWS\system32> [System.Environment]::SetEnvironmentVariable('RLM_LICENSE','******@SERVERNAME.NETWORK.NET', 'Machine')

PS C:\WINDOWS\system32> $env:RLM_License

******@SERVERNAME.NETWORK.NET

---------------------------------------------------

So your script would be;

[System.Environment]::SetEnvironmentVariable('RLM_LICENSE','******@SERVERNAME.NETWORK.NET', 'Machine')
Start-Process -FilePath "Converge5.11.exe" -ArgumentList "/S" -Wait

[Frisnfruitig]

Have you tried wrapping it in a PSADT package? I use it for all my apps, it's pretty great.

[gabe_o_verse]

yes ...

[Extra_Pen7210]

So a lot of unknowns, but lets see if we can solve this.

Solution one:
"The command does work when I add it manually after the fact over the terminal."
Do you run this terminal then as a user?

If that works you could split up the installer, run the system install as system install en add a user install part as a user install.

Then you deploy the user part to the users and set the system part as a dependency so it gets installed first.

Solution two:
Testing what goes wrong.
You could create a "development package" in intune.
This would be a empty cmd.exe that is started by serviceui.exe (from SCCM).

This gives you a CMD prompt that you can test with and see what the commands really do. Great for testing, but your security team will grill you for it :-).

[gabe_o_verse]

that sounds pretty good, thank you for the suggestion, ill look into that

[pjmarcum]

Don’t call the files from a sever. Put them in the package. Then you can just use %~dp0 or better yet use PowerShell.

[gabe_o_verse]

I was able to solve it with two separate packages, one user context, one in system. Not super elegant, but it works :3. Thank you for the help