Use the custom actions based on scripts or batch files. Silent install builder supports windows batch files (bat, cmd), windows scripts (vbs, js), and Powershell (ps1). Include directories with dependency files.
I have a got about 4 to 5 users at the moment. Right now, I send the deployment links to them through my C# program. However, I have got a request from the users where they do not want to be clicking on the link, opening the browser and clicking next, they basically wanna a silent install.
I spent hours looking for a solution for this and never really found an answer. I was looking for a way to automatically and SILENTLY install LMI to my Pro account with a pre-set Access Code. LogMeIn Central provides this option under their Deploy tab, but it does NOT enter an Access Code. Since we are currently not using Active Directory or Windows passwords (Don't ask!) I required an Access Code that was the same for every PC. Here is how I did it:
I used Orca to automate our install: -silent-install-of-logmeinmsi/page__st__140 Post #148. The thread discusses using the automatic FREE install, but you can use it for the Pro install as well. Just don't edit the LICENSETYPE property.
LogMeIn provides a silent automatic install option via a Deploy .msi script. You can find it in LogMeIn Central under Deployment (If you have it).I had to edit the .msi file because doing a SILENT install of LMI does NOT allow you to input an Access Code for every PC.
I followed the guidlines from the above post and edited a few options with ORCA within the LogMeIn.msi. Under the Property Table I added a few options such as USERPASSWORD with the value of whatever I wanted the access code to be. I then used a .bat script to push it out to our workstations using Novell Zenworks.
It looks like your issue has not been resolved. I suggest you contact a LogMeIn Customer Care representative through our email or phone channels in order to resolve your issue. Please see our Contact Us page for ways to reach us.
Since then we've made use of One-To-Many. For the initial install we use the batch + exe option which autostart from a self exctract RAR file I made (this rar file also contains several of our smaller remote support programs that extract to desktop).
We were never able to fully install it silently (even speaking with LogMeIn support was no help). I came up with an alternative solution to that though - get the tech monkey to walk the client through the installation.
However, we're so far unable to install on MacOS or Windows completely silently (without elevation prompt, etc.). Is this possible? The installation guide implies that this should be possible -- using the offline installer -- but yet can't get it to work.
The credential prompt is presented when a standard user attempts to perform a task that requires a user's administrative access token. Administrators can also be required to provide their credentials by setting the User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode policy setting value to Prompt for credentials.
Yes, I'm aware of what UAC is, and on my own machine I can just say OK, and all is fine. But the point of the question is that we are trying to automate the builds, including the download/install of the compiler, and we don't have an opportunity on these build machines -- running headless in the Cloud -- to acknowledge a UAC prompt. We're also not able to disable UAC.
The Fortran install with VS integration is a complicated beast. We see endless posts on this forum where is has gone wrong in siome way and then needs repair/uninstall etc. To have non standard install directories outside UAC would seem a recipe for disaster. You would also need VS to be similarly installed as ifort puts stuff in the VS folder trees. If indeed that was all possible you would be in effect introducing a whole load of additional potential vulnerabilities anyway. To my mind you either disable UAC (a bad idea which you say can't do anyway) or live with the fact that a fully automated install is not possible. As a matter of interest can you launch the installers via a process that is already elevated?
Thank you. We can, and are, using that for Linux, but can't really use containers for Windows or MacOS. We can pre-install the compiler onto EC2 images to run our builds, but would prefer to be able to grab, and work with, the correct version at build time.
So far I'm having no luck at all with silent installation. I'm trying to use some of the commands in the installer, e.g. "--list-components", and it runs, pops up a separate console window, shows something, and then disappears. Why wouldn't it show its output in the same console window it was launched from?
Also, I've been unsuccessful trying to install into an "install-dir". This command line results in a failed install, and the log file complains about removing files in temp, which I don't know what that has to do with anything.
Welcome to the world of the academic researcher who needs to use lots of programs and the IT people even lock the bios update, so even the bios cannot be updated. Every change requires about 3 days of work.
The way larger businesses handle this is to use a product (BigFix is one I have encountered) that handles silent installation on the supported platforms. If it were possible for a product installer to bypass UAC prompts, that would make UAC rather worthless.
We need to get the compiler available to be run on the build machine. I'm happy to have to first install the compiler files on a user's machine, as long as they can be, then, copied into a build machine to run the builds.
Assuming you are referring to my last post. A build machine is designed to solve the so called language problem, ie Fred speaks German, Alice speaks French, but Alan speaks English French and German, so Alan communicates in English with outside world.
So yes I understand your basic problem, the real problem is the great variety of machines that are bought by a single company in even one year. So I feel for your pain, but your problem is somewhat unique, there are some really good people on this forum, excluding myself, who because I get bored coding and spending days alone, I tend to offer insight where it is not needed. But if the real experts here do not answer in about 30 minutes, your problem is likely not solvable by them. I assure you if they can solve the problem the solution is up in a few minutes, usually.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
I found an msi file within the exe file for rv install which allows silent install with /q . It seems the exe file just calls the msi file within it. So thanks for the input but the rv msi installer has the silent install flag.
The MSI seems to give an error when trying to deploy it as a Line-of-Business package in Endpoint Manager (Intune). It shows as the file not having an App ID. Has anyone else experienced this issue? Is there a fix for this?
Trying to perform a silent install for DWG trueview 2022. The original parameters "setup.exe /q /i /w /language en-us CREATE_DESKTOP_SHORTCUT=NO .\setup.xml" i've seen floating around do NOT seem to work for this. Does anyone have any insight into this or unable to get the 2022 version to specifically accept the EULA and silently install ?
One of those was the old command line arguments I used to install TrueView 2020, but that did not work either. One thing I did notice is that TrueView 2020 has a setup.ini file, whereas TrueView 2022 did not have this file, instead there is a setup.exe.config file and a setup.xml file. I quickly looked through those and didn't see anywhere to disable the EULA prompt.
That did the trick!
I can't believe I didn't try that, seems like I only tried with '/' instead of '-'. Considering this is a syntax change from previous versions which required a '/q' you would think AutoDesk would have noted this somewhere.
To AutoDesk: Please release documentation for commandline installation when you release a new version of software. I believe the 2021 version has the same issue and I couldn't find anything on that either.
That does work but then you also have to manually install all dependencies as well (Visual C, Direct X, etc.). @ramsierj 's solution of using '-q' will probably work better, as the dependencies will automatically install.
I haven't had a chance to test this portion yet but @rampini has given the name of an XML file that can be edited to provide additional parameters to the TrueView MSI. I found that file in the \\x64\dwgviewr and the file is named 'pkg.dwgviewr.xml'
Setup.exe -q does not work if you try to install it via SCCM (or now MS Endpointpoint Configuration Manager) because its using the SYSTEM user as installer. You can try it running with "psexec -s -i cmd.exe" and then try to run setup.exe, it will quit without any message and without any log (or i did not find it in the %temp% folder)
What would the full command be for silently installing DWG Viewer 2022 without data collection? I've gotten as far as extracting the downloadable .exe and identifying the .xml file (pkg.dwgviewr.xml) mentioned above.
Wanted to come back and set the record straight. I did finally get it to work. I posted some questions on reddit and everyone there said it was working. For me the installer would throw an error and tell me to retry. So after all the responses saying it worked were posted to reddit I downloaded the installer again.
Given the number of posts I have seen having issues with the autodesk installers I would hope this might influence them to look a bit closer at what people are experiencing and try to adjust accordingly.
c80f0f1006