Hi Jordan, It wasn't clear from your response whether you have applied the hotfix - so could you confirm if you have? If it doesn't resolve the issue, then we recommend contacting our support team. They should be able to work with you to try and reproduce and troubleshoot the problem. Since each installation package is different we would need to test with the one with which you are encountering the problem. Regards, Ajay ... View more

Hi Jørn, Thanks for reporting this problem. It turns out that an issue with the same symptoms was recently reported and fixed. We have a KB article with a hotfix download for AdminStudio 2016 SP1. Please find the link here: https://flexeracommunity.force.com/customer/articles/en_US/ISSUE/Repackaged-Application-Creates-a-Blank-Shortcut Let me know if it resolves this issue for you. Regards, Ajay ... View more

Hi, Thanks for reporting this problem. It turns out that an issue with the same symptoms was recently reported and fixed. We have a KB article with a hotfix download for AdminStudio 2016 SP1. Please find the link here: https://flexeracommunity.force.com/customer/articles/en_US/ISSUE/Repackaged-Application-Creates-a-Blank-Shortcut Let me know if it resolves this issue for you. Regards, Ajay ... View more

Hi Jordan, Thanks for reporting this problem. It turns out that an issue with the same symptoms was recently reported and fixed. We have a KB article with a hotfix download for AdminStudio 2016 SP1. Please find the link here: https://flexeracommunity.force.com/customer/articles/en_US/ISSUE/Repackaged-Application-Creates-a-Blank-Shortcut Let me know if it resolves this issue for you. Regards, Ajay ... View more

Thanks for going through with the detailed testing! It is an interesting suggestion to use the target OS as another variable in trying to determine the run-time value of ProgramFilesFolder. We will take this into consideration. You had mentioned that the following: "The odd thing is that, when using VFS mapping in IS, the Program Files captures correctly as ProgramFilesX86 .... even WITHOUT targeting x64 OS (ie. targeting is set to all OS)" This actually makes sense because we can easily infer that ProgramFilesFolder maps to ProgramFilesX86 because ProgramFilesFolder is always the 32-bit program files folder. The only issue is whether the run-time path of it is 'Program Files' or 'Program Files (x86)'. You should be able to use the option to put all files in the VFS to address this issue and also to be consistent with the latest Microsoft App-V recommendations. Thanks! Ajay ... View more

Hi CsabaK, As you noticed, the App-V conversion is mapping ProgramFilesFolder to the run-time value of 'C:\Program Files' instead of the desired 'C:\Program Files (x86).' The thing is that if you were targeting 32-bit machines, then 'C:\Program Files' actually would be the correct value. This is why this is a bit tricky. The simplest solution is to use the new option in IS 2015 called 'Map all files into the virtual file system (VFS)'. This will map all of the package files into the VFS section of the internal file system. This is the best practice starting with the latest version of the Sequencer which no longer asks for the primary virtual application installation directory. This option can be accessed by selecting the 'File Mapping' link in the 'Files' assistant page of 'Microsoft App-V' assistant. Could you try this option to see if it will address this issue? Thanks! Ajay ... View more

Hi, From your post it seems that you want to have a dedicated build machine for building InstallShield projects (ISM) into Windows Installer and App-V packages. And I believe you have AdminStudio 10 which includes IS 2011. It is possible to install AdminStudio on your dedicated build machine to do the automated build you are looking for, but I believe this may require a license of AdminStudio for the dedicated build machine and another license for your development machine. You should contact your sales representative to get additional clarification on this. Regards, Ajay ... View more

Hi Centrino, Actually, there is a method to set the default App-V runtime drive letter in AdminStudio to support the scenario where you want to use something other than Q: drive. If you are using Automated Application Converter (AAC) to do your App-V conversions, then you can specify the runtime drive letter in Tools - Options - Runtime Drive. Alternatively, you can specify a global value for this in the settings.xml file. This file is located in two places: Repackager\Support\0409 folder InstallShield\2012\Support\0409 Towards the bottom of settings.xml you will see the following XML section: /Virtualization/Properties. You need to add an XML element with name Property. It should contain an attribute with the name 'Name' and value 'AppVRuntimeDrive' and also another attribute called 'Value' with a value of 'B:' to use the B: drive as the new default runtime drive letter. Example: Make this change in both copies of settings.xml, and then the next conversion to an App-V package using AAC, Repackager, or InstallShield Editor will use the new default runtime drive letter. I also wanted to address your second point regarding custom actions. AdminStudio can convert MSI packages to App-V packages directly or by repackaging the MSI and then converting it. A direct conversion is fast and does not require installing the MSI package. However, it is not always possible to determine what certain types of custom actions will do during an actual installation by directly analyzing the MSI package. The second option is to repackage and convert the MSI. This can be done with Repackager or AAC. The advantage of using AAC is that it can spin up virtual machines to do the repackaging and conversion in an automated manner. I hope this helps! Regards, Ajay ... View more

Hello, I am not sure why the registry information in your MSI file is not being transferred into the App-V package (SFT) file. I am familiar with the CustomAction table problem that you outlined, and I believe it should be fixed in our most recent release (AS 9.5). Could you tell me what version of AdminStudio you are using? Is the registry problem just present with a single MSI or with all MSIs that you have tried? Thanks, Ajay ... View more

Hopefully saving before building will be a workaround to the exclusion being ignored behavior that you are seeing. As far as whether this always happens or sometimes happens, I am not sure off-hand. Please update after you have tried saving first. ... View more

Hi, It sounds like you went through the repackaging process with AS 9.5 SP3 bits, and opened the Repackager project, excluded some items, and then tried to build the ISM and MSI. And the excluded items were not really excluded. Could you make sure to hit the Save button in Repackager IDE after making your exclusions and before trying to build the ISM and MSI? Due to a bug in Repackager IDE, sometimes it does not use the newly modified settings when you build if you didn't save first. Please let me know if this helps. ... View more

Hi Mike, I wanted to let you know that I reproduced the missing directory portion of the issue you reported with the Octave package. Thanks for the detailed notes about which directories were not captured and what package you used. I reported an issue with number IOA-000058398 for this behavior. It looks like the CreateFolder entries were created in the ISM for the missing directories, but they were somehow associated with components installing to a different folder with the same name as the correct folder. Regards, Ajay ... View more

Hi Mike, Thanks for bringing this to our attention. I was able to reproduce the problem with your suggested setup (XnView), and then was also able to reproduce the problem with a new simple MSI package that I created with InstallShield. It looks like the capture phase of Repackager worked correctly, but the build phase is not handling brackets correctly. I reported an issue for this behavior with number #IOA-000058270. Thanks, -Ajay ... View more

It looks like you were going for mutually exclusive conditions on the DoAction and EndDialog control events. However, your conditions are not mutually exclusive. Incorrect: NOT (SELECTED_DISK="C:\") OR NOT (SELECTED_DISK="D:\") Correct: NOT (SELECTED_DISK="C:\" OR SELECTED_DISK="D:\") Also Correct: SELECTED_DISK<>"C:\" AND SELECTED_DISK<>"D:\" Perhaps changing the condition to be mutually exclusive will fix the problem? ... View more

Hi, You should add the File Type information to the component containing the associated executable file. Also, the exe file should be the keyfile (keypath) of the component. Then you can remove it from the Registry table or Registry view. Reference: File Type Settings http://helpnet.flexerasoftware.com/robo/projects/installshield16helplib/ComponentFileTypes.htm ... View more