MSITech wrote: ******* Please use only the offline method ******** The online method isn't 100% reliable. With offline, we have record that we performed the deactivation. ---------------------------------------------------- AdminStudio Offline Deactivation: ----------------------------------------------------- 1) Reinstall the software on the previous machine (if it has been uninstalled) 2) Open up a Command Prompt and CD to C:\Program Files\AdminStudio\9.5\Common 3) Type "TPSconfig /return /no_internet" which should generate a request code. 4) E-mail the request code to me (support@flexerasoftware.com) within a notepad attachment and I'll send you a Response code which will complete the de-activation. Please note that with AdminStudio 9.5 deactivating with the TPSconfig will deactivate both InstallShield and AdminStudio. Once this is done you should be able to successfully activate the product on the new machine. ******* DO NOT USE THE ONLINE DEACTIVATION METHOD ******* AdminStudio Online Deactivation: ----------------------------------------------------- 1) Reinstall the software on the previous machine (if it has been uninstalled) 2) Open up a Command Prompt and CD to C:\Program Files\AdminStudio\9.5\Common 3) Type "TPSconfig /return" NOTE: Please allow ports 80, 443 and 8443 access to our servers. command: c:\program files\adminStudio\9.5\Common>tpsconfig /return Hi, I have tried the above steps but I cannot use my license on my upgraded box. Can you help me release the key ? Thanks in advance, Shekhar ... View more

Evan Border wrote: I don't think there is any possible way to do what you're looking to do...it sounds to me like you have source code (.wsx files) but do not have the compiled output. There isn't any tool anywhere that can virtualize that. If you have the raw source files in addition to the source code (.wsx files), then you could use WIX to build the .MSI's. And you could then use AdminStudio to virtualize the .MSI's. But AdminStudio does not have any way of using .wsx files. If I'm understanding it properly, this situation is like the following analogy: It would be like making a film and wanting to convert it to Blu-ray, except you've lost the film and now only have the screenplay. Thanks, Evan. Do you think we can change those XML manifest files to some installscript files and then use then as an input to Admin Studio for virtualization? ... View more

Evan Border wrote: .WSX files are WIX (Windows Installer XML) project files. Do you have the .MSI's that build from them? If so then yes, AdminStudio can convert those .MSI's into virtual packages. If you use AdminStudio 2013, you can convert from .MSI to any of the following virtual formats: Microsoft App-V 4.6 or 5 Citrix XenApp Symantec SWV (formerly known as Altiris SVS) VMware ThinApp Also: if you have the .MSI's that were built from the .WSX project files, you can convert them into InstallShield project files (.ism files) by performing the following steps: 1. Launch the InstallShield Editor 2. Go to File menu > Open 3. On the Open dialog, change the Open As: drop down list from Auto to Wizard 4. Browse to your .MSI that you want to convert to .ISM This displays the Open MSI/MSM Wizard 5. At the Welcome dialog, choose Convert MSI/MSM to an InstallShield Project 6. At the File Locations dialog, choose the desired name and location for storing your project and source files and click Finish. I donot have the MSI with me. Can you suggest how to proceed with the WXS files ? I need to get these files virtualized. BTW, it it possible to get these files converted to any other format which can be used to virtualize them ? Thanks ... View more

Hello, I have some .WXS file to virtualize. Is there any way where Admin Studio helps on get these files virtualized ? ... View more