Edgy41

Hi, This issue was resolved with assistance by Microsoft via several very lengthy support calls. The core issues related to the SQL database and Microsoft had to directly manipulate the db in order to then be able to run the upgrade. Not sure exactly what caused the issues in the first place however all resolved now.

The proxy appears to be working fine in terms of downloading content. I have tested and verified this by manually downloading the content. Also I ran the SQL command to delete the updates from the DB, then deleted all content from the Microsoft Configuration Manager\EasySetupPayload folder and re-started the sever - once done the content re-downloads and goes through the motions of extracting. The issue right now is that in the SCCM console I can see 3 updates that are stuck in a "Downloading" state (1602, 1606, 1610). Checking the dpmdownloader.log shows: File D:\LocalApp\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File SMSSETUP\BIN\X64\SYSTEM32\SMSMSGS\climsgs.cmd is being extracted SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File D:\LocalApp\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File SMSSETUP\BIN\X64\SYSTEM32\SMSMSGS\climsgs.dll is being extracted SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File D:\LocalApp\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File SMSSETUP\BIN\X64\SYSTEM32\SMSMSGS\provmsgs.cmd is being extracted SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File D:\LocalApp\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File SMSSETUP\BIN\X64\SYSTEM32\SMSMSGS\provmsgs.dll is being extracted SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File D:\LocalApp\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File SMSSETUP\BIN\X64\SYSTEM32\SMSMSGS\srvmsgs.cmd is being extracted SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File D:\LocalApp\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File SMSSETUP\BIN\X64\SYSTEM32\SMSMSGS\srvmsgs.dll is being extracted SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File D:\LocalApp\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File SMSSETUP\OSD\bin\I386\00000409\TsRes.dll is being extracted SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File D:\LocalApp\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File SMSSETUP\OSD\bin\x64\00000409\tsres.dll is being extracted SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File D:\LocalApp\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File SMSSETUP\OSD\Tools\WTG\Creator\wtgcreator.exe is being extracted SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File D:\LocalApp\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File SMSSETUP\scripts\00000409\pdfstore\load\DmCliXfer.sms is being extracted SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File D:\LocalApp\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File SMSSETUP\scripts\00000409\pdfstore\load\smsclint.sms is being extracted SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File D:\LocalApp\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File SMSSETUP\OSD\Tools\WTG\BitLocker\I386\OsdBitLocker_wtg.exe is being extracted SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File D:\LocalApp\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File SMSSETUP\OSD\Tools\WTG\BitLocker\x64\OsdBitLocker_wtg.exe is being extracted SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) File D:\LocalApp\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) Check if there is redist to download for update, 609f1263-04e0-49a8-940b-09e0e34de2d2 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) There is web proxy configured for the connector. Use it to download redist SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) Download redist for update 609f1263-04e0-49a8-940b-09e0e34de2d2 SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) Start to download redist for 609f1263-04e0-49a8-940b-09e0e34de2d2 with command /RedistUrl http://go.microsoft.com/fwlink/?LinkID=724436 /LnManifestUrl http://go.microsoft.com/fwlink/?LinkID=724434 /RedistVersion /ProxyUri http://proxy.tnet.internal:8080/ /ProxyUserName TNET\MSSCService /ProxyUserPassword 3082017F06092A864886F70D010703A08201703082016C020102318201303082012C020102801497DC0957A8D11CFE2D104C34B13BE010B2C4716C300D06092A864886F70D01010105000482010025C48363EFC219242CD1316942281EA71C801FA19E40F2E28C124ED067F191F5EED05F2019F61CF198C5D4553A19408EE463952A6C4DEC6D5C3EAEE7848F35C90C0D979295CE532CC34D64432A01C69C4C37EFA3CEE43DECDABA43CBDCC27FEC910EA1013095A662CFAC92718D3214DEDC7311DC58EA6A2032F936D3184BAB8DE539D058EC3FF41A9776A54FE02B6F8BEAB9FACB434BF1773E896A02596547E0D2588A3FBB6E492EA1A836D66EC358AD74775F0396033F8CAE099CEC2CA03415722565114E30E9EDAE72E2B37A00C32197874DDF71D88E02A197D85C4F0060B02E008DFF6A01FAAA3207D582A432950FE36A22B8CE8E01A5D136442D3844C601303306092A864886F70D010701301406082A864886F70D030704087BB712ADB5021810801098ED95A53E3F6D704AC8069335D644A7 /NoUI "\\TWPSCCM1VTO.tnet.internal\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2\redist" . SMS_DMP_DOWNLOADER 27/03/2017 10:04:13 AM 4380 (0x111C) Check whether the site has intune subscription SMS_DMP_DOWNLOADER 27/03/2017 10:06:22 AM 2044 (0x07FC) Check whether the site has intune subscription SMS_DMP_DOWNLOADER 27/03/2017 10:11:24 AM 2044 (0x07FC) Check whether the site has intune subscription SMS_DMP_DOWNLOADER 27/03/2017 10:16:25 AM 2044 (0x07FC) Check whether the site has intune subscription SMS_DMP_DOWNLOADER 27/03/2017 10:21:26 AM 2044 (0x07FC) Check whether the site has intune subscription SMS_DMP_DOWNLOADER 27/03/2017 10:26:28 AM 2044 (0x07FC) The end result is that it wont get past 'Check whether site has intune subscription'. When I upgraded our dev SCCM server I saw that it continued on to the next step after this without issue.

Hi, I'm attempting to upgrade our customers production instance of SCCM from Current Branch version 1511 up to version 1610. Here's the story so far..... 1) Successfully upgraded the dev SCCM server from CB 1511 to 1610. It passed all prerequisite checks. Server 2012 box with SQL Server 2014 SP1 2) Ran prerequisite check on prod SCCM box for the 1610 upgrade and noticed that there was a warning about the version of SQL Server. Checked the version and found it to be SQL Server 2012 which is not a supported version for SCCM current branch 3) Stopped all Configmgr services and upgraded SQL Server on the prod SCCM server to SQL 2014 SP1. The process ran smoothly without issue with the exception of that I cannot seem to manually stop the SMS_Executive service - it just says 'stopping' and eventually times out. This is an ongoing issue. What I did was disable all services and restarted the server so that all services were not running when the server came back online 4) Re-ran the SCCM 1610 prerequisite check and this time it passed the SQL server version and everything else. All ok there so I thought I can now install the 1610 upgrade 5) Attempted to run the upgrade to 1610 and the end result was that it failed.The CMUpdate logs shows SQL related issues. I have attached the whole log to this post 6)There was an option to re-install the 1610 update so I did that. It then got stuck at running the prerequisite check so I ran the following command to delete the entry from the SQl DB: DELETE FROM CM_TGT.dbo.CM_UpdatePackages WHERE PackageGuid='af633310-e419-44b3-9e0e-ab93d57087cf'; Running this removed the update package from the SCCM console 7) I restarted the SMS_DMP_DOWNLOADER service and checked the dmpdownloder log and it appeared that it was re-downloading the 1610 package but then it errored showing "ERROR: Failed to download redist for af633310-e419-44b3-9e0e-ab93d57087cf with command /RedistUrl http://go.microsoft.com/fwlink/?LinkID=831290 /LnManifestUrl http://go.microsoft.com/fwlink/?LinkID=831291 /RedistVersion 201610 /ProxyUri http://proxy.tnet.internal:8080/ /ProxyUserName TNET\MSSCService /ProxyUserPassword 3082017F06092A864886F70D010703A08201703082016C020102318201303082012C020102801497DC0957A8D11CFE2D104C34B13BE010B2C4716C300D06092A864886F70D0101010500048201006095AE9A8B36976488E450652906CEC00F35EADBE8ABA6E08A60BB091163F9DC9DB114B82FFAB91FFFA7E98773EBE02B6E6D482D55FE47F506BD9D71C183E1D709A6B912C2E85AC7E10F7A52C1B8470F07DD13EA10F74EB9873D6FA43ADF1B1735A5EE4AAB957440B78B2D496D0AAD3A11EFBA9F8296AA24162E0AF8EBD8F57225DD122344B40A3B964AE7D508104891F164E1DFABC4E2F80E8025B9F2A498FD94F271563AE644A0AD9B91FA069A4579C9A375540BAF38A77EA78322BABBEFED31067D61BD8BA9F0B54EBB9A7931FD2A6B5D3DC6CF7B2DB2243030074F17DADF4561DA3AC3BBAB4408D3FA0D6EA72864EB35E4A890A2AAAF98C2B28A09F6CE24303306092A864886F70D010701301406082A864886F70D030704088A6E28EFAFDD00798010932CB1B7E2912B29692FECCDB4A59E70 /NoUI "\\TWPSCCM1VTO.tnet.internal\EasySetupPayload\af633310-e419-44b3-9e0e-ab93d57087cf\redist" . I have attached the whole dmpdownloder log as well. 8) I re-ran the SQL command to delete from the DB. Again the 1610 update was removed from SCCM and after a server re-start it again attempted to download the 1610 update but it fails.It does say to re-start the SMS_Executive service but I cannot do that manually so i have to re-start the server to stop and start the service So the end result of all of the above is that now the SCCM 1610 upgrade gets stuck at "Downloading" and I cannot seem to progress or get past this to run the install again. Any help anyone could give me would be much appreciated Is there anything i'm missing here? Happy to provide other logs if needed or further info if any of this is not clear CMUpdate.log dmpdownloader.log

Hi Dan, Glad you resolved this. I have just come across the same ADR errors in SCCM. Am going to the SCCM admin re-start the server. Cheers, David E

Hi all, Need some assistance...... I am currently writing a 'Hardware and Lifecycle Manegement and Assessment Plan' for one of my company's customers in relation to thier fleet of Desktop Computer Systems. We have put in SCCM 2012 as the solution for Systems management and as part of the plan I an writing I would like to include a section that describes where / how to extract a full hardware inventory of all Workstation computers in SCCM. The inventory should include such things as: Name of Computer Serial Number / Service Tag (Dell systems) RAM Make and Model CPU HDD Video Card Spund Card Any other relevany info for Hardware inventory So given all of the above, is there a default report in SCCM that will list this info in one single report? Or do I have to create a custom report for this? If so can someone recommend how I go about doing this exactly? I should mention that I am very much the novice when it comes to SCCM reporting so any assistance here would be appreciated. Thanks

I have setup a Oracle Virtualbox VM SCCM 2012 lab environment and I have recently been experiencing this issue when attempting to run Build and Capture TS for Win 7 Pro x64. It was really weird that it just started happening to me as I am pretty sure I havent made and changes anywhere that would affect permissions. Anyway, I enabled Anonymous auth in IIS manager (as suggested in the previous posts) on the Default Website / SMS_DP_SMSPKG$ and viola it worked!! I am now able to image VM's again. As I have a lab environment I really didn't mind enabling Anonymous auth but I am not sure it would be advisable to do this in full production environments. I have posted my smsts.log file for anyone to peruse. I would love to know what caused this issue to start happening in the first place. smsts.log