I can’t find anything in the documentation or other forum posts regarding this but does the latest release no longer try to get admin rights when running “Invoke-AppDeployToolkit.exe”? In previous versions, when running the exe as a standard user, it would give me a UAC prompt to launch it as an admin.
In this latest version, it seems like it just attempts to run without elevating to admin and then nothing happens. There are also no logs created. If I right click and select “Run as administrator” then it runs as expected.
Is this by design or am I doing something wrong? I do have “RequireAdmin = $true” in the $adtSession variable in Invoke-AppDeployToolkit.ps1.
I definitely appreciate you doing a thorough search! The documentation doesn’t clearly spell it out, but the executable won’t auto-elevate anymore and that’s a specific decision we took as part of 4.1.0.
In the past, the auto-elevation on user-targeted installs has been a source of unnecessary elevation prompts for users, which can look like a phishing attempt. Windows is also including Administrator Protection which uses just-in-time admin access and changes how UAC works. Lastly, and not that this had a bearing, but removing the RequireAdmin check also reduced the code in the executable by about 50%. Determining the value from the config was quite labourious.
We’ll look towards spelling that out better in the documentation, but we’re anticipating this won’t affect many, or any real-world workflows, and probably only impacts people testing their deployments locally on a VM, etc, which of course can be worked around by right-clicking the exe and running it as administrator.