Visio 365 Installer Click To Run
Side-by-side Installation Scenarios with Visio/Project and Office 365 ProPlus Click-to-Run. For this specific scenario, the Office Deployment Tool uses Click-to-Run to do the installation, instead of using Windows Installer (MSI). But, Visio and Project are still activated by volume activation methods, such as Key Management Service (KMS) or Multiple Activation Key (MAK). Office Click-to-Run from Office 365 allows you to automate either a quick repair or an online full repair. OfficeClicktoRun.exe is the executable that will allow you to automate a repair in Office 2016. This executable needs to run with elevated permissions, and it resides in the following location.
Summary:
Office 2016 O365 uses click to run (C2R) deployment technology. It is not possible to have Office 2016 C2R installed on a computer that also has 2016 MSI products on it, like Visio and Project. Some customer want to be able to leverage an existing investment they have in 2016 MSI products by making them available via Citrix. With Citrix the MSI application are not actually installed on the client system.
Click To Run Activex
Office / SharePoint use protocol handers to open files since Visio and Project are not actually installed there is no handler present for them to use and the SharePoint web UI does nothing or gives an error when trying to open these file types from the SharePoint web UI. Details about the protocol handler format can be found here:
https://msdn.microsoft.com/en-us/library/office/Dn906146.aspx?f=255&MSPPError=-2147217396
The advantage of the protocol handers is that they do not require any browser add-ins so they work with all modern browsers.
Solution:
The 'right' solution would be to give users licenses to the O365 version of Visio and Project, your account manager can often make this financially equivalent.
If for some reason you must have the MSI version of Visio and Project available to some of your users you can use Azure RemoteApp or Citrix to provide access to the MSI applications with out actually having to install them on the users local computer.
https://www.remoteapp.windowsazure.com/Default.aspx
The solution presented in this blog post creates a custom protocol hander that can point to any executable you want. It basically routes the request from the web browser to whatever local exe can start the remote application.
**Warning, this blog post contains sample code, there are no warrantees, use at your own risk.
How to deploy and use this solution:
First download this zip file VisioHandler Visual Studio Solution
Unzip the file
Go to the VisioHandlerVisioHandlerbinDebug folder and copy the VisioHandler.exe and VisioHandler.exe.config file to a location on users hard disk, record this location.
I am assuming that the exe that connects to the remote application is under the users AppData folder, like C:UserswarrenAppData
The VisioHandler.exe needs to know where the exe that connects to the remote application is located, you can edit the VisioHandler.exe.config file and replace the value 'CitrixSelfServiceVisio2016.exe' with whatever subdirectory and exe under AppData where your exe that connects to the remote application lives.
Commandos what does promotion do civilization mean. You then need to build a registry file (.reg) to configure the protocol handler, here is a sample registry text:
**PATH_TO_HANDLER needs to be wherever you put the VisioHandler.exe
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOTms-visio]
@='Url:Visio Protocol'
'URL Protocol'='
'UseOriginalUrlEncoding'=dword:00000001
[HKEY_CLASSES_ROOTms-visioDefaultIcon]
@='C:UserswarrenAppDataRoamingCitrixSelfServiceVisio2016.exe,0'
[HKEY_CLASSES_ROOTms-visioshell]
[HKEY_CLASSES_ROOTms-visioshellopen]
[HKEY_CLASSES_ROOTms-visioshellopencommand]
@='C:PATH_TO_HANDLERVisioHandler.exe '%1'
Once you save the .reg file, just double click it to have the data put into the registry.
What about project?
Download this Visual Studio project ProjectHelper
Then follow the same steps as the Visio protocol handler listed above, except in the .reg file you need to use ms-project instead of ms-visio in all places that it is used.
I have been trying to install Microsoft Visio C2R using PowerShell but have been unsuccessful.
This is the code:
Below is the .xml config file created with the Office Deployment Tool (ODT)
It appears like the install begins but then nothing happens. I suspect that setup.exe is not getting the -ArgumentList
The Log reads:
Install Visio 2016 With Office 365
1 Answer
The Command Prompt suffices. No need to use Powershell.
I solved this question yesterday:
Unable to install Microsoft Visio 2016 on server 2012
I have faced exactly the same warning (..Office Click-to-Run installer encountered a problem because you have these Windows Installer based Office programs installed on your computer..), and succeeded to install Visio 2016 to PC that is already installed with MS Office 2016 Professional Plus. Here is the detailed solution.
Root of the problem: Microsoft prevented Click-to-Run (C2R) edition and Windows Installer (MSI) edition to run simultaneously in the same computer.
Workaround hint: C2R checks whether there is already an installed MSI edition (such as MS Office 2016 Professional Plus) in the PC. So, somehow if I hide MSI edition (while still being installed in the PC) from C2R checker, I can install C2R Visio to MSI-installed MS Office Pro Plus machine!
Inspiration for the solution:
http://woshub.com/how-to-hide-installed-programs-from-programs-and-features/
thenicnic's 12.05.2018 brilliant approach:https://social.technet.microsoft.com/Forums/office/de-DE/344c975d-1d36-4338-8f7a-0f0eb685234c/office-2016-msi-installer-volume-license-incompatible-with-visioproject-2016-from-msdn-click-to?forum=Office2016setupdeploy
Solution (step by step):
My PC: 64-bit Windows 10; installed with 32-bit MS Office 2016 Professional Plus
Installation of Visio 2016 Professional Plus:
1. Hide MS Office 2016 Professional Plus from C2R checker:
Go to the registry path:
If you have 64-bit operating system (OS) PC and 32-bit Office:
HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeMicrosoftWindowsCurrentVersionUninstallOffice16.PROPLUS
If you have 64-bit operating system (OS) PC and 64-bit Office:HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionUninstallOffice16.PROPLUSAdd a DWORD value named SystemComponent and set it to 1.Upon addition, Office 2016 Pro Plus becomes invisible in 'Control Panel - Programs and Features' (though it still remains installed in the PC and thereby deceives C2R checker!).
Enjoy the trick a little bit (set SystemComponent to 0 and see Office 2016 Pro Plus becomes visible upon F5 (refresh) in 'Control Panel - Programs and Features'. Now, turn back to our job, i.e., set SystemComponent to 1 once again)
Now, one can install Visio 2016 with the C2R installer.
2. Download Office 2016 Deployment Tool (officedeploymenttool_10321.33602.exe).
https://support.microsoft.com/en-us/help/4026267/office-office-2016-deployment-tool
Run officedeploymenttool_10321.33602.exe. This creates a folder named OfficeDeploymentTool with files setup.exe and configure.xml.
3. Open configure.xml (with NotePad), save it as InstallVisio.xml, delete all its content, and put the following code into InstallVisio.xml file:
Note that this is for Turkish Visio, the one who wants English visio must set en-us in the above Language ID part.
4. Run Office Deployment Tool to install Visio 2016 Pro Plus:
To install Visio (specified in InstallVisio.xml file), Open Command Prompt change directory and come to the folder where setup.exe of OfficeDeploymentTool is located.(in my PC, I put officedeploymenttool_10321.33602.exe to D:Office2016ClickToRunEdition, upon its run, setup.exe and configure.exe was created in D:Office2016ClickToRunEditionOfficeDeploymentTool. Hence, I came to D:Office2016ClickToRunEditionOfficeDeploymentTool in Command Prompt).Run the following command:
5. Installation is successfully made and at the end a message was shown:https : // prnt.sc / k2u256
PS 1: Those who want MS Office 2016 Pro Plus to be seen in 'Control Panel - Programs and Features' should set SystemComponent value to 0 or remove the added registry key (i.e., SystemComponent).
PS 2: I downloaded VisioProRetail.img (4,341,036 KB) and mount it as E, but did not use it in the process. I think that with the above configuration .xml file, Visio was automatically downloaded from Microsoft servers. The resulting successful install message seems to say so.