Deployment of Office 365 Click to Run

Having an issue getting the O365 to install and wondering if I could get some help. I am new to SCCM and have managed to get a few other apps/packages pushed out without issue. I have followed a couple of online resources to get this one
going but am at the end of my rope.
Created an Application that pushes out to a user Group.
Client Computer (default device) is seeing the package and downloading for the appropriate users and I can see the complete package in the \windows\CCMCACHE
The issue appears that it is timing out waiting for user input when doing the install.
the app is calling setup.exe /configure configuration.xml
Contents of configuration.xml below
<Configuration>
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>
Here is the App enforcment log that tells me it is exceeding 120 minutes
<![LOG[+++ Starting Install enforcement for App DT "Deploy Office 365 Pro Plus X32" ApplicationDeliveryType - ScopeId_F0A72C6A-71AD-48AB-9637-3C4F9DC381D0/DeploymentType_ee4472b1-c0c3-4ed5-aeda-b6d844c62944, Revision - 6, ContentPath - C:\windows\ccmcache\1i, Execution Context - System]LOG]!><time="14:16:04.873+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appprovider.cpp:1702">
<![LOG[ A user is logged on to the system.]LOG]!><time="14:16:04.885+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appprovider.cpp:2083">
<![LOG[ Performing detection of app deployment type Deploy Office 365 Pro Plus X32(ScopeId_F0A72C6A-71AD-48AB-9637-3C4F9DC381D0/DeploymentType_ee4472b1-c0c3-4ed5-aeda-b6d844c62944, revision 6) for system.]LOG]!><time="14:16:04.889+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appprovider.cpp:2148">
<![LOG[+++ Application not discovered. [AppDT Id: ScopeId_F0A72C6A-71AD-48AB-9637-3C4F9DC381D0/DeploymentType_ee4472b1-c0c3-4ed5-aeda-b6d844c62944, Revision: 6]]LOG]!><time="14:16:04.910+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="localapphandler.cpp:291">
<![LOG[ App enforcement environment:
Context: Machine
Command line: setup.exe /configure configuration.xml
Allow user interaction: No
UI mode: 0
User token: null
Session Id: 4294967295
Content path: C:\windows\ccmcache\1i
Working directory: ]LOG]!><time="14:16:04.911+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appcontext.cpp:85">
<![LOG[ Prepared working directory: C:\windows\ccmcache\1i]LOG]!><time="14:16:04.912+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appcontext.cpp:189">
<![LOG[ Prepared command line: "C:\windows\ccmcache\1i\setup.exe" /configure configuration.xml]LOG]!><time="14:16:05.012+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appcontext.cpp:338">
<![LOG[ Post install behavior is BasedOnExitCode]LOG]!><time="14:16:05.411+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appcommon.cpp:1094">
<![LOG[ Waiting for process 1612 to finish. Timeout = 120 minutes.]LOG]!><time="14:16:05.414+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appexcnlib.cpp:1958">
<![LOG[Exceeded timeout of 120 minutes while waiting for process 1612 to finish.]LOG]!><time="16:16:05.723+300" date="02-12-2015" component="AppEnforce" context="" type="2" thread="11560" file="appexcnlib.cpp:1972">
<![LOG[WaitForRunningProcess failed. Error 0x87d00213.]LOG]!><time="16:16:05.723+300" date="02-12-2015" component="AppEnforce" context="" type="3" thread="11560" file="appexcnlib.cpp:1988">
<![LOG[CMsiHandler::CompleteEnforcement failed with 0x87d00213]LOG]!><time="16:16:05.724+300" date="02-12-2015" component="AppEnforce" context="" type="3" thread="11560" file="msihandler.cpp:320">
<![LOG[CAppProvider::CompleteEnforcement failed with error 0x87d00213]LOG]!><time="16:16:05.729+300" date="02-12-2015" component="AppEnforce" context="" type="3" thread="11560" file="appprovider.cpp:2544">
<![LOG[++++++ Failed to enforce app. Error 0x87d00213. ++++++]LOG]!><time="16:16:05.736+300" date="02-12-2015" component="AppEnforce" context="" type="3" thread="11560" file="appprovider.cpp:2467">
As this is the first package that really has failed miserably I would love any help trying to troubleshoot what is wrong.

I haven't pushed this application out but I have looked at OneDrive which was very similar.
https://social.technet.microsoft.com/Forums/en-US/fdc35051-796f-4c94-98b4-19df0bc316e3/one-drive-for-business-deployment-with-sccm?forum=configmanagergeneral
Forget about Configuration manager, it's just running the installation via a command line under the system account.
Copy your application to a local machine and run it from from a command line,
It might be worth changing the display level property so you can see if the installation is prompting for anything.
You could also add

and check the temp directory for the log file.
Start run %temp%
or if running under the system account this will be located C:\windows\temp.
Once you have your installation going through silently then run it under the system account. again do this from the local machine without configmgr using PSEXEC -i -s cmd.exe
http://richardbalsley.com/a-simple-tip-to-test-software-installation-using-the-local-system-account
One that works it will fly out using ConfigMgr.

Similar Messages

Office 365 Click to Run April Update version has changed


We are implementing a process for controlling Office 365 click-to-Run updates so that our application testers can verify that the updates have no adverse effects on their applications.
We started distributing the April update on April 14th and the update version at the time was 15.0.4711.1002. We are also using the group policy registry keys to control the version. Today after hours of troubleshooting why we are now getting
errors when PCs are trying to update to that version I discover that there is no longer a version 15.0.4711.1002 and has been replaced by 15.0.4711.1003. I cant find anywhere why this has been updated or what changes were made so I don't know if this
now has to be retested by our testing group.   Just wondering is this a minor change and if so what was it?

Thanks for responding Tony - here is my modified configuration.xml (I've only removed DFS location names)
<Configuration>
<Add SourcePath="\\OurDomain.com\Office365\Files" OfficeClientEdition="32" >
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
</Add>
<Updates Enabled="TRUE" UpdatePath="\\OurDomain.com\Office365\Files\Updates" />
<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="Office2013Setup.log" Path="%windir%\Logs\Office\" />

</Configuration>
Carl Barrett | Twitter: @Mosquat

Need assistance creating applications with superseedence to uninstall Office 2010, Lync 2010 and then install Office 365 click to run 2013

We are getting ready in a few months to uninstall our locally installed Office 2010 and head to the cloud with Office 365 2013. I have created applications to uninstall Office 2010 and Lync 2010 and then added them to the supersedence tab for Office 365
office 2013 click to run with appv5.
When deploying the office 365 2013 application it does not uninstall office 2010 or lync 2010 with the supersedence. I am able to manually uninstall Office 2010 and Lync 2010 with the command lines I am using in the applications.
The application uninstall for Office 2010 is:
The application uninstall is an exe so I created an application, created a deployment type with the location of our Office 2010 admin point, installation program and uninstall program are set with the same line as I have tried to deploy it separately and
also as a supersedence in the Office 365 application setup.exe /uninstall ProPlus /config "\\sccmserver\share\Office2010\ProPlus.ww\silentuninstallconfig.xml. The silentuninstallconfig.xml was created from the original config.xml file and edited
to these settings:<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="NO" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="Reboot" Value="Never" />
<Setting Id="SETUP_REBOOT" Value="NEVER" />
<OptionState Id="ProductFiles" State="Local" Children="force" />
</Configuration>
The detection method is the folder path to see that office 14 exists. When I deploy this the machines finish with success showing this exists, but does not uninstall Office 2010.
running the command line manually mapped to this location on a machine uninstalls office 2010 without issue.
Lync 2010 uninstall:
Lync is an exe so I am using the LyncSetup.exe /silent /uninstall. The application is in the supersedence tab for Office 365 2013. This never installs. If I create a softare distribution and deploy it on its own it uninstalls without issue.
We are going to use Lync 2013 with our office 365 2013 installation so we need to uninstall this. The detection method for lync is file system folder and the Microsoft lync folder for detection.
MS Office 15 (Office 365) was created with the click to run tool. I can install this with the application I created using the appv5 package created with the click to run tool. The issue is we need Office 2010 and Lync 2010 uninstalled first.
Having both versions of Office installed in test has caused issues where Office 15 365 will not list in add and remove programs and cannot be uninstalled even with the fix it article to remove office 2013.
I have looked at many articles and so far it is not working for us. Any help appreciated to get us to the cloud.
Thanks,
Brit

The applications I have for uninstall of office 2010 and Lync 2010 for some reason do not uninstall. Manually testing the command lines they do. The detection method seems to be hanging things up. On the lync uninstall detection method I have
the setting type of file system, type folder, path c:\program files\ folder name Microsoft Lync.
I highly recommend using something other than a file/folder "exists" detection method. Installers are constantly leaving things behind due to environmental inconsistencies. It may leave files/folders behind with a schedule to delete files on next reboot.
These things are unpredictable and very hard to use. I just use the "HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall" Registry location. There you can actually key off the "Product Version" DWORD as well which gives you an even more accurate method
to determine if the application you are trying to deploy (or expect to exist) is truly there. This, of course, being if you are not using an MSI. If you have MSI technology ALWAYS use the product code unless the person writing the MSI chooses to use the same
product code for every version release of their product. In which case, Use the registry method.
As far as getting the supersedence and everything working. You need to start from the basics. Create Applications for all of the apps you want to remove. Make sure they install and uninstall properly (seems like overkill but it isn't that hard). Once you
have working install/uninstall applications then you can easily apply supersedence to your new applications with a setting of Uninstall on the superseded apps you should have no problem getting rid of them. I have done this for numerous things.
For example, I did this with Cisco Jabber to replace older versions of jabber, older versions of cisco unified personal communicator and lync and OSC. All of these replaced versions had to have an Application but once it was in it took two seconds to apply
all the supersedence rules and now I know when I push that software out no matter version is running on any machine it will pull all the old apps off and put the new one on.
Dustin Estes - MCP | www.dustinestes.com

Add-in support on Office 365 click-to-run installed and Office 365 App-V installed

Hi,
We have to make a decision on deploying Office 365 via on premise click-to-run, with the Office Deployment tool, or via App-V. But the way add-ins are supported on Office 365 / Office 2013 on App-V 5.0 SP2 is not clear to me.
Some Technet sites mention that for add-in support on an App-V based office, the add-ins should be sequenced and put together in a connection group with the Office App-V package (created by the Office Deployment tool)
On
http://blogs.technet.com/b/office_resource_kit/archive/2013/12/02/announcing-app-v-5-0-sp2-support-for-office-2013-volume-licensing-editions.aspx however, I read in the table “Full-featured Office with integration with other applications,
add-ins, and Windows”
When testing with third party applications and Visual Studio installed in a classical installer way, the add-ins are added to the App-V installed Office, but we are sometimes experiencing error messages in word / excel with the add-ins
enabled.
Should add-ins be sequenced to be used on an App-V based Office? Or in other words, is there a difference in add-in support between the click-to-run version and the App-V version of Office for non-virtualized add-ins?

Hi,
There is a new feature for Office 365 Pro Plus, it allow administrators the ability to exclude App element. We need to use Office 2013 Click-to-Run (Build 15.0.4615.1001) and logon as administrator.
http://blogs.technet.com/b/odsupport/archive/2014/05/14/new-application-selection-feature-offered-with-the-may-2014-update-of-office-2013-click-to-run.aspx
Then, we'd better follow this link and repeat the steps one by one:
http://lyncme.co.uk/office365/office365-proplus-click-to-run-lets-stop-onedrive-for-business-from-being-installed/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does
not guarantee the accuracy of this information.
Regards,
George Zhao
TechNet Community Support

Lync 2013 (part of Office 365 Click to run package) Crashes at startup.

Faulting application name: lync.exe, version: 15.0.4675.1000, time stamp: 0x54629b81
Faulting module name: KERNELBASE.dll, version: 6.1.7601.22616, time stamp: 0x5315adc5
Exception code: 0xe06d7363
Fault offset: 0x0000c44d
Faulting process id: 0x1848
Faulting application start time: 0x01d01ee1ca36be06
Faulting application path: C:\Program Files\Microsoft Office 15\root\office15\lync.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 0a8fda0a-8ad5-11e4-a243-005056c00008
-Tried to run lync as an Admin
-Deleted all User profile settings under C:\users\<username>\appdata\local\microsoft\office\15.0\lync
-updated Video Card Drivers, tried both WU version and AMD's.
This appears to be a Profile issue, as I can log into the same computer with a different profile and Lync works just fine. Both profiles in use are Local Admins.
Ordinarily I would just delete the Profile and start over, however in this case that's not an option. Any other places I can remove or reset Lync Data?

Hi,
Please try to delete user information from Registry with the following path:
HKCU\Software\Microsoft\Office\15.0\Lync\[email protected], then restart Lync client to test the issue again.
Also, check if there is any duplicate copies of Lync updates on the issued computer. If that is the case, please remove the duplicate, restart Lync client to test again.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Managing Office 365 Click to install with SCCM

Hello,
I am looking at deploying Office 365 via SCCM, but it looks like we will loose the ability to patch via WU/MU and instead need to update via pointing 365 to a static update source in configuration.xml \\server\path\.
Has anyone found a way to deploy the click to run 365 Office version and still effectively manage and updates and patches using SCCM distribution points? We do not want to run the MSI version.
Can anyone from MS here comment on the future of SCCM and 365 click to run integration ?
TIA
Lance

I was hoping you'd ask ;)
We created a second app in SCCM with some different settings for deployment because we expected people would be using Office while we were trying to update. . We used the same deployment method as the original app and the only real difference in the XML
is the version number of the bits we are updating and the display level. We changed the display level so that if people were logged in an using Office when the installation deadline was reached they would get a nice popup that indicated if they wished to continue
with the Office update then they would need to close Office. If they declined then SCCM marked the application as failed and on next software eval cycle would prompt again until success.
Our XML for the update is below - hope this helps.
<Configuration>
<Add SourcePath="" Version="15.0.4623.1003" OfficeClientEdition="32" >
  <Product ID="O365ProPlusRetail">
   <Language ID="en-us" />
  </Product>
</Add>
<Updates Enabled="FALSE" />
<Display Level="Full" AcceptEULA="TRUE" />
<Logging Name="Office365Setup.log" Path="%temp%" />
  <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />
</Configuration>

Can't install the sharepoint designer 2013 (32 or 64 bits) because of the "Office 15 click-to-run extensibility component"

Hi there,
I have a problem installing sharepoint designer 2013 which I downloaded .
When I try to install the 64 bits installation program it it comes up with a popup that there are 32 bits programs found on my laptop. (Office 15 click-to-run extensibility component)
When I try to install the 32 bits program of sharepoint designer it gives the same popup only that it found a 64 bits office program (Office 15 click-to-run extensibility component).
What can I do to resolve this strange problem?
I have a windows 8.1 laptop and use office as part of office 365.

Hi GerritAikema,
According to your description, my understanding is that you got an error when you installed SharePoint 2013 Designer 64-bit.
Please uninstall the Office 15 Click-to-Run Extensibility component, then install SharePoint 2013 Designer 64-bit, compare the result.
For uninstalling the Office 15 Click-to-Run Extensibility component, you can refer to the link:
http://lennytech.wordpress.com/2013/08/10/uninstalling-the-office-15-click-to-run-extensibility-component/
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

Office 2013 Click-to-Run Event Logs

Anyone know what the event logs are (Source, Event ID, etc) for Office 2013 Click-to-Run version? Specifically, I'm trying to find out when my installation was last updated (automatic updates are enabled). In general it would also be nice to know
what all of the different events are that the program will log.
Shaun

Hi,
To view the Office updates log, we can just go to Control Panel > All Control Panel Items > Windows Update and click
View update history.
If you want to know all the event logs related to Microsoft Office, we can use Event Viewer.
http://windows.microsoft.com/en-in/windows/open-event-viewer#1TC=windows-7
To find Office-related logs, click Event Viewer > Applications and Services Logs > Microsoft Office Alerts in the Event Viewer window.
Regards,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Office 2013 click to run: configure specific options like in /admin setup

Hi,
In an Office 2013 click-to-run install, how can we set f.e. the Exchange server, disable Junk mail protection (we have a seperate system for that), disable RSS, username to be used in Outlook (%username%) etc?
We have that when using the office 2013 setup.exe /admin but not in the click to run.
I don't find these options in the config.xml reference: http://technet.microsoft.com/en-us/library/cc179195%28v=office.15%29.aspx
Please advise.
J.
Jan Hoedt

Hi Jan,
Click-To-Run version of Office 2013 does not contain the Office Configuration Tool (OCT). And the
Config.xml file mentioned above is used to customize Windows Installer-based Office 2013 installations, not for Click-To-Run version of Office.
To configure these specific options for Click-To-Run version of Office 2013, you can use
Group Policy Administrative Template files (ADMX, ADML). The policy settings apply to both Windows Installer-based (MSI) and Click-to-Run version of Office 2013.
Download link for the Group Policy Administrative Template files (ADMX, ADML):
http://www.microsoft.com/en-us/download/details.aspx?id=35554
Here is the reference you'll need:
http://technet.microsoft.com/en-us/library/cc178992(v=office.15).aspx
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Deployment Tool to Download Click-to-Run for Office 365

The download gets only so far and then fails. Below is my .xml and the last log from %temp%. Thanks for any help!
I ran:
"setup.exe /download mmmconfiguration.xml"
mmmconfiguration.xml:
<Configuration>
     <Add SourcePath="d:\Shared\O365\downloads" OfficeClientEdition="32" >
           <Product ID="O365ProPlusRetail">
                 <Language ID="en-us" />
           </Product>
      </Add>
          <Updates Enabled="TRUE" UpdatePath="d:\Shared\O365\downloads" />
          <Display Level="None" AcceptEULA="TRUE" />
          <Logging Path="%temp%" />
</Configuration>
BGNBNFILEP01-20140404-1649.log
Timestamp Process TID Area Category EventID Level Message Correlation
04/04/2014 16:49:31.739 SETUP (0x12a4) 0xc28 Click-To-Run aqkhc Medium CmdLine:"D:\Shared\O365\OfficeDeploymentTool\setup.exe" /download mmmconfiguration.xml
04/04/2014 16:49:31.739 SETUP (0x12a4) 0xc28 Click-To-Run Telemetry aqkhd Medium {"SessionID":"415d1df5-8e0e-4875-90ec-5810ed4ecff4","GeoID":"244","Ver":"15.0.4595.1000","Bitness":"32","IntegrityLevel":"0x3000","SecuritySessionId":"3"}
04/04/2014 16:49:31.739 SETUP (0x12a4) 0xc28 Click-To-Run Telemetry aqkhe Medium {"SessionID":"415d1df5-8e0e-4875-90ec-5810ed4ecff4","GeoID":"244","Ver":"15.0.4595.1000","OSVersion":"6.1","SP":"1","ProductType":"3","ProcessorArch":"9","Locale":"1033"}
04/04/2014 16:49:31.739 SETUP (0x12a4) 0xc28 Click-To-Run amawz Medium Args::ParseArgument: Parsing commandline.
04/04/2014 16:49:31.755 SETUP (0x12a4) 0xc28 Click-To-Run ambpm Medium Args::Load: Have Admin scenario
04/04/2014 16:49:31.755 SETUP (0x12a4) 0xc28 Click-To-Run amaw0 Medium Args::GetNextArgument: Next argument: /download
04/04/2014 16:49:31.755 SETUP (0x12a4) 0xc28 Click-To-Run amaw0 Medium Args::GetNextArgument: Next argument: mmmconfiguration.xml
04/04/2014 16:49:31.755 SETUP (0x12a4) 0xc28 Click-To-Run aoh7y Medium Args::GetConfigFile: config file: mmmconfiguration.xml
04/04/2014 16:49:31.755 SETUP (0x12a4) 0xc28 Click-To-Run appfq Medium Args::Load: product release id: none culture: en-us
04/04/2014 16:49:31.755 SETUP (0x12a4) 0xc28 Click-To-Run apvr9 Medium TrySetUserRegistry::TrySetAttemptGetKey: Setting Attempt Get Key for none
04/04/2014 16:49:31.755 SETUP (0x12a4) 0xc28 Click-To-Run amaw8 Medium TrySetUserRegistry::TrySetLicenseTokenOrKey: No key or token found for none
04/04/2014 16:49:31.755 SETUP (0x12a4) 0xc28 Click-To-Run aoh76 Medium HandleCommandLineAction::HandleStateAction: Not OOD scenario nor showing ODT help, check for elevation.
04/04/2014 16:49:31.755 SETUP (0x12a4) 0xc28 Click-To-Run aoh8l Medium TryGetElevation::HandleStateAction: Already running from elevated context.
04/04/2014 16:49:31.755 SETUP (0x12a4) 0xc28 Click-To-Run aoh78 Medium HandleCommandLineAction::HandleStateAction: Starting Admin tool scenario.
04/04/2014 16:49:31.755 SETUP (0x12a4) 0xc28 Click-To-Run aoh8c Medium HandleCommandLineAction::HandleStateAction: Download bits locally.
04/04/2014 16:49:31.755 SETUP (0x12a4) 0xc28 Click-To-Run aoh8r Medium DownloadOffice::HandleStateAction: Download office bits to specified location.
04/04/2014 16:49:31.755 SETUP (0x12a4) 0xc28 Click-To-Run anwvz Medium Configuration::Load: Using config file: mmmconfiguration.xml
04/04/2014 16:49:31.864 SETUP (0x12a4) 0xc28 Click-To-Run anwvy Medium ConfigFile::ParseAttribute: Value of SourcePath: d:\Shared\O365\downloads
04/04/2014 16:49:31.864 SETUP (0x12a4) 0xc28 Click-To-Run anwvu Medium ConfigFile::ParseAddNode: Version not specified.
04/04/2014 16:49:31.864 SETUP (0x12a4) 0xc28 Click-To-Run anwvv Medium ConfigFile::ParseAddNode: ForceDowngrade:
04/04/2014 16:49:31.864 SETUP (0x12a4) 0xc28 Click-To-Run anwvy Medium ConfigFile::ParseAttribute: Value of OfficeClientEdition: 32
04/04/2014 16:49:31.864 SETUP (0x12a4) 0xc28 Click-To-Run anwvy Medium ConfigFile::ParseAttribute: Value of Level: None
04/04/2014 16:49:31.864 SETUP (0x12a4) 0xc28 Click-To-Run anwvy Medium ConfigFile::ParseAttribute: Value of AcceptEULA: TRUE
04/04/2014 16:49:31.864 SETUP (0x12a4) 0xc28 Click-To-Run anwvy Medium ConfigFile::ParseAttribute: Value of Path: %temp%
04/04/2014 16:49:31.864 SETUP (0x12a4) 0xc28 Click-To-Run anwvy Medium ConfigFile::ParseAttribute: Value of Enabled: TRUE
04/04/2014 16:49:31.864 SETUP (0x12a4) 0xc28 Click-To-Run anwvy Medium ConfigFile::ParseAttribute: Value of UpdatePath: d:\Shared\O365\downloads
04/04/2014 16:49:31.864 SETUP (0x12a4) 0xc28 Click-To-Run amaws Medium Configuration::Load: Setting culture to: en-us
04/04/2014 16:49:31.864 SETUP (0x12a4) 0xc28 Click-To-Run amaxd Medium DownloadOffice::DownloadPackages: Getting Office for culture: en-us
04/04/2014 16:49:31.864 SETUP (0x12a4) 0xc28 Click-To-Run amaxd Medium DownloadOffice::DownloadPackages: Getting Office for culture: x-none
04/04/2014 16:49:31.864 SETUP (0x12a4) 0xc28 Click-To-Run amaxe Medium DownloadOffice::DownloadPackages: Getting Office in directory: d:\Shared\O365\downloads\Office\Data
04/04/2014 16:49:31.864 SETUP (0x12a4) 0xc28 Click-To-Run amaxf Medium DownloadOffice::DownloadPackages: Getting version cab file.
04/04/2014 16:49:31.864 SETUP (0x12a4) 0xc28 Click-To-Run aon8k Medium CabManager::DetermineCabName: Type:0, Platform:x86, Version:, Culture:en-us -> v32.cab
04/04/2014 16:49:32.036 SETUP (0x12a4) 0xc28 Click-To-Run aon8i Medium CabManager::Extract: Extracting d:\Shared\O365\downloads\Office\Data\v32.cab -> C:\Users\MMARTE~1\AppData\Local\Temp\3\343E687C
04/04/2014 16:49:32.364 SETUP (0x12a4) 0xc28 Click-To-Run anwv6 Medium Descriptor::Load: Reading Available value from descriptor: 15.0.4569.1508
04/04/2014 16:49:32.364 SETUP (0x12a4) 0xc28 Click-To-Run amawt Medium Descriptor::Load: Prereq Node exists. Being parsing it.
04/04/2014 16:49:32.364 SETUP (0x12a4) 0xc28 Click-To-Run anwv7 Medium Descriptor::Load: Reading Bootstrapper value from descriptor: 15.0
04/04/2014 16:49:32.380 SETUP (0x12a4) 0xc28 Click-To-Run amaxg Medium DownloadOffice::DownloadPackages: Getting Office lcid: 1033
04/04/2014 16:49:32.380 SETUP (0x12a4) 0xc28 Click-To-Run amaxm Medium DownloadOffice::DownloadFile: Downloading file http://officecdn.microsoft.com/pr/39168D7E-077B-48E7-872C-B232C3E72675/Office/Data/15.0.4569.1508/stream.x86.en-us.dat
04/04/2014 16:51:09.584 SETUP (0x12a4) 0xc28 Click-To-Run amaxh Medium DownloadOffice::DownloadPackages: Succesfully downloaded .dat file
04/04/2014 16:51:09.584 SETUP (0x12a4) 0xc28 Click-To-Run aon8k Medium CabManager::DetermineCabName: Type:1, Platform:x86, Version:15.0.4569.1508, Culture:en-us -> i321033.cab
04/04/2014 16:51:10.537 SETUP (0x12a4) 0xc28 Click-To-Run amaxi Medium DownloadOffice::DownloadPackages: Succesfully downloaded client cab
04/04/2014 16:51:10.537 SETUP (0x12a4) 0xc28 Click-To-Run aon8k Medium CabManager::DetermineCabName: Type:1, Platform:x64, Version:15.0.4569.1508, Culture:en-us -> i641033.cab
04/04/2014 16:51:11.724 SETUP (0x12a4) 0xc28 Click-To-Run amaxj Medium DownloadOffice::DownloadPackages: Succesfully downloaded 64bit client cab
04/04/2014 16:51:11.724 SETUP (0x12a4) 0xc28 Click-To-Run aon8k Medium CabManager::DetermineCabName: Type:3, Platform:x86, Version:15.0.4569.1508, Culture:en-us -> s321033.cab
04/04/2014 16:51:11.881 SETUP (0x12a4) 0xc28 Click-To-Run amaxk Medium DownloadOffice::DownloadPackages: Succesfully downloaded stream cab for culture.
04/04/2014 16:51:11.881 SETUP (0x12a4) 0xc28 Click-To-Run amaxg Medium DownloadOffice::DownloadPackages: Getting Office lcid: 0
04/04/2014 16:51:11.881 SETUP (0x12a4) 0xc28 Click-To-Run amaxm Medium DownloadOffice::DownloadFile: Downloading file http://officecdn.microsoft.com/pr/39168D7E-077B-48E7-872C-B232C3E72675/Office/Data/15.0.4569.1508/stream.x86.x-none.dat
04/04/2014 16:51:11.928 SETUP (0x12a4) 0xc28 Click-To-Run aoh8t Unexpected DownloadOffice::HandleStateAction: Failed to download office bits.
04/04/2014 16:51:11.928 SETUP (0x12a4) 0xc28 Click-To-Run aoh71 Medium BootstrapperState::OnError: Error has occured. Go to ExitBootStateMachine.
04/04/2014 16:51:11.943 SETUP (0x12a4) 0xc28 Click-To-Run aoh9f Medium BootStateMachine::ShowFailureUI: Showing failure UI.
04/04/2014 16:51:37.022 SETUP (0x12a4) 0xc28 Click-To-Run aoh72 Medium ExitBootStateMachine::HandleStateAction: Bootstrapper workflow exiting with result: 0x0
04/04/2014 16:51:37.022 SETUP (0x12a4) 0xc28 Click-To-Run aoh9z Medium AdminBootstrapper::Main: Installation came back with -2147418113.
04/04/2014 16:51:37.022 SETUP (0x12a4) 0xc28 Logging Liblet aqc99 Medium Logging liblet uninitializing.

Good to see you have unblocked by yourself. Could you please share your steps/workaround here on how you fixed this? Other people might also experience the same issue, your answers could be helpful to them.
Thanks,
Ethan Hua CHN
TechNet Community Support

SCCM 2012: Office 2013 click to run deploy?

Hi,
We would like to run Office 2013 next to Office 2010. Therefore the click-to-run option (app-v is only possible for Office 2013 ProPlus) looks the way to go.
I found a nice guide a Office 2013 Plus “Click to run” Deploy in SCCM:
http://www.peters.com/Blogs/Lists/Posts/Post.aspx?ID=90 However (posted it also on the site), can I use the /admin to generate the configuration.xml instead and use it within SCCM 2012 deploy?
J
Jan Hoedt

No. Click-to-run does not use the traditional Office setup methodology and thus does not have the same configuration options. More info at
http://technet.microsoft.com/en-us/library/jj219420(v=office.15).aspx
Jason | http://blog.configmgrftw.com | @jasonsandys

Office 2013 Click-to-Run

All,
We are having issues with some customers that have the Office 2013 Home and Business Click-to-Run version of office installed. Users are randomly having their installation corrupted. This interestingly enough didn't start happening until SP1 was released
for Office 2013. I am aware that click-to-run installations of office don't update via Windows Updates direct but through another method. Is anyone else seeing this happen? Any thoughts would be appreciated.
Some of the symptoms are as follows:
1. None of the Office apps open. You double-click but nothing happens nor are there any processes running.
2. If you open an office document direct you might get a message something to the effect of There was a Problem sending the command to the program. None of the documented fixes appear to correct the issue for this type of error.
3. A system restore point fixes it but it breaks again within a day or two.
4. The only fix at this point is to uninstall (Using FixIt KB2739501) and reinstall which of course pulls down the latest build with SP1.

Hi,
You can probably fix the issue by updating the video driver to the latest.
Please refer to this thread below, many users had the same issue and solved it by updating the video driver:
http://social.technet.microsoft.com/Forums/en-US/34401d63-6c3b-47e6-ab20-9ed9b70d890b/outlook-2013-sp1-unusable-since-sp1-update-?forum=officesetupdep
Thanks,
Melon Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

How to remove Office 2013 (Click to run) package?

I am having problems removing Office 2013 sequenced using Click to Run and is published to the machine as per MS guidelines.
It's a member of a connection group with another application.
I have tried many things:
get-appvclientpackage | stop-appvclientpackage | remove-appvclientpackage.
get-appclientconnectiongroup | remove-appvclientconnectiongroup
The connection group and both applications remain.
Error reported is that the application is still in use (no idea which one as it doesnt say). Task manager doesn't seem to list anything running from any virtual environment. I have tried viewing 'processes from all users' also.
I unpublished the connection group and the applications from the App-V Management Server, then retried the above commands which didnt work.
Tried rebooting after doing all the above, then retry PoSH commands and that didnt work either.
Any ideas?

Hello,
See this article;
http://blogs.technet.com/b/virtualvibes/archive/2013/12/03/pending-tasks-in-app-v-5-0-sp2.aspx
Nicke Källén | The Knack| Twitter:
@Znackattack

Office 2010 click to run , Protected Q Drive, cannot reinstall Office

Hello,
I have on my machine a version of office 2010, I am trying to unistall it and install a different version of office, when trying to uninstall the application from the control panel I get the following message :
This 64-bit product may not be installed with Microsoft Office Click-to-Run. Remove Microsoft Office Click-to-Run and try again.
Now on my machine there is nothing that is an office click to run except for a Q drive that is protected, and I cannot edit or format it, when trying to I geet a message about not having rights to do so, although I am an administrator. the problem here is
that I do not have Microsoft Office Click-To-Run 2010
under programs and features. so I cannot uninstall it.
I went to this link : http://support.microsoft.com/kb/290301
I tried the fix it app, I got this message:
Click-to-Run Application Manager
The action cannot be completed. Try the action again. If the problem continues, contact Microsoft Product Support.
OK
Any ideas?

Hi
Thank you for using
Microsoft Office for IT Professionals Forums.
From your description, I understand that "This 64-bit product may not be installed with Microsoft Office Click-to-Run" Error message when
you try to install a 64-bit version of Office 2010. If there is any misunderstanding, please feel free to let me know.
To determine whether you have Microsoft Office Click-to-Run 2010 installed on your computer, click the File tab and then click Help.
If you see a Click-to-Run Product Updates section, then Click-to-Run 2010 is installed on your computer.
To uninstall Microsoft Office Click-to-Run 2010 from your computer, follow these steps:
Click Start, and then click Control Panel.
Click the Add or Remove Programs item or click the Programs and Features
item.
In the list of installed programs, click Microsoft Office Click-to-Run 2010 and then click Uninstall.
Click Yes when you are prompted to remove all applications that were installed by Office Click-to-Run.
More detailed information you can refer to this Knowledge Base link
http://support.microsoft.com/kb/982258
Or follow these article steps to
uninstall Office Click-to-Run products:
Update, repair, or uninstall Office Click-to-Run products
http://office.microsoft.com/en-us/excel-help/update-repair-or-uninstall-office-click-to-run-products-HA010382089.aspx#_Toc272139016
Please take your time to try the suggestions and let me know the results at your earliest convenience. If anything is unclear or if there is anything I
can do for you, please feel free to let me know.
Hope that helps.
Sincerely
William Zhou CHNPlease remember to mark the replies as answers if they help and unmark them if they provide no help.

Office 2013 Click to Run - VAMT error: product SKU is not found

We failed to install the retail key for Office 2013 Home and Business Retail through VAMT. Error is: The Software Licensing Service reported that the product SKU is not found.
VAMT key install and activation worked fine with other retail products. I believe it's somehow related to the click-to-run technology.
Any help would be appreciated.

Hi,
I'm not quite sure how exactly you did in VAMT, but usually, the error message will show up only if you are using a wrong product key.
Do you have any other product keys installed in VAMT? Make sure you are using the correct key. Also, which activation option are you using in VAMT?
http://technet.microsoft.com/en-us/library/hh825164.aspx
Regards,
Ethan Hua
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Deployment of Office 365 Click to Run

Similar Messages

Maybe you are looking for