This appears to be a problem with manage-bde on PE. Disabling our task sequence step to encrypt used space resolved this issue.
Thanks, Jeff Jerousek From: [email protected] [mailto:[email protected]] On Behalf Of Jerousek, Jeff Sent: Wednesday, November 18, 2015 8:06 AM To: [email protected] Subject: RE: [mssms] RE: WinPE10 Powershell PXE problem - New ADK We thought we would try it since we don't use refresh task sequences right now. Not sure if it is related yet but we are getting bitLocker error messages on the first boot from WinPE in to Windows. "There are no more bitlocker recovery options on your pc" Thanks, Jeff Jerousek From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Tuesday, November 17, 2015 8:52 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: WinPE10 Powershell PXE problem - New ADK We know, we're investigating. Stay tuned. Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Shane Alexander Sent: Wednesday, November 18, 2015 12:42 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: WinPE10 Powershell PXE problem - New ADK So can see that newer W10 ADK has been released. (hidden in comments in Michael's post here <http://blogs.technet.com/b/mniehaus/archive/2015/11/11/removing-windows-10-in-box-apps-during-a-task-sequence.aspx> ) Seems to be a new issue with this version, as per below. http://ccmexec.com/2015/11/adk-10-0-10586-breaks-the-refresh-scenario-in-configmgr-2012-sp2-r2-sp1/ Does anyone have any further info on this ? (like does MS know ? Will there be a fix ? Will there be a completely new version of the ADK ? ) Thanks. ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: WinPE10 Powershell PXE problem Date: Mon, 9 Nov 2015 23:28:08 +0000 I can duplicate the issue at any time if you would like :) If it helps my support case was: REG:115081813054046 I was told that they reproduced the issue in a lab and escalated it to the "design team" Dewayne From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Monday, November 9, 2015 9:48 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: WinPE10 Powershell PXE problem We are trying to validate this at the moment. It's possible that it will be fixed in an updated ADK due out this month. But to prove that, we need to duplicate the issue first :) The issue has nothing to do with ConfigMgr, it's strictly a Windows PE issue. Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jerousek, Jeff Sent: Monday, November 9, 2015 8:43 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] WinPE10 Powershell PXE problem We are ready to make Windows 10 generally available but would prefer to wait until the powershell problem with PXE booting is fixed. Has anyone heard anything? Do you think it will be with the official release of vNext? Thanks, Jeff Jerousek
