pembertj

I don't see this issue any more, but I am on SCCM v1511, ADK 10.0.10586 now - so either one could have had a bug fix that made the problem go away.

Running into this error: https://blogs.technet.microsoft.com/sus/2008/09/18/wsus-clients-fail-with-warning-syncserverupdatesinternal-failed-0x80244010/ or https://social.technet.microsoft.com/Forums/systemcenter/en-US/7882521e-8a1d-40a5-95b9-d3105965cbf6/0x80244010-roundtrip-error?forum=configmgrgeneral This only has seemed to start happening after we moved to SCCM v1511. Software update groups did not change when we updated - a machine that is imaging today should see the same # of updates that it did before the upgrade. Suggestions of adding more "software update steps" to the task sequence does not seem to help (as people have posted as a solution in various forums). I have added 10x Software update steps and still see the same behavior... Just looking for any solutions. We keep our base up to date and these updates are deployed to the machines after the TS finishes as well, but it would be nice to figure out why this just started happening...

I put a ticket in to Microsoft. They said it was a bug and it seems to be fixed in SCCM v1511 (which we are on now). I'm not sure when/if it will be fixed in 2012 R2 SP1 CU X ~Tom

The bug was fixed in Win10 ADK build 10586, but that build introduced this bug (http://ccmexec.com/2015/11/windows-10-adk-10-0-10586-solves-the-powershell-net-bug-in-winpe/), so pick your poison. Microsoft has gone on record recommending not to use ADK 10586 until they fix that new bug. I personally have been using it anyway as I would rather have that bug then the no powershell bug...

Adding the steps mentioned (to my base image) mentioned in the technet article worked for me.

Damn, thanks anyweb - I will try some of those suggestions. I've been digging around on the web all weekend looking for a solution to this one and didn't find that post on technet...

Upgraded to v1511 in late December and recently tried to re-capture a base image (Windows 10). I found that the base image will capture ok (all applications, Software Updates, etc install just fine) and the WIM is captured with no issues. If I take that base image and try to use it during site-wide OSD it will hang for a long time on the Setup Windows and ConfigMgr Step and will then completely freeze on the first application install that we have during the Windows Phase. These task sequences (base and osd) are the exact same ones that we were using before the v1511 upgrade. After comparing this log to old "good" logs it seems to me as though the SCCM Client is not being properly prepared on the "Prepare ConfigMgr Client" step at the end of the base image, and then it causes issues during OSD. Let me know any other logs that may be of interest... Certificate Issuer 1 [CN=aabc Root Certificate; DC=aabc; DC=com] ccmsetup 1/8/2016 11:56:33 PM 612 (0x0264) Finding certificate by issuer chain returned error 80092004 ccmsetup 1/8/2016 11:56:33 PM 612 (0x0264) Completed searching client certificates based on Certificate Issuers ccmsetup 1/8/2016 11:56:33 PM 612 (0x0264) Unable to find any Certificate based on Certificate Issuers ccmsetup 1/8/2016 11:56:33 PM 612 (0x0264) Raising event: instance of CCM_ServiceHost_CertRetrieval_Status { DateTime = "20160109055633.941000+000"; HRESULT = "0x87d00215"; ProcessID = 624; ThreadID = 612; }; ccmsetup 1/8/2016 11:56:33 PM 612 (0x0264) Status Agent hasn't been initialized yet. Attempting to create pending event. ccmsetup 1/8/2016 11:56:33 PM 612 (0x0264) ccmsetup.bad.log

For those that are curious... I put a ticket in to Microsoft to see what was up with that error. They said it is coming up because it has to do with SQL Clustering that only exists in SQL 2012 and newer (We are on SQL 2008 R2). They said they are working on a fix and/or upgrading to SQL Server 2012 would fix the error Microsoft: "the view was not created and so that is why it is erroring".

Update went pretty smoothly for us, but I am seeing this error pop up many times in the logs and haven't found much online... any ideas? Component: SMS_HIERARCHY_MANAGER Microsoft SQL Server reported SQL message 208, severity 16: [42S02][208][Microsoft] [sql Server]Invalid object name 'sys.availability_replicas'. Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information. Thanks

I started running into this as well... looks like this is the issue... but haven't found a good fix yet short of disabling pre-provisioning like you did... **Windows 10 1511 (build 10586) includes a new bitlocker encryption, XTS-AES encryption algorithm, which cannot be read by earlier versions of Windows.. so that is most likely the reason.** https://social.technet.microsoft.com/Forums/en-US/07c809fc-486b-49aa-8df8-70e374d90402/sccm-2012-r2-sp1-preprovision-bitlocker-windows-7-cannot-read-drive-after-reboot?forum=configmanagerosd

I am experiencing the exact issue described here. https://communities.intel.com/thread/43218?start=0&tstart=0[1] driver info: using e1d65x64 version 12.13.17.4 Laptop (Dell e6440) will netboot and start the Task Sequence fine (using ADK 10/WinPE 10). After about 30-60 minutes the network driver seems to have issues and switches to APIPA. People in that thread suggest getting the drivers directly from Intel and importing into WinPE. I have tried this but SCCM 2012 R2 SP1 will error out on the Intel "direct" Driver (e1d65x64 12.13.17.7) and will not add it to the Boot Image. I am currently using the newest Dell A01 WinPE 10 driver pack that imports fine into SCCM (specifically driver e1d65x64 version 12.13.17.4) Has anyone else ran into this issue and have a fix? Thanks

Yeah the problem is that message ID 6703 also apparently comes up for "WSUS not configured" error message, so a lot of online hits point to fixing that issue and not the one I am running into... Migrating the site to Server 2012 R2 so might just wait it out...

I am seeing the below error on every wsus sync in SCCM --> Monitoring --> System Status --> Component Status --> SMS-WSUS_SYNC_MANAGER. When I look in WSUS directly on the site server or look at what updates that have synced in "all software updates" in the console everything is syncing perfectly fine... Has anyone ran into this? Online the only suggestions I see are Reinstall SUP and/or WSUS... Message ID: 6703 Component: SMS_WSUS_SYNC_MANAGER WSUS Synchronization failed. Message: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse.

In reference to this new bug: http://ccmexec.com/2015/11/windows-10-adk-10-0-10586-solves-the-powershell-net-bug-in-winpe/ We rarely do refreshes so I tested this new build out - turns out this error also seems to happen during WinPE if it needs to reboot/stage the boot wim on the HDD during WinPE phase (which is a deal breaker for me...)

Thanks for the info severina, we will have to check that out. The only case that would break for me is (as you mentioned) Windows 10 upgrades as we do not do other refreshes where I work. ~Tom

I'm at the MMSMOA conference in Minnesota and asked a Microsoft SCCM presenter about this problem directly. He said it is a known bug (I know Dewayne submitted a ticket to Microsoft and was probably told this as well). He said that "hopefully" (he didn't sound 100% sure) that this bug would be fixed in a Win10 ADK update that is supposed to be released "soon".

80070002 means file not found so it must not have been able to copy it to the share. I would double-check that the file exists on whatever file share you store it (where it gets pulled from up onto the DP) and that the DP has space on the hard drive to store it as well. ~Tom

We install os and apps (including offices) then two passes of the software update steps seems to get office and windows updates installed just fine. ~Tom

I think it is a combination of Windows 10 and Dell's Drivers. On our Windows 7 task sequence we use Auto Apply Drivers for that model (runs faster than Install Driver Package). I only had to switch it when I tested Win10 on this model (with Dell's Win10 drivers)... ~Tom

Ever since I've upgraded to ADK 10 I've had issues with not being able to do Offline servicing with some WIM files. I had issues with all OS Wims (from the DVDs) until I realized that WAIK was still installed on the server. After taking that off and reparing ADK I am now able to update Win7 and Win10 WIMs with offline servicing. I am still getting the following errors in the Offlineservicingmgr.log whenever I try to update a Windows 8.1 wim. This error will come up for every update that I try to inject... Failed to install update with error code 87 - it seems to think any update that is injected is not needed for this OS... Any Ideas? Thanks ~Tom STATMSG: ID=7909 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=sccm01.xxx.xx SITE=SITE PID=5344 TID=11104 GMTDATE=Fri Oct 02 15:23:01.000 2015 ISTR0="17312406" ISTR1="SITE00709" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 10/2/2015 10:23:01 AM 11104 (0x2B60) No need to apply this update binary since it's not required on the mounted image. SMS_OFFLINE_SERVICING_MANAGER 10/2/2015 10:23:01 AM 11104 (0x2B60) Checking if update (9 of 10) with ID 17312445 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 10/2/2015 10:23:01 AM 11104 (0x2B60) dism.exe tool info: version=10.0.10240.16384, architecture=9 SMS_OFFLINE_SERVICING_MANAGER 10/2/2015 10:23:01 AM 11104 (0x2B60) Update applicability check is not supported. Dism.exe command line is below: SMS_OFFLINE_SERVICING_MANAGER 10/2/2015 10:23:19 AM 11104 (0x2B60) "C:\Windows\system32\cmd.exe" /q /c ""C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Image:"C:\ConfigMgr_OfflineImageServicing\SITE00709\ImageMountDir" /LogPath:%WINDIR%\Logs\Dism\dism_sccmAMD64.log /English /Get-PackageInfo /Packagepath:"C:\ConfigMgr_OfflineImageServicing\81be14ed-6cda-4cb9-b645-5b5045e119e4\Windows8.1-KB2962184-x64.cab">>C:\ConfigMgr_OfflineImageServicing\SITE00709\_@A60C.tmp" SMS_OFFLINE_SERVICING_MANAGER 10/2/2015 10:23:19 AM 11104 (0x2B60) GetUpdateApplicability returned code 0x80070057 SMS_OFFLINE_SERVICING_MANAGER 10/2/2015 10:23:19 AM 11104 (0x2B60) Applicability State = APPLICABILITY_CHECK_NOT_SUPPORTED, Update Binary = C:\ConfigMgr_OfflineImageServicing\81be14ed-6cda-4cb9-b645-5b5045e119e4\Windows8.1-KB2962184-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 10/2/2015 10:23:19 AM 11104 (0x2B60) Applying update with ID 17312445 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 10/2/2015 10:23:19 AM 11104 (0x2B60) dism.exe tool info: version=10.0.10240.16384, architecture=9 SMS_OFFLINE_SERVICING_MANAGER 10/2/2015 10:23:19 AM 11104 (0x2B60) Failed to install update with error code 87 SMS_OFFLINE_SERVICING_MANAGER 10/2/2015 10:23:37 AM 11104 (0x2B60) Offline.log

I just checked our task sequence. I had a similar problem with our E7450, I switched the driver install for that model to Install Driver Package instead of Auto Apply Drivers and it seemed to have gone away at that point.

Did you upgrade to ADK 10? I think I had the same issue until I made the change...

If you are on ADK 10 you can only edit the Win10 boot images, to edit your old boot images you would have to downgrade your ADK again. I talked to D3w4yne (he has a ticket open with Microsoft for this problem) a few days ago on a different mailing list. He said that Microsoft is still looking at the problem and has no solution yet.... ~Tom

If you are ADK 10 you can only edit the Win10 boot images, to edit your old boot images you would have to downgrade your ADK again. I talked to D3w4yne (he has a ticket open with Microsoft for this problem) a few days ago on a different mailing list. He said that Microsoft is still looking at the problem and has no solution yet.... ~Tom

I've never done a site restore but looked at it when I was considering moving our MP from Virtual to Physical. From what I remember you have to keep the server name and domain name the same if you are going to do a site restore. Also from what I remember it is recommended to keep the site server name the same, so that when you join the new MP to the domain you can have it take over the existing AD Computer object for the old site server. The computer object itself in AD has permissions to do some activities, if you were to make a new computer object you would have to go back through and grant it permissions again... ~Tom