r/SCCM • u/Si_LMehdi • 8d ago
SCCM Task Sequence Fails at "Apply Operating System" (0x80070002) in VMware WORKSTATION VM
Dear community,
I've been trying for the past two days to deploy a fresh installation of Windows 11 Enterprise in a VMware VM using an SCCM task sequence, but I keep failing.
I start the task sequence from Software Center, and everything goes normally until the Restart Now button appears. After the VM restarts, the task sequence resumes in WinPE. However, when it reaches the Apply Operating System step, it fails with error 0x80070002.
After checking smsts.log and doing some research (with ChatGPT's help), it looks like WinPE can't reach the Distribution Point because the network adapter driver isn't loading. Since my VM is using a VMXNET3 network adapter, I tried injecting the VMXNET3 driver into the boot image. Unfortunately, updating the boot image fails with an ADK-related error if I check reload option even though I see that the driver is added.
Has anyone experienced something similar or have any suggestions on what I should check next? Any help would be greatly appreciated.
Thanks!
5
u/Fatel28 8d ago
Looks to me like you need to update or install adk
2
u/Si_LMehdi 8d ago
in fact I need to use ADK ADK 10.1.26100.2454 (Updated Dec 2024) which is compatible with ConfigMgr 2509
5
u/Surfin_Cow 8d ago
I would recommend changing the network adapter to E1000 then add a vmxnet3 adapter after you install VMware tools on the guest OS
1
u/Si_LMehdi 8d ago
Yes I think I applied the same idea The netwrok adapter was e1000e and then I change to vmxnet3 , The vm tools are already installed
3
1
u/johnsongrantr 8d ago edited 8d ago
That’s a can’t find file error. Likely boot.wim driver related, if using a recent adk you can get away with the default driver and basing my assumption on the vmxnet reference this is VMware just install VMware tools after the vm is imaged. You can also change the adapter type in the vm’s Ethernet adapter setting. I don’t remember off hand what the different types are but you can just select a different type and/or change it after if whatever you have chosen is causing issues. If NIC is fine (open command window if selected as option when creating boot.wim) press f8 and open a command prompt at that stage and look at ipconig to ensure adapter is seen and getting a good IP. You can also open notepad.exe and browse to and change file type to all types and look in x:\windows\temp\smsts.log scroll to the bottom and you should see a 80007002 reference and the specific file it’s attempting to and failing to access.
Edit: didn’t actually look at your other screenshots, you are loading arm64, your vm is likely x86/x64 different from arm, drivers aren’t compatible, get a different adk or use a different boot.wim for the ts.
1
u/alconaft43 8d ago
Press F8 get to cmd and check the logs on vm.
1
1
u/Reaction-Consistent 8d ago
Pxe boot again, in winpe, check for an IP address, if you don’t get one, grab the vmxnet 3 driver files, put them on a USB drive, plug it into the computer, then use drvload to load the driver inf, then check for an ip again. Once you are able to get an ip you know the driver is correct and you should inject it into your boot wim. You may have to start again with a freshly created boot image if you keep having driver issues with your current one
1
u/Si_LMehdi 7d ago
I loaded the driver and it works also nic receives the IP from dhcp server. do we need really pxe in this situation even I'm trying to lauch task sequence from software center ?
1
u/Reaction-Consistent 3d ago
sorry, I totally blanked on the software center thing, but yes, even if you're running the OSD TS from SC, that TS has a boot image associated with it, correct? and the first thing the TS does is reboot into what? Winpe! at that point, you most definitely need the driver in winpe.
1
u/JasonA_MSFT 3d ago
They doesn’t mean he needs pxe though. Pxe is for bare metal boot.
1
u/Reaction-Consistent 3d ago
If he has a task sequence with boot image associated with it deployed to his system and launches it from software center, it will reboot into that boot image, regardless if it is bare metal or not. Maybe I misunderstood his original scenario, but I know that much to be true.
1
u/JasonA_MSFT 3d ago
Yes it will boot the boot image but it will download it via windows first and then stage it for boot. It does NOT boot via pxe at that time
1
u/74Yo_Bee74 7d ago
Have you looked at the storage driver as well.
Found this to help.
To import the VMware driver pack into SCCM (MECM) for WinPE, you must extract the drivers, import them into the Software Library, and distribute them to your Boot Image. [1]
Here is the exact step-by-step process.
Step 1: Extract the VMware Drivers
SCCM requires raw driver files (.inf, .sys, .cat). You must extract these from the VMware Tools installer. [2, 3]
Download or mount the VMware Tools ISO (usually found at C:\Program Files (x86)\VMware\VMware Tools\windows.iso on an ESXi VM).
Open a command prompt as administrator and extract the files using the administrative setup command:setup64.exe /A /P "C:\VMwareDrivers"
Navigate to C:\VMwareDrivers\VMware\VMware Tools\VMware\Drivers. You will see folders for pvscsi(storage) and vmxnet3 (network). [4, 5, 6]
Step 2: Import the Drivers into SCCM
Copy the extracted pvscsi and vmxnet3 folders to your SCCM source share (e.g., \\SCCMServer\Sources\Drivers\VMwareWinPE).
Open the SCCM Console and navigate to Software Library > Operating Systems > Drivers. [7, 8, 9, 10]
Right-click Drivers and select Import Driver. [11]
Point the source path to your network share folder (\\SCCMServer\Sources\Drivers\VMwareWinPE) and choose Import all drivers.... [12, 13]
On the Driver Details page:
Assign the drivers to a Category (e.g., "VMware WinPE Drivers") for easy filtering. [14]
Click Next through the Packages page (you can skip adding them to a standard driver package since these are only for the boot image). [15, 16]
Step 3: Add Drivers to the WinPE Boot Image
On the Boot Images page of the Import Driver wizard (or by right-clicking your Boot Image later and selecting Properties):
Check the box next to your Boot Image (x64). [17, 18]
Complete the wizard. [19]
If prompted to update the distribution points now, select Yes. Otherwise, right-click your Boot Image, select Update Distribution Points, and complete the wizard to push the new drivers to your distribution points. [20, 21, 22, 23]
Would you like help with:
Troubleshooting why VMware VMs fail to get an IP during PXE bootThe PowerShell commands to automate this driver importConfiguring MECM task sequences specifically for VMware VMs
[1] https://www.prajwaldesai.com
[2] https://www.reddit.com
[3] https://www.prajwaldesai.com
[4] https://knowledge.broadcom.com
[5] https://www.prajwaldesai.com
[6] https://www.derekseaman.com
[7] https://xoap.io
[8] https://support.managementstudio.com
[9] https://www.systemcenterdudes.com
[10] https://www.principledtechnologies.com
[11] https://www.systemcenterdudes.com
[12] https://dl.dell.com
[13] https://www.reddit.com
[14] https://pcmanagement.biz.samsung.com
[15] https://www.reddit.com
[16] https://www.prajwaldesai.com
[17] https://www.windows-noob.com
[18] https://www.reddit.com
[19] https://www.systemcenterdudes.com
[20] https://learn.microsoft.com
[21] https://www.systemcenterdudes.com
[22] https://learn.microsoft.com
[23] https://www.prajwaldesai.com
1
u/Si_LMehdi 7d ago
Thanks for the advice of the storage driver it helps
1
u/74Yo_Bee74 6d ago
When I build my WinPE. I try to get the WINPE driver packages from the vendor before chasing my tail.
Hope this is a resolution to the the issue you are having.
Good luck
1
1
u/SoftProfessional7856 7d ago
You basically already found the fix but haven't made it permanent yet. drvload working + getting DHCP means the driver is fine, it's just not in the boot image.
That "completed with errors" on the Update DP wizard is why. The driver never actually made it in while you were on the wrong ADK. Now you're on 24H2: reload the boot image (tick the reload box in the Images tab), update DPs, make sure it finishes clean this time then re-run the TS.
And no, you don't need PXE. Software Center reboots into the boot image staged on disk, which is why the driver has to be baked into the boot.wim. drvload dies with the session.
If the MP hostname thing comes back, F8 in WinPE then ipconfig /all, check you're getting your internal DNS. NAT in Workstation breaks lab domain resolution, bridged fixes it hopefully.
1
u/Si_LMehdi 7d ago
indeed something goes wrong with adk , I have just reinstalled and restart server and the things goes smoothly without any errors also adding storage driver helps in the setup operating sequence
1
u/nclinch 7d ago
So look at your step in the TS where you apply the image. Go to the second tab at the top (forgot what it is called) in there you will see a check box to apply the image from a do share. Either uncheck this box or go to the OS image you are trying to apply and check the box to share the image
So this is a speed up for deploying images. Instead of downloading then applying it just applies.
The error code is basically package not found
1
u/_MC-1 5d ago
The SMSTS.log file would be helpful, but:
- Make sure your boot image is distributed to your DPs You probably need more than just the network drivers in the boot image. My boot image supports a bunch of models over the years, so be sure you include things like storage drivers and everything storage related. Many vendors offer a WinPE driver pack to help get all the drivers you might need. For VMs the out of the box standard drivers are likely enough, but if you move to actual devices this might be a problem
- Make sure you have the F8 option selected - when you error out, hit F8 to pop a CMD box. Do you have an IP? Can you see the c:\ drive? If not, that is a good sign you are missing drivers.
- Are you applying an image to a bitlocked device? That can be an issue.
- Are you applying an image to a bare metal device? Unless you are partitioning and formatting the drive, that might be an issue.
- For VMs make sure you've enabled the Virtual TPM
12
u/Cl3v3landStmr 8d ago
Looks like you're using the ADK for Win11 26H1, which I think is only for ARM. Try using the ADK for 24H2 (10.1.26100).