Problems with multicast deployment
All,
I'm having some issues with multicast deployment. I just follwed Steve Rachui's excellent guide here: http://blogs.msdn.com/steverac/archive/2008/10/19/setting-up-multicasting-in-sccm.aspx, but now that everything is enabled and installed, I have the following errors in my MceExec.log:
========== HealthCheck ffffffff-ffff-ffff-ffff-ffffffffffff McsExec 5/7/2009 4:13:16 PM 6912 (0x1B00)
Executing MCS_GetPkgInfoForShare(VDOVCCM201, \\MCSTEST\SERVER, *) McsExec 5/7/2009 4:13:16 PM 6912 (0x1B00)
No Rows Returned McsExec 5/7/2009 4:13:16 PM 6912 (0x1B00)
SignedSerializedMCSKey is empty McsExec 5/7/2009 4:13:16 PM 6912 (0x1B00)
Error checking MCS certificate in registry: 0x80004005 McsExec 5/7/2009 4:13:16 PM 6912 (0x1B00)
Found 0 namespaces McsExec 5/7/2009 4:17:42 PM 3492 (0x0DA4)Additionally, my SMSTS.log on clients where I attempt to deploy via multicast shows this:
Performing multicast download from mcs://VDOVCCM201.company.com/SMS_MCS/.sms_mcs?filePath=\\VDOVCCM201.company.com\SMSPKGD$\DOV0002C\&PackageFlags=201326592&packageID=DOV0002C&version=2. encryption required:false ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Initializing Multicast Download ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Using MulticastURL: mcs://VDOVCCM201.company.com/SMS_MCS/.sms_mcs?filePath=\\VDOVCCM201.company.com\SMSPKGD$\DOV0002C\&PackageFlags=201326592&packageID=DOV0002C&version=2 ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Using Multicast Host:VDOVCCM201.company.com FilePath:\\VDOVCCM201.company.com\SMSPKGD$\DOV0002C\ PackageID=DOV0002C Version=2 ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Using MCSServer: VDOVCCM201.company.com ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Using RemotePath: \\VDOVCCM201.company.com\SMSPKGD$\DOV0002C\ ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Using PackageID: DOV0002C ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Using Version: 2 ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Using Encryption: false ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Using SSL ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Got Authenticator Info ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Initializing HTTP transport. ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Setting URL = VDOVCCM201.company.com. ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Setting Default Port = 443. ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Setting SSL = true. ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Setting CRL = false. ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Setting Media Certificate. ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Setting Authenticator. ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Preparing Multicast Session Request. ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Setting transport. ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Initializing CLibSMSMessageHeader with authenticator ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Setting site code = DOV. ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Setting client ID = 2f0196f9-bb07-49b1-a15b-4812457f67d8. ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Executing MCSKeyInfo Request. ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Sending RequestKeyInfo ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Messaging Auth Using V4 Mode ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
Formatted header: ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>2f0196f9-bb07-49b1-a15b-4812457f67d8</SourceID><SourceHost/><TargetAddress/><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2009-05-07T23:02:35Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="6"/><Hooks><Hook2 Name="clientauth"><Property Name="Token"><![CDATA[CCMClientID: 2f0196f9-bb07-49b1-a15b-4812457f67d8
CCMClientIDSignature: 8E5AF8384C7A6600EF913383AA3BFB10A76280E6325859541EF77838B8FE4C630C0D6E31FF930D2E28EF617995988B04D1F0781860BCDBFEC1BF1AB6B4EE26D10B05B8836ACDCDAE134143AC5B87088DE3D60F9850D32B5112D32CC9499915C4E6C50441A7841CAE9925EEBC0B268536C50D53DE0910F3F1CE2AAAB292225803A2FB1488879BC806406CB932F8A79F8FE037AA92843E52A6496722375E72FD7D9EFD73ED97CD8B8679575A415EEA92B152A73492AC2ED05B7174189A2E67BF367CA71E85D6F43B462BDC67E1F2700903A88F9C5C3B5F6A9699244447D9C691780CD60EDBBA28A67F56557FD006492BCA201056075742C70F0E9A46591B53DFA2
CCMClientTimestamp: 2009-05-08T00:01:14Z
CCMClientTimestampSignature: 7462EC7CC7DDC06933C799D9CE2253023903BFCA8F9DFC2AF1C188812A54B3EE4603930744FC6FA97B1D45DD58FF0AF4F8926A6CB31B86E28157FAB44BA9565F7427CB62C500A3736C885026CA36DC5D14A1915C43A79C5BDEFA72B0E71A2D4C044FDBB6923703B14BEFB274F77954BC50D82246DF0ACCBEFCC7FADB8D69F230C01ADE142F1F369EA21428F31CA0038334D22563B0A8AE1373B6A4D05C6357B8A5D675976E8B7B45D994AA004A7C575C5A9A3CB2D1D103CA4CEC03F37EAF943B4353ACE50C2524EC65250F56E74942764F68B5DBBE373050E497152D5034780B8B30BD461BB78B66FDD4B221A1A7E63EF119EB363C35461D5D22F4AC26C9AB1B
]]></Property></Hook2></Hooks><Payload Type="inline"/><TargetHost/><TargetEndpoint/><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
ApplyOperatingSystem 5/7/2009 4:02:35 PM 1984 (0x07C0)
CLibSMSMessageWinHttpTransport::Send: URL: VDOVCCM201.company.com:443 CCM_POST /SMS_MCS_AltAuth/.sms_mcs?op=keyinfo ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
In SSL, but with no client cert ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
The request has succeeded. 200 OK ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
pNext != NULL, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2072) ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
reply has no message header marker ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,8985) ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
oMcsRequest.GetMCSKey(mcsKeyInfoResponse), HRESULT=80004005 (e:\nts_sms_fre\sms\server\mcs\consumer\mcsisapiclient.cpp,417) ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
Failed to get MCS key (Code 0x80004005) ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
ClientRequestToMCS::DoRequest failed. error = (0x80004005). ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
Request to MCS 'VDOVCCM201.company.com' failed with error (Code 0x80004005). ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
Multicast OpenSessionRequest failed (0x80004005). ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
Sending status message: SMS_OSDeployment_PackageDownloadMulticastStatusFail ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
Setting authenticator. ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
Initializing CLibSMSMessageHeader with authenticator ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
Sending StatusMessage ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
Messaging Auth Using V4 Mode ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
Formatted header: ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>2f0196f9-bb07-49b1-a15b-4812457f67d8</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2009-05-07T23:02:36Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="1350"/><Hooks><Hook2 Name="clientauth"><Property Name="Token"><![CDATA[CCMClientID: 2f0196f9-bb07-49b1-a15b-4812457f67d8
CCMClientIDSignature: 8E5AF8384C7A6600EF913383AA3BFB10A76280E6325859541EF77838B8FE4C630C0D6E31FF930D2E28EF617995988B04D1F0781860BCDBFEC1BF1AB6B4EE26D10B05B8836ACDCDAE134143AC5B87088DE3D60F9850D32B5112D32CC9499915C4E6C50441A7841CAE9925EEBC0B268536C50D53DE0910F3F1CE2AAAB292225803A2FB1488879BC806406CB932F8A79F8FE037AA92843E52A6496722375E72FD7D9EFD73ED97CD8B8679575A415EEA92B152A73492AC2ED05B7174189A2E67BF367CA71E85D6F43B462BDC67E1F2700903A88F9C5C3B5F6A9699244447D9C691780CD60EDBBA28A67F56557FD006492BCA201056075742C70F0E9A46591B53DFA2
CCMClientTimestamp: 2009-05-08T00:01:14Z
CCMClientTimestampSignature: 7462EC7CC7DDC06933C799D9CE2253023903BFCA8F9DFC2AF1C188812A54B3EE4603930744FC6FA97B1D45DD58FF0AF4F8926A6CB31B86E28157FAB44BA9565F7427CB62C500A3736C885026CA36DC5D14A1915C43A79C5BDEFA72B0E71A2D4C044FDBB6923703B14BEFB274F77954BC50D82246DF0ACCBEFCC7FADB8D69F230C01ADE142F1F369EA21428F31CA0038334D22563B0A8AE1373B6A4D05C6357B8A5D675976E8B7B45D994AA004A7C575C5A9A3CB2D1D103CA4CEC03F37EAF943B4353ACE50C2524EC65250F56E74942764F68B5DBBE373050E497152D5034780B8B30BD461BB78B66FDD4B221A1A7E63EF119EB363C35461D5D22F4AC26C9AB1B
]]></Property></Hook2></Hooks><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
CLibSMSMessageWinHttpTransport::Send: URL: VDOVCCM201.company.com:443 CCM_POST /ccm_system_AltAuth/request ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
In SSL, but with no client cert ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
The request has succeeded. 200 OK ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
McsTransferDirectory(sHost.c_str(), sFilename.c_str(), sPackageID.c_str(), sVersion.c_str(), pwszLocalDirectory, pbEncrypt, fpProgressCallback, pvProgressCallbackData, hCancelEvent), HRESULT=80004005 (e:\nts_sms_fre\sms\server\mcs\consumer\mcsisapiclient.cpp,1104) ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
g_pfnMcsTransferDirectoryByURL(pwszMcsServer, pwszLocalDirectory, pbEncrypt, fpProgressCallback, pvProgressCallbackData, hCancelEvent), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\multicast.cpp,261) ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
McsTransferDirectoryByURL(sSourceURL, sDestinationPath, pbEncrypt, Multicast_Progress, 0, 0), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2592) ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
Received error: 0x80004005 while initiating multicast download ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)
waiting some time before retrying multicast servers ApplyOperatingSystem 5/7/2009 4:02:36 PM 1984 (0x07C0)I am totally unable to find anything on google pertaining to any of these errors - I'm just wondering if I need to do anything more than what's covered in the guide I've followed (obviously the answer is yes). My environment is simple - Just one server for SCCM, Native Mode, running on Server 2008 x64, with both WDS Deployment and Transport components installed. It seems like something didn't get written to the registry, or some certificate isn't in place - do I need to issue a multicast certificate from my CA?
I should stress that this environment has been totally problem free, 100% functional, until I enabled multicast. Even then, deployments fail back to HTTP ad my task sequences run perfectly. So this isn't causing me any downtime, I'm just getting ready to do a lot of imaging, so multicast would be nice.
Thanks,
Andrew- Edited byandroidtopp Sunday, May 10, 2009 3:40 PM
- Edited byandroidtopp Thursday, May 07, 2009 11:48 PM
All Replies
- I'm epxiriencing the exact same error,
Did you found a solution for it ? My configuration is Mixed mode, so i don't think it's related to native mode
Or. - Hi,I had the same problem the other day.What I did:unchecked Allow this package to transfered via multicast at package/image propertiescleared SerializedMCSKey and SignedSerializedMCSKey in registry (HKLM\Software\SMS\MCS)unchecked enable multicast at dp propertieschecked enable multicast at dp propertieschecked Allow this package to transfered via multicast at package/image propertieschecked transfer this package only via multicastthat got it working again for me.
Kind Regards, Henk Hofs
