Today I’ve released a new version of my MDT Factory Tool. Since this version include some fixes for WSUS and Application import, I suggest that you grab it right away if you’ve been using the older version.

Whats new:

  • I’ve noticed that there’s a bug in the WSUS API when you create an automatic approval rule. When you try to execute it, the updates eligable for approval is not approved. Instead I’ve chosen to re-write the parts where the tool created a automatic approval rule, to leverage the ‘Default Automatic Approval Rule’ instead.
  • Fixed a bug where if you’ve tried to import some applications and the SourcePath was not successfully validated, the tool would still try to import those applications even though they weren’t added to the DataGridView.

You’ll find the tool and its documentation here:

MDT Factory Tool 1.0.0 – Create reference images

You can download the tool from the TechNet Gallery here:

Download from TechNet Gallery

Nickolaj Andersen
Principal Consultant and Enterprise Mobility MVP. Nickolaj has been in the IT industry for the past 10 years specializing in Enterprise Mobility and Security, Windows deployments and Automation. In 2015 Nickolaj was awarded as PowerShell Hero by the community for his script and tools contributions. Author of ConfigMgr Prerequisites Tool, ConfigMgr OSD FrontEnd, ConfigMgr WebService and a frequent speaker at user groups.

(85)

comments
  • Sergey
    Posted at 09:21 September 7, 2015
    Sergey
    Reply
    Author

    Good day
    https://yadi.sk/i/QLcOSVsViuteA
    There’s a problem. WSUS setup does not understand the path to the database. The screenshot below shows how it looks. Please help.

  • Sergey
    Posted at 09:44 September 7, 2015
    Sergey
    Reply
    Author

    Good day. a little checked the logic of the program and found a bug in it. Put the wrong path to the database WSUS and received when checking – approx. Picture attached.

    https://yadi.sk/i/-S1KMwIdiuvfq

    • Nickolaj
      Posted at 13:51 September 7, 2015
      Nickolaj
      Reply
      Author

      Hi Sergey,

      You’re indeed right, that’s a bug.

      I’ll release an updated version as soon as possible.

      In the mean time I think that you can simply add the following before row 1091:

      $WSUSContentFolder = $TBWSUSContentFolder.Text

      Regards,
      Nickolaj

  • Dahasan
    Posted at 17:37 February 26, 2016
    Dahasan
    Reply
    Author

    Hey Boe, Great tool!I am curious if there is a way to exrpot a list of all NotIntalled’ patches, with the KB and Title, along with a list of all computers that require it.I am stuck patching some servers before I can finish rolling out SCCM and I require a report for my governance team. Any help would be appreciated.I have made some headway with Get-WSUSUpdatePerClient, but I seem to be unable to limit it to a specific WSUS Computer Group \All Computers\Servers\Infrasctructure Dev and Test’

  • Leave a Reply