Started 3 weeks, 4 days ago (2009-11-11 16:17:00)
by HennoKeers
That's no problem.
reg,
Henno
Started 2 weeks, 5 days ago (2009-11-18 09:10:00)
by sandeep.madhu14's Avatar
try the following command:
msiexec /i "path to your msi" /qn
it will silently withour
user interaction...
If it helps let me know...
Thanks
Madhu
Started 3 weeks ago (2009-11-16 12:39:00)
by Ajay Ladsaria
AdminStudio
Professional edition does not include AdminStudio Web/Enterprise Server. For Professional edition you will want to set-up a SQL Server. Depending on how many users you have you can decide to set it up on a different machine or on the same machine as where AS is installed. Most likely you will want to have the Software Repository on a shared UNC path (could be on a different machine...
Started 3 weeks, 6 days ago (2009-11-09 18:14:00)
by Ajay Ladsaria
Hi Alain,
AdminStudio would be the best Flexera product to meet the requirements you listed:
1. Use Repackager to repackage existing installations into MSI packages.
2. Use ConflictSolver/ApplicationManager to identify any conflicts between your MSI packages.
If you end up going down the SCCM route, then you can use the AdminStudio
Configuration Manager Web Console to publish MSI...
Started 1 month ago (2009-11-04 18:51:00)
by Cary R
Hi there,
This is a really common scenario, usually triggered by per-user data that isn't present under HKCU after a different user logs in to use the application.
The thing to do in this case is:
1. Look at the Application
Event viewer. This will give you a message from MsiInstaller that says a component is missing. (sometimes it will tell you the file)
2. find the ...
Started 1 month ago (2009-11-03 14:03:00)
by Cary R
Hi Atlas,
AdminStudio plans to include 64 bit support in an upcoming release; if youre interested in testing this functionality you can email AdminStudio@Flexerasoftware.com
Started 1 month, 1 week ago (2009-10-29 14:18:00)
by Cary R
Generally, with what's called "Pure InstallScript Projects", you have a limited ability to account for whatever
bad behavior the original setup developer authored into it. (Less so with 'InstallScript MSI') So the case may be that repackaging is the way to go.
What I would typically recommend in a case like this is check to see if possibly the setup.exe file contains an MSI file. If it ...