dverbern Posted April 14, 2014 Report post Posted April 14, 2014 Hello, After recently restarted our SCCM primary site server for periodic maintenance, we then found that our Desktop team could not build machines using Operating System Deployment (OSD). The machines would boot via PXE and would only proceed to the point where they had to download content. The smsts.log on the machines gave this important line: Failed to resolve the source for SMS PKGID=PR10006D, hr=0x80070002 My first line of investigation was to check that the content used in the Task Sequence was distributed to each of our DPs, it was. I then checked whether the service accounts in Active Directory used for build, capture, network access were enabled and that their passwords hadn't expired or accounts weren't locked, those accounts were fine. I then logged into a server with the credentials of our SCCM Network access account and tried to browse to the location on the DP where packages are stored - it wouldn't let me access that location. This was strange because that account had rights. Ultimately, I found the fix - Our SCCM server is a Windows Server 2012 server sitting in VMWare and the server was set to allow hotplugging of devices, including its hard disks. This seems to cause issues with some applications, including SCCM. To resolve, I followed the steps in this VMWare KB article to turn off the hotplug settings: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012225 To make this change, I had to power off our SCCM server, but the change itself was quick and once the server was back, Windows was no longer treating the disks as removable and suddenly content on the server was accessible for OSD, Windows Updates, etc. I just thought I'd share this topic if anyone else runs into this issue. 1 Quote Share this post Link to post Share on other sites More sharing options...