Configuration Manager 2012 R2 Hotfixes

SCCM 2012 R2 has some hotfixes you might need:

2905002

An update is available for the “Operating System Deployment” feature of System Center 2012 R2 Configuration Manager

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

Issue 1

After you enable the PXE Service Point role (http://msdn.microsoft.com/en-us/library/jj217832.aspx) 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 behavior when the target client is running Windows PE or a full Windows operating system.

2907591

Per-computer variables for imported computers are not read in System Center 2012 R2 Configuration Manager

Per-computer task sequence variables that are defined for imported computers are filtered out of client policies. This prevents the variables from being read during task sequence execution. This problem does not affect per-computer variables that are defined for existing clients.

2907566

November 2013 anti-malware platform update for Endpoint Protection clients

This anti-malware platform update contains the following improvements:

  • Adds anti-tampering functionality to reduce the risk that malware will disable or bypass anti-malware scanning.  For example, access to files and folders that are used by the anti-malware platform can be changed only by trusted system processes or by the anti-malware platform itself.
  • Improves overall performance of the anti-malware platform. Anti-malware performance is improved compared to that of previous platform versions. Improvements were made to scan functionality. These changes involve no configurable effects.
  • Ongoing improvements to Microsoft Active Protection Service (http://technet.microsoft.com/en-us/library/ff823779.aspx) (MAPS) and Dynamic Signature Service (http://technet.microsoft.com/en-us/library/ff823908.aspx) (DSS). These make real-time cloud-based protection easier. Scale and performance improvements were made to the MAPS and DSS systems. Make sure that you opt-in to at least Basic or Advanced MAPS to make sure that you are benefitting from cloud-based protection.

Configmgr 2012 R2 Toolkit

We all know that sometimes the good old SCCM toolkit can help up troubleshoot problems. Well Microsoft has released the updated version for SCCM 2012 R2.

It can be found here: ConfigMgr 2012R2 Toolkit

For the site this information is found:

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.

What is new in System Center 2012 R2

José Rodas has made a nice overview of all the new features of the What’s New in System Center 2012 R2!

Here is the overview:

Configuration Manager R2

  • Deploy and manage Windows 8.1 and Windows Server 2012 R2
  • Configure and deploy WiFi profiles, VPN configurations and certificates
  • Maintenance windows exclusively for updates
  • UI improvements for filtering and automation update deployment rule management
  • Optimizes content distribution, providing clearer summary messages, and offering new distribution point usage data
  • Reports to help with infrastructure planning and troubleshooting
  • Make virtual hard drive (VHD) management easier by enabling the creation, modification and offline servicing of VHDs
  • More information here

Operations Manager R2

  • The Fabric Health Dashboard shows a detailed overview of the health of your private clouds and the fabric that services those clouds
  • Microsoft Monitoring Agent is a new version of Operations Manager Agent that includes full functionality of Visual Studio IntelliTrace Collector for gathering full application profiling traces
  • Synchronize OM alerts and Team Foundation Server (TFS) work items
  • Support for taking IPv6 addresses as input for Network Discovery and display IPv6 addresses in the network-related views
  • Support for monitoring Java applications
  • More information here

Virtual Machine Manager

  • Site-to-site network connections using private IP address
  • Simplified guest IP management
  • Site-to-site NVGRE gateway
  • Enhancements to connectivity options of virtual machines networks to enable most tenant scenarios
  • Live Cloning of virtual machines: Support for a new Hyper-V feature in Windows Server 2012 R2 Preview
  • Enhanced support for Windows Server 2012 Dynamic Memory Features.
  • Ability to create Windows and Linux-based virtual machines and multi-VM Services, from a gallery of templates.
  • More information here

Orchestrator

  • Support for Windows Server 2012 R2
  • Install Service Management Automation web service and up to three (3) Runbook workers
  • Use as part of the Windows Azure Pack for Windows Server configuration
  • Enable use of Runbooks and perform other automation tasks using Windows PowerShell cmdlets
  • Integration Pack for Microsoft SharePoint
  • More information here

Data Protection Manager R2

  • Back up DPM data in System Center 2012 R2 to Windows Azure Backup
  • SQL Server Cluster Support – DPM now supports the use of clustered SQL Server node
  • Virtualized deployment – DPM can be deployed in a virtual environment.
  • Linux virtual machine backup provides support for the protection and backup of Linux virtual machines, in addition to the support already provided for Hyper-V virtual machines
  • More Information here

Other Resources

  • Server and Cloud Platform here
  • Configuration Manager here
  • Windows Azure Pack (WAP) here
  • Cloud OS here
  • News here
  • Note: Service Manager R2 is compatible with Windows Server R2, and will have feature parity with the latest hotfix rollup of Service Manager SP1

 

 

The original post can be found here!

Monitoring ConfigMgr 2012 SP1 via OpsMgr 2012 SP1

This post will describe the setup that is needed in order for your OpsMgr 2012 SP1 environment to monitor your ConfigMgr 2012 SP1 site.
First download the MP via this URL http://www.microsoft.com/en-us/download/details.aspx?id=34709

Execute the installer and you will end up with 4 files:

  • EULA.rtf
  • Microsoft.SystemCenter2012.ConfigurationManager.Discovery.mp
  • Microsoft.SystemCenter2012.ConfigurationManager.Library.mp
  • Microsoft.SystemCenter2012.ConfigurationManager.Monitoring.mp

Import the 3 Management Pack Files for ConfigMgr.

So go the Administration tab –> Management Packs –> choose the Add button from disk.

Then make an Override Management Pack for this MP!

After importing and installing you get a new monitoring view (System Center 2012 Configuration Manager)

For the Configuration Manager monitoring pack to discover objects, you must turn on Agent Proxy on every site server except for the primary site and the central administration site.

It might take some time before your ConfigMgr 2012 SP1 components appear in the OpsMgr 2012 SP1 environment…

After that is done, you can go back to the monitoring tab and choose under SCCM 2012.
Hierarchy Diagram. This will give you a diagram over your SCCM site.

Any alerts (RED X’s) can be clicked and you can drill down to your problem. The MP looks very good and complete.

Be sure to read the manual, a lot of rules are disabled by default. Also performance monitoring is disabled by default.

OpsMgr 2012 Management Packs for Windows Server 2012 and SCCM 2012 SP1

All Management Packs can be found in Pinpoint:

http://systemcenter.pinpoint.microsoft.com/en-US/applications/search/operations-manager-d11?q=

Here is an overview of Server 2012 MPs:

Monitoring Pack for System Center Configuration Manager 2012 (SCCM) http://www.microsoft.com/en-us/download/details.aspx?id=34709
Exchange Server 2013 Management Pack http://www.microsoft.com/en-us/download/details.aspx?id=39039
Windows Server Hyper-V 2012 http://www.microsoft.com/en-us/download/details.aspx?id=36438
Windows Server DNS 2012 http://www.microsoft.com/en-us/download/details.aspx?id=37141
J2EE, JBoss, Tomcat, Weblogic, WebSphere http://www.microsoft.com/en-us/download/details.aspx?id=29270
Windows Server Cluster http://www.microsoft.com/en-us/download/details.aspx?id=2268
Windows Server Network Load Balancing http://www.microsoft.com/en-us/download/details.aspx?id=13302
Windows Deployment Services http://www.microsoft.com/en-us/download/details.aspx?id=36817
Windows Server File iSCSI & Services http://www.microsoft.com/en-us/download/details.aspx?id=34970
Windows Server Backup http://www.microsoft.com/en-us/download/details.aspx?id=36390
Network Devices with Extended Monitoring Capability http://www.microsoft.com/en-us/download/details.aspx?id=26831
Monitoring Pack for Message Queuing http://www.microsoft.com/en-us/download/details.aspx?id=36775

SQL Server 2012 SP1 – MsiInstaller Application Log Entries

If you are on SQL Server 2012 SP1 (11.0.3000) and you notice the Windows Application log filling up with MSI Installer events:

  • Information / Event ID 10000 / RestartManager / Starting session 0 – YYYY-MM-DDTHH:mm:sss.xxxxxxxxxxxxxxxxxx.
  • Information / Event ID 11724 / MsiInstaller / Product: SQL Server 2012 Management Studio — Install started.
  • Information / Event ID 11728 / MsiInstaller / Product: SQL Server 2012 Management Studio — Configuration completed successfully.
  • Information / Event ID 1035 / MsiInstaller / Windows Installer reconfigured the product. Product Name: SQL Server 2012 Management Studio. Product Version: 11.1.3000.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.
  • Information / Event ID 1040 / MsiInstaller / Beginning a Windows Installer transaction: {A7037EB2-F953-4B12-B843-195F4D988DA1}. Client Process Id: XXXX.
  • Information / Event ID 1042 / MsiInstaller / Ending a Windows Installer transaction: {A7037EB2-F953-4B12-B843-195F4D988DA1}. Client Process Id: XXXXX.
  • Information / Event ID 10001 / RestartManager / Ending session 0 started YYYY-MM-DDTHH:mm:sss.xxxxxxxxxxxxxxxxxx.
  • Warning / Event ID 1004 / MsiInstaller / Detection of product ‘{A7037EB2-F953-4B12-B843-195F4D988DA1}’, feature ‘SQL_Tools_ANS’, component ‘{0CECE655-2A0F-4593-AF4B-EFC31D622982}’ failed. The resource ” does not exist.
  • Warning / Event ID 1001 / MsiInstaller / Detection of product ‘{A7037EB2-F953-4B12-B843-195F4D988DA1}’, feature ‘SQL_Tools_ANS’ failed during request for component ‘{6E985C15-8B6D-413D-B456-4F624D9C11C2}’

If you have the above symptoms, please look at this non-security hotfix KB download: http://www.microsoft.com/en-us/download/details.aspx?id=36215.

Do not install if you have already applied any post SP1 hotfixes, such as SP1 CU1.

Installing that fix will bring your SQL version to 11.0.3128, fix the problem with the MSI installer, and it should drop your CPU consumption a bit as well.

Change Management console language Configuration Manager 2012 SP1

 

When starting the management console the language of the local OS will be detected. Then it will search if a language pack is present. When found, the corresponding language will be shown and troubleshooting will become a lot harder. Try searching errors in Dutch 😉 for instance…

Two solutions are possible to show the interface in English:

1. Change your OS  language from your control panel (Regional settings).

2. Rename the language pack folder within the install directory of your Management console. Default language pack locations of SCCM 2012 SP1 Management console:

  • System Center Configuration Manager 2012:
    C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\{language_code}

Close the management console, rename the language pack folder corresponding to your current OS language, restart the console and the default language (English) will be shown.

PXE boost SCCM 2012

PXE booting during a OS Deployment with ConfigMgr 2012 can be a bit slow on a Windows 2008 R2 / 2012 server. This is because Microsoft has set values that will suite most network environments.

But I want SPEED. Now what?

Good news. You can tweak your PXE-enabled Distribution Point!

Add a registry key:

HLKM\SOFTWARE\Microsoft\SMS\DP\RamDiskTFTPBlockSize

With a REG_DWORD value of MAX 4000 Hex!!

Then restart the WDS Service.

I set this value to 2000 Hex and speed is blazing fast!

 

Remember the higher value the more risk of packet loss if you have a bad network connection.
Try this out carefully in your network environment.
If you experience problems, lower the value.

Components in WinPE Boot Image – SCCM 2012 SP1

I was going through the Optional Componets you can select to inject in your SCCM 2012 SP1 Boot image. Then I found this reference to the excellent Microsoft site:

http://technet.microsoft.com/en-us/library/hh824926.aspx

Here is an overview for the components. First the standard and then the optional ones!

Area

Optional component name

Description

Scripting

WinPE-Scripting

WinPE-Scripting contains a multiple-language scripting environment that is ideal for automating system administration tasks, such as batch file processing. Scripts that run in the Windows Script Host (WSH) environment can call WSH objects and other COM-based technologies that support Automation, such as WMI, to manage the Windows subsystems that are central to many system administration tasks.

Dependencies: Install WinPE-Scripting to make sure that full scripting functionality is available when you are using WinPE-NetFX4 and WinPE-HTA. The installation order is irrelevant.

Scripting

WinPE-WMI

WinPE-WMI contains a subset of the Windows Management Instrumentation (WMI) providers that enable minimal system diagnostics. WMI is the infrastructure for management data and operations on Windows-based operating systems. You can write WMI scripts or applications to automate administrative tasks on remote computers. Additionally, WMI supplies management data to other parts of the operating system and products.

Startup

WinPE-SecureStartup

New for Windows 8. WinPE-SecureStartup enables provisioning and management of BitLocker and the Trusted Platform Module (TPM). It includes BitLocker command-line tools, BitLocker WMI management libraries, a TPM driver, TPM Base Services (TBS), the Win32_TPM class, the BitLocker Unlock Wizard, and BitLocker UI libraries. The TPM driver provides better support for both BitLocker and the TPM in this preboot environment.

Dependencies: Install WinPE-WMI before you install WinPE-SecureStartup.

Network

WinPE-WDS-Tools

WinPE-WDS-Tools includes APIs to enable the Image Capture tool and a multicast scenario that involves a custom Windows Deployment Services client. It must be installed if you intend to run the Windows Deployment Services client on a custom Windows PE image.

Optional Components

Area

Optional component name

Description

Database

WinPE-MDAC

WinPE-MDAC supports Microsoft® Open Database Connectivity (ODBC), OLE DB, and Microsoft ActiveX® Data Objects (ADO). This set of technologies provides access to various data sources, such as Microsoft SQL Server®. For example, this access enables queries to Microsoft SQL Server installations that contain ADO objects. You can build a dynamic answer file from unique system information. Similarly, you can build data-driven client or server applications that integrate information from a variety of data sources, both relational (SQL Server) and non-relational.

File management

WinPE-FMAPI

WinPE-FMAPI provides access to the Windows PE File Management API (FMAPI) for discovering and restoring deleted files from unencrypted volumes. The FMAPI also provides the ability to use a password or recovery key file for the discovery and recovery of deleted files from Windows BitLocker Drive Encryption encrypted volumes.

Fonts

WinPE-Font Support-JA-JP

WinPE-Font Support-JA-JP contains two Japanese font families that are packaged as TrueType Collection (TTC) files. MS Gothic is the Windows Japanese user interface font in versions of Windows before Windows Vista®. MS Gothic contains a large character set and embedded bitmaps to ensure legible rendering at small sizes. Meiryo, a font that was introduced in Windows Vista, is designed specifically for use in a Microsoft ClearType® rendering environment. Meiryo does not include embedded bitmaps. Instead, Meiryo relies on hinting instructions to produce legible characters at small sizes. In addition, the module contains two Japanese bitmap fonts, App932.fon and Vga932.fon. The module also contains a bitmap-only TrueType font, Jpn_font.ttf. This font is used on boot screens.

Fonts

WinPE-Font Support-KO-KR

WinPE-Font Support-KO-KR contains three core Korean font families: Gulim, Batang and Malgun Gothic. Gulim is the legacy UI font and, as a TTC file, contains Gulim, GulimChe, Dotum and DotumChe. Batang is the legacy text font and is also a TTC file, containing Batang, BatangChe, GungSuh and GungSuhChe. Malgun Gothic, a font that was introduced in Windows Vista, is designed specifically for use in a ClearType rendering environment. Malgun Gothic does not include embedded bitmaps and instead relies on hinting instructions to produce legible characters at small sizes.

Fonts

WinPE-Font Support-ZH-CN

WinPE-Font Support-ZH-CN contains two Chinese font families that are packaged as TTC files. Simsun is the Simplified Chinese user interface font in Windows versions before Windows Vista. Simsun contains embedded bitmaps to ensure legible rendering at small sizes. The other TTC font is MingLiu. MingLiu has embedded bitmaps and provides support for the Hong Kong Supplementary Character Set (HKSCS). YaHei, a font that was introduced in Windows Vista, is designed specifically for use in a ClearType rendering environment. YaHei does not include embedded bitmaps. YaHei relies on hinting instructions to produce legible characters at small sizes. In addition, the module contains one bitmap-only TrueType font, Chs_boot.ttf. This font is used on boot screens.

Fonts

WinPE-Font Support-ZH-HK

and

WinPE-Font Support-ZH-TW

The Hong Kong and Taiwan optional components contain two Chinese font families that are packaged as TTC files. Simsun is the Simplified Chinese user interface font in Windows versions before Windows Vista. Simsun contains embedded bitmaps to ensure legible rendering at small sizes. MingLiu has embedded bitmaps and provides support for the HKSCS. JhengHei, a font that was introduced in Windows Vista, is designed specifically for use in a ClearType rendering environment. JhengHei does not include embedded bitmaps. JhengHei relies on hinting instructions to produce legible characters at small sizes. In addition, the module contains one bitmap-only TrueType font, Cht_boot.ttf. This font is used on boot screens.

HTML

WinPE-HTA

WinPE-HTA provides HTML Application (HTA) support to create GUI applications through the Windows Internet Explorer® script engine and HTML services. These applications are trusted and display only the menus, icons, toolbars, and title information that you create.

Microsoft .NET

WinPE-NetFX4

WinPE-NetFX4 contains a subset of the .NET Framework 4.5 that is designed for client applications.

Not all Windows binaries are present in Windows PE, and therefore not all Windows APIs are present or usable. Due to the limited API set, the following .NET Framework features have no or reduced functionality in Windows PE:

  • Windows Runtime
  • .NET Framework Fusion APIs
  • Windows Control Library event logging
  • .NET Framework COM Interoperability
  • .NET Framework Cryptography Model

Dependencies: Install WinPE-WMI before you install WinPE-NetFX4.

Network

WinPE-PPPoE

WinPE-PPPoE enables you to use Point-to-Point Protocol over Ethernet (PPPoE) to create, connect, disconnect, and delete PPPoE connections from Windows PE. PPPoE is a network protocol for encapsulating Point-to-Point Protocol (PPP) frames inside Ethernet frames. PPPoE enables Windows users to remotely connect their computers to the web. By using PPPoE, users can virtually dial from one computer to another over an Ethernet network, to establish a point-to-point connection between the computers. The computers can use this point-to-point connection to transport data packets.

Network

WinPE-RNDIS

WinPE-RNDIS contains Remote Network Driver Interface Specification (Remote NDIS) support. WinPE-RNDIS enables network support for devices that implement the Remote NDIS specification over USB. Remote NDIS defines a bus-independent message set and a description of how this message set operates over various I/O buses. Therefore, hardware vendors do not have to write an NDIS miniport device driver. Because this Remote NDIS interface is standardized, one set of host drivers can support any number of bus-attached networking devices.

Windows PowerShell

WinPE-PowerShell3

WinPE-PowerShell3 contains Windows PowerShell–based diagnostics that simplify using Windows Management Instrumentation (WMI) to query the hardware during manufacturing. You can create Windows PowerShell–based deployment and administrative Windows PE–based tools. In addition to deployment, you can use Windows PowerShell for recovery scenarios. Customers can boot in Windows RE and then use Windows PowerShell scripts to resolve issues. Customers are not limited to the toolsets that run in Windows PE. Similarly, you can build scripted offline solutions to recover some computers from no-boot scenarios.

WinPE-PowerShell3 has the following known limitations:

  • Windows PowerShell remoting is not supported. Any cmdlets that have remoting functionality will return an error.
  • The Windows PowerShell Integrated Scripting Environment (ISE) is not supported.
  • Windows PowerShell 2.0 is not supported.

Dependencies: Install WinPE-WMI > WinPE-NetFX4 > WinPE-Scripting before you install WinPE-PowerShell3.

Windows PowerShell

WinPE-DismCmdlets

WinPE-DismCmdlets contains the DISM PowerShell module, which includes cmdlets used for managing and servicing Windows images.

For more info, see Deployment Imaging Servicing Management (DISM) Cmdlets in Windows PowerShell.

Dependencies: Install WinPE-WMI > WinPE-NetFX4 > WinPE-Scripting > WinPE-PowerShell3 before you install WinPE-DismCmdlets.

Windows PowerShell

WinPE-StorageWMI

WinPE-StorageWMI contains PowerShell cmdlets for storage management. These cmdlets use the Windows Storage Management API (SMAPI) to manage local storage, such as disk, partition, and volume objects. Or, these cmdlets use the Windows SMAPI together with array storage management by using a storage management provider. WinPE-StorageWMI also contains Internet SCSI (iSCSI) Initiator cmdlets for connecting a host computer or server to virtual disks on external iSCSI-based storage arrays through an Ethernet network adapter or iSCSI Host Bus Adapter (HBA).

Dependencies: Install WinPE-WMI > WinPE-NetFX4 > WinPE-Scripting > WinPE-PowerShell3 before you install WinPE-StorageWMI.

Recovery

WinPE-WinReCfg

WinPE-WinReCfg contains the Winrecfg.exe tool, and it enables the following scenarios:

  • Boot from x86-based Windows PE to configure Windows RE settings on an offline x64-based operating system image.
  • Boot from x64-based Windows PE to configure Windows RE settings on an offline x86-based operating system image.

Before Windows 8, the Winrecfg.exe tool was included in the Windows 7 OEM Preinstallation Kit (Windows OPK).

Setup

Winpe-LegacySetup

Winpe-LegacySetup contains all Setup files from the \Sources folder on the Windows media. Add this optional component when you service Setup or the \Sources folder on the Windows media. You must add this optional component together with the optional component for the Setup feature. To add a new Boot.wim file to the media, add the parent WinPE-Setup, either of the children (WinPE-Setup-Client or WinPE-Setup-Server), and Media optional components. Media Setup is required to support Windows Server® 2008 R2 installation.

Setup

WinPE-Setup

WinPE-Setup is the parent of WinPE-Setup-Client and WinPE-Setup-Server. It contains all Setup files from the \Sources folder that are common to the client and the server.

Setup

WinPE-Setup-Client

WinPE-Setup-Client contains the client branding files for the parent WinPE-Setup optional component.

Dependencies: Install WinPE-Setup before you install WinPE-Setup-Client.

Setup

WinPE-Setup-Server

WinPE-Setup-Server includes the server branding files for the parent WinPE-Setup optional component.

Dependencies: Install WinPE-Setup before you install WinPE-Setup-Server.

Storage

WinPE-EnhancedStorage

New for Windows 8. WinPE-EnhancedStorage enables Windows to discover additional functionality for storage devices, such as encrypted drives, and implementations that combine Trusted Computing Group (TCG) and IEEE 1667 (“Standard Protocol for Authentication in Host Attachments of Transient Storage Devices”) specifications. This optional component enables Windows to manage these storage devices natively by using BitLocker.

Cumulative Update (CU1) Pack for System Center 2012 Configuration Manager Service Pack 1 (SP1)

Microsoft has released the first Cumulative Update (CU1) Pack for System Center 2012 Configuration Manager Service Pack 1 (SP1).

This CU1 is available here!

An overview:

Issues that are fixed

Administrator Console

  • A Discovery Data Record (DDR) that contains organizational unit (OU) paths that are longer than 220 characters are not processed. The DDM.log file on the site server contains event messages that resemble the following:

CDiscoverySource::ValidateSchema – array property User OU Name cannot expand size so rejecting.


CDiscoverDataManager::ProcessDDRs – Unable to update data source.

  • The Allow clients to use a fallback source location for content option is missing from the Distribution Points tab of the package properties.

Site systems

  • Replication Configuration Manager incorrectly reports the link status as Degraded and then reports the status as Activeone minute later.
  • Site replication fails after a site database is restored to a new server. Additionally, the Rcmctrl.log file contains the following error message:

ERROR: Received unhandled SQL exception, printing info and throwing it again. This will be retried in next cycle.
SqlException number: [8115]
ERROR: Exception message: [Arithmetic overflow error converting expression to data type int.~~The ‘spGetChangeTrackingMinValidVersion’ procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead.]


Device management

  • The Configuration Manager client cannot be installed on devices that contain newer ARM processors. Additionally, the following error message is logged in the DmClientSetup log file:

    Fail to get the CAB file name because of unsupported processor type: 0

Software updates

  • The Allow clients to share content with other clients on the same subnet option in the properties of a Software Update Group Deployment is ignored. Additionally, the DataTransferService.log file contains the following message:

    Not using branch cache option.

  • When a custom port is configured for software updates, an Internet only client may append the custom port to the URL for the Windows Update service. Additionally, when the custom port is set to 880, log entries that resemble the following may be logged in the DataTransferService.log file:

    UpdateURLWithTransportSettings(): OLD URL – http://download.windowsupdate.com/msdownload/update.cab

    UpdateURLWithTransportSettings(): NEW URL – http://download.windowsupdate.com:880/msdownload/update.cab

  • The Schedule Updates Wizard does not list content for Windows Server 2012. For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:

    2793237 FIX: The Schedule Updates Wizard does not list content for Windows Server 2012 in System Center 2012 Configuration Manager Service Pack 1

Client

  • The MicrosoftPolicyPlatformSetup.msi file is now correctly signed.
  • The selection of multiple targeted applications in Software Center will fail if the calendar region is set to Arabic (Saudi Arabia). Additionally, Software Center displays the following error message:

    Software Center cannot be loaded. There is a problem loading the required components for Software Center. You can try launching Software Center at a later time. If the problem continues, you can contact your helpdesk.

  • The hardware inventory on a computer that is running a 32-bit version of Windows Server 2003 R2 may cause the Wmiprvse.exe process to exit unexpectedly. Additionally, when you view the results of the fault, the details of the fault resemble the following:

    Faulting application wmiprvse.exe, version 5.2.3790.4455, faulting module msvcr90.dll, version 9.0.30729.6161, fault address 0x00056b1d

  • PXE support is added for IA-32 EFI computers.

PowerShell

  • When the Clear-CMPxeDeployment cmdlet is run, you receive the following error message:

    The method or operation is not implemented.

  • When the Update-CMDistributionPoint –DeploymentTypeName cmdlet is run, you receive the following error message:

    Key not Found Exception.

  • When the New-CMDeviceCollection cmdlet is run, the refreshschedule parameter is not defined in theNewByLimitName parameter set.
  • When the New-CMDeviceCollection cmdlet is run together with the LimitingCollectionName option, the cmdlet is unsuccessful. Additionally, you receive the following error message:

    Unable to cast object of type ‘Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlArrayItems’ to type’System.Management.ManagementBaseObject’.

  • When the .GetType method is used for the object that is returned by the New-CMSchedule cmdlet, the method is unsuccessful. Additionally, you receive the following error message:

    The adapter cannot get property “GetType” for instance of SMS_ST_RecurInterval.

  • When the Import-CMComputerInformation -CollectionName “All Systems” -ComputerName “Computer01” -MacAddress “xx:xx:xx:xx:xx:xx command is run, the command is unsuccessful. Additionally, you receive the following error message:

    WARNING: The collection All Systems does not exist or is not suitable for adding the new device.

Functionality that is updated

PowerShell

Help for PowerShell is updated for the cmdlets that are included in Configuration Manager Service Pack 1 and in this cumulative update. In a PowerShell environment, use the Update-Help –Module ConfigurationManager cmdlet to retrieve the latest Help information from Microsoft.

The following cmdlets are added to the PowerShell module:

  • Add-CMDistributionPoint
  • Import-CMAntiMalwarePolicy
  • Import-CMDriver
  • New-CMAppVVirtualEnvironment
  • New-CMMigrationJob
  • New-CMPackage
  • New-CMSoftwareUpdateAutoDeploymentRule
  • New-CMTaskSequence
  • New-CMTaskSequenceInstallUpdateAction
  • New-CMTaskSequenceMedia
  • New-CMUserDataAndProfileConfigurationItem
  • Remove-CMTaskSequenceInstallUpdateAction
  • Set-CMTaskSequenceGroup
  • New-CMTaskSequenceGroup
  • Remove-CMTaskSequenceGroup
  • Set-CMApplicationCatalogWebsitePoint
  • Set-CMAppVVirtualEnvironment
  • Set-CMClientPushInstallation
  • Set-CMClientSetting
  • Set-CMDistributionPoint
  • Set-CMDriver
  • Set-CMEndpointProtectionPoint
  • Set-CMEnrollmentPoint
  • Set-CMEnrollmentProxyPoint
  • Set-CMHierarchySetting
  • Set-CMManagementPointComponent
  • Set-CMOperatingSystemImageUpdateSchedule
  • Set-CMOutOfBandManagementComponent
  • Set-CMReportingServicePoint
  • Set-CMSite
  • Set-CMSoftwareUpdateAutoDeploymentRule
  • Set-CMSoftwareUpdatePointComponent
  • Set-CMStateMigrationPoint
  • Set-CMStatusSummarizer
  • Set-CMSystemHealthValidatorPointComponent
  • Set-CMTaskSequence
  • Set-CMTaskSequenceInstallUpdateAction
  • Set-CMUserDataAndProfileConfigurationItem
  • Start-CMDistributionPointUpgrade