SCCM 2012: Intel driver, scale to fullscreen with fixed screen resolution

In some cases, you may want to set a fixed screen resolution for all clients. Then you will have the Challenge with the Picture was not scaled to fit the monitor. In my case, it was due to a Intel driver setting. I found no registry setting, no documented API or command line reference, so as a last measure I had to use keyboard shortcuts, as the Intel software listens for ctrl + alt + f11 to change monitor scaling. I created a simple script to find the Intel video adapter in WMI and used sendkeys to utilize the keyboard shortcut. This script must be run at user log on.


set WshShell= WScript.CreateObject(“WScript.Shell”)
‘Connect to WMI
Set objWMIService = GetObject(“winmgmts:\\.\root\cimv2”)
Set colItems = objWMIService.ExecQuery(“Select * from Win32_VideoController”)
Dim VideoCard
‘Get Video Card
For Each objItem in colItems
VideoCard = objItem.Description
‘Check if VideoCard is Intel then Send Ctrl + Alt + F11
If VideoCard = “Intel(R) HD Graphics” then
WshShell.SendKeys “^%{F11}”
end if
Set colItems = Nothing
Set objWMIService = Nothing

SCCM 2012: Detailed Port Information

If you struggle to read the official documentation and identify witch ports to open for System Center 2012 Configuration Manager.

Odd-Magne Kristoffersen has done the job for everyone and created a Excel spreadsheet documenting all the ports.

Please read his blogpost and download the spreadsheet.


Microsoft Documentation:

SCCM 2012: System Error Codes for troubleshooting failed application installations.

SCCM will Return System Error Codes from failed Application installations. Microsoft have published the complete list With for Developers for troubleshooting purposes.

Example Return codes:

  • 1633 (0x661) – This installation package is not supported by this processor type. Contact your product vendor.
  • 1603 (0x643) – Fatal error during installation.

Complete list:


SCCM 2012: How to run an application after Task Sequence have completed

In some cases you may have to run a script or application after completion of your task sequence. In my case this was related to pre-staging of applications (more of this later).

Anyway Michael Murgolo have written a great blogpost describing how to implement this. If you are not in a hurry i recommend you to wait for SCCM SP1 RTM then you will have this included.

If you are in a hurry like me..

SCCM 2012: dynamic app install Policy download failed

Using System Center 2012 Configuration Manager together with the MDT integration and the new UDI wizard I discovered that using comma (,) in the application name will cause the deployment to break.  

Make sure the application is marked for dynamic app install Policy download failed, hr=0x80004005. The operating system reported error 2147500037: Unspecified error


SCCM 2012: User device affinity with MDT 2012

Cameron has written a great blog post explaining user centric deployment with SCCM 2012 and MDT 2012.

Read up

Another one from John Vintzel

SCCM 2012: I want to access content directly from distribution point!

If you have been using SCCM 2007 and now SCCM 2012 for a while you may see that your deployment time has increased, if you used the “Access content directly from distribution point option” in SCCM 2007.

Microsoft introduced the new content library, the idea is to save space by saving all files in a library but only save identical files once, and refer to the location for all other instances of the file. The idea is good, but it comes with a price. All content stored in the library must be extracted during installation. This slows down the deployment meaning all files will have to be downloaded by the client.

If you want to change this and store your content in a share, you can. Please be aware that this has a cost in disk space.

On all your content in the task sequence meaning packages, boot, images, drivers even the configuration manager agent, select “copy the content in this package to a package share on distribution points.”

After doing this you will be able to select “access content directly from..” on your deployments.

Be aware!

This limits you to use the old package model. So you have to decide what’s most important to you. A workaround could be to use the MDT integration for installing apps. Then you will have the best from both worlds.

System Center 2012 Private Cloud

Microsoft has released a whitepaper where they compare private cloud solutions from Microsoft and VMware. If you are curious about private cloud technology and what Microsoft has to offer, i recommend reading this whitepaper.

Download it her:



SCCM 2012: Service Pack 1 Beta 1, download now!

Want to deploy Windows 8 and Server 2012 with SCCM, start the preparation in your test/lab environment now!

  • Deployment and management of Windows 8 and Windows Server 2012
  • Distribution point for Windows Azure to help reduce infrastructure costs
  • Automation of administrative tasks through PowerShell support
  • Management of Mac OS X clients and Linux and UNIX servers
  • Real-time administrative actions for Endpoint Protection related tasks


SCCM 2012 – Application Catalog: Cannot Connect to the application server

If you get this error: Cannot connect to the application server. It may be because you are missing WCF activation.

  • Start Server Manager > Features > Add Features > .NET Framework 3.5.1 Features > WCF Activation > HTTP Activation.


  • Open Command Prompt (start > run > cmd)
  • CD %windir%\Microsoft.NET\Framework64\v4.0.30319
  •  run: aspnet_regiis.exe /iru




Free E-book – Deploying Windows® 7

Free E-book from Microsoft press. Great book to get a better understanding of the Windows 7 deployment platform.

Chapter 3 Deployment Platform . . . . . . . . . 85
Chapter 4 Planning Deployment . . . . . . . . . 113
Chapter 5 Testing Application Compatibility . . . . . . . . . 139
Chapter 6 Developing Disk Images . . . . . . . . . 179
Chapter 7 Migrating User State Data . . . . . . . . . 223
Chapter 8 Deploying Applications . . . . . . . . .  247
Chapter 9 Preparing Windows PE . . . . . . . . . 273
Chapter 10 Configuring Windows Deployment Services . . . . . . . . . 293
Chapter 11 Using Volume Activation . . . . . . . . . 335
Chapter 12 Deploying with Microsoft Deployment Toolkit . . . . . . . . . 355

SCCM 2007 – Change PXE Cache Expire

Great blogpost by Chaohao Xu regarding PXE Cache Expire in SCCM 2007 SP2

“If a Configuration Manager client has received and started an advertised operating system deployment task sequence, attempting to start another operating system deployment advertisement within a certain period of time might result in the deployment being ignored and failed to start. In this case, the client ignores the PXE boot request and falls back to the local hard disk when booting up.”

Create a custom Windows Pe Image

  • Mount Wim file: Dism /Mount-Wim /WimFile:C:\winpe_x86\ISO\sources\boot.wim /index:1 /MountDir:C:\winpe_x86\mount
  • In between step (see walktrough from Microsoft for more detailed information). In my case i updated the hosts file in the image.
  • Commit Wim file: Dism /unmount-Wim /MountDir:C:\winpe_x86\mount /Commit


Windows 8 ADK:


SCCM 2012 – The Import Computer information Wizard completed with errors.

If you get this error when trying to import computer information into the SCCM database, it’s probably because a object already exists with the same MAC address. Look for objects imported by various discovery methods. Or if you have enabled unknown computer support, you may have a “unknown computer” object in conflict with the computer object you are trying to import.


SCCM 2007 – Client firewall exceptions

Client Requests

In order for client computers to communicate with Configuration Manager 2007 site systems, you must add the following as exceptions to the Windows Firewall:

  • TCP Port 80 (mixed mode)
  • TCP Port 443 (native mode)

Remote Control

In order to use the remote tools features of Configuration Manager 2007, you need to allow the following ports:

  • TCP port 2701
  • TCP port 2702
  • TCP port 135

Client Push Installation

In order to successfully use client push to install the Configuration Manager 2007 client, you must add the following as exceptions to the Windows Firewall:

  • File and Printer Sharing
  • Windows Management Instrumentation (WMI)

SCCM 2012 – Task sequence deploy button is grayed out

If the deploy button is grayed out after you have made ​​your first build and capture task sequence, it may be because you have not yet created a valid client package.

  • Navigate to: “Software Library” > “Application Management” > “Packages”
  • Right click the packages node > select “Create package from definition”

  • Right Click the “Configuration Manager Client Upgrade” package > Select “Distribute Content”

  • Navigate to: “Software Library” > “Operating System Deployment” > Right click your task sequence > Edit
  • Update the “Setup Windows and Configuration manager” step with your new Client Package.

  • You should now have the “Deploy” option available.

SCCM 2007 – Remote SQL

Having SCCM database hosted on a remote SQL server rather than installing a dedicated instance on a primary site server often have a performance upside.

To succeed with the installation we have some perequsites:

  • SQL Server must have registered SPN
  • SCCM Admin user (used to run installation) must have sysadmin permissions on the SQL instance
  •  SCCM Admin user  (used to run installation) must be members of builtin/Administrators on the SQL server.
  •  Computer account of the primary site server should be member of builtin/Administrators
  • (If you are installing on a cluster, these perequsites must be applied on both nodes)

If you get this error:

Setup either could not verify that short file name (8.3) support is enabled on the computer specified for site system installation or the server could not be contacted to determine short file name support information. No further prerequisite checking rules can be evaluated on the specified system. Setup cannot continue.

please verify that the user account used to run the sccm perequsite checker have local administrator permissions on the SQL server. Also check that short file name support is not disabled.