pmrowley

Okay, never mind. The client had the wrong FQDN in the statement. Customer forgot where they put the SCCM server account.

I have 3 statements in my CCM installation properties: SMSCACHESIZE, SMSMP=fqdn, and SMSSLP=fqdn. It doesn't work. I joined the machine to the domain during the process and the updates download works, but if it's joined to the domain. the sysprep task breaks.

I'm getting the "timeout waiting for updates refresh complete notification" in my 2012 build and cap task sequence. -Updates are deployed to the Build and Cap collection -Machine is in the Build and Cap collection Machine just sits there at "Running action: Install Software Updates" without any additional status messages (like downloading updates, etc.) Machine is NOT joined to the domain during build. Do we still need a SMSSLP= line in the client config? I thought the SLP was integrated into the MP in 2012 (I have the line, just in case.) What am I missing here? Has anyone actually gotten this to work in 2012? Thanks, -P

It's definitely an update in October that has broken it. I removed everything from October on, and updates work fine in a Build and Capture sequence. Haven't narrowed it down further than that yet, because I'm under the gun to produce a working, patched capture. -P