Answered Deploying an MSU file with GPO

  • Thursday, June 03, 2010 5:41 AM
     
     
    I have a hotfix for an issue in Windows 7 and need to get it out to several hundred domain computers.  Can I use Group policy to get it there or will need to manufacture something??

All Replies

  • Thursday, June 03, 2010 7:09 AM
    Moderator
     
     Answered

    Hi,

     

    As I know, deploying software through Group Policy requires .MSI format. You may re-package the update file from .MSU file to .MSI file, then deploy it through Group Policy. You can visit the following KB for detailed steps:

     

    How to use Group Policy to remotely install software in Windows Server 2003 and in Windows Server 2008

     

    Meanwhile, MDT supports distributing updates using .MSU format. Perhaps you could use MDT to manage Windows Updates.

     

    Best Regards

    Dale

  • Thursday, August 05, 2010 7:41 PM
     
     

    i've got the same issue: looking for a way to deploy a *.msu-Hotfix to ~100 Win7-Clients....the solution stated above does NOT help.

    Did you find a working solution Bracer ?

     

    Ove 

  • Tuesday, September 07, 2010 4:50 AM
     
     

    Not yet I Haven't.  Still looking tho.

  • Thursday, August 04, 2011 10:15 PM
     
     Proposed Answer
    you colossal piece of shit. first you say "oh yeah just repackage it" without giving an instruction as to HOW, then YOU mark it as the "answer". way to go champ.
  • Wednesday, October 12, 2011 8:20 PM
     
     Proposed Answer

    On Windows 7, you can use the following command to create a batch file or cmd file and use it as a startup script:

     wusa.exe \\server\Share\Windows6.1-KBxxxxxx-v3-x86.msu /quiet /norestart

    For more information on this command visit : http://support.microsoft.com/kb/934307

    On XP, you can you the following command to create a batch file or cmd file and use it as a startup script:

    \\server\Share\WindowsXP-KBxxxxxxxx-x86-ENU.exe /quiet /norestart  (you cannot use the msu, have to convert it to a exe)

    You can use WMI filters and deploy the scripts using the same policy

    For Windows 7 : select * from Win32_OperatingSystem where Version like "6.1%" and ProductType = "1" 

    For Windows XP : select * from Win32_OperatingSystem where Version like "5.1%" and ProductType = "1"

    For more information on these WMI filters visit : http://technet.microsoft.com/en-us/library/cc754488%28WS.10%29.aspx

     

    • Proposed As Answer by StBenedicts Monday, March 05, 2012 4:26 PM
    •  
  • Monday, March 05, 2012 10:48 PM
     
     Proposed Answer

    I lol'd and agreed. 

    Also, better late than never...  For remotely doing this, the commenter who said wusa is the way to go is correct.  To do it remotely you will need to use psexec with the -s switch. 

    psexec \\servername -s wusa.exe \\server\Share\Windows6.1-KBxxxxxx-v3-x86.msu /quiet /norestart

    • Proposed As Answer by brgnewman Tuesday, March 06, 2012 4:46 AM
    •