I have tried review related topics but couldn't resolve my issues

Multicast works on one of DP with same boot image and task sequence with all same settings but fails on rest 2 DP's.

Reviewed McsPrv.log, MCSIsapi.log, McsExec.log but couldn't find any specific error.

Smsts.log shows following errors

Records task sequence activities. This log file is from a client running the OSD task sequence and attempting to use multicast. 

• Encountered error transferring file (0x800705B4)
• Sending status message: SMS_OSDeployment_PackageDownloadMulticastStatusFail

These two lines above show that the multicast transmission has not taken place and has failed.

 

• Hash could not be matched for the downloaded content (followed by hash number)
• DownloadContentAnd VerifyHash() failed. 80091007.

I have tried remove and reinstall WDS on faulty DP. Enable and disable multicast on distribution but no luck.

I would really appreciate for any help...

RJ

Unfortunately I've seen a lot of different issues with an hash error in multicast and there hasn't been one solution that fits it all... See for some possible problems this blog post: http://henkhoogendoorn.blogspot.nl/2013/02/multicast-error-0x80091007-during.html

Hi,

Please refer to the link below:

SCCM 2012x Multicast: Another Bites The Dust With Error 0x80091007

http://thoughtsonopsmgr.blogspot.in/2014/08/sccm-2012x-multicast-another-bites-dust.html

Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

I followed suggestion and after turning off/on Multicast on DP's, resolved my issues 

But since I am doing imaging again using multicast and getting same errors again. Please see logs below from 2 distribution points. Exact same error. 

I turned off and on multicast again and it worked on one of DP's. 

Could someone take a look and advise please

Failed to perform health check (0x80004005) McsIsapi 26/12/2014 4:10:44 PM 1700 (0x06A4)
HealthCheckRequest::HandleMessage failed with errorcode (0x80004005) McsIsapi 26/12/2014 4:10:44 PM 1700 (0x06A4)
Failed to process HEALTHCHECK request for client ffffffff-ffff-ffff-ffff-ffffffffffff McsIsapi 26/12/2014 4:10:44 PM 1700 (0x06A4)
MCSRequestHandler::HandleMessage for Op HEALTHCHECK failed with server errorcode 2052 McsIsapi 26/12/2014 4:10:44 PM 1700 (0x06A4)

Could not create an instance of the MCSISAPIProxy object (0x80070005) McsIsapi 29/12/2014 7:56:53 AM 5800 (0x16A8)
HealthCheckRequest::HandleMessage failed with errorcode (0x80070005) McsIsapi 29/12/2014 7:56:53 AM 5800 (0x16A8)
Failed to process HEALTHCHECK request for client ffffffff-ffff-ffff-ffff-ffffffffffff McsIsapi 29/12/2014 7:56:53 AM 5800 (0x16A8)
MCSRequestHandler::HandleMessage for Op HEALTHCHECK failed with server errorcode 2052 McsIsapi 29/12/2014 7:56:53 AM 5800 (0x16A8)

I would really appreciate any help..

RJ

RJ09

Take a look at this thread, it might help. Without knowing your network setup, I can't say for sure, but your client does not seem to be able to find the multicast DP. I was receiving the hash error myself because my DHCP client was not using the FQDN to connect to the DP. This was verified with network traces\packet captures. I think this is a possible bug. We see the connection also trying to use NetBios which does not cross sub-nets. I had to use a host file at first, but then I just used DNS alias on my DP's to match the "Connection-Specific DNS Suffix" that is being assigned to my clients. P.S. What type of speeds are you getting with multicasting on the one working DP.

• Proposed as answer by Tony Chirillo Monday, December 29, 2014 8:24 PM
• Edited by Tony Chirillo Wednesday, December 31, 2014 2:40 PM

Not exactly sure if I am looking at right spot for network speed.

I have checked in Task Manager and under Networking tab on client getting imaged.

It shows 0% Network utilization on 1Gbps link Speed at this stage of imaging..

In task manager under "views" you can turn on columns for "bytes per interval" and "bytes received per interval". The data will show in megabits so it needed to be manually converted to megabytes. I just used a Google search of "megabits to megabytes" to find a calculator.

Thanks,

Although Bytes Sent and received per interval varies during downloading and apply operating system image step

But average is about Bytes sent Interval- 7800 Received Interval= 2267 

Not sure how would this help figuring out why multicast fails!!

Please let me know if you need any more information, I am stuck with ongoing multicast issues.

One more thing to mension I just enable PXE on one of DP's DP1 for first time but it still getting PXE from head office DP0( it was always getting PXE from DP0).

Verified with network team, all pxe required ports are open.

But multicast still works for this moment on this DP1.

I really appreciate your

Your are right, the speed stuff wont help to figure out why multicasting is failing. Sorry for the confusion. I was just interested in your speeds because were are experiencing very slow multicast speeds and  still trying to figure that out.

On the DP where multicast is working, is that DP in the same subnet as your client your are successfully multicasting to?

What about the other DP's, are they on the same or different subnets as your clients? My issues spanned from the clients being on different subnets as our multicast enabled DP's. All of our servers are kept in a separate subnet. The client was trying to find the DP's through Netbios broadcasts which that traffic doesn't cross subnets, I had to you one on the workaround talked about here.

--Tony

Clients are on different subnets and DP's are on different subnet.

If we can use unicast why would this only effect multicast imaging? 

And other thing I don't understand why it works intermittently. if its Netbios why would it happen occasionally?

Its just confusing me..

Thanks

RJ

From my experience unicast uses a FQDN to identify the DP where as multicast does not. You are saying multicast works sometimes on one DP and never on the other two? Correct? From the original post, I thought it was working all the time on 1 DP.

I was having this same issue. I had put the it down as I will never be able to multicast and was only using unicast. Just today I stumbled across this 

https://support.microsoft.com/en-us/kb/977512

Made the one registry change and voila multicast is working all of a sudden.

Hope this helps.