Today I’ve released the newest version 1.3.0 for my ConfigMgr 2012 R2 Prerequisites Installation tool.

95_1

Whats new:

  • Re-designed the user interface to feature tabs instead of buttons
  • Validation checks are now executed on first launch, some minor validation checks still exists for specific parts of the tool
  • Support for Windows Server 2008 R2 has been removed, supported platforms are now Windows Server 2012 and Windows Server 2012 R2

You’ll find the tool and its documentation here:

ConfigMgr 2012 R2 Prerequisites Installation tool 1.2.1

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.

(115)

comments
  • Louis
    Posted at 04:26 June 17, 2014
    Louis
    Reply
    Author

    Great improvement. Thanks for your effort to save a lot of time of global admins and engineers.

    • Nickolaj
      Posted at 13:33 June 18, 2014
      Nickolaj
      Reply
      Author

      Thank you for the kind words Louis! 🙂

      Regards,
      Nickolaj

  • Ioan Popovici
    Posted at 15:45 June 18, 2014
    Ioan Popovici
    Reply
    Author

    Hi,

    This tool seems like a great ideea but it’s not working for me.

    I have a 2012R2 Server fully updated with powershell 4.0.
    I’m running the script elevated, I see the progress bar but the features are not installed. A logging function would be useful here.
    As far as I can tell the script does not get to the Add-WindowsFeature $CurrentFeature part of the script, by the way I had to add Import-ServerManager line in order for the script to work.

  • Odd-Magne Kristoffersen
    Posted at 09:04 June 19, 2014
    Odd-Magne Kristoffersen
    Reply
    Author

    Hi,

    In case no one else has reported it to you; If there is a space in the folder path that is specified when selecting the “Download prerequisites files” the download will fail with a showing the parameters for setupdl.exe. (If my folder is called “SCCM Prerequisites” it fails, works with “SCCMPrequisites”)

    • Nickolaj
      Posted at 09:59 June 19, 2014
      Nickolaj
      Reply
      Author

      Hi Odd-Magne,

      Thank you for pointing that out, you were actually the first!

      I believe that I’ve now resolved this issue. It worked out well in my lab environment when I chose a folder containing spaces. The updated script is now available on the TechNet Gallery. I’d appreciate if you could also verify that it works.

      Best regards,
      Nickolaj

      • Odd-Magne Kristoffersen
        Posted at 10:24 June 19, 2014
        Odd-Magne Kristoffersen
        Reply
        Author

        Hi Nickolaj,

        just tested it now and I can confirm the issue is resolved. Thank you for a great tool.

        Regards,
        Odd-Magne

        • Nickolaj
          Posted at 10:38 June 19, 2014
          Nickolaj
          Reply
          Author

          Thank you for confirming that it has been resolved!

          Regards,
          Nickolaj

  • Mattias
    Posted at 09:21 March 26, 2015
    Mattias
    Reply
    Author

    Hi,

    I had some issues on a site that we connect to over VPN. It would always give the error “The trust relationship between the primary domain and the trusted domain failed.” When running the “Validate-Elevated” function in the script.
    The part in the function that was causing this issue was “$UserWP.IsInRole(“S-1-5-32-544″)”.
    It was possible to “manually” look at the $UserWP variable and find the value. But not when it was written as above.

    So I edited the top part of the “Validate-Elevated” function to look like this:
    ————–
    $UserIdentity = [System.Security.Principal.WindowsIdentity]::GetCurrent()
    $UserWP = [bool](([Security.Principal.WindowsIdentity]$UserIdentity).groups|?{$_.value -eq ‘S-1-5-32-544’})
    if ($UserWP -eq $true)
    ————–

    /Mattias

    • Nickolaj
      Posted at 14:34 March 28, 2015
      Nickolaj
      Reply
      Author

      Hi Mattias,

      Thank you for sharing your findings, it’s highly appreciated!

      Regards,
      Nickolaj

  • Leave a Reply