通过Powershell安装Microsoft Visio / Project即点即用(C2R)

时间:2018-03-14 12:53:25

标签: powershell visio

我一直在尝试使用PowerShell安装Microsoft Visio C2R,但一直没有成功。

这是代码:

$ScriptRoot = Split-Path -Path $MyInvocation.MyCommand.Path

    {
    Start-Process -FilePath $ScriptRoot\Setup.exe -ArgumentList "/configure configuration.xml" -Wait -PassThru
    }

以下是使用Office部署工具(ODT)

创建的.xml配置文件
<Configuration>
    <Add>
        <Product ID="VisioProXVolume" > 
            <Language ID="en-us" />
        </Product>
    </Add>
    <Display Level="None" AcceptEULA="TRUE" />
    <Property Name="AUTOACTIVATE" Value="1" />
    <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />
    <Property Name="SharedComputerLicensing" Value="0" />
    <Property Name="PinIconsToTaskbar" Value="FALSE" />
</Configuration>

看起来安装开始但没有任何反应。我怀疑setup.exe没有得到-ArgumentList

日志记载:

    03/14/2018 12:40:58.824 SETUP (0x1758)  0x1504  Activity    bjtct   Medium  ActivityStarted {"Name": "Office.Telemetry.ProcessIdleQueueJob", "CV": "J0FjfgfwIkanMNSjMi3JWg.3", "ProcessIdentifier": "Setup.exe_16.0.8528.3000_X86_{7E634127-F007-4622-A730-D4A3322DC95A}"}
    03/14/2018 12:40:58.824 SETUP (0x1758)  0x1504  OfficeTelemetry_RuleProcessing  axbjw   Medium  OTele_ETW_TDC_LoadingRulesStarted {"ETW_EventId": 119, "ETW_Keywords": 4}
    03/14/2018 12:40:58.824 SETUP (0x1758)  0x1504  Activity    bjtct   Medium  ActivityStarted {"Name": "Office.Telemetry.LoadXmlRules", "CV": "J0FjfgfwIkanMNSjMi3JWg.3.1", "ProcessIdentifier": "Setup.exe_16.0.8528.3000_X86_{7E634127-F007-4622-A730-D4A3322DC95A}"}
03/14/2018 12:40:58.824 SETUP (0x1758)  0x1504  Telemetry Rules Engine  bcdgv   Monitorable Unrecognized category specified in UlsCategorySeveritySource {"Category": "NexusTenantTokenApphost"}
03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  OfficeTelemetry_PerfMetrics axbjw   Medium  RuleFieldNamesImpact {"ETW_EventId": 196, "ETW_Keywords": 128, "cbMemory": 5900, "count": 182}
03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  OfficeTelemetry_RuleProcessing  axbjw   Medium  OTele_ETW_TDC_LoadingRulesEnded {"ETW_EventId": 120, "ETW_Keywords": 4}
03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  Activity    bjtcw   Medium  ActivityEnded {"Name": "Office.Telemetry.LoadXmlRules", "CV": "J0FjfgfwIkanMNSjMi3JWg.3.1", "ProcessIdentifier": "Setup.exe_16.0.8528.3000_X86_{7E634127-F007-4622-A730-D4A3322DC95A}"}

    03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  Telemetry Event biyhq   Medium  SendEvent {"EventName": "Office.Telemetry.LoadXmlRules", "Flags": 16843009, "InternalSequenceNumber": 4, "Time": "2018-03-14T12:40:58Z", "Contract": "Office.System.Activity", "Activity.CV": "J0FjfgfwIkanMNSjMi3JWg.3.1", "Activity.Duration": 16138, "Activity.Count": 1, "Activity.AggMode": 0, "Activity.Success": true, "Activity.Result.Code": 0, "Activity.Result.Type": "HRESULT"}
    03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  Telemetry Rules Engine  bd3fw   Medium  Loaded rule list. {"Rules": "606.1 615.0 616.0 620.0 622.0 623.0 625.0 626.0 627.1 629.0 630.3 631.0 633.0 634.0 635.0 636.3 637.0 642.0 643.4 644.3 645.4 646.4 647.8 648.3 649.11 652.0 662.0 669.0 671.1 675.0 682.0 685.0 120100.2 120103.9 120119.0 120122.0 120123.1 120402.10 224900.0 224901.7 224902.2 230104.0 230153.0 230156.0 230157.0 340002.12 340008.0 ", "BatchCount": 47, "TotalCount": 47, "HadRuleFileAtBoot": true}
    03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  Telemetry Rules Engine  bd3fx   Medium  Loaded rule count. {"Count": 47, "HadRuleFileAtBoot": true}
    03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  OfficeTelemetry_RuleProcessing  axbjw   Medium  OTele_ETW_RuleProcessing_RuleMetadataWritten {"ETW_EventId": 174, "ETW_Keywords": 4, "Count": 0}
    03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  OfficeTelemetry_RuleProcessing  axbjw   Medium  Otele_ETW_TDC_TimerSet {"ETW_EventId": 184, "ETW_Keywords": 4, "TimerInterval": 60000}
    03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  Activity    bjtcw   Medium  ActivityEnded {"Name": "Office.Telemetry.ProcessIdleQueueJob", "CV": "J0FjfgfwIkanMNSjMi3JWg.3", "ProcessIdentifier": "Setup.exe_16.0.8528.3000_X86_{7E634127-F007-4622-A730-D4A3322DC95A}"}
    03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  Telemetry Event biyhq   Medium  SendEvent {"EventName": "Office.Telemetry.ProcessIdleQueueJob", "Flags": 16843009, "InternalSequenceNumber": 5, "Time": "2018-03-14T12:40:58Z", "Contract": "Office.System.Activity", "Activity.CV": "J0FjfgfwIkanMNSjMi3JWg.3", "Activity.Duration": 25959, "Activity.Count": 1, "Activity.AggMode": 0}
    03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  Activity    bjtct   Medium  ActivityStarted {"Name": "Office.Experimentation.TasFetch", "CV": "J0FjfgfwIkanMNSjMi3JWg.4", "ProcessIdentifier": "Setup.exe_16.0.8528.3000_X86_{7E634127-F007-4622-A730-D4A3322DC95A}"}
    03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  Experiment Liblet   bse1v   Medium  Feature Query Status {"FeatureName": "Microsoft.Office.Experimentation.TasEndpoint", "TreatmentValue": "https://client-office365-tas.msedge.net/ab?", "TreatmentSource": 1}
    03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  Experiment Liblet   bse1v   Medium  Feature Query Status {"FeatureName": "Microsoft.Office.Experimentation.3rdPartyFlightingEnabled", "TreatmentValue": "true", "TreatmentSource": 11}
    03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  Experiment Liblet   bse1v   Medium  Feature Query Status {"FeatureName": "Microsoft.Office.Experimentation.SendChannelInformation", "TreatmentValue": "true", "TreatmentSource": 11}
    03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  Experiment Liblet   bse1v   Medium  Feature Query Status {"FeatureName": "Microsoft.Office.Experimentation.SendUserIdToEcs", "TreatmentValue": "false", "TreatmentSource": 1}
    03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  Experiment Liblet   bse1v   Medium  Feature Query Status {"FeatureName": "Microsoft.Office.Experimentation.SendInstallTypeTas", "TreatmentValue": "true", "TreatmentSource": 11}
    03/14/2018 12:40:58.840 SETUP (0x1758)  0x1504  Experiment Liblet   bse1v   Medium  Feature Query Status {"FeatureName": "Microsoft.Office.Experimentation.CheckConnectivity", "TreatmentValue": "false", "TreatmentSource": 1}
    03/14/2018 12:40:58.856 SETUP (0x1758)  0x620   Click-To-Run General Telemetry  aqkhc   Medium  InitLogging {"MachineId": "7aaf6283e7d28f45932e66ce5de7eff7", "SessionID": "d282aea9-ad15-4e3d-b4de-8b8b919a8ea2", "GeoID": 242, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "{\"AppVVersion\":\"0.0\",\"Bitness\":\"32\",\"CommandLine\":\"/configure configuration.xml \",\"ExeVer\":\"16.0.8528.3000\",\"IntegrityLevel\":\"0x2000\",\"Locale\":\"2057\",\"ModulePath\":\"C:\\\\Source\\\\Microsoft_Visio_Pro_2016_C2R_VL\\\\Setup.exe\",\"OSVersion\":\"10.0\",\"ProcessType\":\"ODT\",\"ProcessorArch\":\"9\",\"ProductType\":\"1\",\"SecuritySessionId\":\"1\"}"}
    03/14/2018 12:40:58.856 SETUP (0x1758)  0x620   Click-To-Run General Telemetry  b0fkw   Medium  wWinMain {"MachineId": "7aaf6283e7d28f45932e66ce5de7eff7", "SessionID": "d282aea9-ad15-4e3d-b4de-8b8b919a8ea2", "GeoID": 242, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "Unable to set audience Id as bitfield didn't exist"}
    03/14/2018 12:40:58.856 SETUP (0x1758)  0x620   Click-To-Run    arql8   Medium  Args::ParseArgument: Parsing commandline.
    03/14/2018 12:40:58.856 SETUP (0x1758)  0x620   Click-To-Run    arqmb   Medium  Args::Load: Have Admin scenario
    03/14/2018 12:40:58.856 SETUP (0x1758)  0x620   Click-To-Run    arql9   Medium  Args::GetNextArgument: Next argument: /configure
    03/14/2018 12:40:58.856 SETUP (0x1758)  0x620   Click-To-Run    arql9   Medium  Args::GetNextArgument: Next argument: configuration.xml
    03/14/2018 12:40:58.856 SETUP (0x1758)  0x620   Click-To-Run    aoh7y   Medium  Args::GetConfigFile: config file: configuration.xml
    03/14/2018 12:40:58.856 SETUP (0x1758)  0x620   Click-To-Run    appfq   Medium  Args::Load: product release id: none  culture: en-us
    03/14/2018 12:40:58.856 SETUP (0x1758)  0x620   Click-To-Run    apvr9   Medium  TrySetUserRegistry::TrySetAttemptGetKey: Setting Attempt Get Key for none
    03/14/2018 12:40:58.856 SETUP (0x1758)  0x620   Click-To-Run General Telemetry  ayef6   Medium  TrySetUserRegistry::TrySetLicenseTokenOrKey {"MachineId": "7aaf6283e7d28f45932e66ce5de7eff7", "SessionID": "d282aea9-ad15-4e3d-b4de-8b8b919a8ea2", "GeoID": 242, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "No key or token found for none"}
    03/14/2018 12:40:58.856 SETUP (0x1758)  0x620   Click-To-Run General Telemetry  buhx5   Medium  DetermineCentennialInstallEligibility::HandleStateAction {"MachineId": "7aaf6283e7d28f45932e66ce5de7eff7", "SessionID": "d282aea9-ad15-4e3d-b4de-8b8b919a8ea2", "GeoID": 242, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "Eligibility Check Skipped."}
    03/14/2018 12:40:58.856 SETUP (0x1758)  0x620   Click-To-Run General Telemetry  buhx6   Medium  DetermineCentennialInstallEligibility::HandleStateAction {"MachineId": "7aaf6283e7d28f45932e66ce5de7eff7", "SessionID": "d282aea9-ad15-4e3d-b4de-8b8b919a8ea2", "GeoID": 242, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "Force C2R or empty."}
    03/14/2018 12:40:58.856 SETUP (0x1758)  0x620   Click-To-Run General Telemetry  buhya   Medium  DetermineCentennialInstallEligibility::HandleStateAction {"MachineId": "7aaf6283e7d28f45932e66ce5de7eff7", "SessionID": "d282aea9-ad15-4e3d-b4de-8b8b919a8ea2", "GeoID": 242, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "Install Status : {'status':'1'}"}
    03/14/2018 12:40:58.856 SETUP (0x1758)  0x620   Click-To-Run    aoh76   Medium  HandleCommandLineAction::HandleStateAction: Not OOD scenario nor showing ODT help, check for elevation.
    03/14/2018 12:40:58.856 SETUP (0x1758)  0x620   Click-To-Run    aoh8i   Medium  TryGetElevation::HandleStateAction: Need to get elevation.
    03/14/2018 12:41:03.104 SETUP (0x1758)  0x620   Click-To-Run    aoh8j   Medium  TryGetElevation::HandleStateAction: Succesfully ran eleveated.
    03/14/2018 12:41:08.350 SETUP (0x1758)  0x620   Click-To-Run    aoh72   Medium  ExitBootStateMachine::HandleStateAction: Bootstrapper workflow exiting with result: 0x0
    03/14/2018 12:41:08.350 SETUP (0x1758)  0x620   Click-To-Run General Telemetry  arqpm   Medium  AdminBootstrapper::Main {"MachineId": "7aaf6283e7d28f45932e66ce5de7eff7", "SessionID": "d282aea9-ad15-4e3d-b4de-8b8b919a8ea2", "GeoID": 242, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "AdminBootstrapper::Main: Installation came back with 0."}

1 个答案:

答案 0 :(得分:2)

命令提示符就足够了。无需使用Powershell。

我昨天解决了这个问题:
Unable to install Microsoft Visio 2016 on server 2012

我已经遇到了完全相同的警告( ... Office即点即用安装程序遇到了问题,因为您在计算机上安装了这些基于Windows Installer的Office程序... ),并且成功将Visio 2016安装到已与MS Office 2016 Professional Plus一起安装的PC上。这是详细的解决方案。

问题的根源::Microsoft阻止了即点即用(C2R)版本和Windows Installer(MSI)版本在同一台计算机上同时运行。

解决方法提示:C2R检查PC中是否已经安装了MSI版本(例如MS Office 2016 Professional Plus)。因此,以某种方式,如果我从C2R检查器中隐藏了MSI版本(仍在PC中安装),则可以将C2R Visio安装到安装了MSI的MS Office Pro Plus机器上!

解决方案的灵感
http://woshub.com/how-to-hide-installed-programs-from-programs-and-features/
thenicnic的12.05.2018出色的方法: 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

解决方案(逐步):
我的电脑:64位Windows 10;已安装32位MS Office 2016 Professional Plus
Visio 2016 Professional Plus的安装:
1。。从C2R检查器中隐藏MS Office 2016 Professional Plus:

  • 转到注册表路径:
    如果您拥有64位操作系统(OS)PC和32位Office:
    HKEY_LOCAL_MACHINE \ SOFTWARE \ WOW6432Node \ Microsoft \ Windows \ CurrentVersion \ Uninstall \ Office16.PROPLUS
    如果您拥有64位操作系统(OS)PC和64位Office: HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ CurrentVersion \ Uninstall \ Office16.PROPLUS

  • 添加一个名为 SystemComponent 的DWORD值并将其设置为 1 。 此外,Office 2016 Pro Plus在“控制面板-程序和功能”中不可见(尽管它仍然保留在PC中,因此欺骗了C2R检查器!)。

  • 稍微享受一下技巧(将SystemComponent设置为0,然后在“控制面板-程序和功能”中按F5(刷新)即可看到Office 2016 Pro Plus。现在,回到我们的工作,即,再次将SystemComponent设置为1)

  • 现在,可以使用C2R安装程序安装Visio 2016。

2。。下载Office 2016部署工具(officedeploymenttool_10321.33602.exe)。
https://support.microsoft.com/en-us/help/4026267/office-office-2016-deployment-tool

运行officedeploymenttool_10321.33602.exe。这将创建一个名为 OfficeDeploymentTool 的文件夹,其中包含文件 setup.exe configure.xml

3。。打开configure.xml(使用NotePad),将其另存为InstallVisio.xml,删除其所有内容,然后将以下代码放入InstallVisio.xml文件中:

<Configuration>
  <Add OfficeClientEdition="32" >
    <Product ID="VisioProXVolume" PIDKEY="69WXN-MBYV6-22PQG-3WGHK-RM6XC">
        <Language ID="tr-tr" />
     </Product>
   </Add>  
</Configuration>

请注意,这是针对土耳其语Visio的,想要使用英语visio的人必须在上述语言ID部分中设置 zh-cn

4。。运行Office部署工具以安装Visio 2016 Pro Plus:
若要安装Visio(在InstallVisio.xml文件中指定),请打开“命令提示符”更改目录,然后进入OfficeDeploymentTool的setup.exe所在的文件夹。 (在我的PC上,我将officedeploymenttool_10321.33602.exe放到D:\ Office2016ClickToRunEdition,在运行时,在D:\ Office2016ClickToRunEdition \ OfficeDeploymentTool中创建了setup.exe和configure.exe。因此,我进入了D:\ Office2016ClickToRunEdition \ OfficeDeploymentTool。在命令提示符下)。 运行以下命令:

setup.exe /configure InstallVisio.xml

5。。安装成功完成,并显示以下消息: https:// prnt.sc / k2u256

PS 1:那些希望在“控制面板-程序和功能”中显示MS Office 2016 Pro Plus的用户应将SystemComponent值设置为 0 或删除添加的注册表项(即SystemComponent)

PS 2:我下载了VisioProRetail.img(4,341,036 KB)并将其安装为E,但在此过程中未使用它。我认为,使用上述配置.xml文件,Visio是自动从Microsoft服务器下载的。产生的成功安装消息似乎是这样。