Fragmented indexes in your SQL database can make your application slow down your significantly. And the indexes on SCCM database get fragmented very quickly. Ola Hallengren developed a maintenance solution for SQL that I use on every SQL server I manage, there is a huge performance gain in the SCCM console after optimizing sql database with this solution. This tutorial will go through how to implement his SQL Maintenance Solution and schedule it to run every night. Read More
This series will go through SCCM performance tuning and look at typical issues that may slow down your SCCM server. These are the same guidelines I follow when I install and configure SCCM for my customers.
It is my impression that many SCCM installations are done with default settings, and no maintenance tasks are configured on SQL or the server to increase performance. The result is a horrible slow console to work with. These are things we will look at in this series.
When your brakes fail and lock on your car, a bigger engine is not the solution. A hardware upgrade for your SCCM server may not be the solution to a slow and unresponsive SCCM console. Read More
How to upgrade Configuration Manager 2012 R2 SP1 to Current Branch. This guide is based on my experiences after upgrading several ConfigMgr installations to Current Branch and is a step-by-step guide with everything you need to know to perform a successful upgrade.
This guide applies to the following Configuration Manager 2012 versions:
- SCCM 2012 SP1
- SCCM 2012 SP2
- SCCM 2012 R2
- SCCM 2012 R2 SP1
These are the DHCP options you need for PXE boot to work with SCCM across different networks.
- DHCP Option 66: Boot server hostname or IP address. (sccm.domain.com). If you use hostname, you must use the fully qualified domain name (sccm.domain.com)
- DHCP Option 67: Boot file name. \SMSBoot\x86\wdsnbp.com
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.
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.
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.
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.
- Run configuration manager setup from the start menu. This ensures that setup is run wil the latest updates.
- Select perform site maintenance or reset this site.
- Select Convert from Evaluation to Full Product Version and enter the key.
I had a weird problem with a customer during deployment of Windows 7. Deployment of the image went fine but during the phase “Setup Windows and Configuration Manager” I would get the following error message: TSMBOOTSTRAP.EXE The program couldn´t start, becuase ccmcore.dll is missing. Read More
Today I did some work for a customer who had already installed configuration manager, but they had not set up deployment. I enabled PXE on the distribution point but the clients did not get a repsonse when trying to pxe boot. The first place I check is the SMSPXE.LOG to see what happends but the file did not exist.
My colleage at Atea, Oddvar Håland Moe, have written a script that dumps the password of the network access account from the boot image in plain text. This is why you never enable command line support in your boot images on a production network. Anyone will be able to retrieve the password during PXE boot / OS deployment. Read More
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.
In this guide for System Center Configuration Manager 2012 I will show how to create a limiting device collection structure. We start with All Systems as root, and create one collection for all servers and one for all workstations.