SCCM vNext Technical Preview 3 was released a few hours ago.
This release adds the following additional capabilities:
- Diagnostics and Usage Data
- Service a server cluster
- Support for SQL Server AlwaysOn for highly available databases
- Deploy Windows Business Store applications
- App deployment to Windows 10 devices with on-premises MDM
- Compliance settings for Windows 10
- Improved workflow for creating mobile device configuration items
- Updates for Windows 10 in-place upgrade
- Updates for bulk enrollment of Windows 10 devices with on-premises MDM
Download System Center Configuration Manager vNext Technical Preview 3;
Official blog from ConfigMgr team;
Detailed description of new features System Center Configuration Manager vNext Technical Preview 3.
FAILURE (5616): 1: Verify BCDBootEx
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to save environment to (80070057)
Failed to run the action: Install Operating System.
Unknown error (error 000015F0; Source: Unknown)
The execution of the group (Install) has failed and the execution has aborted. An action failed.
Operation aborted (Error: 80004004: Source: Windows)
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015F0: Source: Unknown)
Task Sequence Engine Failed: Code: enExecutionFail
Task sequence execution failed with error code: 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005.
Possible solution: check spaces in UNC path MDT DeploymentShare and delete them if they are:
Yesterday Microsoft released Cumulative Update 1 for System Center 2012 R2 Configuration Manager Service Pack 1 and System Center 2012 Configuration Manager Service Pack 2.
After applying Cumulative Update 1 Configuration Manager client package is updated automatically, so you can install the latest version (5.0.8239.1203) of SCCM client during operating system deployment of by Client Push Installation method. Existing clients will install this cumulative update through Automatic Client Upgrade:
“Classic” packages with client update files are created as well: