Search the Community

Hello, We recently turned on Multicast within our SCCM environment and have been progressively searching for an answer to the following task sequence error: Task Sequence has failed with error code (0x80091007). In searching through the client workstation's SMSTS.log file we see the following: 1. pDownload->Download(pwszServer, pwszNamespace, pwszRemoteObject, pwszLocalObject, uCacheSize), HRESULT=800706ba (e:\nts_sccm_release\sms\server\mcs\consumer\mcclient.cpp,120) ApplyOperatingSystem 5/16/2017 5:25:34 PM 1712 (0x06B0) 2. Encountered error transfering file (0x800706BA). ApplyOperatingSystem 5/16/2017 5:25:34 PM 1712 (0x06B0) 3. Sending status message: SMS_OSDeployment_PackageDownloadMulticastStatusFail ApplyOperatingSystem 5/16/2017 5:25:34 PM 1712 (0x06B0) Since it is unable to transfer the file via multicast you get the following: 4. Hash could not be matched for the downloded content. Original ContentHash = C61CCE4D5DA21B9A531B268C6690D5A1D79867A1CC428E84E96C9CDDFCE1B94A, Downloaded ContentHash = ApplyOperatingSystem 5/16/2017 5:25:34 PM 1712 (0x06B0) 5. 0L == TS::Utility::VerifyPackageHash (pszContentID, sDestination), HRESULT=80091007 (e:\cm1702_rtm\sms\framework\tscore\resolvesource.cpp,3291) ApplyOperatingSystem 5/16/2017 5:25:34 PM 1712 (0x06B0) 6. DownloadContentAndVerifyHash() failed. 80091007. ApplyOperatingSystem 5/16/2017 5:25:34 PM 1712 (0x06B0) 7. Installation of image 1 in package DL100069 failed to complete.. The hash value is not correct. (Error: 80091007; Source: Windows) ApplyOperatingSystem 5/16/2017 5:25:34 PM 1712 (0x06B0) We've verified the proper core switch configurations for across VLAN multicasting and have also ensured the OS, driver packages, etc are set to "allow multicast" within SCCM. We've also redistributed the content to the distribution points using multicasting to ensure there isn't an issue there. With how quickly it fails it doesn't appear that it is even able to pull the OS multicast file. In looking at the distribution point we have enabled for multicast we see the following in the MCSIsapi.log: 1. Could not create an instance of the MCSISAPIProxy object (0x80070005) McsIsapi 5/16/2017 8:00:03 PM 3000 (0x0BB8) 2. HealthCheckRequest::HandleMessage failed with errorcode (0x80070005) McsIsapi 5/16/2017 8:00:03 PM 3000 (0x0BB8) 3. Failed to process HEALTHCHECK request for client ffffffff-ffff-ffff-ffff-ffffffffffff McsIsapi 5/16/2017 8:00:03 PM 3000 (0x0BB8) 4. MCSRequestHandler::HandleMessage for Op HEALTHCHECK failed with server errorcode 2052 McsIsapi 5/16/2017 8:00:03 PM 3000 (0x0BB8) 5. Looking for: E:\SCCMContentLib\DataLib\DL100069* McsIsapi 5/16/2017 8:06:52 PM 2972 (0x0B9C) 6. Looking for: E:\SCCMContentLib\DataLib\DL100069* McsIsapi 5/16/2017 8:35:22 PM 2972 (0x0B9C) Even though it is looking for that package, the distribution point has it when you search in that location. We've found several forums/articles with people who have similar issues but none of the items they recommend trying to seem to work for us. The closest article to what we are experiencing is the following: http://thoughtsonopsmgr.blogspot.in/2014/08/sccm-2012x-multicast-another-bites-dust.html We are running Configuration Manager 1702 running on Server 2012 R2 x64. All of the distribution points are also on Server 2012 R2 x64. I would also like to add that as soon as we turn off multicast in the distribution point, it works flawlessly on unicast. Any thoughts on where to go on this one would be greatly appreciated. Thanks /Gus

Hello all. I am running into multicast issues and looking for some help. Current system: SCCM 2012 R2 Cumulative Update 3 (5.0.7958.1401) with 1 site server, 1 db server, and 1 distribution point. I have a task sequence to push out an image via multicast but on the client computer I keep getting error number 80070002. The DP is set to enable multicast, all the contact within the task sequence is located on the DP and all packages are set to "allow this package to be transferred via multicast." I read a few places that turning off multicast support on the DP for an hour then turning it back on would correct the issue. This is a copy of the log file after doing so. Notice the Error finding namespace entry in the log. Any help and suggestions would be greatly appreciated. Thank you. Josh Multicast error file: Setting WDS IpAddressSource McsExec 11/21/2014 1:38:51 PM 5088 (0x13E0) Running: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:51 PM 5088 (0x13E0) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:51 PM 5088 (0x13E0) Run completed for: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:52 PM 5088 (0x13E0) Running: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:52 PM 5088 (0x13E0) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:52 PM 5088 (0x13E0) Run completed for: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) Succesfully Configured WDS McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) Error finding namespace McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) Checking MCS Certificate McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) MCSEncryptionCert Created. Length 980. McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) ========== HealthCheck ffffffff-ffff-ffff-ffff-ffffffffffff McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) Error finding namespace: 0xc1100113 McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) Setting WDS IpAddressSource McsExec 11/21/2014 1:38:55 PM 2468 (0x09A4) Running: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:55 PM 2468 (0x09A4) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:55 PM 2468 (0x09A4) Run completed for: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:56 PM 2468 (0x09A4) Running: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:56 PM 2468 (0x09A4) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:56 PM 2468 (0x09A4) Run completed for: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:57 PM 2468 (0x09A4) Succesfully Configured WDS McsExec 11/21/2014 1:38:57 PM 2468 (0x09A4) Setting WDS IpAddressSource McsExec 11/21/2014 1:43:36 PM 4924 (0x133C) Running: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:43:36 PM 4924 (0x133C) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:43:36 PM 4924 (0x133C) Run completed for: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:43:37 PM 4924 (0x133C) Running: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:43:37 PM 4924 (0x133C) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:43:37 PM 4924 (0x133C) Run completed for: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:43:38 PM 4924 (0x133C) Succesfully Configured WDS McsExec 11/21/2014 1:43:38 PM 4924 (0x133C) ========== HealthCheck ffffffff-ffff-ffff-ffff-ffffffffffff McsExec 11/21/2014 1:43:53 PM 4244 (0x1094) Error finding namespace: 0xc1100113 McsExec 11/21/2014 1:43:53 PM 4244 (0x1094) Error finding namespace McsExec 11/21/2014 1:48:53 PM 3328 (0x0D00) ========== HealthCheck ffffffff-ffff-ffff-ffff-ffffffffffff McsExec 11/21/2014 1:48:53 PM 312 (0x0138) Error finding namespace: 0xc1100113 McsExec 11/21/2014 1:48:53 PM 312 (0x0138) ========== HashAndSignBuffer McsExec 11/21/2014 1:52:19 PM 312 (0x0138) ========== OpenSession McsExec 11/21/2014 1:52:19 PM 312 (0x0138) Error finding namespace McsExec 11/21/2014 1:52:19 PM 312 (0x0138) ========== OpenSession -- exit code: 0xc1100113 McsExec 11/21/2014 1:52:19 PM 312 (0x0138) ========== HashAndSignBuffer McsExec 11/21/2014 1:52:19 PM 312 (0x0138) ========== OpenSession McsExec 11/21/2014 1:52:20 PM 312 (0x0138) Error finding namespace McsExec 11/21/2014 1:52:20 PM 312 (0x0138) ========== OpenSession -- exit code: 0xc1100113 McsExec 11/21/2014 1:52:20 PM 312 (0x0138) ========== HealthCheck ffffffff-ffff-ffff-ffff-ffffffffffff McsExec 11/21/2014 1:53:53 PM 312 (0x0138) Error finding namespace: 0xc1100113 McsExec 11/21/2014 1:53:53 PM 312 (0x0138)

I need to refresh clients in a classroom environment every 3 months to ensure compliance and keep drift under control. I am not sure whether I need to use OSD or Multicast for the deployments. Does anyone have a chart or list of the Pro's and Con's of each?

Hey Everyone! Hopefully someone will be able to help me on this as I have been tearing my hair out the last few days trying to nail down what is causing my issues. OK, so I have had an MDT 2012 Update 1 server (Server 2008 R2 with WDS) up and running for quite some time now with (usually) no issues. I have gone ahead and started making my new image for my school system (Windows 7 x64 w/SP1) and am using a thick image approach so that everything is in the image and we can hopefully get things deployed faster. However, when I go to deploy my new image, the client makes the connection and goes through the process of downloading the image, restarts (as part of the normal standard task sequence) and then presents the attached error shown below in PrimaryImageError2.PNG. After click OK on that error, I am then presented with the deployment summary screen with a listing of errors (as shown in PrimaryImageError.PNG). The odd thing is that if I go into my Deployment Workbench, right-click on my Deployment Share and turn off multicasting, the image loads perfectly every time. Seeing as how I am trying to apply this to several hundred machines this Summer, using unicast sessions is far from ideal. I have Googled up and down the internet for possible fixes. I have re-captured my image (made in VMWare Workstation) several times with different options in sysprep thinking that may have caused issues, but no luck. We were hoping to start imaging machines almost 2 full days ago now and I can only stay up till 1-2AM so many times in a row trying to figure this out. Anybody out there have any ideas or advise? Was debating upgrading to MDT 2013 to see if that fixes any issues, but I'm trying not to cause other problems/conflicts as well this close to my deployment time . However, if anyone thinks that might work, I'll definitely try it... Thanks in advance for any suggestions and your time Scott

On my site distribution points, I am having an issue with after installing them that the SMS_MULTICAST_SERVICE_POINT comes up as critical under component status. This is because the mutli cast is not being installed for some reason. In teh status Message Details, i recieve this message, "Site Component Manager failed to install this component, because the Microsoft Installer File for this component (mcs.msi) could not install." in the mcsMSI.log.LastError I see these messages: Property(S): System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61 = C:\Windows\system32\ Property(S): SMSCACHEDIR = Default Property(S): SMSCACHEFLAGS = Default Property(S): DISABLESITEOPT = Default Property(S): DISABLECACHEOPT = Default Property(S): SMSCACHESIZE = 5120 Property(S): SmsShellNotify_ActionText = Notifies the shell for the file-association icon changes. Property(S): CcmInstallMCS = D:\SMS_CCM\ 0 Property(S): WDS_ActionData = WDS Property(S): WDS_UnregisterActionData = WDS_UNINST Property(S): SmsMCSDetectDowngrade_ErrorMessage = A newer version of the SCCM Multicast Service Point is already installed Property(S): ARPSYSTEMCOMPONENT = 1 Property(S): ARPNOREMOVE = 1 Property(S): ARPNOMODIFY = 1 Property(S): MCSENABLELOGGING_Default = TRUE Property(S): MCSLOGLEVEL_Default = 0 Property(S): MCSLOGMAXSIZE_Default = 2000000 Property(S): MCSLOGMAXHISTORY_Default = 1 In the MCSSetup.log I see this: <05/12/14 15:14:16> ======== Completed Installation of Pre Reqs for Role SMSMCS ======== <05/12/14 15:14:16> Installing the SMSMCS <05/12/14 15:14:16> Machine is running Windows Operating System or later. (NTVersion=0X601, ServicePack=1) <05/12/14 15:14:16> IIS Service is installed. <05/12/14 15:14:16> Created the DP mutex key for WDS. <05/12/14 15:14:16> Created the DP mutex value for WDS. <05/12/14 15:14:16> Machine is running Windows Server. (NTVersion=0X601, ServicePack=1) <05/12/14 15:14:16> WDS is INSTALLED <05/12/14 15:14:16> WDS Service is installed. <05/12/14 15:14:16> No versions of SMSMCS are installed. Installing new SMSMCS. <05/12/14 15:14:16> Enabling MSI logging. mcs.msi will log to D:\SMS\logs\mcsMSI.log <05/12/14 15:14:16> Installing D:\SMS\bin\x64\mcs.msi CCMINSTALLDIR="D:\SMS_CCM" CCMSERVERDATAROOT="D:\SMS" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 MCSENABLELOGGING=TRUE MCSLOGLEVEL=1 MCSLOGMAXSIZE=1000000 MCSLOGMAXHISTORY=1 <05/12/14 15:14:27> mcs.msi exited with return code: 1603 <05/12/14 15:14:27> Backing up D:\SMS\logs\mcsMSI.log to D:\SMS\logs\mcsMSI.log.LastError <05/12/14 15:14:27> Fatal MSI Error - mcs.msi could not be installed. <05/12/14 15:14:27> ~MCSRoleSetup(). <05/12/14 15:14:27> Stopping wdsserver service <05/12/14 15:14:32> Starting wdsserver service <05/12/14 15:14:32> RegOpenKeyEx failed (2) for: Software\Microsoft\CCM\Logging <05/12/14 15:14:32> RegOpenKeyEx failed (2) for: Software\Microsoft\CCM\Logging\@GLOBAL <05/12/14 15:14:32> RegOpenKeyEx failed (2) for: Software\Microsoft\CCM\Logging\McsIsapi <05/12/14 15:14:32> RegOpenKeyEx failed for Software\Microsoft\CCM\Logging\@GLOBAL <05/12/14 15:14:32> RegWriteDWord failed. 80070002. <05/12/14 15:14:32> ReleaseDpMutexForWDS: Deleting the DP mutex key for WDS. <05/12/14 15:14:32> ~MCSRoleSetup() - 00000000 <05/12/14 15:14:32> ~RoleSetup(). Any hep with this is greatly appreciated

Question on setting up multicast? What kind of bandwidth chatter do you guys see when turning on SCCM 2012 R2 multicast for image deployments? My network guys are not wanting to turn on multicast on the router/switches because they say it causes too much traffic network wide. Do you guys see this as an issue? We've discussed putting a DP at each of our 20 remote sites, they have 100MB connections but we're saturating those with only a few non-multicast deployments running at one time. So why would multicast cause more traffic when that's what we're trying to avoid? How do you guys deploy images to 30+ computers at a time without saturating your networks? We used to use Altiris and it would make one machine the master then the rest clients so it would only push one image for all 30 machines.

I've run into a strange problem and I'm not sure if it's a bug or something isn't functioning properly or if it's just the way Config Mgr Clients work. If I boot WinPE from PXE or USB media and run an OSD task sequence multicast works perfect. If I run the same OSD task sequence from the ConfigMgr Client on a machine (which just downloads WinPE and then boots into it) when it reboots into WinPE it starts downloading the OS image via unicast instead of multicast. I'm using the exact same task sequence and WinPE boot image. The OS image is even set to "Transfer this package only via multicast". The SMSTS log does not indicate that it's attempting to start a multicast session, it just starts unicast. Any ideas?

Hey guys, my first topic, but a really strange problem. When installing a baremetal pc my multicast works. When reinstalling a computer the multicast doesn't work ... it just starts downloading without counting down and with no multicast-stream. I receive no error and everything is ok except that the multicast never worked. The settings on my windows 7 package are "allow this package to be transferred via multicast (winpe only) with the extra option "Transfer this package only via multicast". When I look at the log files I see no intention to start a multicaststream, thats pretty weird. i'll go a bit into detail about my setup (SCCM SP1): 1 server - SQL 1 server - primary site + distribution point 1 server - distribution point With unknown computers I work with a frontend HTA where I can select wheter to use multicast or not. Depending on that variable the correct wim file is selected and use of multicast or not. When reinstalling computers the correct wim file is selected but there is no multicast session. Downloading just starts ... The variable to use multicast is given with a collection variable and according to the logfile is working. Also I can see on the name that the correct multicast-wim-file is selected. The primary site does not contain the OS-package and multicast is disabled. The distribution point has multicast enabled and obviously contains the os-package for multicasting. Do you guys have any idea?