Support for SQL Server versions for System Center Configuration Manager (current branch)

Support for SQL Server versions for System Center Configuration Manager (current branch)


SQL Server 2008 R2 SP3 No minimum cumulative update
Central administration site, Primary site, Secondary site

SQL Server 2012 SP2 No minimum cumulative update
Central administration site, Primary site, Secondary site

SQL Server 2014 SP1 No minimum cumulative update
Central administration site, Primary site, Secondary site

SQL Server 2012 Express SP2 No minimum cumulative update
Secondary site

SQL Server 2014 Express SP1 No minimum cumulative update
Secondary site

Reference:
https://technet.microsoft.com/sv-se/library/mt589592.aspx

New version of CU2 for ConfigMgr 2012 SP2 and ConfigMgr 2012 R2 SP1

Issues were found with the original CU2 release

If you downloaded and installed CU2 before November 13, 2015 and you are experiencing the issues described in the link below, you should download the updated CU2 media and follow the instructions in KB 3118546 to reinstall the Administrator Console patch.

http://blogs.technet.com/b/configmgrteam/archive/2015/11/10/now-available-cu2-for-sc-2012-r2-configmgr-sp1-and-sc-2012-configmgr-sp2.aspx

CU 2 for ConfigMgr 2012 SP2 and ConfigMgr 2012 R2 SP1 released

CU 2 for ConfigMgr 2012 SP2 and ConfigMgr 2012 R2 SP1 released

https://support.microsoft.com/en-us/kb/3100144

Skipping task sequence [Task Sequence ID] because it is not active yet

I have seen this in smsts.log if you just run trough the wizard when deploying a task sequence as "available".
It doesn't seem to matter if you mark the checkbox "Schedule when this deployment will become available" or not. What does seem to help is to set the available time one hour back in time.

MDT 2013 Update 1 re-released

MDT 2013 Update 1 is now re-released but make sure that you get the correct build
(build 8298 is the new one, build 8290 is the old one)

http://blogs.technet.com/b/msdeployment/archive/2015/09/15/mdt-2013-update-1-re-released-build-8298.aspx

Sometimes impossible to right click deployments in ConfigMgr 2012 R2 SP1

Lately I've seen that it sometimes is impossible to right click any deployments on a ConfigMgr 2012 R2 SP1 site, if you for an example would like to delete a deployment or just view properties for it.
Does not seem to matter if the site is upgraded or newly installed (from SP2 media).
The resolution.. Close the Console and reopen it again.

ConfigMgr news at Microsoft Ignite

At Microsoft Ignite held in Chicago this week a technical preview of the next version of ConfigMgr was released, which is planned to have final release in Q4.

Next week service packs to support Windows 10 for ConfigMgr 2012 and ConfigMgr 2012 R2 will be released.

((ConfigMgr 2007 (SP2, R2, and R3) support for managing Windows 10 is coming via a compatibility pack in Q4 (OS and client deployment will not be supported)).


Read more here: http://blogs.technet.com/b/configmgrteam/archive/2015/05/04/announcing-support-for-windows-10-management-with-system-center-configuration-manager.aspx

ConfigMgr agent policies suddenly dissappear

Just recently I ran into a problem at a customer that runs ConfigMgr 2012 SP1 (no CU).
The problem was that after OSD completes the agent recievs all the policies, but after a few minutes they are gone again.. Leaving the client with only Machine policy and User policy actions.
By waiting (45-60 min) usually makes the policies come back again.

Found this forum thread (even though we are not using HTTPS):
https://social.technet.microsoft.com/Forums/en-US/5a82bcb3-4cde-4eb0-a016-5d4f2a60f2d7/pki-client-starts-to-intialize-then-7-minutes-later-client-agents-go-back-to-disabled-for-upwards

The resolution for me was:
1. Either delete the ConfigMgr object and re-create it prior to deploying the operating system to it.
2. Or add the following run-command line at the end of the task sequence (as suggested in the thread)

cmd /c reg add HKLM\Software\Microsoft\CCM /v "UserPolicyReRequestDelay" /t REG_DWORD /d "6000000" /f

IE 10 on Windows 7 SP1

Installing IE 10 on Windows 7 SP1 x64 has these prerequisites:

wusa "Windows6.1-KB2670838-x64.msu" /quiet /norestart
wusa "Windows6.1-KB2533623-x64.msu" /quiet /norestart
wusa "Windows6.1-KB2731771-x64.msu" /quiet /norestart
wusa "Windows6.1-KB2729094-v2-x64.msu" /quiet /norestart
wusa "Windows6.1-KB2786081-x64.msu" /quiet /norestart


https://support.microsoft.com/kb/2818833

Installation log can be found in C:\Windows\IE10_Main.log

CU4 for Configuration Manager 2012 R2

More information can be found here:
http://support.microsoft.com/kb/3026739