Catalin wrote: ↑Mon Dec 12, 2022 3:57 pm
Hello,
Most likely, what you have used there is the
"EXE to MSI" converter.
What this does is it adds your EXE setup as a feature-based prerequisite in your MSI project. Basically, this MSI is a bootstrapper over your EXE.
With that being said, behind the scenes, the installation of your EXE is still performed.
So i tried to unpack the setup.exe, to take all files in a folder and to build from scratch the MSI with Advanced Installer. It was done quickly, but when I launch the program, no windows is opening, and the process is not in task manager.
This aproach, although it seems correct, actually isn't.
Beside the files, there are still many things to consider from the setup package created with NSIS, such as registry entries, custom actions, etc.
If you are not the developer of that setup package, it's almost impossible to recreate that manually.
What you can do here, however, is use our Repackager feature, available in the Architect suite. Below you can find some articles which should be helpful:
1. Repackaging an installation
2. Repackaging using Virtual Machines
3. Repackaging an installation on a Hyper-V virtual machine
Best regards,
Catalin
Ok I'm back with informations, and most of all, issues... I've done this thing :
Upgrade ESXi (this should be done and all prereqs from AI or VMWARE are now all full set)
Upgrade Vsphere (this should be done and all prereqs from AI or VMWARE are now all full set)
Installation of VMWARE Workstation Pro 17 (because it did not work in the vcenter when the VM is at the root or under another folder, i got the problem "shared folder" and try your FAQ but nothing worked, and in the combobox i don't see all my vm..)
Build a fresh install of W10x64 uptodate
Install / Upgrade VMWARE Tools
Ok now I've a clean VM and a clean environment, I'm following the tutorial you gave me for repackaging with VMWARE.
So I launch the repackage, i'm choosing my setup.exe files, i'm adding additional params to commandline.
Then I'm editing VM and feeding it with credentials and do all stuff in tutorial, then i launch the process :
- first issue : the iso is not mounted automatically for osprovision in local, however it's ok in the vcenter
:> i mounted it manually in the VM and click retry
-second issue :
process tries to install osprovision tool and throw a "AI Tools can be installed only in a virtual machine"
:> no solution found here except in the forum a guy who said "it's under investigation in 2017"
So, in the vcenter I can mount the tools and launch the process but I cannot solve the problem of "shared folders" and I don't see all my VM, only 3 or 4 directories instead of 40 (so i cannot choose some of vm), finally it doesn't work.
In Local, with all frsh install workstation,w10,tools, same I cannot launch the entire process which is blocked at AI tools installation.
I'm someway stuck... any ideas or link to solutions ? (of course all my AI and OS and drivers are uptodate). Thanks