Why this is not working on intune, i mean app is getting installed but no shortcut
getting created can someone confirm it? i tried slack, Kiro and still same issue
I am integrating it as system-based app in Intune with custom registry as detection method
A few questions: what exactly are you trying to accomplish, why are you running the process as another user instead of just SYSTEM and what do you currently have in your Invoke-AppDeployToolkit.ps1 script?
Most installers should be able to create their own shortcuts correctly without needing to do anything specific.
Yes using invoke-appdeploytookit.ps1 and trying to install amazon kiro app which is user based. in past we have created many user based app in same manner which were executing in system context but was creating shortcut in user profile. We were using old template so far and we observed since last couple of month this logic not working anymore on intune and works fine from sccm, so now i am trying with new template but issue is same installation complete but no shortcut
You'll have to provide more information about what you have inside the Invoke-AppDeployToolkit.ps1 script and if you are doing something different in Intune vs SCCM.
Nothing different using same package in sccm and in intune just calling start-adtprocessasuser with kiro.exe with silent parameter and then in post install section writing hklm key for detection method…for your information i have used similar logic in many user based app but something is changed in intune couple of months back which is causing this, the same logic was worked fine couple of months back. User based app supposed to create shortcut within user appdata local or roaming profile on intune… i am not complaining about sccm as similar thing works fine in sccm but not in intune
for your information using below command
Start-ADTProcessAsUser -FilePath 'Kiro-win32-x64.exe' -ArgumentList '/VERYSILENT /SUPPRESSMSGBOXES' -ErrorAction SilentlyContinue
in post install section writing reg key
Set-ADTRegistryKey -LiteralPath "HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Amazone_Kiro" -Name 'Systemcomponent' -Type 'Dword' -Value '1'
Okay so I had a look at Kiro-IDE installer for Windows x64.
It's a good idea to get used to this sort of thing so I'll mention it in case you're new to application installers. Launch the setup executable from a PowerShell prompt using /?. This is what you get:
This application installer uses the Inno Setup installation builder. This type of installer accepts a configuration file in the form of a .INF file. If you want to learn more about it check out the Inno Setup documentation. Here's an example of the setup generated when I went through the installer manually, selecting the desktopicon as an additional task, file association and adding it to PATH.
[Setup]
Lang=english
Dir=C:\Users\USERNAMEHERE\AppData\Local\Programs\Kiro
Group=Kiro
NoIcons=0
Tasks=desktopicon,associatewithfiles,addtopath
I checked the default setup bahavior for the latest .EXE available on Kiro's site for Windows. It does not seemingly create the desktop icon.
You're not giving me a whole lot of information to go off of here but where I'd start is run the installer manually on a system via PowerShell prompt like this:
.\kiro-ide-0.6.0-stable-win32-x64.exe /SAVEINF=kiroSetup.inf
This will allow you to go through the setup windows manually and select what defaults you want in your installer. Once you've completed the install the .INF file will be available wherever the current directory is pointing to when you run the .EXE.
Voila, you have a setup .INF file that does what you want. Use it as a parameter when you call the setup executable using -LOADINF [filename goes here]. See if this gives you more consistent results.
As far as I am aware, no major changes have been introduced from Intune's perspective as far as Win32App applications go.
If this doesn't give you better results, it would be good to share your deployment settings on SCCM and on Intune as well as the entirety of the Invoke-AppDeployToolkit.ps1 script, or at the very least the section that covers this install.
Kindly,
Nik
i am aware if this and already tried, with no luck
C:\Users\USERNAMEHERE\AppData\Local\Programs\Kiro
it will be hardcoded, if i use %localappdata% it goes to system appdata.
my simple question is can i use psadt to execute the setup as user inside intune?
or i wil just need to write down simple ps1 and execute it as user? and avoid PSADT as it requires elevation on Intune...
What you're doing is something we consider an unsupported scenario. The Start-ADTProcessAsUser function is not there so you can drive every install from SYSTEM as the user; it's there to provide user-level functionality as part of a SYSTEM-based deployment.
Use Start-ADTProcess, reupload the app to Intune and scope it as user, not as system.
ok will try and reply back
Your posts are all over the place... Your initial screenshots show Invoke-AppDeployToolkit.exe, implying v4, yet these most recent ones show Deploy-Application.exe, implying v3.
We only support v4; v3 needs to die. Can you please check your setup and ensure you're working with the right package? In a 4.1.x deployment, you'll also need to set RequireAdmin to $false. This value is specified in the initial $adtSession hashtable at the start of the script.
Yes tried with the older template for testing, if i use latest template v4 do i need to setRequireAdmin to $false?.
You're installing the application in user context and the application will live in user app data. There is no need to be an administrator to accomplish this and so yes, you need to specify that the session does not require administrator.
See Open-ADTSession · PSAppDeployToolkit for more details.
Thank you everyone for your help, i am just wondering since last 3 years we used older template and ran it as system by using execute-processasuser and worked fine on intune, since last couple of months it stopped working on intune i mean facing above issue...just curious if anyone explain me technically what changed
Worked with this option inside Invoke-AppDeployToolkit.ps1
AppScriptAuthor = 'RM'
RequireAdmin = $false