SCCM Clients Stuck In Provisioning Mode

I have seen sccm clients stuck in provisioning mode several times during OSD deployment. The typical symptoms of clients stuck in provisioning mode are:

  • Client shows: client certificate none, it should be self-signed or PKI
  • Client does not receive any policy
  • The computer have just been installed with a task sequence.

To verify if it is actually stuck in provisioning mode we need to take a look at the registry of the client.

Read More

Remove the CD and do not boot from CD – extra restart during deployment

Deployment took an extra restart after selecting which task sequence to use. This happend because multiple task sequences where published to the computer and the boot image for the selected task sequence where not used initially when booting.

extrareboot1

I fixed this by making the task sequences use the same boot image. I know this might not be the ideal solution for everyone but the problem with this extra reboot is different version of bootimages beeing used.

 

Configuration Manager build numbers

How to upgrade ConfigMgr from evaluation version to full version

This is how you upgrade from evaluation version to full version of configmgr 2012. You enter the product key during the install phase of configuration manager 2012.

  1. Run configuration manager setup from the start menu. This ensures that setup is run wil the latest updates.
  2. Select perform site maintenance or reset this site.
  3. Select Convert from Evaluation to Full Product Version and enter the key.

How to manage Windows Server 2008 in Server Manager

The new server manager in Windows Server 2012 can also manage Windows Server 2008. This is how you set it up in 3 simple steps:

Windows Server 2008 with SP2 and Windows Server 2008 R2 with SP1

  1. Install .NET Framework 4.0 (Download from Microsoft)
  2. Install Windows Management Framework 3.0 (Download from Microsoft)
  3. Run the following command in powershell to enable and configure Windows Management Framework “winrm quickconfig

Read More

Log files to troubleshoot ConfigMgr 2012 Client installation

These log files are useful to troubleshoot the errors with the configuration manager client.

Log files on server.

  • ccm.log – Client push installation log file.
  • chmgr.log – Client health manager log file.
  • cidm.log – Changes to the client settings by the Client Install Data Manager (CIDM).

Log files on client.

  • ccmsetup.log – Installation, client health, client upgrade and client removal. Very useful to troubleshoot client installation errors.
  • ccmrepair.log – Repeair activites by the client.
  • client.msi.log – Logs from the installation process of client.msi application.

Also check out this TechNet article for more information about log files sin System Center Configuration Manager 2012.

SCCM: How to limit distribution point packages to one drive.

When you install a distribution point, you specify which drive it should use. When this drive is full, the distribution point will automatically start using another drive.

For drives where you don’t want any packages from the distribution point, create an empty file with the name “NO_SMS_ON_DRIVE.SMS” and place it in the root of the drives.

This trick works on both SCCM 2007 and SCCM 2012.