ECM Task Sequenz Windwos 10 22H2 problems
Hello all,
it's been a while since I created Client OS Task Sequences and now I'm a bit surprised that I can't seem to adapt(?) my complete Task Sequences that I use for Server 2019 for Windows 10!
I always install SCCM applications in a powershell wrapper. This now fails completely with the following entries in SMSTS.log:
<![LOG[pInstall->InstallApplications(saAppNames, sContinueOnError), HRESULT=80004005 (X:\bt\1216594\repo\src\client\OsDeployment\InstallApplication\main. cpp,361)]LOG]!><time="16:14:38.230-60" date="01-04-2023" component="InstallApplication" context="" type="0" thread="2244" file="main.cpp:361">
<![LOG[Install Static Applications failed, hr=0x80004005]LOG]!><time="16:14:38.230-60" date="01-04-2023" component="InstallApplication" context="" type="3" thread="2244" file="main.cpp:361">
<![LOG[Process completed with exit code 2147500037]LOG]!><time="16:14:38.230-60" date="01-04-2023" component="TSManager" context="" type="0" thread="1628" file="CommandLine.cpp:1161">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="16:14:38.230-60" date="01-04-2023" component="TSManager" context="" type="1" thread="1628" file="instruction.cxx:809">
<![LOG[Failed to run the action: Install VMware Tools. Error -2147467259]LOG]!><time="16:14:38.230-60" date="01-04-2023" component="TSManager" context="" type="3" thread="1628" file="instruction.cxx:915">
The only way I know of to get the whole thing working again is to set the PS execution policy to "bypass", but this isn't the way it should work.
My next problem concerns the Language Packs: So far I have always installed them in a TS via DISM /Online /Add-Package. Works wonderfully under WS2019, but also here there seem to be innovations that I do not know. Can anyone tell me the gold standard here?
The SCCM (new ECM) version is: 2211
ADK: 10.1.22621.1
WinPE: 10.1.22621.1
Windows 10 22H2 Build 19045.2251
I am very grateful for any support.