OSD Multicasting
Hi there,
System setup -
ConfigMgr 2007 R2 - mixed mode
Windows 2008 (32-bit) server
Issue - Multicasting failing
I can deploy WIM files without any issues using unicast, however OSD fails when I specify to use Multicast. The system PXE boots, then starts the task sequence, it sits at the Installation Progress screen saying "Opening Multicast Sesssion
for \\SCCMSrv\SMSPKG.....". Then it fails at the point when I would expect the WIM file to be downloaded. The error code is 0x80004005.
The multicast test is not across subnets, and I'm told that our switches have been configured to allow Multicasting.
I have looked at the SMSTSLOG, there are references all over the place to the error 0x80004005. There are some below -
<![LOG[Received error: 0x80004005 while initiating multicast download]LOG]!><time="09:12:27.591+000" date="02-14-2012" component="ApplyOperatingSystem" context="" type="3" thread="1884" file="resolvesource.cpp:2765">
<![LOG[Installation of image 1 in package EH100020 failed to complete..
Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="09:12:27.591+000" date="02-14-2012" component="ApplyOperatingSystem" context="" type="3" thread="1884" file="installimage.cpp:1476">
I'm aware of other folk having similar issues
http://support.microsoft.com/default.aspx?scid=kb;EN-US;971413 - but this doesn't apply to me beause I'm on R2
Can anyone shed some light or help? I don't have a lot of experience with Multicasting within SCCM so let me know if you need further information or log files.
Cheers
February 14th, 2012 6:01am
Did you remember to check off "Allow this package to be transferred via multicast (WinPE only)" on all packages needed in the winpe phase?Michael Petersen | My blogs:
blog.coretech.dk/author/mip/ and SCUG.dk/ | Twitter:
@OSDeploy | Linkedin:
Michael Petersen
Free Windows Admin Tool Kit Click here and download it now
February 14th, 2012 6:21am
Hi Michael,
WinPE stage, what exactly is that?
I have ensured that the tickbox is ticked (are you saying it should not be ticked?) in the following locations -
- WIN PE boot image>Distribution Settings
- OS Images WIM file>Distribution Settings (set to "Transfer this package only via multicast")
- unattend.xml answer file package > Distribution Settings
Essentially, I've followed this guide -
http://blogs.msdn.com/b/steverac/archive/2008/10/19/setting-up-multicasting-in-sccm.aspx
Thanks
Puskas
February 14th, 2012 7:07am
Looks right.. Have you made sure your network/switches are set up to support multicast?Michael Petersen | My blogs:
blog.coretech.dk/author/mip/ and SCUG.dk/ | Twitter:
@OSDeploy | Linkedin:
Michael Petersen
Free Windows Admin Tool Kit Click here and download it now
February 14th, 2012 7:18am
Looks right.. Have you made sure your network/switches are set up to support multicast?
Michael Petersen | My blogs:
blog.coretech.dk/author/mip/and SCUG.dk/| Twitter:
@OSDeploy| Linkedin:
Michael Petersen
I can ask our network guys to have a look at them again, but they have told me it is setup and good to go. Is there anyway of easily testing the switches/network?
Do you have any idea what the error message signifies?
Thanks.
Puskas
February 14th, 2012 7:27am
8004005 could be may things, but generally relates to files not being accessible for some reason! Could you upload the entire smsts.log to somewhere so we can have a look at it!Michael Petersen | My blogs:
blog.coretech.dk/author/mip/ and SCUG.dk/ | Twitter:
@OSDeploy | Linkedin:
Michael Petersen
Free Windows Admin Tool Kit Click here and download it now
February 14th, 2012 7:54am
8004005 could be may things, but generally relates to files not being accessible for some reason! Could you upload the entire smsts.log to somewhere so we can have a look at it!
Michael Petersen | My blogs:
blog.coretech.dk/author/mip/and SCUG.dk/| Twitter:
@OSDeploy| Linkedin:
Michael Petersen
Michael,
Thanks for spending a little time on this. You can access the download of the SMSTS.log file here >
LINK REMOVED
Let me know if there is anything else you need.
Puskas
February 14th, 2012 9:06am
I'm finding this interesting "Failed to get MCS key (Code 0x80004005)"
Here is what another guy did to make it work!
unchecke "Allow this package to transfered via multicast" at package/image properties
clear SerializedMCSKey and SignedSerializedMCSKey in registry (HKLM\Software\microsoft\SMS\MCS)
uncheck enable multicast at dp properties
check enable multicast at dp properties
check "Allow this package to transfered via multicast" at package/image properties
check "transfer this package only via multicast"Michael Petersen | My blogs:
blog.coretech.dk/author/mip/ and SCUG.dk/ | Twitter:
@OSDeploy | Linkedin:
Michael Petersen
Free Windows Admin Tool Kit Click here and download it now
February 14th, 2012 9:33am
I'm finding this interesting "Failed to get MCS key (Code 0x80004005)"
Here is what another guy did to make it work!
unchecke "Allow this package to transfered via multicast" at package/image properties
clear SerializedMCSKey and SignedSerializedMCSKey in registry (HKLM\Software\microsoft\SMS\MCS)
uncheck enable multicast at dp properties
check enable multicast at dp properties
check "Allow this package to transfered via multicast" at package/image properties
check "transfer this package only via multicast"
Michael Petersen | My blogs:
blog.coretech.dk/author/mip/and SCUG.dk/| Twitter:
@OSDeploy| Linkedin:
Michael Petersen
Hi Michael,
Wow, it did the trick!
It's very strange behaviour, I mean, who on earth would ever know that you have to follow the strange sequence that you posted?!? The weird thing is that the two reg keys are populated with the exact same data as it was below.
Anyway, it's working now, but not across VLANs - I'll assume that this is a switch configuration issue.
Cheers
Puskas
February 15th, 2012 5:34am