Share This Post

SCCM 2012 SP1 Uber Console

How would you like to install the SCCM 2012 SP1 Console/Help files/Toolkit, MDT 2012 Update 1, DaRT 8.0, PowerShell Right Click Tools, and the SCCM Client Center all with one click? I have created a task sequence that will do just that. Deploying out the SCCM administration tools can be difficult for new users of SCCM. A big part of my job is to train new SCCM administrators. I’ve gotten tired of repeating the same steps with every new customer. So I put this together and made it public so the whole SCCM community can benefit. Download the Task sequence and follow the instructions below to get the Uber Console loaded in your environment.

Note: This is only compatible with SCCM 2012 SP1 and the following OS’s Windows 7, Windows 8, Server 2008R2, and Server 2012.

Step 1. Download and extract the Uber Console

The Uber Console consists of a Task sequence and several applications that will be responsible for installing the console and the third party add-ons. It will also contain a package that will be used to attach MDT deployment shares. Extract this zip file to a location that you wish to use as the source location for all of the applications. For example, I would extract it to the E:\Content\ folder on my SCCM server. Note the Attach MDT package is separate from the Task Sequence because an MDT deployment share has to be created under the user account and not system.

Uber Console Download:

Step 2. Populate the Uber Console content folder

You may have noticed that the Uber Console is very small in size. This is because I have stripped out all of the copy righted content. All that is in those content folders are readme files and scripts that I have created. Read each readme file to determine what content needs to be placed in the folder. Do not continue on to the next step until every folder has been populated with content.


Step 3. Import the Uber Console Task Sequence and Attach MDT Package

Only continue with Step 3 after you have completed populating all of the content folders from step 2.

Open your SCCM console and go to: Software Library-> Operating Systems -> Right click on Task Sequences -> Select Import Task Sequence. Follow the wizard to import the task sequence and all of the corresponding applications.


From within the SCCM Console go to: Software Library-> Right Click on Packages-> Select Import. Follow the wizard to import the package.


Step 4. Modify the Applications and Packages to Work with your Environment

You will need to only modify two of the imported items.

First modify the “Configuration Manger Console Installer” installation program. The defaults are as follows:

ConsoleSetup.exe /q TargetDir=”C:\Program Files\ConfigMgr” EnableSQM=0

For more information on the console setup parameters see:



Next modify the “Attach MDT Deployment Share” program. This package contains a PowerShell script that is used to attach an MDT deployment share to an existing share. This is very useful for technicians when DaRT integration is enabled because it gives them easy access to the monitoring section of the MDT Deployment share. Replace the parameters to match the deployment share information of your environment.

Powershell.exe -executionpolicy bypass -file .\AttachDS.ps1 -Sharename “DS777” -SharePath “\\SCCM01\DeploymentShare$” -Description “My MDT Share”

For information on how to create a deployment share:



Step 5. Deploy the “Uber Console” task sequence and “Attach MDT” package

First, I recommend creating a collection for these two new deployments. For example, I created a new collection and populated it with just the computers I want to receive the console.

Next, run the deploy wizard for the Uber Console task sequence. It is always important to remember to distribute the content to the DP’s from within the wizard if you have not already done so. I also find it best to just make the deployment available (instead of required) so the technicians can decide when and where they want the console installed.


Now run the deployment wizard for the Attach MDT program.


Step 6. Run the deployments for the “Uber Console” task sequence and “Attach MDT” package

It is important to run the Uber Console task sequence before running the Attach MDT package. This is because the Attach MDT package relies on the MDT Console to already be installed. From a client with the available deployments open the SCCM 2012 Software Center and run the Uber Console then run the Attach MDT Package.


Remove/Add applications from the Uber Console Install:

It is very easy to add or remove any applications from the Uber Console install since it is a task sequence. Edit the task sequence to remove/add what you would like. Below is the layout of the default task sequence:


Product Information for the included applications:

System Center Configuration Manger Help Updater:

ConfigMgr Toolkit 2012 Update 1:

MDT 2012 Update 1:

DaRT 8.0 Information:

How to integrate the DaRT 8.0 remote viewer with your task sequences:

PowerShell Right Click Tools:

SCCM Client Center:

Known Issues:

Windows 7 and Server 2008R2: DaRT 8.0 is not fully compatible. However the Remote Viewer application is needed when DaRT 8 is integrated into OSD. So I created a script (already in the Uber Console) that will install DaRT 8 with “/a” and then copy the contents to the older DaRT 7 path. For more information:

Windows 8 and Server 2012: The SCCM 2012 SP1 Help files will not install unless .Net 3.5 is installed. I didn’t include .Net 3.5 in the Uber console because of the complexity it would have added for such a little gain. If you wish to deploy .Net 3.5 to those OS’s please see the following:

Share This Post


  1. Nice!

  2. Hi Brett, Thanks for the article. I’m having an issue distributing content for the PowerShell Right Click Tools. The following error message shows when I check on the content status:

    Distribution Manager failed to access the source directory ‘\\sccm-unv\e$
    \Content_2f14559a-9d48-4387-b49e-1db75d84e3a3” for content
    “Scopeld_EDB82410-9C 54-411C -AEF5-C64731191F8E/
    DeploymentType_33ac4599-cfOd-41f6-9270-eS2bed6dddl6/1” (content ID =
    Possible cause: Distribution Manager does not have sufficient rights to the
    source directory.
    Solution: Verify that the site server computer account has at least Read access to
    the directory you specify as the source directory.
    Possible cause: There is not enough disk space available on the site server.
    Solution: Verify that there is enough free disk space available on the site server.

    Is anybody else having the same problems? All other packages seem to have been distributed without issue. We definitely have enough space, and the folder permissions look the same as the other folders.

  3. Yes I need to update my scripts for the new Power Shell Right Click tools. A new version was released 2 days ago and the install is completely different.

    For now I would just remove the Power Shell Right Click Tools from the task sequence until I can get a new silent install scripted. It’s on my to do list.

  4. Great news Rebecca! Ryan updated the Power Shell Right Click Tools so my install script will work. Download the newest right click tools and try again. Also if you get the error “failed to access the source directory” check the NTFS permissions on the folder.

  5. Hello!

    Some problem with deploy Uber SCCM 2012 SP1 Console Install Task Sequnces – Unable to make change to your software: None of the applications you tried to install began installation successfully. Investigate the reason for the installation failures and then try to install the applications again…. I tray install in Windows 8 x64

    Please solve this problem.


Leave a Reply