installing a exe but not working

[AB21805]

Hi all,

I am trying to install an emulator which is an exe with a license key but when installing it fails. 

I have been told that the install command is: 

But this doesnt seem to work via intune. 

I have packaged the .intunewin file pointing to the exe but no luck any ideas? 

[#2]

I would just create a install.cmd in c:\install and copy the installation files in it. Command-line in it would be "installer.exe ISX_IED="license code" LOCALE=xxxx" Package it using the intunewinapp util specifying c:\install as location and install.cmd as install command and also in the installation parameters. You can also put a Uninstall.cmd in c:\install too or specify the command-line in the uninstall parameters in Intune.

[#3]

Hi Harm, when creating the intunewin file is the setup file the install.cmd or the exe?

[#4]

install.cmd

[#5]

Thank you just testing I will let you know how I get on tomorrow! Just out of interest why a CMD rather than a powershell file? for install and uninstall

[#6]

It's a habit I guess, you can use cmd or ps1 files to start the installation. powershell.exe -executionpolicy bypass -file .\install.ps1 will also work. (When creating a .intunewin package just specify install.ps1 in that case)

[#7]

Ohhh fair! Also when running the install runs on test device locally unless I move the install folder with all files inside into my onedrive location on the device is there a reason for that?

[#8]

No, you can specify any folder you want from any location when creating .intunewin file. If I understand your question correctly 😉

[#9]

I understand that but when trying to run the install.cmd within the install folder in my onedrive this just fails the cmd window just shuts down but when I move the install folder to another location which isnt my onedrive this works perfectly. wonder if there is some sort of settings that block cmd files running in the onedrive location

[#10]

Ah, ok.. Don't know the security measures of your computer, it could be... But test run it from locally and save/keep it in OneDrive.. Or start using Github for storing and versioning of your installations 😉

[#11]

Hi Harm, I have just checked endpoint and seem to get this error
(0x80070001) what does this mean? How do I investigate it

[#12]

Could you post the contents of your installation folder in a screenshot, your install script and the settings of your App in Intune?

[#13]

@Harm_Veenstra

The install.cmd contains : "ClassWiz Emulator Subscription for fx-83GT X_85GT X Ver.2.01_b.exe" /l"1033" /s /v" /qn ISX_EID=My license"

@Harm_Veenstra 

[#14]

normally that error codes means: invalid function. But it would help indeed if you post the content of the install folder and the install.cmd.

Also I would advice to do some troubleshooting of the install itself like I am explaining in this blog
https://call4cloud.nl/2021/05/imecache-attack-of-the-cleaner/

So you could get back some errors what could be causing it

[#15]

Here are the screenshots @Harm_Veenstra @Rudy_Ooms_MVP 

in the package part for the win32 set up i used install.cmd

[#16]

What happens when you use psexec to elevate yourself to system and try to execute that same install command from that cal emulator\install folder

[#17]

What do you mean? how would that look?

When I tested locally without using intune this works. So the command itself locally works

[#18]

Testing an installation with system could be just a little bit different then using a normal admin account. And because intune installs that software as system..... 🙂

[#19]

@AB21805 

Sometimes I use something like this as command-line:

%~dp0\"ClassWiz Emulator Subscription for fx-83GT X_85GT X Ver.2.01_b.exe" /l"1033" /s /v" /qn ISX_EID=My license"

 Or this as install command-line:

.\"ClassWiz Emulator Subscription for fx-83GT X_85GT X Ver.2.01_b.exe" /l"1033" /s /v" /qn ISX_EID=My license" 

[#20]

@Rudy_Ooms_MVP 

You could try using Windows Sandbox (Add/Remove Features) in combination with Run-in-Sandbox (https://github.com/damienvanrobaeys/Run-in-Sandbox). You can right-click a .intunewin file and choose "Test intunewin in Sandbox". Makes testing a lot easier 😉