image

After applying KB971413 to fix Multicasting for SCCM 2007 OSD deployments where the Windows OS WIM file is over 4GB, Multicast OS deployments may no longer work, including for Windows OS WIM files that are under 4GB. If enabled, the deployment falls back to Unicast and completes successfully.

Cause

The most likely cause is the site reset initiated during the install of KB971413. A site reset initiates a reinstall of all of the site components. If a Multicasting session is initiated too soon after the site reset, and if the site reset has not completed and if not all of the components have finished reinstalling, in particular the components associated with Multicasting, then the Multicasting session will fail.

Resolution

The first and easiest resolution is to give the site reset some time to complete. However, if after waiting Multicasting is still not working, then some or all of the following actions may need to be taken:

  1. Disable and then reenable “Allow this package to be transferred via multicast (WinPE only)” in the properties of the OS image
  2. Disable and then reenable the Multicast option in the properties of the DP
  3. Reinstall WDS

The exact and detailed steps that need to be taken are listed below. Please note that we want to minimize server reboots in case the site reset is still being performed in the background:

  1. In the SCCM 2007 console, under the Operating System Images, right click on the OS Image being multicasted and choose “Properties”
  2. Click on the “Distribution Settings” tab
  3. Uncheck the option “Allow this package to be transferred via multicast (WinPE only)” and then click “Apply”
  4. Recheck the option “Allow this package to be transferred via multicast (WinPE only)” and then click “OK”
  5. Repeat steps 1-4 for each OS image you have set to multicast
  6. Run a Multicast deployment over 4GB and make sure that everything works

If that does not resolve the issue:

  1. In the SCCM 2007 console, under the Operating System Images, right click on the OS Image being multicasted and choose “Properties”
  2. Click on the “Distribution Settings” tab
  3. Uncheck the option “Allow this package to be transferred via multicast (WinPE only)” and then click “OK”
  4. Repeat steps 7-9 for each OS WIM image that you have set for Multicast
  5. Disable the Multicast DP by going into the properties of the DP role, clicking on the Multicast tab, uncheck “Enable Multicast”, and then click OK.
  6. Monitor the MCSSetup.log and the MCSMSI.log. Wait until it uninstalls successfully.
  7. Reinstall Multicast by going to the properties of the DP role, clicking on the “Multicast” tab, check “Enable Multicast”, and then click OK.
  8. Monitor the MCSSetup.log and the MCSMSI.log. Wait until it installs successfully.
  9. In the SCCM 2007 console, under the Operating System Images, right click on the OS Image being multicasted and choose “Properties”
  10. Click on the “Distribution Settings” tab
  11. Check the option “Allow this package to be transferred via multicast (WinPE only)” and then click “OK”
  12. Repeat steps 15-17 for each OS WIM image you have set to multicast
  13. Run a Multicast deployment over 4GB and make sure that everything works

And finally if the issue is still not resolved:

  1. Follow steps 7-12 above
  2. If the server is not a PXE Service Point, skip to step 24
  3. If the server is also a PXE Service Point, delete the Boot Images from the PXEBOOTIMAGES$ DP and uninstall the ConfigMgr PXE service point role.
  4. Monitor the PXESetup.log and ensure that the PXE service point is uninstalled correctly
  5. Uninstall WDS
  6. If prompted to do so, restart the server
  7. Reinstall WDS, making sure to select the both the Deployment Server and the Transport Server
  8. If the server is not a PXE Service Point, skip to step 31
  9. If the server is also a PXE Service Point, reinstall the ConfigMgr PXE service point role
  10. Monitor the PXESetup.log and ensure that the PXE service point is installed correctly. If the log prompts to restart the server, restart the server.
  11. Add the Boot Images back to the PXEBOOTIMAGES$ DP.
  12. Follow steps 13-19 above

Frank Rojas | Senior Support Engineer