Never seen or heard anything similar. You can try installing it on first boot with the /source switch. Create a folder with all source client files.
On Thu, Apr 28, 2016, 6:03 AM Joe Krilov <[email protected]> wrote: > To be honest I never leave the SCCM client on my images, I've had too many > problems. You can just let it install during your task sequence. Plus with > the way the current branch is being released it will likely be outdated > before you update your image again. > > -Joe > > On Thu, Apr 28, 2016 at 8:35 AM, Mike Murray <[email protected]> wrote: > >> Hi, >> >> I’m using MDT 2013 U2 to do a build/capture of Windows 10 1511. As this >> image will be used as part of a Windows to Go/Direct Access deployment, I >> can’t install the SCCM client at deployment – it has to be included in the >> master image. I followed the guidance for preparing the SCCM client prior >> to capture, but somehow it is removed during the sysprep or capture portion >> of the sequence. My task sequence is set to shut the computer down after >> capturing the image. If I restart it after the capture, the SCCM client is >> still there, but if I mount the wim that is captured, the entire CCM, >> ccmcache and ccmsetup directories are gone. Any ideas are appreciated! >> >> Thanks, (and sorry if this is a long email) >> >> Mike Murray >> Sr. Systems Engineer >> PNI Media >> >> Sent from Outlook Mobile<https://aka.ms/qtex0l> >> >> >
