I've developed a VSTO addin with VS2012 signed by a DigiCert certificate. I need to deploy it to all the Enterprise users so the installer shouldn't prompt the user because it will fail since all the installation process is silent.
I'm not able to do it since it always ask the user if it should or shouldn't install. If I set VSTOInstaller /S it doesn't install 'silently'.
Is there any way to do this?
Thanks on advanced.
I found the answer. To solve this you have to install the public key certificate in your installer:
certutil -addstore TRUSTEDPUBLISHER "yourcertificate.cer"
Then, you just use VSTOInstaller:
VSTOInstaller.exe /I "youraddin.vsto" /S
That's all folks!
Yes you can.
Just Uncheck the ClickOnce manifest CheckBox and Check the signing the assembly using any .snk file.
You will need to create installer project and the rebuild the installer project will provide you the .msi and .exe file you can execute the following command on command prompt(Administator).
Though rebuilding of installer project will automatically check the ClickOnce checkBox but you can ignore that.
Below is the link for creating Installer project for AddIn.
https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2010/ff937654(v=msdn.10)
Looks like you need to GPO for deploying the software (using MSI installers).
How to use Group Policy to remotely install software in Windows Server 2008 and in Windows Server 2003
How to use Windows Installer and Group Policy to deploy the VPModule.msi in an Active Directory domain
Installing Software Using GPO
Also see the Deploying an Office Solution section in MSDN.
Related
I'm using an Administrator account. I can install an MSI for the current user only, but when I try to uninstall it, I get the error message
You do not have sufficient privileges to complete this installation for all users of the machine. Log on as administrator and then retry this installation.
The three ways I tried to uninstall the app:
From both a regular powershell and a run-as-admin powershell:
msiexec /x MyFile.msi
Just run ./MyFile.msi and choose the Remove option
Run appwiz.cpl and choose to uninstall MyFile.
I suspect all three paths are to the same function that's failing. How can I delete this app?
If it's relevant, MyFile.msi was built with Wix.
The Wix file from which the MSI was generated was flawed.
Fixed by using Orca to edit the MSI, and adding AND NOT REMOVE to the SetALLUSERS and SetMSIINSTALLPERUSER tasks for the InstallExecuteSequence and InstallUISequence things.
Thanks for offering an answer though, Vivek.
I'm using Advanced Installer to try to create an installation package (single EXE setup file) for an MS Project VSTO add-in. I need the installation Type to be Per Machine but when I chose this option and run the setup.exe file, the Add-in will not load for any of the user's on the target machine. The only way I can get it to load is if I change the installation type to Per User, which I don't want.
I'm fairly certain the problem is related to the registry, because the setup.exe is not adding the proper registry keys under HKEY_LOCAL_MACHINE to load the add-in, even though I have it set up to do so:
What am I doing wrong?
There are other things that needs to be done except windows registry keys. For example, you need to specify whether you want to support per-user or per-computer installations.
The Deploy an Office solution by using Windows Installer article describes all the necessary steps for creating per-use and per-machine Office add-in installers. Make sure that you did everything in your installation package.
I am installing my application in a fully offline environment. Our machines will be completely incapable of connecting to the internet during production scenarios.
I am writing a WiX Burn custom bootstrapper, and part of the reason was to install a Microsoft root certificate required for .NET 4.7.2 to install properly on Windows versions earlier than 8.1. My original plan was to use the .NET certificate namespace to do this, but aside from the warning that popped up saying not to, I realized that Burn runs at the current user's elevation level, which means that it would likely fail to install the certificate without acquiring elevated privileges first.
According to a Microsoft document regarding installing certificates for Visual Studio, the preferred way of doing this is to bundle a copy of of certmgr.exe with your program and call it to add the certificate to the root store.
Is it best practice or even possible at all to do this using an ExePackage element? As in, setting the element to call certmgr, set InstallCommand to /add MicRooCerAut2011_2011_03_22.cer /s /r localMachine root, PerMachine to True and let it rip? Or does ExePackage have some kind of special behavior?
I'm new to Wix and am wondering if there's a way to install files to several machines that are all on the same network from a single MSI?
The installer would prompt the user for all the machine names and then the installer would install on each of the machines.
Microsoft Active directory's Group policy is used exactly for this. For tutorial see for example this link.
i have a problem with the installation of a Firebreath plugin on Windows XP machine.
I'm using Visual Studio 2008 setup project to place generated plugin dll in program folder to get the plugin work but when i run the installer the plugin is usable only by the user who install the plugin and if i log in the machine with another user with limited privileges Firefox cannot see the plugin.
What i'm doing wrong with this process?
Should i use Wix installer instead of Visual studio 2008 setup project to get the plugin work for all users in the machine ?
What is the correct "Firebreath" way to install a plugin and to make it visible to all users in the machine?
Thank for your time!
Francesco.
1) Nothing. This is as designed; FireBreath installs per-user by default, always has. This is a feature, since it means you don't have to have administrator privileges to install.
2) Not by default, no.
3) Uncomment the following line in your PluginConfig.cmake file and rerun the prep script:
# If you want to register per-machine on Windows, uncomment this line
set (FB_ATLREG_MACHINEWIDE 1)