locked
Installing windows management framework 3.0 on windows 7 through MDT 2013 RRS feed

  • Question

  • I'm trying to install WMF 3.0 on win 7 sp1 through MDT 2013 and it keeps failing. I tried to include it in my task sequence at various levels with no luck. 

    - Failed installing it as a offline package( which I later found it wouldnt work, coz it has .net 4.0 as its pre-requisite)

    - Created a custom task for installing .net 4.0 and underneath added another task to install WMF 3.0. The installation of .net 4.0 succeeds but WMF wouldnt install.

    Could someone please shed some light on this?

    Friday, May 30, 2014 10:23 PM

Answers

  • Resolved the issue. I had to specify the right command line for installation. Thanks for your help anyway.
    Sunday, June 1, 2014 8:50 AM

All replies

  • what does the logfile say? (maybe it needs a reboot between .NET FW 4.0, and WMF 3.0 ?)

    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!)

    Saturday, May 31, 2014 7:46 AM
  • Haven't tried it yet. Will give it a go. Can you point me the location of the logfile to look at?
    Saturday, May 31, 2014 10:19 AM
  • Haven't tried it yet. Will give it a go. Can you point me the location of the logfile to look at?

    most of the patchpackages for components/products out of the VS team, seem to write to %windir%\temp

    e.g. c:\windows\temp\

    "Microsoft Visual C++ 2010  x86 Redistributable Setup_20140418_091143376-Microsoft Visual C++ 2010  x86 Redistributable - 10.0.30319-MSP0.txt"

    "ASPNETSetup_00001.log"

    "dd_NDP45-KB2931368-x64_decompression_log.txt"

    etc


    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!)


    • Edited by DonPick Saturday, May 31, 2014 10:27 AM
    Saturday, May 31, 2014 10:25 AM
  • Resolved the issue. I had to specify the right command line for installation. Thanks for your help anyway.
    Sunday, June 1, 2014 8:50 AM
  • Could you please specify the command line???


    Alex Olver

    Thursday, May 14, 2015 12:17 AM
  • Could you please specify the command line???


    Alex Olver

    For WMF 4.0, see the "Install instructions" section on MS DLC https://www.microsoft.com/en-us/download/confirmation.aspx?id=40855

    For WMF 3.0, which is also an MSU, it's probably a very similar command line.

    For .NET Framework, command lines, check here:
    http://blogs.msdn.com/b/astebner/archive/2009/04/16/9553804.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!)

    Thursday, May 14, 2015 9:58 AM
  • Could you give me the command line for WMF 3.0?

    Also how do we add to MDT as a command line an application?


    Alex Olver

    Thursday, May 14, 2015 11:24 PM
    • On x86-based computers that are running Windows 7 SP1 or Windows Server 2008 R2 SP1, run Windows6.1-KB2819745-x86.msu /quiet.
    • On x64-based computers that are running Windows 7 SP1 or Windows Server 2008 R2 SP1, run Windows6.1-KB2819745-x64-MultiPkg.msu /quiet.
    • On computers that are running Windows Server 2012, run Windows8-RT-KB2799888-x64.msu /quiet

    Just try the same /quiet switch for WMF 3.0

    If you like scripting you can make a vbscript wrapper or a simple batch file and import it as an application. Then add the application to your sequence.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Friday, May 15, 2015 2:25 AM
  • So would this work?


    Alex Olver

    Friday, May 15, 2015 2:39 AM

  • Alex Olver

    Friday, May 15, 2015 3:08 AM
  • Does it install manually? If not, the problem is something else and not necessarily your TS. Your error code means MDT doesn't know what went wrong. I'd really recommend importing it as an application into MDT and then adding it as an application to your TS rather than a run command line. When an application fails to install, first make sure you can manually install it using the same command line so you don't waste time troubleshooting the wrong thing.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Friday, May 15, 2015 1:04 PM
  • Yea so my image works and this is the only thing I had added.

    I have added it as an application now so I will try that...


    Alex Olver

    Sunday, May 17, 2015 10:49 PM