I'm dealing with a new critical business software that doesn't seem to install properly. It's an executable file rather than an MSI, and it asks for User Account Control (UAC) permission, which is fine. However, it's sometimes placing files in a domain admin's AppData folder instead of the local user's AppData folder. This causes issues when launching the program, as it can't find the necessary config.xml and other files in the right location. I've attempted deploying it manually via Intune and NinjaOne but have hit a wall, so now I'm trying to install it directly, yet I'm having issues with that as well. I think some testing on IT's devices might have messed up something in the registry or configurations because the installation never puts the needed files in the user folder. I even tried using PsExec to force the installation under the user context, but it keeps asking for a password as if the user is a domain admin. Copying the files over from the appdata folders doesn't work either since it still errors out when starting the software. I'm lost here!
4 Answers
For a more hands-on approach, have you considered launching the installer with PowerShell? You could create a Win32 Intunewin file that bundles the executable along with the necessary XML files. That way, you’re not relying solely on the installer. If you're using NinjaOne, their support could be very useful, especially for this kind of issue.
If it’s crucial for the installation to run under a user context but still needs admin permission, you might want to check out a workaround. There's a service called ServiceUI that allows Intune to deploy apps that require user interaction, but keep in mind it implies that users will have to provide input during installation. Just be cautious—this method isn't the most secure.
You might want to reach out to the vendor about these installation issues. It sounds like their installer is fundamentally broken. Also, check whether the admin account has local admin rights; that might be why it defaults to a user-level install. If you try the install with a non-admin account, does it still try to install as a user? It could be that the installation fails when it doesn't have proper permissions to access certain directories. Without being able to see the installer details, it's tough to diagnose the exact issue.
It sounds like you’re hitting a classic software installation problem. Several factors could be at play here, particularly around permissions. If the installer is inconsistent and works for some users but not others, you might want to test with a clean local user who has admin rights. If that works, it means there could be domain policies interfering. Also, double-check if the installer is hardcoded to pull paths from places like the registry instead of using %APPDATA%. Fixing that could be on the vendor, but you’ll need examples to show them what’s not working.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures