SCCM 2012 with MDT 2012 integration

When trying to create a MDT 2012 Client Task Sequence i received an error "access to the path is denied"..

The solution was to delete the following file:
 C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Scripts\Autorun.inf

SCCM 2012 RTM supported SQL versions

SQL Server version	Central administration site	Primary site	Secondary site
SQL Server 2008 SP2 with Cumulative Update 9	x	x	x
SQL Server 2008 SP3 with Cumulative Update 4	x	x	x
SQL Server 2008 R2 with SP1 and Cumulative Update 6	x	x	x
SQL Server Express 2008 R2 with SP1 and Cumulative Update 4	Not Supported	Not Supported	x

Back from USA

The Microsoft Management Summit 2012 in Las Vegas was a great event!
I'm now filled with knowledge and inspiration!

MMS 2012 Las Vegas here we come!

Tomorrow I'm bound for Las Vegas to attend the 2012 Microsoft Management Summit.
Hope to get lots of new SCCM 2012 tips and trix to update this site with.

Enable PXE on Distribution Point

Steps how to enable PXE on a distribution point in SCCM 2012

1. Add the Windows Deployment Services role to the server by using server manager.

2. From the SCCM Console: \Administration\Overview\Distribution Points
          Right Click the DP and select properties.
          Under the tab “PXE”, check “Enable PXE support for clients”
          Check “Allow this distribution point to respond to incoming PXE Requests”

3. From the SCCM Console: \Software Library\Overview\Operating Systems\Boot Images
          Right click the boot image and select “Properties”
          On the “Data Source” tab mark
          “Enable binary differential replication” and
          “Deploy this boot image from the PXE service point”

 

Package status turns from successful to in progress

I have noticed that when you distribute a package to a DP it shows up fairly quickly in the console as 100% "successful" (green). If I then start the execution of a task sequence it will fail due to a package that's not available on the DP..
If I go back to the console,  after a while the package status turns over to "in progress" (yellow) instead and won't turn back to "successful" (green) again for 5-10 min..
Cannot find anything obvous in the logs about SCCM resending the package..

Hope this is a RC bug..

MININT- as computername second time computer installs

Experienced an odd behavour when using a boot.iso with unknown computer support enabled.

If I added a computer to the SCCM console and installed the computer, the computer got the same name as I gave it when importing the computer (correct).
But when I reinstalled the same computer a second time it was named with a MININT- name instead..
Created a new boot.iso without unknown computer support (not using it anyway) and the problem went away. The computer now gets the name entered in the SCCM console every time.

Application with dependencies during Task Secuence

Configuration Manager 2012 (RC2) can handle installation of applications with dependencies during Task sequence execution. (Not possible with Configuration Manager 2007)

New location for the Client Logs

In SCCM 2012 RC2 the client logs are stored in C:\Windows\CCM\Logs

SCCM 2012 RC2 on separate instances on the same SQL Server

My SCCM 2012 RC2 environment consists of one CAS and one Primary site.
To make this work in a common SQL hotel with seperate instances you need to make shure that they don't communicate with the database on the same ports.

During the SCCM 2012 site installation you need to set:
On the CAS-Server "SSB Port" = 4022
On the P01-Server "SSB Port" = 4023

To configure this, go to the SQL Server:
Start SQL Server Configuration Manager
Go to SQL Server Network Configuration
Protocols for CAS-Instance - TCP/IP - Properties - IP Addresses - Set TCP Port = 1433 on all
Protocols for P01-Instance - TCP/IP - Properties - IP Addresses - Set TCP Port = 1434 on all

Done

First post..

Hello,

My name is Henrik Ericsson and I work for a company called Enfo Zipper in Stockholm Sweden.
I will blog about my, and my customers, experience from using Configuration Manager 2012.
Starting today, with Configuration Manager 2012 RC2.

Welcome!