SCCM
--
Questions
--
Followers
Top Experts
SCCm Imaging win7
I have Updated a widows 7 image, Patched, added apps then captured as a wim.
ie Sys prep etc (This is just a thin image No apps)
I deploy the task with sccm and its all running correctly.
the issue is that the looking for updates doesn't appear to stop .I left it running over night on both Physical and Vm machines and in the morning it was still looking .
If i reboot the machines they come up fine, then after several minutes they will discover updates .
the 2 updates are SEp definition files . which i would expect
In my mind, the looking for updates should be quick as the Test machine was fully patched !
could anyone suggest what could be failing .
My task sequence is attached
Task-sccm.JPG
ie Sys prep etc (This is just a thin image No apps)
I deploy the task with sccm and its all running correctly.
the issue is that the looking for updates doesn't appear to stop .I left it running over night on both Physical and Vm machines and in the morning it was still looking .
If i reboot the machines they come up fine, then after several minutes they will discover updates .
the 2 updates are SEp definition files . which i would expect
In my mind, the looking for updates should be quick as the Test machine was fully patched !
could anyone suggest what could be failing .
My task sequence is attached
Task-sccm.JPG
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Could you provide some more info please?
what info do you need.?
I have build a physical machine , patched it and downloaded all updates.
Sys prepped and then extracted the wim.
saved wim to sccm.
Added as a NEw OS and deployed.
Added the New Os to my task and deployed to my test container.
THe task runs as required . the last step in the task is to check for updates.
This task does not complete or rather it does not fail .
I noticed in the log was
No actionable updates for install task. No attempt required.
and - Total actionable updates = 0
as the image is fully patched this makes sense.. But I would expect the windows update to know there are no updates and finish in a timely matter then restart in windows oh sorry this is windows 7.
So if I reboot the machine if comes up correctly .
So either ive messed up my image or ???
If I change the image to a basic WIN7EntX64-Sp1 it completes normally after installing updates .... HELP
I have build a physical machine , patched it and downloaded all updates.
Sys prepped and then extracted the wim.
saved wim to sccm.
Added as a NEw OS and deployed.
Added the New Os to my task and deployed to my test container.
THe task runs as required . the last step in the task is to check for updates.
This task does not complete or rather it does not fail .
I noticed in the log was
No actionable updates for install task. No attempt required.
and - Total actionable updates = 0
as the image is fully patched this makes sense.. But I would expect the windows update to know there are no updates and finish in a timely matter then restart in windows oh sorry this is windows 7.
So if I reboot the machine if comes up correctly .
So either ive messed up my image or ???
If I change the image to a basic WIN7EntX64-Sp1 it completes normally after installing updates .... HELP
Hi,
I'll stop you there:
Using a physical machine will lead to indeterminate issues owing to drivers from the original hardware affecting new hardware. I have read of people having problems with Windows update running on and on and it's fixed by an update, but I can't name it or say that's definitely the cause here.
So, the recommended method:
1) use MDT + a VM to create a reference image
2) add WSUS role to your MDT server and let it do the patching
3) Run the integrate MDT step on your CM box - this will add a new button to the ribbon that creates an MDT TS
4) Use the MDT TS to deploy your image
5) Use SUP and an unconfigured/unfiltered WSUS role to patch beyond your reference image
I know that's more work, but this is the recommended, fully supported method. I don't think MS support images from physical kit.
For troubleshooting if you're not ready to do all the above yet, you need to provide more info, as requested:
1) a list of patches you applied
2) list of patches you excluded
3) are you using an existing "dirty" WSUS
4) are you using SUP or just WSUS (clean or dirty)
5) Attach logs: Smsts.log, windowsupdate.log
Mike
I'll stop you there:
I have build a physical machine
Using a physical machine will lead to indeterminate issues owing to drivers from the original hardware affecting new hardware. I have read of people having problems with Windows update running on and on and it's fixed by an update, but I can't name it or say that's definitely the cause here.
So, the recommended method:
1) use MDT + a VM to create a reference image
2) add WSUS role to your MDT server and let it do the patching
3) Run the integrate MDT step on your CM box - this will add a new button to the ribbon that creates an MDT TS
4) Use the MDT TS to deploy your image
5) Use SUP and an unconfigured/unfiltered WSUS role to patch beyond your reference image
I know that's more work, but this is the recommended, fully supported method. I don't think MS support images from physical kit.
For troubleshooting if you're not ready to do all the above yet, you need to provide more info, as requested:
1) a list of patches you applied
2) list of patches you excluded
3) are you using an existing "dirty" WSUS
4) are you using SUP or just WSUS (clean or dirty)
5) Attach logs: Smsts.log, windowsupdate.log
Mike
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Hi Mike Thanks for your reply
I am fairly new to Sccm and so my main companion has been a large book.
what I have done so far. Is Import my current Image in from WDS (thick) which is up to date and has all the apps in. I am deploying this fine.
I have also got a thin image (basic win7ENT-X64SP1) which I can deploy and add all the drivers and updates and that works fine.
But what I was trying to achieve was to have a “patched sp1 image and so the process would be quicker. (I used the physical box for this)
Once successful I want to explore adding the apps on deployment.
I am learning as I go so haven’t used the MDT part of Sccm yet but I have it installed.
Although I am using the MDT boot image.
Can you briefly run through the Serio of capture again as I’m missing a few steps?
This what I have been trying .
smsts.log
ZTIWindowsUpdate.log
I am fairly new to Sccm and so my main companion has been a large book.
what I have done so far. Is Import my current Image in from WDS (thick) which is up to date and has all the apps in. I am deploying this fine.
I have also got a thin image (basic win7ENT-X64SP1) which I can deploy and add all the drivers and updates and that works fine.
But what I was trying to achieve was to have a “patched sp1 image and so the process would be quicker. (I used the physical box for this)
Once successful I want to explore adding the apps on deployment.
I am learning as I go so haven’t used the MDT part of Sccm yet but I have it installed.
Although I am using the MDT boot image.
Can you briefly run through the Serio of capture again as I’m missing a few steps?
This what I have been trying .
smsts.log
ZTIWindowsUpdate.log
missed a bit
this is what i have been doing
1 Deploy the Basic image to a Vm,
2. Patch, b
I can add the updates to this task or manually add.
Once done are there any files or logs i should remove before trying to capture.
and finally i am not too sure how to capture the Image back from the VM
thanks
this is what i have been doing
1 Deploy the Basic image to a Vm,
2. Patch, b
I can add the updates to this task or manually add.
Once done are there any files or logs i should remove before trying to capture.
and finally i am not too sure how to capture the Image back from the VM
thanks
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
THanks for the Great Explanation
the book i am using is System Center2012 Configuration Manager ,Mastering the Fundamentals By Kent Agerlund.
Thanks for looking at my logs Okay so waiting for 20, But i have left it over night and it didn't finish ,or am i being impatient.
I have tried the capture before but abandoned it (when i first started learning) So re tweaked my task sequence and reran
it runs as expected, except failes after sysprep with error
Windows PE initialization failed with error code 0x80220014. THe image continues to run and iam greeted with the OOB experience
After a few googles seems that i need a hot fix, as i am running WADK Windows PE v10.0.10586 are you able to confirm?
also in my first messge There is a image of my task sequence and i havea reboot after updates
If i use the task "check for microsoft update " using ZTIWindowsUpdate.wsf it apears to hang !, But will complete after i reboot,
Or should i just use the task "install software Updates"
I have attatched the 2 logs there appear errors in Dism buti havnt yet investigated what they are
Thanks again
thanks
dism.log
smsts.log
the book i am using is System Center2012 Configuration Manager ,Mastering the Fundamentals By Kent Agerlund.
Thanks for looking at my logs Okay so waiting for 20, But i have left it over night and it didn't finish ,or am i being impatient.
I have tried the capture before but abandoned it (when i first started learning) So re tweaked my task sequence and reran
it runs as expected, except failes after sysprep with error
Windows PE initialization failed with error code 0x80220014. THe image continues to run and iam greeted with the OOB experience
After a few googles seems that i need a hot fix, as i am running WADK Windows PE v10.0.10586 are you able to confirm?
also in my first messge There is a image of my task sequence and i havea reboot after updates
If i use the task "check for microsoft update " using ZTIWindowsUpdate.wsf it apears to hang !, But will complete after i reboot,
Or should i just use the task "install software Updates"
I have attatched the 2 logs there appear errors in Dism buti havnt yet investigated what they are
Thanks again
thanks
dism.log
smsts.log
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Hi,
Working last first, yes task just use the "install software Updates" step. This assumes you have set up SUP (with WSUS) already though? Have you done that?
Kent's book is the first book I read on 2012 too. It's very good. If you work through it like a lab book you won't go far wrong.
What I will say with CM though, is don't rush. Do one thing at a time. So create a build and capture with NO updates, and get that working. Then create a deployment and get that working. Just drivers and no apps. Then add your apps in (as packages because OSD likes them better). When you're totally happy you have a working OS with working drivers, then you're ready to start putting OS updates in.
with regards the 20 patches, they looked like they installed so I'm not sure what was left pending. Adding a reboot won't hurt.
As for WinPE and capturing, I've never had any problems with that. It's one of the few things that just works.
The error you have is: Error. Received 0x80072ee7 from WinHttpSendRequest.
It starts to go wrong earlier with Start executing an instruction. Instruction name: Apply Device Drivers. Instruction pointer: 6
"Unsuccessful in finding a suitable device driver for device 'Motherboard resources'."
if you are applying a driver package then remove it. The reference image needs to have NO drivers injected at all. It uses native OS drivers for disk and network. Those are the only two you ever need. You definitely don't need these:
File: http://<snip>.com:80/SMS_DP_SMSPK
This is bad if it worked because now your reference image has AMD network drivers in, regardless of whether your physical kit has AMD anything. Potentially it can kill the Plug and Play enumeration.
So the step works (Successfully completed the action (Apply Device Drivers) with the exit win32 code 0) but it has to do lots of unnecessary weeding.
Step 8 is Install updates - I would grey that out for now.
It fails anyway (This operation returned because the timeout period expired. (Error: 800705B4; Source: Windows). This is a known issue if you have *too many* update pending. If SUP is not setup correctly though it will fail too. SUP is a much later chapter in Kent's book.
Finally got to the problem: "Found network adapter "Intel(R) PRO/1000 MT Network Connection" with IP Address 0.0.0.0." and then machine reboots and stages WinPE on the D: drive before this:
Error. Received 0x80072ee7 from WinHttpSendRequest.
which points to there being no network drivers. See this article, by err, me:
https://4sysops.com/archives/sccm-windows-deployment-troubleshooting-part-3-networking-issues-xml-and-media-errors/
That's another reason why capturing on a VM works better than a physical box. There are no drivers to worry about, so you don't have to mess about - it just works.
Mike
Working last first, yes task just use the "install software Updates" step. This assumes you have set up SUP (with WSUS) already though? Have you done that?
Kent's book is the first book I read on 2012 too. It's very good. If you work through it like a lab book you won't go far wrong.
What I will say with CM though, is don't rush. Do one thing at a time. So create a build and capture with NO updates, and get that working. Then create a deployment and get that working. Just drivers and no apps. Then add your apps in (as packages because OSD likes them better). When you're totally happy you have a working OS with working drivers, then you're ready to start putting OS updates in.
with regards the 20 patches, they looked like they installed so I'm not sure what was left pending. Adding a reboot won't hurt.
As for WinPE and capturing, I've never had any problems with that. It's one of the few things that just works.
The error you have is: Error. Received 0x80072ee7 from WinHttpSendRequest.
It starts to go wrong earlier with Start executing an instruction. Instruction name: Apply Device Drivers. Instruction pointer: 6
"Unsuccessful in finding a suitable device driver for device 'Motherboard resources'."
if you are applying a driver package then remove it. The reference image needs to have NO drivers injected at all. It uses native OS drivers for disk and network. Those are the only two you ever need. You definitely don't need these:
File: http://<snip>.com:80/SMS_DP_SMSPK
This is bad if it worked because now your reference image has AMD network drivers in, regardless of whether your physical kit has AMD anything. Potentially it can kill the Plug and Play enumeration.
So the step works (Successfully completed the action (Apply Device Drivers) with the exit win32 code 0) but it has to do lots of unnecessary weeding.
Step 8 is Install updates - I would grey that out for now.
It fails anyway (This operation returned because the timeout period expired. (Error: 800705B4; Source: Windows). This is a known issue if you have *too many* update pending. If SUP is not setup correctly though it will fail too. SUP is a much later chapter in Kent's book.
Finally got to the problem: "Found network adapter "Intel(R) PRO/1000 MT Network Connection" with IP Address 0.0.0.0." and then machine reboots and stages WinPE on the D: drive before this:
Error. Received 0x80072ee7 from WinHttpSendRequest.
which points to there being no network drivers. See this article, by err, me:
https://4sysops.com/archives/sccm-windows-deployment-troubleshooting-part-3-networking-issues-xml-and-media-errors/
That's another reason why capturing on a VM works better than a physical box. There are no drivers to worry about, so you don't have to mess about - it just works.
Mike
Starting From the Bottom , when i first was trying to deploy via the console i was getting network errors so yes i have injected the Intel R adapter into the boot image . so should i just remove that ?
also from your page " torch animation is taking too long, " I had noticed that getting longer .
Also just a quick overview , I added a thick patched image from my Old WDS and that works brilliant;y , adds to the domain .
but what i wanted to do was create a new patched thin image , that i was going to add apps to on deployment (future).
So i have flitted back wards and forwards . BUt thanks again hopefully i am now on the right path
so i will try the capture again and not add updates .
Not sure how amd drivers got in as i basically have just used the win from a sp1 Disc
also from your page " torch animation is taking too long, " I had noticed that getting longer .
Also just a quick overview , I added a thick patched image from my Old WDS and that works brilliant;y , adds to the domain .
but what i wanted to do was create a new patched thin image , that i was going to add apps to on deployment (future).
So i have flitted back wards and forwards . BUt thanks again hopefully i am now on the right path
so i will try the capture again and not add updates .
Not sure how amd drivers got in as i basically have just used the win from a sp1 Disc
Yes - never add drivers to the boot image unless you are 100% sure it fails without.
The "Add drivers" step is in the default task-sequence, but for capture should do nothing. Maybe you gave it a driver package thinking it was needed. Grey it out if it causes issues.
Thin images are generally best unless you really, gotta have a very quick build process. Even then it has issues (and more work).
Good luck.
The "Add drivers" step is in the default task-sequence, but for capture should do nothing. Maybe you gave it a driver package thinking it was needed. Grey it out if it causes issues.
Thin images are generally best unless you really, gotta have a very quick build process. Even then it has issues (and more work).
Good luck.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
HI Mike thought i replied but appears missing
Anyway i reran the capture with the nic removed from the boot image and no updates selected.
runs well after sys prep it fails again ""Windows PE initialization failed with error code 0x80220014.""
which is the capture stage , is this due to it needing the hot fix or an other issue ?
Thanks
Anyway i reran the capture with the nic removed from the boot image and no updates selected.
runs well after sys prep it fails again ""Windows PE initialization failed with error code 0x80220014.""
which is the capture stage , is this due to it needing the hot fix or an other issue ?
Thanks
When i look through the logs i see Remediation failed with error code 8027000C which i believe is networking issues , thats why i originally added the driver . Am i missing the point here ?
Hi - to test create a WinPE boot disk with F8 enabled, boot the machine and press F8, then type IPconfig.
What machine are you doing this on? And also what flavour of WinPE are you running? You need to match the architecture if you do need a driver.
Native support is very good so normally if you have new hardware it works without hassle.
What machine are you doing this on? And also what flavour of WinPE are you running? You need to match the architecture if you do need a driver.
Native support is very good so normally if you have new hardware it works without hassle.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Im using a VM I am using the MDT boot Image X64 Os version 10.0.10586.0
that why im thinking hot fix
https://support.microsoft.com/en-gb/kb/3143760
I dint set these Vms up but noticed my two test machines were using E100 nics rather than VMXNET3 are they okay to use or should i change ?
Off now till monday but will try your test then
have a good weekend
sccm--nic-error.JPG
that why im thinking hot fix
https://support.microsoft.com/en-gb/kb/3143760
I dint set these Vms up but noticed my two test machines were using E100 nics rather than VMXNET3 are they okay to use or should i change ?
Off now till monday but will try your test then
have a good weekend
sccm--nic-error.JPG
The E1000s will work but I seem to remember needing to change the vmx file (for workstation). Try using VMXNet3 as that's native.
The VMs I have here are ESX, VM version 8 (ESX is 5.x) and are using E1000. I don't have any VMware drivers in my boot image.
Maybe the patch is required. It's not one I've seen or used.
Mike
The VMs I have here are ESX, VM version 8 (ESX is 5.x) and are using E1000. I don't have any VMware drivers in my boot image.
Maybe the patch is required. It's not one I've seen or used.
Mike
Hi Mike I went back to basics
started a fresh built on a Vm patched, cleaned up
then created a capture task on SCCm
Fairly basic but that fails with error ox00000032
I can deploy okay but i seem unable to capture
started a fresh built on a Vm patched, cleaned up
then created a capture task on SCCm
Fairly basic but that fails with error ox00000032
I can deploy okay but i seem unable to capture
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Hi,
Good plan to start again. I know using old images is easier but it's not always best in the long run. Far better to have a system that can spit out an image on demand and like clockwork.
Attach the log and I'll take a look. I can't remember what 0032 means.
Good plan to start again. I know using old images is easier but it's not always best in the long run. Far better to have a system that can spit out an image on demand and like clockwork.
Attach the log and I'll take a look. I can't remember what 0032 means.
Hi Mike
after a couple of hours with fresh builds etc i keep arriving at the same spot which points to the hot fix in the ADK
https://support.microsoft.com/en-gb/kb/3143760
So i will strip this out , and upgrade to the latest's version and branch and i then believe everything that i have tried before will work so thanks again for all your help
as i cant go forward with out this i am happy to mark as resolved .
I will log a new one if after all that it still fails but im optimistic that it will not
Thanks again
after a couple of hours with fresh builds etc i keep arriving at the same spot which points to the hot fix in the ADK
https://support.microsoft.com/en-gb/kb/3143760
So i will strip this out , and upgrade to the latest's version and branch and i then believe everything that i have tried before will work so thanks again for all your help
as i cant go forward with out this i am happy to mark as resolved .
I will log a new one if after all that it still fails but im optimistic that it will not
Thanks again
Hi Roger,
Thanks for letting me know. Unfortunately MS is moving very fast at the moment so yes, they have a new OS, new MDT version and a new ADK too.
Mike
Thanks for letting me know. Unfortunately MS is moving very fast at the moment so yes, they have a new OS, new MDT version and a new ADK too.
Mike
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Cheers and thanks again for all your great advise
Sometimes it's best to start from scratch
SCCM
--
Questions
--
Followers
Top Experts
Systems Center Configuration Manager (SCCM, formerly known as Systems Management Server) is Microsoft’s system software for managing large groups of not only Microsoft computers, but those running other operating systems, such as Linux, OS-X, and various mobile technologies.