Error installing repackaged MSI using Intune for education
Hi everyone,
Let me start of by saying that I have been employed as a software packager for the past 6 months, and I'm completely self taught with the help of the internet and being helped by a different software packager for 3 weeks. I know my knowledge is lacking and that I might do things unconventionally, but I'm really stuck this time and the internet has not helped me find a solution yet, hence why I'm posting this question here.
What I've done:
- I have repackaged a .exe installer for a piece of software into an .msi by using the AdminStudio 11 repackager.
- I captured the installation and built the .msi file.
- This .msi file installs fine when I run it from a local disk drive and does what I would expect it to do.
- I've uploaded the installer to the Intune environment and assigned the app to a group that contains my VM client.
- I waited until the software installed but got an error: "Can't find an installer package for this product <installer name>. Run the installation again with a valid version of this installer package {C77F2818-A3F8-4C08-8B3C-0FEB48F2EBA2}.msi"
A second error I got was: "Can't find the path C:\WINDOWS\system32\config\systemprofile\AppData\Local\mdm\{C77F2818-A3F8-4C08-8B3C-0FEB48F2EBA2}.msi. Check if you have access to this location and try again, or find the installation package {C77F2818-A3F8-4C08-8B3C-0FEB48F2EBA2}.msi in a folder, from which you can install the product.
I translated these error messages from Dutch, so the actual English error messages might be worded differently.
- I checked the location in the second error message and the folder does not exist
- I checked the hex code, and concluded that it is generated by Intune. It is not listed in the .msi I created and it changes based on different uploads in the intune environment.
- I looked online for a solution related to my issue, but I have not yet found anything that could help me.
My questions:
Does anyone have an idea where I need to look to find a solution, or an indication to set me on the right path?
Does anyone know what the Microsoft Intune environment does when it installs a .msi package on a client, and is there something I need to include in the .msi packages I make?
Does Microsoft Intune download the .msi package locally and then remove it for installation? This last part I have not been able to figure out, as installation happens somewhere within a 72 hour period after it has been assigned, and cannot be pushed in any way (if this is possible, I'd love to know how, because that will make testing so much easier).
Things I can't change:
I need to have a .msi package. Microsoft Intune for Education does not accept any other installer type.
I cannot use other repackaging software unless it is free to use.
Testing new packages/solutions can take up to 72 hours before it syncs to the client and starts installation.
My suspicions:
Based on the error codes, I suspect that the installer does not get downloaded to the client. The .msi expects a local install, but does not have one as it isn't actually downloaded.
Another option is that the temporary save location of the installer is not the C:\WINDOWS\system32\config\systemprofile\AppData\Local\mdm\ path, but something else.
I need to add a property or a custom action to ensure that the .msi gets installed properly when using Microsoft Intune.
I have tried to include as much relevant information as I can. If you need more information or if I posted in the wrong place, please let me know and I will (try) to fix this. Lastly, thank you people in advance for helping me on this issue, and thanks in general for all the solutions that have been posted in this site. It has been a valuable source of information for me so far!
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
anonymous_9363
6 years ago
You can see that InTune (about which I know nothing) is looking for the MSI in a folder beneath the System user's profile. If the installation is being run under the currently logged-in user's credentials, that account will not have access to the System user's profile, hence the error.
