Installing outlook add-in every time user logs off - outlook

I have an Outlook add-in that is working fine for every client. They get the installation (ClickOnce) from the web, install it and run it without any problem. However, I just got this client that it's complaining about seeing that "Microsoft Office Customization Installer" window (and of course, downloading and installing the add-in again) every time he logs off and logs back (he can close outlook and re-open it without any issues). BTW, He is using a Terminal Services environment.
Does anyone have any idea why this is happening and/or how to solve it?

It is probably a policy or login script that removes any installed applications. You'd best talk to his system administrator.

Related

Visual Studio 2017 Installer is "Unable to download installation files"

I've just finished talking to the "Microsoft Support Chat" and he told me to post this here (i can't post it on the developercommunity forums because i need to click a button in the installer which isn't there at that stage).
When I'm trying to run the VS Enterprise 2017 installer (or any other edition) the installer cancels with the error message: "Unable to download installation files. Check your internet connection and try again."
What I tried so far:
Running as Administrator
Downloading the installer with a different browser
Using the --layout option to download files first (same error message, no files downloaded)
Installing the certificates
Using the --update option before running the installer regularly
Running the Windows 10 Windows Update Troubleshooter (couldn't identify the problem)
Disabling Bitdefender Antivirus
Multiple Reboots/Re-Downloads
One more thing that might be helpful is that quite a while back when i was installing "Cyber Ghost VPN" on the same machine i had trouble connecting using that application because a windows service that should've been active wasn't running.
Also I would've included the Logs from running the vscollect tool but i can't seem to figure out how to attach a file here. Do i have to upload it somewhere else and include the link or is there a way i can just attach the file here?
It could be a certificate issue, maybe your time and region are not set correctly, so the certificate is in a different date than the server. I followed this three spets a couple weeks ago and it worked.
Install the certificates, usually in "certificates" folder,(inside Layout folder).
Right-click each one to install it with administrator rigths.
3.Run the installation file.

Visual Studio 2013 Outlook plugin, installing on a restricted citrix enviroment

I have been struggling to figure this out.
We have made a Outlook Add-In in Visual Studio 2013.
I can install this using the .vsto that they provide without a problem on a windows machine.
Now I try the same thing, placing the .vsto on the citrix server, installing this works fine, although it does a call to the internet which isn't allowed, so I had to work around that (anybody know why it calls to the internet? and what?).
Than I got it installed at the server, go to the thin clients, its right there, the only thing I have to do is activate it.
The second I activate it, it runs an executable, which obviously is not allowed, and I cannot activate it on the client.
You need to create an MSI installer for the add-in. See Deploying an Office Solution by Using Windows Installer for more information.

Visual Studio 2013 Community Edition - "Your license has expired." even though it's a release (Update 4)

This is weird. I installed Visual Studio 2013 Community Edition on two computers, with the same installer (and the installation started/finished around the same time) and there seems to be a problem with my licensing; one is activated and the other is... Locked, with no option to refresh or update.
After going through the installer and logging in, my first installation on my Windows 7 laptop went without any problem; it can run properly.
But when I finished installation on my Windows 8 laptop and logged in, I was presented with the following message:
Your license has expired.
Reason: Pre-release software.
[Insert image of the error screen]
I've tried reinstalling, and there seems to be no difference.Neither does logging out and back in (or logging out, restarting the computer then log back in) do any help in refreshing the license.
As for this question, it isn't asking me to upgrade any trial licenses; just a "you can't use this anymore message" and no option to refresh or "upgrade".
Note: Please give me a hot moment to gather the screenshots from my computers.
I had a similar issue. The way I solved it was to go to Control panel and try to uninstall it. When the dialog box appeared I pressed the Update (or Fix) button. After that, I rebooted and logged in and it worked.
My VS2013 was a trial version though so my license was expired but I was not able to pass the screen of the screenshot you posted.
Hope it works!

Cannot install Nuget Package Manager

I am using VS2010 on Windows 7 (64 bits). When trying to install "Nuget Package Manager" from VS's "Extension Manager" it fails. The download works, but then I am stuck at the installing progress bar. When looking in Windows' task manager yo can see that the installer keeps on starting up new instances of the "vsixinstaller.exe" process. It goes on and on until the computer ultimately crashes.
The same behaviour occurrs when starting the file "NuGet.Tools.vsix" directly.
I have searched the net for the solution but haven't been able to find anything useful.
I received the same behavior today so I decided to open Process Monitor to investigate.
Guess what...Process Monitor gives the same behavior. Then the light bulb went off... :)
Answer: I previously had administrator privileges on my laptop, but those were removed at the beginning of the new year. For some reason, when these programs use credentials that are not in the administrator group, they recursively call themselves instead of failing, timing out or reporting access denied, etc.
Please ensure that your attempting to update after launching VS as an Administrator.
I will be providing this feedback to the nuget support thread as well.
Fixed by installing Nuget with admin right under SP1.
I found a solution at NuGet Docs Known Issues. Installing the hotfix they recommend even though I have SP1. It includes KB2581019.

VSTO solution using ClickOnce via IIS 6 fails to download manifest

I have an Office solution for Word 2007 that I publish using ClickOnce. When I publish it to a local directory, I can install the .vsto file and everything works. When I publish it to our web server, though, I cannot install it. The error I get is:
Downloading file:///C:/DOCUME~1/Dave/LOCALS~1/Temp/Application Files/MyApp_1_0_0_0/MyApp.dll.manifest did not succeed.
I have been Googling for most of the day, and have already tried the following:
Added the correct MIME types to IIS 6 config (as described here and here on MSDN).
Created a test certificate, imported it into my trusted root authorities, and signed the app with it.
Published the solution to a network share and tried installing from there. It worked fine.
Tried accessing the MyApp.dll.manifest file directly from the web URL. The browser is able to find the file just fine.
What am I missing? Thanks.
Make sure that Windows Installer 3.1 is installed on the end-users PC. If it's not, you may want to add it as a prerequisite to your application.
Also, you may want to check and see if the application is installed from the Windows Add/Remove Programs screen. If it is in the list, you may need to uninstall the application, first. I know, you're probably thinking 'But the application hasn't been installed yet.'
Quite a few application that are published via ClickOnce. ClickOnce works great most of the time, but every now and then I see users who run into hiccups similar to yours when they try to initially install the application. The best solution is to usually uninstall all prerequisites, reboot, manually re-install the prerequisites (not from the ClickOnce setup.exe file) and then launch the application.
Some of those steps may not be necessary but it tends to fix the problem nearly every single time.

Resources