Deployment Solution

 View Only
  • 1.  Surface Laptop 5 WinPE Issues

    Posted Jul 03, 2023 09:19 AM

    Hi,

    Just a quick question.

    Any one currently deploying Microsoft Surface Laptop 5?

    We just received a device, and is trying to deploy it. (of course the new drivers has been added to WinPE). But we see an issue where the WMI service dies, and all commands to try and fix it does not work. (trying to restart services, IPconfig and so on.) Further more, the powershell module also dies, which is kind of a problem, when we deploy the image both with dism and with some underlying powershell scripts.

    When some of our scripts has been executed, then the error "An error has occurred that was not propery handled. Additional information is shown below. The Winodws powershell process will exit."

    Also it appears to be some kind of memory issue, since we now get the message: "There is not enough free memory to run this program". Even when only 1,5GB memory is used...

    So.... Anyone seen this error before?



  • 2.  RE: Surface Laptop 5 WinPE Issues

    Posted Jul 04, 2023 05:04 AM

    So I did some more testing.

    It appears that it is Powershell that some how "breaks" WMI.

    I have tested with a "clean" WinPE (from ITMS/CMS installation), and as soon as I execute some different scripts, where it is a combination of powershell commands calling WMI it suddenly breaks.

    It appears that the issues are in both WinPE10 and WinPE11. I even tried generating a "non" ITMS/CMS WinPE to see if the issue would be there. And it seems so…

    Not sure if some KB needs to be injected into the boot.wim file to correct the issue. It is the only model that we have experienced this issue. So it has to be something new…




  • 3.  RE: Surface Laptop 5 WinPE Issues

    Posted Jul 05, 2023 07:30 AM

    Ok. So... I found the culprit...

    Apparently MS have added a few extra digits in the serial number, thus getting close to the limit of naming lenght of the device.

    Our script, reads what computername the device should be assigned, based on the prestage of the device. (through a webservice)

    In this case the device needs to be prefixed with a few extra characters, and that resulted in the naming going over the limit of 15 characters...

    Have not ran into this problem since early windows 7 days  :-)

    So to all of you deploying Surface Laptop 5's where you are perhaps prefixing the device name. Be aware of the limit of 15 Charactes