Skip to main content

How to setup the Sccm console on your own PC

Working with the management console for SCCM on the server might be a slow experience, and often it's not a sign for bad performance on the sever itself (even though it might be).

The main reason are that your session are a foreground session, and you will then have low priority on the server system since it as default are setup to prioritize background sessions. This is how it should be on a server so don't go in and change this. The solution are to install the Sccm console on your own pc and run it from there.

Microsoft have documentet this on the TechNet pages:
How to install the configuration manager console
How to Configure DCOM Permissions for Configuration Manager Console Connections

To install the Configuration Manager console

  1. From the product DVD, if the startup screen does not run automatically, double-click splash.hta.
  2. On the Start page, click Configuration Manager 2007.
  3. On the Welcome page, click Next.
  4. On the Available Setup Options page, click Install or upgrade an administrator console and then click Next until you reach the end of the wizard.

To grant Remote Activation permissions to the SMS Admins group

  1. From the Start menu, click Run and type Dcomcnfg.exe.
  2. In Component Services, click Console root, expand Component Services, expand Computers, and then click My Computer. On the Action menu, click Properties.
  3. In the My Computer Properties dialog box, on the COM Security tab, in the Launch and Activation Permissions section, click Edit Limits.
  4. In the Launch Permissions dialog box, click Add.
  5. In the Select User, Computers, or Groups dialog box, in the Enter the object names to select (examples): box, type SMS Admins and click OK.
  6. In the Permissions for SMS Admins section, select the check box to allow Remote Activation.
  7. Click OK twice, and then close Computer Management.

Popular posts from this blog

Changing Windows product key (license) for a MDT OS deployment task

Creating a new OS deployment task in MDT you will be asked to specify product key

That’s easy enough, but what if you type in the wrong key or just want to change it (add it) later? You might even have gotten a new MAK.

That is not as easy, you cannot do it from the graphical interface, you have to do it from one of the configuration files. Well you might to it from graphical interface by typing it in every time deploying a computer gets deployed but that is not a great solution.

MDT - The task sequence has been suspended. LiteTouch is trying to install applications

Every now and then I get this error message when fuelling a computer with MDT:
"The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."

How to get and use the Windows key from UEFI/BIOS

I found myself in the situation that I needed to get the Windows key out from the ACPI in the UEFI bios and preferable get to use it in a task sequence in MDT.

There are different ways of doing this, but I wanted to do this with little code and easy to understand.
There is a nice tool created to get the key on github, created by Christian Korneck, called get_win81key. This tool gives you the key in plane text. You can get it

If I were supposed to do this manually, I now would just take that key and type it in with slmgr command or in the GUI. But I want to do this within a task in MDT.
Testing a couple of solutions without using the get_win8key with my great scripting guru colleague HÃ¥vard ( and figuring out that it cannot be done with default powershell stuff, it needs more code. Therefore, we quickly figured out that some use of the “get_win8key” files is the easiest way, but we need a way of setting the output fro…