Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1218
  • Last Modified:

MDT 2013 and Office 365

I want to build a reference image using MDT 2013 that just has the MS OS 8.1 and Office 365 in it.  I have the operating system part down, but am having some troubles putting O365 in it.  I have the files downloaded fine but when I go to package them into the reference image, I am using a script to get them copied in there.  That is where I run into some trouble.  I am following the information in this link here:  http://renshollanders.nl/2014/02/office-365-automatic-deployment-of-office-365-with-mdt/#comment-674.  What I am having trouble understanding is whether or not I need to include the install.cmd file in the same directory as the source files.  In other words, I have the folder called "O365" and in there I have the downloaded files from Microsoft, as well as the setup.exe and the .xml files that I've configured accordingly.  Would the install.cmd file also go in there as well?  Any help would certainly be appreciated to get this packaged into a reference image that I can capture successfully as I want to import that reference image into ConfigMgr 2012 R2 so that I can deploy it to other systems from there and incorporate other applications, packages, drivers, etc. from ConfigMgr.  I've attached the related files to assist in getting an answer.
install.cmd
install.xml
download.xml
O365-Contents.jpg
0
shawn_snavely
Asked:
shawn_snavely
1 Solution
 
shawn_snavelyAuthor Commented:
I figured this out on my own that the install.cmd file should be in the same location as the other files in that directory.  This was proven by a successful capture of a reference image through MDT 2013.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now