locked
Windows 10 1709 & Office 2016 (Not click to run) RRS feed

  • Question

  • I have an issue with a Client task sequence performing a build and capture of a base image, Windows 10 1709, with office 2016 (not click to run), does not matter if it is 32 or 64 bit Office.

    Just installing OS & Office and patching then capturing but no updates are found for Office and there should be 50 of them, windows updates install without issue.

    This process is working fine with Windows 10 1703 and the same Office packages, Windows and Office are installed and the updates applied.  

    The only difference between the task sequences is the OS source 1703 or 1709, all other steps are the same.

    Using MDT 6.3.8450.1000

    Monday, February 12, 2018 4:51 PM

All replies

  • Are OS updates being installed?
    Wednesday, February 14, 2018 8:12 PM
  • Yes, OS updates are found and install without issue.
    Wednesday, February 14, 2018 10:00 PM
  • Further I can build the reference machine manually using all the same install sources and order that the MDT task sequence uses and it works as expected, both OS and Office patches are found and installed in both 1703 and 1709.

    So what is happening with the MDT build for 1709 that would prevent Office updates from being found?  But does not happen with a build of 1703? Or what extra setting is needed buried somewhere in the OS?

    Thursday, February 15, 2018 3:48 AM
  • I have the same issue with Windows 10 1709 and Office 2013 32 bits.

    It works as expected with 1703 but not with 1709.1...

    Did you fix the problem ?

    Thursday, May 3, 2018 9:31 AM