Important Config Mgr Hotfix for OS Deployment (KB2910552)

Microsoft has just released an Important Config Mgr Hotfix for OS Deployment issue. The problem was a compatibility issue between Windows XP and the Windows Assessment and Deployment Kit (ADK) 8.1. which prevents deployments when you use WinPe 3.1 boot image with a task sequence in Windows XP update scenarios.

Error message in the Smsts.log file:

Installing boot image to hard drive TSManager datetime 3048 (0x0BE8)
Backing up existing boot system before trying to set up new boot system TSManager datetime 3048 (0x0BE8)
BootLoader::backup: C:\, C:\_SMSTaskSequence\backup TSManager datetime 3048 (0x0BE8)
BootLoader::restore: C:\_SMSTaskSequence\WinPE, C:\ TSManager datetime 3048 (0x0BE8)
Saving bcd store to C:\_SMSTaskSequence\WinPE\boot\BCD TSManager datetime 3048 (0x0BE8)
Executing command line: "C:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR TSManager datetime 3048 (0x0BE8)
CreateProcess failed. Code(0x800700C1) TSManager datetime 3048 (0x0BE8)
Command line execution failed (800700C1) TSManager datetime 3048 (0x0BE8)
Failed to install boot image. 
is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)
Failed to install boot image CCR00004. 
is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)
Failed to reboot the system. Error 0x(800700c1) TSManager datetime 3048 (0x0BE8)
Failed to initialize a system reboot. 
is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)
Fatal error is returned in check for reboot request of the action (Restart in Windows PE). 
is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)

The hotfix applies to sites, admin consoles and clients. 

Don't forget to update your boot images after the update is installed.

Task sequence component version becomes 5.00.7958.1104 after the hotfix installation.

 

The hotfix KB2910552 can be downloaded from http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2910552&kbln=en-us

And you can read more detail at http://support.microsoft.com/kb/2910552

Ports used by Configuration Manager Management Point

Ports used by Configuration Manager Management Point

Management Point <> Domain Controller

Description	UDP	TCP
Lightweight Directory Access Protocol (LDAP)	--	389
LDAP (Secure Sockets Layer [SSL] connection)	636	636
Global Catalog LDAP	--	3268
Global Catalog LDAP SSL	--	3269
RPC Endpoint Mapper	135	135
RPC	--	DYNAMIC

Management Point <> Site Server

Description	UDP	TCP
RPC Endpoint mapper	--	135
RPC	--	DYNAMIC
Server Message Block (SMB)	--	445

Management Point <> SQL Server

Description	UDP	TCP
SQL over TCP	--	1433

Enable Verbose Logging on the SCCM Client for Application Deployment Troubleshooting

You might need to enable verbose logging on the SCCM client for application deployment troubleshooting to be able to see what is happening in more detail.

The default logging level for the client logs information, error and warning level messages. And this is set by a registry value named LogLevel which can be found under

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\CCM\Logging\@GLOBAL\LogLevel (For x86 SCCM Client)

or

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\@GLOBAL\LogLevel

default value of LogLevel is 1, so you can change it 0 (Zero) and restart the SMS Agent service to enable verbose logging. (You'll need to change Administrators permissions to Full on @GLOBAL before changing this value)



Client-side debug logging

If you need more detail you can also enable debug level logging by creating a new key named DebugLogging and a value named Enabled REG_SZ (String) = True under the

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\CCM\Logging\@GLOBAL\ (For x86 SCCM Client)

or

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\@GLOBAL\



Creating new key named DebugLogging



Creating new REG_SZ (String) named Enabled

Haber: SCCM 2012 SQL Server Views dokümantasyonu yayınlandı.

SCCM ürün takımı SCCM 2012 için SQL Server Views dokümantasyonunu yayınladı.

Yeni dokümantasyonu aşağıdaki TechNet adresinde bulabilirsiniz.

Creating Custom Reports by Using SQL Server Views in System Center 2012 Configuration Manager

Dokümantasyon genel olarak üç ana bölüme ayrılmış:

• SQL Server Views in System Center 2012 Configuration Manager – SCCM veritabanında bulunan viewların detaylı bir listesini içermekte.

• Working with Reports in System Center 2012 Configuration Manager – SQL dili ile SCCM raporlarının kavranması ve yaratılabilmesi için bilgi ve örnekler içermekte.

• Technical Reference for SQL Server Views in System Center 2012 Configuration Manager – Kendi SCCM raporlarınız yaratabilmeniz için örnek sorgular ve SQL sunucusu bilgileri içermekte. Ayrıca SCCM de bulunan raporların bir listesi ve bunları kendi raporlariniz için nasıl örnek alabileceğiniz açıklanmakta.

 

News: SQL Server Views documentation for SCCM 2012

SCCM Team has announced the SQL Server Views documentation for System Center 2012 Configuration Manager is now available.

You will find the new documentation on TechNet at the following URL:

Creating Custom Reports by Using SQL Server Views in System Center 2012 Configuration Manager

This documentation is split into three sections:

• SQL Server Views in System Center 2012 Configuration Manager – Provides a detailed list of the views contained in the Configuration Manager SQL database.


• Working with Reports in System Center 2012 Configuration Manager – Provides information and exercises about how to understand and create Configuration Manager reports by using SQL statements.


• Technical Reference for SQL Server Views in System Center 2012 Configuration Manager – Provides sample queries and SQL Server information that can help you to create your own Configuration Manager reports. Also provides a list of the built-in Configuration Manager reports that you can use, or use as the basis for your own reports.

System Center 2012 R2 Configuration Manager Toolkit

A useful announcement from J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division

( http://www.microsoft.com/en-us/download/details.aspx?id=36213 )

The Microsoft System Center 2012 R2 Configuration Manager Toolkit contains fifteen downloadable tools to help you manage and troubleshoot Microsoft System Center 2012 R2 Configuration Manager. The following list provides specific information about each tool in the toolkit.

Note: Items with an * are new in the R2 Toolkit and require Microsoft System Center 2012 R2 Configuration Manager for full functionality.

Server Based Tools

• * DP Job Manager - A tool that helps troubleshoot and manage ongoing content distribution jobs to Configuration Manager distribution points.


• * Collection Evaluation Viewer - A tool that assists in troubleshooting collection evaluation related issues by viewing collection evaluation details.


• * Content Library Explorer - A tool that assists in troubleshooting issues with and viewing the contents of the content library.


• Security Configuration Wizard Template for Microsoft System Center 2012 R2 Configuration Manager - The Security Configuration Wizard (SCW) is an attack-surface reduction tool for the Microsoft Windows Server 2008 R2 operating system. Security Configuration Wizard determines the minimum functionality required for a server's role or roles, and disables functionality that is not required.


• Content Library Transfer – A tool that transfers content from one disk drive to another.


• Content Ownership Tool – A tool that changes ownership of orphaned packages (packages without an owner site server).


• Role-based Administration Modeling and Auditing Tool – This tool helps administrators to model and audit RBA configurations.


• Run Metering Summarization Tool - The purpose of this tool is to run the metering summarization task to analyze raw metering data

Client Based Tools

• Client Spy - A tool that helps you troubleshoot issues related to software distribution, inventory, and software metering on System Center 2012 Configuration Manager clients.


• Configuration Manager Trace Log Viewer – A tool used to view log files created by Configuration Manager components and agents.


• Deployment Monitoring Tool - The Deployment Monitoring Tool is a graphical user interface designed help troubleshoot Applications, Updates, and Baseline deployments on System Center 2012 Configuration Manager clients.


• Policy Spy - A policy viewer that helps you review and troubleshoot the policy system on System Center 2012 Configuration Manager clients.


•   Power Viewer Tool – A tool to view the status of power management feature on System Center 2012 Configuration Manager clients.


• Send Schedule Tool - A tool used to trigger a schedule on a client or trigger the evaluation of a specified DCM Baseline. You can trigger a schedule either locally or remotely.


• Wakeup Spy – A tool that provides a view of the power state of Configuration Manager client computers and which operate as managers or manages.

MS Güncelleme : SCCM 2012 R2 (OSD, PXE, WDS)

MS'in yayınladığı bu SCCM 2012 R2 güncellemesini özellikle OSD bileşenini ve PXE-enabled dağıtım noktalarını kullanıyorsanız kaçırmamanızı tavsiye ederim. zira WDS ve yavaş imaj transferi problemlerinizin çözümü olabilir.

Don't miss this update for SCCM 2012 R2 if you use OSD feature with PXE-enabled DPs. As it might be your saviour for your WDS or slow transfer problems.

Makaleden alıntı.

Özet

Bu güncelleme Microsoft System Center 2012 R2 Configuration Manager'de aşağıdaki sorunları giderir.

Sorun 1

Bir dağıtım noktasında (Dist. Point) a PXE rolü atadığınızda veya bir boot imajında 'Deploy this boot image from the PXE-enabled distribution point' seçeneğini seçtiğinizde WDS yani Windows Deployment Servisi duruyorsa. Ayrıca Windows Uygulama günlüğünde aşağıdaki hatasının alınması.

Faulting application name: svchost.exe_WDSServer, version: 6.3.9600.16384, time stamp: 0x5215dfe3
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a Exception code: 0xc0000005
Fault offset: 0x000000000005f61a
Faulting process id: 0xae4
Faulting application start time: 0x01cec5d767184634
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll

Not Bu problem sadece site sucnularındaki dağıtım noktalarını etkiler.

Sorun 2

İşletim sistemi imajının SCCM 2012 R2 istemcisine indirilme işlemi daha eski versiyona sahip SCCM 2012 istemcilerinden uzun sürüyor olması.

Kurulum

Bu güncelleme Central Admin. ve Primary sitelara, yönetim konsollarına ve istemcilere uygulanır. Site sunucusuna kurduğunuzda size istemci güncelleme paketi oluşturma imkanı da sunar.

Site sunucularına kurulumdan sonra boot imajlarının update edilmesi gerektiğini unutmayın.

Tam makaleye http://support.microsoft.com/kb/2905002 adresinden ulaşabilirsiniz.

 

MS Update for SCCM 2012 R2 (OSD, PXE, WDS)

Don't miss this update for SCCM 2012 R2 if you use OSD feature with PXE-enabled DPs. As it might be your saviour for your WDS or slow transfer problems.

Excerpt from the article.

Summary

This update resolves the following issues in Microsoft System Center 2012 R2 Configuration Manager.

Issue 1

After you enable the PXE Service Point role on an instance of a specific distribution point, or you select the Deploy this boot image from the PXE-enabled distribution point property of a boot image, the Windows Deployment Service (WDS) stops running. Additionally, entries that resemble the following are logged in the Windows Application log:

Faulting application name: svchost.exe_WDSServer, version: 6.3.9600.16384, time stamp: 0x5215dfe3
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a
Exception code: 0xc0000005
Fault offset: 0x000000000005f61a
Faulting process id: 0xae4
Faulting application start time: 0x01cec5d767184634
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll

Note This problem affects only distribution points that are installed on site servers.

Issue 2

When operating system image files are downloaded to Configuration Manager 2012 R2 clients, you may find that the download takes longer than it did in previous versions of Configuration Manager 2012 clients. You may see this behaviour when the target client is running Windows PE or a full Windows operating system.

Installation information

This update applies to Central Administration sites, primary sites, administrator consoles, and clients. Applying this update to a site server will let you create client update packages.

After the update is installed on site servers, any operating system boot images should be updated.

Notes

• All existing media (such as stand-alone, boot, or prestaged) that use existing boot images (default or custom) will have to be re-created.


• To fully fix the problem in Issue 2, the client side .msp file has to be installed during the "Setup Windows and ConfigMgr task by using the PATCH= command.

Full article can be reached at http://support.microsoft.com/kb/2905002

 

ConfMgr SP1 - WSUS Upstream Server

One of the useful things that Configuration Manager 2012 SP1 has brought is allowing usage of WSUS as an upstream server.

Paragraph from http://technet.microsoft.com/en-us/library/jj591552.aspx

At the top-level Configuration Manager site, you can now specify an existing WSUS server as the upstream synchronization source location. During synchronization, the site connects to this location to synchronize software updates. For example, if you have an existing WSUS server that is not part of the Configuration Manager hierarchy, you can specify the existing WSUS server to synchronize software updates.