Search the Community

Hello, I recently deployed an OS task sequence to a device collection and all of the computers came up with "Inaccessible Boot Device" afterward. This is the first time I have tried pushing an OSD as a required deployment to computers that are already powered up and running Windows. The OSD works fine with booting to media, and this same OSD worked fine on these computers after I circled back around to reload them via bootable media. The computers showed up in AD with the automatically generated name, so I believe the OSD was successful, maybe just missing some drivers? Has anyone run into this before, or can you suggest a course of action? Thanks for any help you can offer! Scott

Hello, I've deployed a group of Windows updates to a collection which has no maintenance window and it's works correcty and all devices are comliant excep one who do not getting the updates and showing "Client check passed/Active" state. I've tried to stop wuauserv service and delete "SoftwareDistribution" floder but it isn't works for me. below details about my environment. Client Device : windows Server 2012 R2 whitch hosts the McAfee antivirus solution. FYI: I've tried to stop McAfee services but it restart automaticaly when the process of updates begin. SCCM Management Server: SCCM 2012 R2 SP1, WSUS 4.0 (6.3.9600.18694) Logs : - WUAHandler.log : Successfully completed scan - UpdatesDeployment.log : EnumerateUpdates for action (UpdateActionInstall) - Total actionable updates = 0 - LocationServices.log : ALL its correct - WindowsUpdate.log : 4 Warning WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 9, GetLastError=2250 WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037 WARNING: Failed to initialize event uploader for new server {9482F4B4-E343-43B6-B170-9A65BC822C77} with hr = 8024043d. WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll Thank you in advance for your help. cordially. Hadjer YAHIAOUI Infra Admin

We just downloaded Win 10 1809 and started to attempt to roll it out (testing) but every time the task sequence fails with unknown errors (0x80004005) at the Apply Operating System Step. I did some searching and it sounded like the version of SCCM we were on was not compatible so yesterday I upgraded to Config Mgr 1806 and also the 1806 hotfix. Thought that would resolve the issue but it doesn't. I copied the original task sequence for 1803 that was working and replaced the OS thinking that would be the easiest way to do it. Any ideas what might we wrong with the 1809 version? *Edit, my Network Admin downloaded the ARM version which will not work on our pc's. Now that 1809 is paused, I'm not going to worry about it anymore. Until the next version...

We just upgraded SCCM to 1806 including the hotfix. Everything seemed to be ok. I updated the ADK as well so I could install the new version of Windows 10. I'm currently having trouble with that as well, but that's a different post. Any idea why my windows 7 images fail at the driver package now that I upgraded SCCM? Nothing else has changed. Logs don't show anything of use that I can find. ** Update ** For all my windows 7 driver packages, I had to check "Install driver package via running DISM with recurse option". Wish that was in some kind of documentation I had read ahead of time.