In my organisation only a few members of staff need to have access to the SCCM console, for obvious reasons I want to keep that to a minimum, never too good to let the patients run the asylum. When someone needs access they generally need more than the basic console. So I created an Uber console with all the addons and extensions that are needed.

I’m using the Powershell App Deployment Toolkit (PADT) created by Seán Lillis and Dan Cunningham, its one of my favourite resources and I pretty much package everything using this now. If you have not used it before, in a nut shell its a powershell wrapper and is incredibly powerful.

BTW I understand that I could have just created a deployment with many dependencies but for this deployment i prefer PADT

The PADT folder structure, the installation files go into the Files folder.

Whats installed

System Center Configuration Manager Console
The files are located on the site server \\SERVER\SMS_CM1\tools\ConsoleSetup

System Center Configuration Manager Support Center
Pretty handy for looking at logs.

NowMicro – Recast Right Click tools
Brilliant set of right click tools that every admin should use.

System Center 2012 R2 Configuration Manager Toolkit
Pretty handy set of tools including Content Library Explorer, CEViewer etc

Microsoft Deployment Toolkit (6.3.8443.1000)
I use MDT OSD task sequences, this is also used for DaRT(on the site server).

System Center Configuration Manager Cmdlet Library
Who can live with out PowerShell

Microsoft DaRT
Great for remotly viewing machines when in the PXE phase of OSD

Microsoft DaRT Console Extension
Our buddy Nickolaj Andersen @NickolajA wrote this console extension.

MDT Intergration with the SCCM Console
Johan Arwidmark @jarwidmark wrote this using Powershell to automate the integration with the SCCM console.

What you could add

Log Launcher
This is a brilliant new tool created by our WMUG colleague Robert Marshall

Clean Software Update Groups console extension for ConfigMgr
This is another one by Nickolaj @NickolajA

Dell Warranty Tool 3.0 console extension for ConfigMgr
Nickolaj @NickolajA is just showing off now but this one shows the dell warranty status.

Get BitLocker Recovery Password from ConfigMgr
This allows you to see the recovery key from AD

LAPS Extension for SCCM 2012 R2 +
LAPS is higly recommended for most enterprises see Maurice’s post about it


This is using the Powershell Application Deployment Toolkit.

Creating the Deployment

You can add detection methods for the MSI’s

I added Microsoft Windows Assessment and Deployment Kit as a dependency as its needed for MDT but is also deployed separately so is not included in the package.


Users get a nice progress bar so they can see whats happening, it can also be branded with your company logo/colours etc



  • Shelby Price
    Posted at 4:00 pm 6th January 2017
    Shelby Price

    Awesome post. If nothing else, it’s a good look at different extensions. I didn’t even know about the LAPS extension. Put that sucker in immediately. In case this post serves as a curation of SCCM extensions, you might consider adding the SCCM Servicing Extension.

    • Terence Beggs
      Posted at 9:20 am 9th January 2017
      Terence Beggs

      Hello Shelby, i thought that extension was replaced by the update and servicing node, i think it only works for Windows 7 and 2008 R.

  • Jason Sandys
    Posted at 8:04 pm 6th January 2017
    Jason Sandys

    Nice post. No need to do the PowerShell cmdlets though if doing ConfigMgr CB — they’ve unified the releases again so you’ll always get the latest with the latest CB version.

    • Terence Beggs
      Posted at 12:24 am 8th January 2017
      Terence Beggs

      Thanks Jason forgot about that. Will update the post.

  • Aaron Whittaker
    Posted at 7:10 am 8th March 2017
    Aaron Whittaker

    Great post. I am using the PSAppDeployToolkit for all my installations here and have been for a while. With the latest version you dont need to specify the deployment type in the install program as install is now the default. Your install/uninstall would become “Deploy-Application.exe” and “Deploy-Application.exe Uninstall” respectively.

    Something else you might look at adding is PathCopyCopy ( and Ditto ( They speed up my packaging to no end.

  • Leave a Reply