WIN32
14 TopicsWe’re running into an Intune issue where a Win32 app with a dependency sits at "Download Pending"
Setup: Main App: Installs in User Context Dependency: Installs in System Context Dependency Detection: Hosts file modification detection script Direct file detection does NOT work either When the hosts file modification is present (detection is met), detection works, and everything installs fine manually The Problem: If detection passes (exit 0) → Everything installs fine. If detection fails (exit 1) → Intune never moves forward, just stays at "Download Pending" indefinitely. Happens with both file-based detection and script-based detection. Dependency app as well at parent app install fine via Intune on their own as well as manual testing. What We Need to Know: Does Intune get stuck in "Download Pending" instead of moving forward when dependency detection fails? Could the install context mismatch (dependency in SYSTEM, main app in USER) be causing this? Myth or fact? Does Intune break the install process if a dependency app is in system context and the parent app is in user context? Again, both apps work fine independent of each other. Thanks for any help!459Views2likes3CommentsDeploying Script as Win32 App
Hi all, I created a script that is supposed to check if a certain app was installed from a managed installer, then create a file in the C:\Temp folder if it was installed from a managed installer. I would deploy this as a Win32 app so that I could use the detection rules in the Win32 App deployment to check which device was installed via a managed installer. However, it doesn't seem to work. I created a transcript log as well to check if I would get an output from the variables, but it seems to only run the else block in the If Statement. We use a Business Premium license, so I don't access to Enterprise license capabilities like proactive remediation scripts. It is run using the System credentials, I've tested the script locally which works. Thank you, I've included some images of the script and transcript log. Script: Transcript Log Output:66Views1like1CommentCopy a OVPN file in Powershell from Intune
Sounds easy, my powershell script works fine if i run it on my machine, it copies the file into the %USERPROFILE%\OpenVPN\config folder. Its packaged up using the Intunewinapp program, but when i put it into intune it fails to install and copy the file over. Culd something like defender be stopping this process? The script works, the intune package works when launched from powershell, so what causes it to fail when i run it as a win32 app from intune? Anyone had this issue before? This is my script; $PSScriptRoot = Split-Path -Parent -Path $MyInvocation.MyCommand.Definition $Source = "$PSScriptRoot\Thornes.ovpn" $Destination = "$env:USERPROFILE\OpenVPN\config\" Copy-Item -Path $Source -Destination $Destination -Recurse -Force Thanks5.7KViews0likes17CommentsIntune Win32 apps with Intune (error 0x87D30000)
Hi, I am having issues deploying applications to some of my company's devices. In the Intune console I keep getting the error Unknown (0x87D30000). I am unable to find any solution. Something to note is that for most of my computers the applications installs just fine, but for others it fails with that error code. Has anyone seen this problem, and found a fix?Solved57KViews0likes3CommentsApplications not appearing in Company Portal
I am looking for some help on why my applications I set up in Intune are not appearing in our Company Portal. Background Info: I work for an MSP and we have a client that we are taking on with devices enrolled in Intune. We have a remote agent that we would like to push to one of our clients as a Win32 app and make it a required install for the devices. My Setup: I have run through the process of packaging the app as a .intunewin file, I don't believe there is any error here. I am familiar with the install/uninstall commands and have tested via a direct install on a VM to ensure they work. I have a group set up with both a test user, and the test VM which is enrolled in Intune. I assigned this group and required the install. I also made the application available to all users in the Company Portal. The Issue: I believe all of these settings and setup are correct; however, I am not seeing any install or anything show up in the Company Portal. I verified that the device is definitely Intune-enrolled from within Endpoint Manager, and I verified I was logged in as my test user to the Company Portal app. I also checked the online version and same issue there. Within Intune, if I go to Devices > 'Test VM' > Managed Apps I can see my application listed there, with a status of "Waiting for Install Status". After letting this cook overnight, nothing changed. I synced from the VM and from Endpoint Manager with no success. To eliminate some of the complexity, I set up another app, this time just Spotify from the Windows Store which is fairly cut and dry. Same issue- I made it available for all users, it says that status is "Available for Install" from within Endpoint Manager on my test VM, but I see no apps in the Company Portal on that device. Has anyone experienced this before? Can you see anything I may be missing? Thanks in advance for any help you provide.22KViews0likes5CommentsWin32 applications are not appearing in the company portal
Hello, I am new to Intune and am experiencing an issue with Win32 apps not appearing in the company portal application. I can upload line-of-business apps and these apps do appear the company portal application and I can install them successfully. However, I seem to be missing something when uploading Win32 apps. To clarify, the Win32 application's Assignment is set under "Available for all enrolled devices" to a group that contains the Intune user who is logged in to the company portal. Any ideas why I can upload LOB apps to the company portal but not Win32? Thanks Joe F912Views0likes0CommentsWindows 10 and 11 package icons resources
Hello, I have a problem with my Packaged Win32 application icons resources on Windows 10 and 11. The icons look great in the Start menu and Taskbar but when I add a desktop short to my app, the icon is displayed with a blue background color. Here is my scenario : 1. I generate the resources.pri file using native Visual Studio tool (see attached capture) 2. Then I build an APPX package to publish it on the Store using the command line : "C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86\makeappx.exe" pack /d "E:[compiled app folder]" /p e:\package.appx 3. I can sideload my app using the PS1 command Add-AppxPackage -Register [package app folder]\AppxManifest.xml When deployed (sideload or by Store) the icons look nice in the Start menu and taskbar (see captures). When I drag the Icon from the Start menu to the desktop to create a shortcut, then the icon is not correct. Note : I generated all the visual assets using VS for all sizes/scales, and light/dark variants, and unplated. The appmanifest looks like that : <uap:VisualElements DisplayName="PageFabric" Description="PageFabric" BackgroundColor="transparent" Square150x150Logo="Assets\Square150x150Logo.png" Square44x44Logo="Assets\Square44x44Logo.png"> <uap:DefaultTile Wide310x150Logo="Assets\Wide310x150Logo.png" Square310x310Logo="Assets\LargeTile.png" Square71x71Logo="Assets\SmallTile.png"> <uap:ShowNameOnTiles> <uap:ShowOn Tile="square150x150Logo" /> <uap:ShowOn Tile="wide310x150Logo" /> <uap:ShowOn Tile="square310x310Logo" /> </uap:ShowNameOnTiles> </uap:DefaultTile> Anybody has an idea of what I miss for the desktop shortcuts? Thank you!3.3KViews0likes3CommentsUnable to deploy PowerShell scripts to a newly co-managed device with Intune
Hi there, I am having issues deploying a PowerShell script through Intune to a device that has recently become co-managed with Configuration Manager. The CCM client was successfully installed and uses a CMG when off-network. The user logs into the device with a local admin account not a domain account. This https://learn.microsoft.com/en-us/mem/configmgr/comanage/workloads#client-apps states that the Client Apps workload in ConfigMgr doesn't need to be switched to Intune for PowerShell scripts when running on Windows 10 clients newer than 1903. But in case, I have moved the Client Apps workload to Pilot Intune with a device collection containing my device. Intune acknowledges this and displays the correct Intune Managed Workloads on the device overview screen. Even with this switched, I noticed the issue also impacts Win32 and LoB applications too. I cannot get any new applications to push down to the device anymore (since becoming co-managed) despite the workload supposedly being managed by Intune. The other workloads such as Device Configuration can be correctly controlled with Intune as tested with several configuration policies. Running the same script manually on the device worked as expected. Pushing the script to a separate device that isn't co-managed, only AADJ, also worked as expected. I've also tried targeting the script to a user security group instead of a device based group to no avail. I would appreciate any help on this. Best EthanSolved3.5KViews0likes2Comments