Thanks Don, that gave me someplace to start digging this morning. I
started the os deployment to my test machine again this morning. Once it
got to the Install Software Updates step and got stuck, I looked for
wuahandler.log and found that it hadn't been created yet. It looks like a
little over 2 hours later the file was created, with just one line in it so
far:
> CWuaHandler::SetCategoriesForStateReportingExclusion called with
> E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3;
> for leaves and
> E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3;
> for bundles
The windowsupdate.log does shed a little more light on things though. I
see repeatedly entries reporting "WSUS server: NULL". I also see a lot of
entries referencing connections to URLs at microsoft.com...
Here are a couple of sections from the log with examples of where it's
referencing MS servers:
> [sls]SLS DatastoreLookup: 0x80248007
> [sls]Retrieving SLS response from server...
[downloadfile]Failed to get proxy settings token, not impersonating user.
> hr=800703f0
[sls]Making request with URL
> HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/10.0.15063.0/0?CH=108&L=en-US&P=&PT=0x4&WUA=10.0.15063.483&MK=Microsoft+Corporation&MD=Virtual+Machine
>
[client]Validating signature for
> C:\windows\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\sls.cab
> with dwProvFlags 0x00000080:
[client] Infrastructure signed: Yes
[client]Validating signature for
> C:\windows\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\TMPFC90.tmp
> with dwProvFlags 0x00000080:
[client] Infrastructure signed: Yes
[sls]SLS DatastoreLookup: 0x80248007
<snip>
> [agent]Caller SID for Applicability: S-1-5-18
> [endpointproviders]Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir
> Client/Server URL:
> https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx"";
> [lib]Skipping printer driver 4 due to incomplete info or mismatched
> environment - HWID[microsoftmicrosoft_musd] Provider[Microsoft]
> MfgName[Microsoft] Name[Microsoft enhanced Point and Print compatibility
> driver] pEnvironment[Windows NT x86] LocalPrintServerEnv[Windows x64]
> [agent]ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL =
> https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
> [agent]OK to reuse existing configuration
> [agent]Existing cookie is valid, just use it
> [endpointproviders]Got 8B24B027-1DEE-BABB-9A95-3517DFB9C552 redir
> Client/Server URL:
> https://fe3.delivery.mp.microsoft.com/ClientWebService/client.asmx"";
> [agent]WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover)
> started; operation # 68; does<NULL> use network; is<NULL> at background
> priority<NULL>
It looks to me like the client is not configured to get updates from
WSUS/SCCM, and is trying to download updates from the internet instead. Do
I have that right?
Anyone know what might cause this behavior during OSD?
Steve
On Fri, Dec 1, 2017 at 6:27 PM, Don Pickard <don.l.pick...@gmail.com> wrote:
> You’ll need to dig deeper into wuahandler.log and windowsupdates.log (or
> if this is Win10, the equivalent WUA log) to find out if it’s the WUA (COM)
> “server” which is dying with that 0x80080005 or if it’s some other “server”
> failing (although it’s pretty likely to be WUA given the context/scenario
> you’ve described)
>
>
>
> BR
>
>
>
> DonPick
>
>
>
>
>
>
>
> *From: *Steve Whitcher <st...@whitcher.org>
> *Sent: *Saturday, 2 December 2017 8:15 AM
> *To: *mssms@lists.myitforum.com
> *Subject: *[mssms] OSD Hangs during Install Software Updates step - CM
> 1710
>
>
>
> Recently my deployments have been getting stuck at the "Install Software
> Updates" step for several hours, before eventually continuing on. I first
> noticed it after updating to CM 1710, but can't say whether that is related
> or not.
>
>
>
> The UpdatesDeployment.log file shows the following repeated over and over
> (different assignment guids, but otherwise the same):
>
>
>
> Assignment {2627036A-F8CB-4694-B2B9-10CD01537069} has total CI = 1
>
> Redetecting Assignment ({2627036A-F8CB-4694-B2B9-10CD01537069})
> UpdatesDeploymentAgent 12/1/2017 12:49:17 PM 4672 (0x1240)
>
> CoCreateInstance failed for CIAgent, error 80080005
> UpdatesDeploymentAgent 12/1/2017 12:53:18 PM 4672
> (0x1240)
>
> Detection job failed for assignment ({2627036A-F8CB-4694-B2B9-10CD01537069})
> UpdatesDeploymentAgent 12/1/2017 12:53:18 PM 4672 (0x1240)
>
> Assignment redetection failed, error = 0x80080005
> UpdatesDeploymentAgent 12/1/2017 12:53:18 PM 4672 (0x1240)
>
> Failed to redetect assignment {2627036A-F8CB-4694-B2B9-10CD01537069},
> error = 0x80080005 UpdatesDeploymentAgent 12/1/2017
> 12:53:18 PM 4672 (0x1240)
>
> Assignment {C5149607-C83C-4D5B-8D22-3F184E087789} has total CI = 2
> UpdatesDeploymentAgent 12/1/2017 12:53:18 PM 4672 (0x1240)
>
> Redetecting Assignment ({C5149607-C83C-4D5B-8D22-3F184E087789})
> UpdatesDeploymentAgent 12/1/2017 12:53:18 PM 4672 (0x1240)
>
> CoCreateInstance failed for CIAgent, error 80080005
> UpdatesDeploymentAgent 12/1/2017 12:57:20 PM 4672
> (0x1240)
>
> Detection job failed for assignment ({C5149607-C83C-4D5B-8D22-3F184E087789})
> UpdatesDeploymentAgent 12/1/2017 12:57:20 PM 4672 (0x1240)
>
> Assignment redetection failed, error = 0x80080005
> UpdatesDeploymentAgent 12/1/2017 12:57:20 PM 4672 (0x1240)
>
> Failed to redetect assignment {C5149607-C83C-4D5B-8D22-3F184E087789},
> error = 0x80080005 UpdatesDeploymentAgent 12/1/2017
> 12:57:20 PM 4672 (0x1240)
>
> Assignment {D324C98C-A976-4650-9A92-729F10AD8FF4} has total CI = 2
> UpdatesDeploymentAgent 12/1/2017 12:57:20 PM 4672 (0x1240)
>
> Redetecting Assignment ({D324C98C-A976-4650-9A92-729F10AD8FF4})
> UpdatesDeploymentAgent 12/1/2017 12:57:20 PM 4672 (0x1240)
>
>
>
> I've been searching online for similar error messages, but I'm not finding
> anything that seems to apply to my situation. Any ideas as to what's going
> wrong?
>
>
>
> Thanks,
>
> Steve
>
>
>
>
>
>
