I cannot vbscript :( We had similar issues with "fast" systems failing on "Apply Driver Package" step. Dism would report a sharing violation in its log. I'm not using any PoSH in the bootimage yet. Although a work around for these "fast" systems was to slow it down before driver injection then we speed it back up using powercfg.
-Stephen > On Sep 18, 2015, at 3:37 PM, Jason Sandys <[email protected]> wrote: > > Native code FTW! > > From: [email protected] [mailto:[email protected]] > On Behalf Of Schwan, Phil > Sent: Friday, September 18, 2015 2:05 PM > To: [email protected] > Subject: RE: [mssms] RE: Powershell on WinPE10 (UEFI) > > I’m two-for-two today on replicating issues on this list J Just reproduced > this same issue booting in WinPE 10 x64 with it bombing out on the PowerShell > script we’re using to prompt for a computer name. > > -Phil > > From: [email protected] [mailto:[email protected]] > On Behalf Of Jörgen Nilsson > Sent: Thursday, September 17, 2015 5:13 PM > To: [email protected] > Subject: RE: [mssms] RE: Powershell on WinPE10 (UEFI) > > Hi, > Yes, that is my co-worker in the project we are working on now.. we have done > a lot of testing… we tested the below scenario on a Hyper-V after reading > about the other issue in the ADK with “fast disks” > We use a .NET framework application and a Powershell menu in the deployments > at this customer. > Sent the feedback to Aaron and on Connect as well. > > Jörgen Nilsson > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Niall Brady > Sent: den 17 september 2015 19:47 > To: [email protected] > Subject: Re: [mssms] RE: Powershell on WinPE10 (UEFI) > > I've seen people talking about it on windows-noob, here's an interesting > quote, i can't see any way to limit the cpu via the options in the surface > pro 3 however, > > "so far that's been the case... However, by limiting the available Resources > (CPU), as described above, it works in most cases - that behaviour is > binary... 2 CPU == 100 % failure, 1 CPU == 80 % Success.... " > > http://www.windows-noob.com/forums/topic/12833-sccm-2012-r2-sp1-task-sequence-powershell-adk-10-error-800703e9/page-2 > > On Thu, Sep 17, 2015 at 7:24 PM, Michael Niehaus > <[email protected]> wrote: > We’ve been investigating, but so far there’s no concrete information on the > cause (other than it’s only on x64). > > Thanks, > -Michael > > From: [email protected] [mailto:[email protected]] > On Behalf Of Jerousek, Jeff > Sent: Thursday, September 17, 2015 10:08 AM > To: [email protected] > Subject: [mssms] Powershell on WinPE10 (UEFI) > > Has anyone narrowed down or fixed what’s causing errors with PowerShell on > certain devices in PE 10? > > I’ve only seen the errors on UEFI devices. > > So far Surface Pro 3s and Lenovo T440s are failing to even run PowerShell > from the command line sometimes. > > I’ve gotten memory exception errors and a mscorelib error. > > Turning Legacy mode on for the T440s fixed the problem. Haven’t found a fix > for the SP3. > > Hyper-V Gen 2, Dell 9010, 9020s all work fine. > > Thanks, > Jeff Jerousek > > > > > > > >
