Office365(Click to Run) Deployment with MDT Offline Media

Hi,
I have a scenario where i have to deploy Office365 using click to run with MDT offline media. Now the problem is with configuration.xml file in which we specify the source path of office files.
Here in this scenario as i have to deploy client machines with offline media, so in this case what will be the path in the config.xml file?
For testing purpose, after downloading the office source files, placed the setup.exe,config.xml file and office source folder in a same folder. Here is the config.xml file that i am using
<Configuration>
<Add SourcePath=" " OfficeClientEdition="32" >
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
In source path, i leave it blank,so that it will use the office source files which was saved in the same folder.
Then in MDT server, created a new application for Office365.In command line used the command :- setup.exe /config configuration.xml
Created a new task sequence for OS deployment and added the step install application for installation of Office365.
After creating a selection profile for the deployment, created a offline media for deployment of client machine.
Now while i am running the offline media on the bare-metal machine, after OS installation the deployment got stuck at step install Office 365. Got error message pop up, according to which internet connection needed during installation process so that the
click to run set-up will download the office source files, It means this will not use the previously downloaded file which was saved in the same folder.
So this is what my problem is.. How can i customize the configuration.xml file so that i can install office 365 with offline media.
Regards
Pallavi

<Add SourcePath=" "
....In source path, i leave it blank,so that it will use the office source files which was saved in the same folder.
As per
https://technet.microsoft.com/en-us/library/jj219426.aspx#BKMK_AddElement
SourcePath indicates the installation source path from which to install Office when you run the Office Deployment Tool in
configure mode. If you don’t specify SourcePath in
configure mode, Setup will look in the current folder for the Office source files. If the Office source files aren’t found in the current folder, Setup will look on Office 365 for them
So, for the /configure mode, you should remove the Sourcepath element completely - do not specify as <space>
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Similar Messages

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

MDT2013 - How to deploy Office365 Click-to-Run in Applications?

I used the Office Deployment Tool to create a click-to-run setup to install Office 365 Pro Plus Retail. This works well if I map the network share, and run it with: setup.exe /configure configuration.xml. Unfortunately, I can't seem to get this
to work if I create a new Application in my Deployment Share. Is there a way to do this through MDT 2013? Can you please explain how to do this? I'm an MDT newbie :)
Thank you!

Hi,
From
stackoverflow.com
Let's dissect it. There are three parts:
cd --
This is change directory command.
/d --
This switch makes cd change
both drive and directory at once. Without it you would have to do cd
%~d0 & cd %~p0.
%~dp0 --
This can be dissected further into three parts:
%0 --
This represents zeroth parameter of your batch script. It expands into the name of the batch file itself.
%~0 --
The ~ there
strips double quotes (")
around the expanded argument.
%dp0 --
The d and p there
are modifiers of the expansion. The d forces
addition of a drive letter and the p adds
full path.
So basically it represents the full path to the location from where the script is executed, without having to use the full path like you did. Your script creates a dependency with that specific server or IP address, so whenever the location changes, you'll
need to modify your script. While using the %~DP0 represents the full path.
Also I would not recommend removing the temp directory immediately in the same script but do a cleanup action with another commandline or script afterwards. Reason for this is that the installation of Office-365 takes time, and you don't want to have the
directory removed due to execution of the script, when Office-365 is still installing.
Not having the rmdir in your script forces MDT to wait for the completion of the Office-365 installation, according to my experience.
Cheers!
If this post is helpful please click "Mark for answer", thanks! Kind regards

Office 2010 post SP2 updates deploy with MDT

So I'm looking forward to deploy my office 2010 pro plus (VLK media, activating via KMS host) with MDT, and I have some configs setup using Office Customization Tool to install it. I have the SP2 installer that installs after Office 2010 is installed.
Everything works well, however until i realize that are still a few hundred MB's of update (security patches etc) after the SP2 install. So allowing MDT to install the update on run time is not ideal ( consumes more time and bandwidth) so my question is where
can I get all the post SP2 updates for office pro 2010? (I'm assuming they're all .msp files where i can dump it all into the update folder in office).
Thank you for your feedback!

Hi Jack,
Microsoft Office sustained Engineering team publish news about security updates, public updates, service packs for Office in this site:
http://blogs.technet.com/b/office_sustained_engineering/archive/tags/office+2010/default.aspx
You can find all the Office updates that released each month in this site. However, the updates that applicable to your computer are really depend on your setup environment, not all that released are applicable.
I would suggest you to go to Windows Update, and Check for updates. Windows Update will automatically search updates that are applicable to your computer. You can choose to download the updates manually and save it
to your computer.
Thanks,
Ethan Hua CHN
TechNet Community Support

Office 2013 local Click to Run deployment error

I have downloaded the x32 version of Office2013 to a local deployment share, making use of the Office Deployment tools. The download succeeded. Share is read access for everyone.
When launching the installer from the share, on a x64 Win7 client, the splash screen is displayed, followed by an error after a few seconds which reads "Windows cannot find C:\Program Files\Microsoft Office 15\ClientX64\integratedoffice.exe"
(I need x32 office due to compatibility with our CRM system)
I reviewed the log file, and can confirm that the files do extract to the path listed in the error.
If I open explorer and browse to the path just after launching the installer, I can see that 'C:\Pogram Files\Microsoft Office 15\ClientX64\integratedoffice.exe' exists momentarily, then the entire "Microsoft Office 15" folder is deleted and the
error appears.
I did try delete the reg keys as per the windows fix recommendation, this made no difference.
There are no errors in the OfficeSetup log All move file commands succeed. The last line in the log file reads|:
[4512] ShellExec: C:\Program Files\Microsoft Office 15\ClientX64\integratedoffice.exe CUSTOMIZE RERUNMODE config "configuration.xml" app root\office15\firstrun.exe admin=1
Please help

Try to run the following hotfix and then check if we can install 32 bit version Office on 64 bit hardware without problem.
http://support.microsoft.com/kb/2809219/en-us
Tony Chen
TechNet Community Support

Image engineering of windows xp with WADK 8.1 and deployed with MDT

Hello,
We know that image engineering of Windows XP with WADK 8.1 is not compatible then even if there is any ways to achieve this anyway....(by refresh scenario or any enabling setting).
Thanks
Richa KM

No you need the older version MDT 2012 Update 1 with ADK 8.0 to deploy XP

Keep extra partition on deployment with MDT 2013

hello all,
I am using MDT 2013 to make the
deployment of some workstations in the company,
however they all have an extra
partition (D: \),
doing some testing I noticed that the
MDT does clean the entire
disk, not just on the C:\ drive.
Is it possible to get the MDT format
just drive the system keeping
the extra drive (D:\)?
Thank you.
Eduardo Sena | Microsoft Certified Professional | Embaixador Windows 8 | MVP Windows-Expert IT Pro | [email protected] Blog - www.eduardosena.com.br

if you are just replacing the OS, then I recommend the "Refresh" scenario. Refresh will take an existing Machine and refresh it to a new OS version, persisting the existing partition configuration.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Need to clone an Image created with MDT

Hi All,
I have a custom image which I created in VMWare with MTD 2013. The MDT server is local, I am the only one using it and it is not on the network or available in other sites. I was asked to provide an Acronis or Northon Ghost cloned image so that other admins
can image workstations/laptops without having to ship the device to me, to deploy with MDT. I thought about imaging a workstation and cloning the drive before sysprep starts, but the problem is that I run a task sequence at the end
Final Configuration for MDT 2013 LT created by Jonan, to delete any leftover by MDT (C:\MININT, C:\_SMSTaskSequence) and auto login the first time. I might be wrong, but I believe that the workstation needs to be connected to the MDT server for all task
sequence to complete.
What is the best way to clone this image?

Hi,
The simplest option IMHO would be to completely deploy a simalar machine using MDT and then, after deployment completes, run sysprep manually. Used with the option "shut down", your machine sould be off and in a syprepped state. Than manually create
the Acronis/Ghost image and distribut that.
Even better howerver would be to provide MDT deployment in your other sites. You can utilize DFS Replication to maintain a single point of administration, while still proving a coherent deployment method throughout your network.
Hope this helps,
Regards,
Martin
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Successfully installed Lync 2013 via Click-to-Run, but getting "Choose your product" prompt

After installing Lync 2013 client using method
Click-to-Run "Deploy Office 365 ProPlus from an on-premises location",downloaded Office source is on local hard drive with the
"config.xml" shown below.
I'm getting "Choose your Product" prompt after signing-in. We have Office 365 Enterprise E3 plan and we just wanted to upgrade Lync 2010 to Lync 2013 (not the Basic).
<Configuration>
<Add SourcePath="E:\Temp" OfficeClientEdition="32" >
    <Product ID="LyncRetail">
      <Language ID="en-us" />
    </Product>

</Add>
<Display Level="NONE" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="E:\Temp" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>
Though Lync will continue to work when you close the window. I need to deploy the full 2013 client to several
machines locally.
Thanks.

Hello,
Looks like you‘ve tried a hybrid deployment with Lync 2010 and 2013, right? This might be the reason why Lync 2013 keep prompting to choose your product. Lync 2013 will automatically identify the products that it found for your account which you used to
login Lync 2013.
So, please try to remove any earlier version (Better to remove all Office 2010 suite) on your computer and try a fresh installation again. Let’s see the "Choose your product" prompt would appear again.

Windows 7 deployment with unwanted updates

Hello! I have been deploying with MDT for some time now. My method is to fully update my golden image then run a TS to capture it. When I deploy that WIM in a new TS everything works and comes out fully activated with all post installed applications/configurations.
One issue I do have is that we administer the updates for our clients. They are not able to change any settings for Windows Updates. I have set "protectmypc" parameter in the answer file to 3 to disable the updates but am still getting updates in
queue. Since Group Policy disables settings for the updates they cannot be removed. Where in the process does these updates get checked for and how do I stop this from happening? My TS does not allow this due to the post task being disabled. Someone has to
know what is going on. Regards,
Joseph N. Sunderman | IT Professional

Hi,
How did you write the tab? It shoulbe be the like this below instead of "protectmypc".
<OOBE>
   <HideEULAPage>true</HideEULAPage>
   <NetworkLocation>Other</NetworkLocation>
   <ProtectYourPC>3</ProtectYourPC>
   <SkipMachineOOBE>true</SkipMachineOOBE>
   <SkipUserOOBE>true</SkipUserOOBE>
</OOBE>
In addition, If you use group policy to achieve this, follow this:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/0a46b8ac-0b16-4b87-a881-260c8d5609f7/disabling-windows-update-via-group-policy
Karen Hu
TechNet Community Support

Office Click-to-Run and WSUS

Is there a reason Microsoft chose to subvert WSUS by building a separate update system in Office 2013 click-to-run versions?

Hi,
This is due to the new technology that used to deploy Office. Click-to-Run is a Microsoft streaming and virtualization technology, these streaming and virtualization capabilities are based on technologies in Microsoft Application Virtualization (App-V).
Users don't have to download or install updates manually, the Click-to-Run product seamlessly updates itself in the background.
WSUS is not used in a click-to-run deployment. Office is actually downloaded from cloud (O365 Content Delivery Network (CDN)).
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.

"Offline material is present in this export and will be encoded using the offline media graphic"

This comes up every so often with my renders. I have a 28:30 minute project that is 100% complete. All the files are present locally, and nothing shows as offline or missing. I've gone through the final sequence frame by frame and NOTHING is offline or missing. But when I want to send it out to export, I get the message above in the title.
What's strage is if I ignore it, then sometimes the final render WILL have display the offline graphic even though it didn't display as such in the Premiere timeline.
Often, restarting Premiere and reopening the project irons that glitch out just fine, but I have one particular project that seems to do it every time. I've tried the "import into a new project" trick, but with no luck.
Clueless in Exportville

Hey Guys,
Anybody find a solution to this yet? I am working with Premiere Pro cs5, working with r3d footage, and am having the "offline material is present" error pop up when I try to export using adobe media encoder. Prior to that error box popping up, there is another dialogue box that says that premiere has detected that there is an update to media encoder, I am running media encoder 5.01 and tried to update it but it tells me all files are up to date.
Anyways back to the problem, there is only one shot that is affected and is rendered with the offline media image( this clip also happens to be a different colour(green or teal) than the other clips in my sequence(which are blue or greyish), not sure if this is an indication of anything. I reimported the clip, and re did the edits and then exported just that new small section to see if the error would happen again,this time however, when I did the export, instead of "queue", I just hit "export" ,and the export happened without media encoder actually opening. The file came out fine,even though I had the offline media present pop up, the video was all good. I know I changed a couple of variables in that troubleshooting, so now I am trying the entire sequence with the "export" button instead of "queue" button in the media encoder pop up box, hopefully that will help. The only downside is that it seams like it takes way longer to export this way than in the queue.
I'll report back to let you know if that helps and if I can reproduce the error with the "queue" button.
EDIT
Both exports worked, so it must have been due to the re importing and re editing of the clips, however I still get the error message "offline material is present..." I guess I'll see what happens next time I do an export. Cross my fingers.

Help with Windows 8.1 Update 1 Offline Deployment using MDT 2013

Hi guys,
Hoping that someone has encountered this problem and that there is a simple solution that I am overlooking. Essentially the problem we seem to be having is that after the OS is installed the process of updating the boot partition incorrectly updates
the boot partition on the offline media, rather than on the local disk. Because UEFI requires boot media to be formatted FAT32 and our deployment is a little on the heavy side (upwards of 40GB) we are generating multi-partition boot media and
this seems to be creating a problem, our previous Windows 7 offline media (single NTFS partition) worked perfectly.
By looking at the BDD.log I can see where it appears to examine the potential boot partitions, finds the local disk boot partition and the external usb hdd boot partition and chooses to write to the external. The task sequence restarts the machine shortly
thereafter at which point the device cannot boot with an error "No operating system found."
Thank you in advance for any assistance.

Hello Erik,
it seems to be a bug in MDT.
The routine in ZTIDiskUtility.vbs is looking for the last available boot device:
For each oWMIDiskPart in AllDiskPartEx ( " WHERE Bootable = TRUE or BootPartition = TRUE " )
  oLogging.CreateEntry "Found bootable drive: " & oWMIDiskPart.Path_ , logTypeVerbose
  set oDiskPart = new ZTIDiskPartition
  set oDiskPart.DiskPart = oWMIDiskPart
  set oDisk = oDiskPart.GetDiskObject
  If oDisk.isOSReady( sOSBuild ) then
   set oLogical = oDiskPart.oWMIDrive( bForced )
   If isValidObject(oLogical) then
    If not bBootFiles then
     oLogging.CreateEntry "Found bootable drive (No Boot File Test) [ " & oLogical.DeviceID & " ]: " & oLogical.Path_ , logTypeInfo
     set GetBootDriveEx = oDiskPart
     ' My change
     Exit For
    ElseIf oFSO.FileExists( oLogical.DeviceID & "\ntldr" ) or oFSO.FileExists( oLogical.DeviceID & "\bootmgr" ) or oFSO.FileExists( oLogical.DeviceID & "\EFI\Microsoft\Boot\bootmgr.efi" ) then
     oLogging.CreateEntry "Found bootable drive [ " & oLogical.DeviceID & " ]: " & oLogical.Path_ , logTypeInfo
     set GetBootDriveEx = oDiskPart
    Else
     oLogging.CreateEntry "No boot files found: " & oLogical.Path_ , logTypeInfo
    End if
   End if
  End if
next
I implemented an "Exit For", so you will get the first possible boot drive.

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

Problems with getting O365 Click to Run to install on systems

I have the click to run tool, my customized xml files, and the downloaded office files on a server share external to my CM server.
The tool version is 15.0.4595.1000, and the Office version I have downloaded is 15.0.4605.1003
I created the Application and set the application to call setup.exe /configure configuration.xml.
My current configuration.xml looks like this (I have tried multiple variations of this):
<Configuration>
<Add Version="15.0.4605.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>
My detection method is looking for the following: C:\Program Files\Microsoft Office 15\ClientX64\integratedoffice.exe (I got this detection method from here:
http://www.itsdelivers.com/newsroom/office-365-configuration-manager/. I think this is what is causing the deployment to fail, but not certain)
Once completed, I distributed the content to my DP for testing, and tried deploying it to myself on 2 separate machines; 1 has Office 2010, the other has no Office installed. In each case, I go to my User application portal, and click on the install button
to initiate the O365 Office 2013 download and install to the local client, but I receive the following error in the Software Center:
"There was a problem applying changes to the softwware... etc. The software change returned error code 0x426A(17002)."
I've been unable to find what this error code signifies.
The AppEnforce.log file reads the like this:
+++ Starting Install enforcement for App DT "Deploy Office 365 Pro Plus" ApplicationDeliveryType - ScopeId_D0583E36-6F74-44D4-8436-DB405C987883/DeploymentType_db222e09-5b15-4b3c-abe9-ec845a002a6b, Revision - 14, ContentPath - C:\WINDOWS\ccmcache\l,
Execution Context - User AppEnforce 4/22/2014 8:10:46 AM 6828 (0x1AAC)
    A user is logged on to the system. AppEnforce 4/22/2014 8:10:46 AM 6828 (0x1AAC)
    Performing detection of app deployment type Deploy Office 365 Pro Plus(ScopeId_D0583E36-6F74-44D4-8436-DB405C987883/DeploymentType_db222e09-5b15-4b3c-abe9-ec845a002a6b, revision 14) for user. AppEnforce 4/22/2014 8:10:46 AM 6828
(0x1AAC)
+++ Application not discovered. [AppDT Id: ScopeId_D0583E36-6F74-44D4-8436-DB405C987883/DeploymentType_db222e09-5b15-4b3c-abe9-ec845a002a6b, Revision: 14] AppEnforce 4/22/2014 8:10:46 AM 6828 (0x1AAC)
    App enforcement environment:
Context: User
Command line: setup.exe /configure configuration.xml
Allow user interaction: Yes
UI mode: 1
User token: not null
Session Id: 1
Content path: C:\WINDOWS\ccmcache\l
Working directory: AppEnforce 4/22/2014 8:10:46 AM 6828 (0x1AAC)
    Prepared working directory: C:\WINDOWS\ccmcache\l AppEnforce 4/22/2014 8:10:46 AM 6828 (0x1AAC)
    Prepared command line: "C:\WINDOWS\ccmcache\l\setup.exe" /configure configuration.xml AppEnforce 4/22/2014 8:10:46 AM 6828 (0x1AAC)
    Post install behavior is BasedOnExitCode AppEnforce 4/22/2014 8:10:47 AM 6828 (0x1AAC)
    Waiting for process 5464 to finish. Timeout = 120 minutes. AppEnforce 4/22/2014 8:10:47 AM 6828 (0x1AAC)
    Process 5464 terminated with exitcode: 17002 AppEnforce 4/22/2014 8:10:48 AM 6828 (0x1AAC)
    Looking for exit code 17002 in exit codes table... AppEnforce 4/22/2014 8:10:48 AM 6828 (0x1AAC)
    Unmatched exit code (17002) is considered an execution failure. AppEnforce 4/22/2014 8:10:48 AM 6828 (0x1AAC)
++++++ App enforcement completed (1 seconds) for App DT "Deploy Office 365 Pro Plus" [ScopeId_D0583E36-6F74-44D4-8436-DB405C987883/DeploymentType_db222e09-5b15-4b3c-abe9-ec845a002a6b], Revision: 14, User SID: S-1-5-21-1645522239-854245398-839522115-34966]
++++++ AppEnforce 4/22/2014 8:10:48 AM 6828 (0x1AAC)
Any ideas on how to resolve this?

Well the configuration.xml file has the log path defined as %temp%. I cleared out all the old log files and the cached data, and tried running the application install again, and got the same results. The odd thing is that although in the configuration.xml
file I defined the name to be ="Office365Setup.log", there is no such file with that specified name. I did find a log file under C:\Windows\temp with several error lines that seem to point to a problem accessing the source files:
04/22/2014 09:23:02.863 OFFICECL (0x1538) 0x1518  Click-To-Run 00000 Medium CCS::GetStreamCabs: Caught OException, fallback not allowed for x-none. {"SessionID":"e19b23fb-8b9b-4321-a5f3-662840fa442f","GeoID":"244","Ver":"15.0.4605.1003","ErrorCode":"2","ErrorMessage":"FileNotFound
(Source not reachable.)","AppVErrorSource":"","ErrorType":"FileNotFound"}
I'm logged into the target machine as myself, so I should have full access to the network share when calling it through CM12.
If I run setup.exe /configure configration.xml from a command line, the install succeeds with no errors.
The setup.exe for O365ProPlus, is "special".
When you launch setup.exe in a user-contact (e.g. when you are logged in as yourself), setup.exe launches in the current-user context, but then it spawns a second installer, and that second installer executes in the LocalSystem context (e.g. the computer account
of the client machine), so, you must grant the computer account for the client machine read-access to the configured source. This is typically done by granting "Domain Computers" or "Authenticated Users" read-access to the source folder.
It works when you launch it yourself, because your account is being used, and you will have granted yourself access to the source folder.
This is documented in the O365ProPlus installation documentation.
When using ConfigMgr, you should create the package/application so that it is "download-and-run-local", this way, the source folder for the installation will be in the client cache on the local machine.
http://technet.microsoft.com/en-us/library/jj219423(v=office.15).aspx#PrepareDeploy
! Important:
The computer account for the computer on which you install Click-to-Run for Office 365 products must have read permission to the network share that contains the Office Deployment Tool, the customized Configuration.xml file, and the Click-to-Run for Office
365 product and language files. If you cannot give read permission to the computer account, you can copy the files down to the computer from the network share, and then run Setup from the computer. After the installation is complete, you can delete those files
from the computer.
Logfiles: http://support.microsoft.com/kb/2826852/en
Share permissions: http://blogs.technet.com/b/odsupport/archive/2012/11/20/office-2013-installation-hangs-at-10-percent-when-installing-from-a-network-share.aspx
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Office365(Click to Run) Deployment with MDT Offline Media

Similar Messages

Maybe you are looking for