I'm trying to deploy our OS image using multicast where the server and clients are in different VLANS and am having absolutly no luck. All the packages and images are setup for multicast ("allow this package to be transfered via multicast" is ticked), i've had HP look over the config of our switches and they cannot find any errors. I have used a tool called Multicast Hammer to test whether multicast traffic can be routed and it works across VLANS using this, but not using SCCM. The OSD task starts correctly, boots into WinPE and formats the drive but fails at Applying Operating Systems with the following error: Received error: 0x8004080b while initiating multicast download. I've uploaded the smsts.log and the all the multicast logs I have from the server to our SkyDrive: https://skydrive.live.com/redir.aspx?cid=2cac77a324aaca98&resid=2CAC77A324AACA98!124 At the moment both the server and client are plugged into the same switch. If the server and client are on the same VLAN I have no issues and the task downloads packages using multicast. Additionally, we are able to use multicast with Symantec Ghost so I am fairly sure this isn't a networking problem. We are using HP Procurve 5406zl as the switch, SCCM is 2007 R3 installed as VM on W2K8 R2 SP1 Std, the VM host runs W2K8 R2 SP1 Data Centre. Any suggestions as to what might be wrong?

have any iphelpers been configured ? My step by step SCCM Guides I'm on Twitter > ncbrady

Yes, but only to our DHCP servers. DHCP is on a different server. I did try and configure an ip helper to the SCCM server on VLAN the client is connected to, that didn't make a difference. In DHCP I have configured options 66 to point to the IP of the SCCM server and option 67 is \SMSBOOT\x64\wdsnbp.com I figured that as it works with server and client on the same VLAN that this was correct.

most time config DHCP Scope take affect. but config IP helper is more efficicency in different vlan

DHCP scopes appear to be working, but to see if this makes a difference is it just a case of removing the options from the scopes and adding a ip helper to each vlan pointing at the SCCM server?

please also check IGMP snooping on your router- http://technet.microsoft.com/en-us/library/dd637994%28WS.10%29.aspx "Routers that support multicasting. In particular, Internet Group Membership Protocol (IGMP) snooping should be enabled on all devices. This will cause your network hardware to forward multicast packets only to those devices that are requesting data. If IGMP snooping is turned off, multicast packets are treated as broadcast packets, and will be sent to every device in the subnet." My step by step SCCM Guides I'm on Twitter > ncbrady

Already checkd that, IGMP is enabled on all devices.

Have you already seen http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/f0028279-8832-4a0f-b07b-3d71ee8944dd/? You should trace the network traffic using Netmon/Wireshark if the link does not help. Torsten Meringer | http://www.mssccmfaq.de

I had looked at that. IPv6 is already disabled and i've checked the resolution of the server by enabling command prompt on the boot image then pinging the server by it's fqdn and it's resolving fine. I started to look at the network traffic using Wireshark but to be honest don't really know what I am looking at or for!

most time config DHCP Scope take affect. but config IP helper is more efficicency in different vlan I've removed all of the options from the DHCP scpoes and configured IP helpers. This hasn't made a difference.

I have got this partly resolved with the help of Microsoft PSS. We did not have the WINS options set on our DHCP scopes. Once there were set, the WIM file is being downloaded using multicast. However, the additional packages that we are installing outside of the WIM are not downloading using multicast. Instead they are producing the following error in the smsts.log: 0x8007002 unable to find multicast dll. I'm waiting for the engineer to come back to me on this, but in the meantime has anybody else seen this error?

I am getting the same issue with an HP switch across vlans. Did you get a resolution to this issue? - I ahve the same set up you have described.

Yep I did. We did not have the WINS address set on our DHCP scope options. This was the root cause of the issue in the end. Cheers Adam.