Had an interesting issue with a client on a fresh install today. SQL Server Management Studio would crash as soon as you tried to open a new query window or open a saved query. Also if you tried to view the local server in Server Manager it was crash as well.
After some searching, I came across the following KB which fixed both my issues. This occurred on 2 separate servers that were fresh installs.
The issue apparently has to do with the winspool.drv
Pretty nasty bug out there right now with 32-bit Windows 7 and Software Updates. If you are struggling with getting your clients to download/install updates. Check your WindowsUpdate.log, if you see the following error:
WARNING: ISusInternal::GetUpdateMetadata2 failed, hr=8007000E
Then I’d strongly encourage you to apply the following KB/Hotfix (KB3050265).
Here is also a great article explaining what is going on from the ConfigMgr Team Blog. Read that article here.
After applying this update in my client environment, patches immediately started working again.
Issues that are fixed
- The Continue on error check box is not selected under Task Sequences when an Install Software step and a Virtual Application package are defined as the source. This affects only task sequences that are migrated from Configuration Manager 2007 to System Center 2012 Configuration Manager.
- The Task Sequence Agent (TSAgent) does not use the logging-related values that are set in the following registry subkey on a client computer:
- 2961924 A command-line action that has a linked package doesn’t start in System Center 2012 Configuration Manager
- 2923078 Reporting Services installation fails on System Center 2012 Configuration Manager Service Pack 1 that has SQL Server 2014 installed
- 2931044 Discovery Data Manager slows when it rebuilds .ncf files on startup in System Center 2012 Configuration Manager Service Pack 1
- Applications cannot be changed or copied after they are migrated from one System Center 2012 Configuration Manager site to another site. Messages that resemble the following are logged in the Distmgr.log file after you try to make changes:
Package <PkgID> is in Pending state and will not be processed
- 2952686 You cannot install an application by using stand-alone media in System Center 2012 Configuration Manager Service Pack 1
Configuration Manager client
- The SMS Agent Host service may stop unexpectedly in an environment that uses multiple overlapping boundary groups that are configured for automatic site assignment. The ScanAgent.log file contains an entry that resembles the following:
[FATAL ERROR] Invalid params exception was raised.
- When you view the Primary Device that is associated with a user, you may see other devices that have the same name, even if they are associated with a different user.
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.
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:
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.
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. To update boot images after the hotfix is applied, follow these steps:
- In the Configuration Manager console, click Software Library.
- In the Software Library workspace, expand Operating Systems, and then click Boot Images.
- Select the boot image that you want to update.
- Right-click and then select the Update Distribution Points action.
Note This action updates all distribution points and may have an adverse effect on an environment that contains many distribution points.
- Repeat steps 3 and 4 for all boot images that have previously been distributed.
- 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.
- For more information about how to update boot images, see the How to Manage Boot Images in Configuration Manager topic on the Microsoft TechNet website.
Issues that are fixed
Note These issues do not affect Microsoft System Center 2012 R2 Configuration Manager.
The SQL Update part of the Cumulative Update 3 installation fails when the date format on the instance of Microsoft SQL Server is defined in the DD/MM/YYYY format.
Additionally, the CM12-SP1CU3-KB2882125-X64-ENU.log file contains entries that resemble the following:
Msg 242, Level 16, State 3, Procedure #SP_CICategoryInstance_00065D65, Line 20
The conversion of a varchar data type to a datetime data type resulted in an out-of-range value.
The statement has been terminated.
Note The overall installation of the cumulative update is complete and has a warning status.
The All Windows RT and All Windows RT 8.1 Preview entries should not appear in the supported platform list for new configuration items.
Task sequences that contain Windows 8.1 as a condition on the Options tab generate an exception when they are changed or accessed. Details of the exception are displayed in text that resembles the following:
Exception has been thrown by the target of an invocation.
If a Configuration Manager Task Sequence that leverages the Install Software Updates step installs a software update that triggers multiple reboots, after successfully running the Install Software Updates task, the task sequence can fail with the following error message:
“Task Sequence environment not found”
The first restart that is initiated by the software update is controlled by the task sequence. However, the second restart request is initiated by a Windows component (typically, Component-Based Servicing) and therefore is not controlled by the task sequence. As the second reboot is not controlled by the Task Sequence, the Task Sequence execution state is not saved before the restart. When the task sequence resumes after the second restart, no state is available to continue successfully.
To resolve this issue, we recommend that you apply any updates that require dual restarts by using the usual Software Updates feature of Configuration Manager instead of using task sequences. The following software updates were reported as requiring multiple restarts. This article will be updated as more updates are reported.
2862330 MS13-081: Description of the security update for 2862330: October 8, 2013
2771431 A servicing stack update is available for Windows 8 and Windows Server 2012
2871777 A servicing stack update is available for Windows RT, Windows 8, and Windows Server 2012: September 2013
2821895 A servicing stack update is available for Windows RT and Windows 8: June 2013
2545698 Text in some core fonts appears blurred in Internet Explorer 9 on a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2
2529073 Binary files in some USB drivers are not updated after you install Windows 7 SP1 or Windows Server 2008 R2 SP1
Recently had an issue at a client site where the Software Update Point was failing to fully sync even though the updates appeared to be in the console. This was a on Server 2012 box with ConfigMgr 2012 SP1 CU2.
The error we were receiving was:
Error: The Microsoft Software License Terms have not been completely downloaded and cannot be accepted.
Client uses a proxy server for web authentication and this error appears to be specific to that situation. Turns out there is a hotfix available from Microsoft that address the issue. We applied the hotfix and everything was sync’ing fine after that.
WSUS server can’t connect to Windows Update in Windows Server 2012
Hope it helps someone else out.
Probably one of the biggest fixes in CU2 is the support of WinPE 3.1 images for OSD. So if you were holding off on SP1 because of WinPE 4.0 and old hardware, that roadblock has been removed.
Another nice change is including a KB that addresses the "in progress – waiting for content" bug.
The binaries for System Center Configuration Manager 2012 and System Center Endpoint Protection 2012 have been updated to correct some minor issues. The binaries have been updated at the Download Center, and also on the Technet and MSDN download sites. For Configuration Manager 2012 SP1, the updated download release of SP1 includes the following hotfix:
Installation error 0x800b0101: System Center 2012 Configuration Manager Service Pack 1 client
For Endpoint Protection, the new binaries include fixed files (Linux/iOS) that were corrupt in the initial release.
MSDN Download Link:
Technet Download Link:
Microsoft System Center 2012 Service Pack 1 Configuration Manager – Clients for Additional Operating Systems
This means if you downloaded the binaries prior to today (1/25) – you will likely need to re-download them.