SCCM 2012 SP1 agent install via WSUS

Hi guys,
I'm having got an issue when I try installing the agent via WSUS. When I try installing manually everything seems to work.
Here are the infos from the ccmsetup.log:
==========[ ccmsetup started in process 2252 ]========== ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Running on platform X86 ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Updated security on object C:\WINDOWS\ccmsetup\cache\. ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Launch from folder C:\WINDOWS\SoftwareDistribution\Download\Install\ ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
CcmSetup version: 5.0.7804.1000 ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Running on OS (6.1.7601). Service Pack (1.0). SuiteMask = 256. Product Type = 1 ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Ccmsetup command line: "C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe" ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSJoinedToADDomain ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Local Machine is joined to an AD domain ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSGetAssignedSiteFromAD ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
DhcpGetOriginalSubnetMask entry point is supported. ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Begin checking Alternate Network Configuration ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
spNamespace.Open(sNamespacePath), HRESULT=8004100e (e:\nts_sccm_release\sms\framework\ccmutillib\ccmiputil.cpp,1109) ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Finished checking Alternate Network Configuration ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSGetADSiteName ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Current AD site of machine is DE-Zeilarn ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Attempting to query AD for assigned site code ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=2887256160)(MSSMSRangedIPHigh>=2887256160))))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=172.24.8.0)(mSSMSRoamingBoundaries=DE-Zeilarn)(mSSMSSiteCode=XYZ)))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSIsSiteCompatible : Verifying Site Compatibility for <XYZ> ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetSiteVersionFromAD ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetSiteVersionFromAD : Attempting to query AD for MPs for site 'XYZ' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSSiteCode=XYZ))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetSiteVersionFromAD : Successfully retrieved version '5.00.7804.1000' for site 'XYZ' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSIsSiteCompatible : Site Version = '5.00.7804.1000' Site Capabilities = <Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="31"/></Capabilities> ccmsetup 08.02.2013
13:45:47 196 (0x00C4)
LSIsSiteVersionCompatible : Site Version '5.00.7804.1000' is compatible. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSIsSiteCompatible : Site <XYZ> Version '5.00.7804.1000' is compatible. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetAssignedSiteFromAD : Trying to Assign to the Site <XYZ> ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Got site code 'XYZ' from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Retrieving client operational settings from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=XYZ))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
OperationalXml '<ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=root-ca</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA003020102021011B05A5A5C9B0BBA4299C744025DA257300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303131363138303730375A180F32313132313232343138303730375A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009855D66E3C7F2CBA9E701E06597B77942120C27D6A4B7FACE3DB214363C20E6AD12BFFB7225A5D9B84A316B6EC20979007CB6FEE71A82D879091A0EEC7E07C7952EDA27ED31C76E63CF8ABA411B8BA79AB8B48B4FA4204085E8836B7F4619A0E29160528C91D205A8C4F1CBDF5C78CC27ED7C5BAA9369E74F7B610C77BAA777E5B31DF65DC562129D26A5C730161D7D1E2946B3953F8923BFE80A812AE2304A8B3701400CE11BF4F1521A693B9624BF25A19AD1A8E56DE9B99793D60CFA4D9B83E4777B169FF33CEF04298AAEECE733AB9A9CCD7380C8073079D95D650434D2FF7AD33AB21A0DAE4EDB64343E94141108F594925BE214933AC9E3BC043FD332F0203010001A33C303A30220603551D11041B301982175649455343434D322E65696E737465696E2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010089A4B76FFBF73A0F9872BF2B6C14B7EAFAEDBCDEB2793675048BEA300BADC1E168FE75E6A8207B0BADD5C9FC533F62687DD393DDE8C0E68E1973DE32B9DC85DAF41D2AB62F34AC8C88CF8C02FCCE04695D732317430561D3D0F8C95719AA605D0E68488CAB9B3A98461D19EF9E62FF2F37A8E45CCAFE65E48A46CE48987A41858CE2B7324D5F529E0E3A76DE8374787851C9F7044FBEF89C583CC42717F3BDFDF4E73A64FBE4A2991B32C7C2C30117EFE584111112C39368A4712BBD147934D38B4C4FB9E12A6254969A6DDFFE40DA7D687F42D8528A6F8117028C3F25401D1892574303F6C02E208E4F938429B0AC4DC9F9EDC98B6D40D2EBD9266223D02EBF</SiteSigningCert></SecurityConfiguration><RootSiteCode>XYZ</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=XYZ</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState"
Value="31" /></Capabilities><Domain Value="mydomain.tld" /><Forest Value="mydomain.tld" /></ClientOperationalSettings>' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
HTTP is selected for Client. The current state is 0. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
The MP name retrieved is 'mysccmserver.mydomain.tld' with version '7804' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="31"/></Capabilities>' ccmsetup 08.02.2013
13:45:47 196 (0x00C4)
MP 'mysccmserver.mydomain.tld' is not compatible ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Retrieved 0 MP records from AD for site 'XYZ' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Received client operational settings: <ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=root-ca</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA003020102021011B05A5A5C9B0BBA4299C744025DA257300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303131363138303730375A180F32313132313232343138303730375A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009855D66E3C7F2CBA9E701E06597B77942120C27D6A4B7FACE3DB214363C20E6AD12BFFB7225A5D9B84A316B6EC20979007CB6FEE71A82D879091A0EEC7E07C7952EDA27ED31C76E63CF8ABA411B8BA79AB8B48B4FA4204085E8836B7F4619A0E29160528C91D205A8C4F1CBDF5C78CC27ED7C5BAA9369E74F7B610C77BAA777E5B31DF65DC562129D26A5C730161D7D1E2946B3953F8923BFE80A812AE2304A8B3701400CE11BF4F1521A693B9624BF25A19AD1A8E56DE9B99793D60CFA4D9B83E4777B169FF33CEF04298AAEECE733AB9A9CCD7380C8073079D95D650434D2FF7AD33AB21A0DAE4EDB64343E94141108F594925BE214933AC9E3BC043FD332F0203010001A33C303A30220603551D11041B301982175649455343434D322E65696E737465696E2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010089A4B76FFBF73A0F9872BF2B6C14B7EAFAEDBCDEB2793675048BEA300BADC1E168FE75E6A8207B0BADD5C9FC533F62687DD393DDE8C0E68E1973DE32B9DC85DAF41D2AB62F34AC8C88CF8C02FCCE04695D732317430561D3D0F8C95719AA605D0E68488CAB9B3A98461D19EF9E62FF2F37A8E45CCAFE65E48A46CE48987A41858CE2B7324D5F529E0E3A76DE8374787851C9F7044FBEF89C583CC42717F3BDFDF4E73A64FBE4A2991B32C7C2C30117EFE584111112C39368A4712BBD147934D38B4C4FB9E12A6254969A6DDFFE40DA7D687F42D8528A6F8117028C3F25401D1892574303F6C02E208E4F938429B0AC4DC9F9EDC98B6D40D2EBD9266223D02EBF</SiteSigningCert></SecurityConfiguration><RootSiteCode>XYZ</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=XYZ</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState"
Value="31" /></Capabilities><Domain Value="mydomain.tld" /><Forest Value="mydomain.tld" /></ClientOperationalSettings>. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Http port 80; https port 443; select first cert 1; sslstate 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Certificate Issuers = ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
FromAD: command line = SMSSITECODE=XYZ ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetManagementPointsForSiteFromAD ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
SslState value: 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Ccmsetup was run without any user parameters specified. Running without registering ccmsetup as a service. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Detected sitecode 'XYZ' from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPPORT:    80 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPSPORT:    443 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPSSTATE:    480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPSCERTNAME:    ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
FSP:    ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMCERTISSUERS:    CN=root-ca ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMFIRSTCERT:    1 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Creating CCMCertStore ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMCERTID:    SMS;FB0F35392A7FF68D2FA9C97D0CD54A3E0057964E ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
No MP or source location has been explicitly specified. Trying to discover a valid content location... ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Looking for MPs from AD... ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Retrieving client operational settings from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Received client operational settings: <ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=root-ca</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA003020102021011B05A5A5C9B0BBA4299C744025DA257300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303131363138303730375A180F32313132313232343138303730375A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009855D66E3C7F2CBA9E701E06597B77942120C27D6A4B7FACE3DB214363C20E6AD12BFFB7225A5D9B84A316B6EC20979007CB6FEE71A82D879091A0EEC7E07C7952EDA27ED31C76E63CF8ABA411B8BA79AB8B48B4FA4204085E8836B7F4619A0E29160528C91D205A8C4F1CBDF5C78CC27ED7C5BAA9369E74F7B610C77BAA777E5B31DF65DC562129D26A5C730161D7D1E2946B3953F8923BFE80A812AE2304A8B3701400CE11BF4F1521A693B9624BF25A19AD1A8E56DE9B99793D60CFA4D9B83E4777B169FF33CEF04298AAEECE733AB9A9CCD7380C8073079D95D650434D2FF7AD33AB21A0DAE4EDB64343E94141108F594925BE214933AC9E3BC043FD332F0203010001A33C303A30220603551D11041B301982175649455343434D322E65696E737465696E2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010089A4B76FFBF73A0F9872BF2B6C14B7EAFAEDBCDEB2793675048BEA300BADC1E168FE75E6A8207B0BADD5C9FC533F62687DD393DDE8C0E68E1973DE32B9DC85DAF41D2AB62F34AC8C88CF8C02FCCE04695D732317430561D3D0F8C95719AA605D0E68488CAB9B3A98461D19EF9E62FF2F37A8E45CCAFE65E48A46CE48987A41858CE2B7324D5F529E0E3A76DE8374787851C9F7044FBEF89C583CC42717F3BDFDF4E73A64FBE4A2991B32C7C2C30117EFE584111112C39368A4712BBD147934D38B4C4FB9E12A6254969A6DDFFE40DA7D687F42D8528A6F8117028C3F25401D1892574303F6C02E208E4F938429B0AC4DC9F9EDC98B6D40D2EBD9266223D02EBF</SiteSigningCert></SecurityConfiguration><RootSiteCode>XYZ</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=XYZ</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState"
Value="31" /></Capabilities><Domain Value="mydomain.tld" /><Forest Value="mydomain.tld" /></ClientOperationalSettings>. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Http port 80; https port 443; select first cert 1; sslstate 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Certificate Issuers = CN=root-ca ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
FromAD: command line = SMSSITECODE=XYZ ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetManagementPointsForSiteFromAD ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current directory 'C:\WINDOWS\SoftwareDistribution\Download\Install' is not a valid source location. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
No valid source or MP locations could be identified to download content from. Ccmsetup.exe cannot continue. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
DetermineInstallSource(), HRESULT=80004005 (e:\nts_sccm_release\sms\setup\ccmsetup\ccmsetup.cpp,4426) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Failed to parse '"C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe" ' with error 0x80004005 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::~CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
A Fallback Status Point has not been specified. Message with STATEID='307' will not be sent. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::~CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
ParseCommandLine(), HRESULT=80004005
My boundaries and boundary groups are configured, I can see the objects in the Systems Management Container in AD, but still the agent install via WSUS will not work. Any suggestions?
Cheers
Sebastian Bammer

see my latest post. It looks like a bug in the setup. It selects a certificate but still it presents information that iis on the mp does not accept. Check your iis logs. Manual install works for ssl only sites. I haven't got any other methods yet. I will
keep you updated.

Similar Messages

SCCM 2012 SP1 - Multiple SUP - common WSUS DB

Hello,
Is it supported / recommend to share a common WSUS DB for multiple WSUS / SUP roles ?
If yes, how to perform a clean deployment of additional SUP dealing with additional KB requirements.Following article explains the problem but the solution looks very complex: http://scug.be/sccm/2012/10/03/configmgr-2012-sp1-installing-multiple-software-update-points-per-single-primary-site-and-use-a-single-shared-wsus-database-on-your-sql-cluster/
I tried to test this procedure in my test environment but it broken WSUS and now refuse to sync with Microsoft (can't establish SSL connection).
I have not been able to find any official Microsoft setup guide for this ?
As an alternative, is it possible to sync additional SUP as downstream servers with the first one. I ask for this because I use SCUP, and I don't want to maintain multiple WSUS environment.
Regards.

Hi.
We have the same problem with our WSUS 3.0 SP2 installation, when I install WSUS on an SCCM 2012 server in the "Secondary Site".
That server is in a different domain (one way Trust); but I have Logged On to that server with an specific account from the Top Domain that has Owner rights on the excisting DB). The Installation connect's succcesfully to the DB, and on the
Next Window I get the error "The existing DB is not compatible with this version of Windows Server Update Services 3.0 SP2"
The first two Wsus Installations in the "Top" domain worked just fine.
Anyone an idea?

SCOM 2012 SP1 Agent install issue

Dear all,
Wheni try to push SCOM client , getting below error. Any idea what would be issue ?
The Operations Manager Server could not execute WMI Query "Select * from Win32_OperatingSystem" on computer XXX.XXX.XXX
Operation: Agent Install
Install account: XXXXXX
Error Code: 800706BA
Error Description: The RPC server is unavailable.

Looks Firewall issue only , i have opened below ports , is there any mandatory ports required for SCOM agent installation ?
443
TCP
445
TCP
135
TCP

WSUS 4.0 and SCCM 2012 SP1 Sync Errors

SCCM 2012 SP1 is installed on a Windows 2012 Std server with the WSUS 4.0 Role installed.
All other links I have found list a 2008 R2 Server with WSUS 3.0 SP2 hence all the "fixes" revolve around hot fixes and patches/settings for WSUS 3.0 or 2008 R2 systems.
WSUS is set for port 8530/8531
SCCM SUP is set for ports 8530/8531
Both are on same machine (single site SCCM 2012 SP1 System)
What does Bad Configuration, SUPs present but no default SUP
mean and how do I fix it?
Recent entry in my WCM.LOG states:
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.401+420><thread=6052 (0x17A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.454+420><thread=6052 (0x17A4)>
Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.481+420><thread=6052 (0x17A4)>
Changes in active SUP list detected. New active SUP List is:~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.489+420><thread=6052 (0x17A4)>
SUP0: SCCM2012.xxdomainnamexx.ORG, group = , nlb = ~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.496+420><thread=6052 (0x17A4)>
Updating active SUP groups...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.503+420><thread=6052 (0x17A4)>
Bad Configuration, SUPs present but no default SUP $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.510+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.525+420><thread=6052 (0x17A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.535+420><thread=6052 (0x17A4)>
Waiting for changes for 11 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.543+420><thread=6052 (0x17A4)>
Wait timed out after 11 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:04:54.569+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.577+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.585+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.592+420><thread=6052 (0x17A4)>
Wait timed out after 60 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:04:54.714+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.721+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.728+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.734+420><thread=6052 (0x17A4)>
Randall

Here is my WCM Log from this mornings "re-attempt"
Trigger event array index 0 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:22.156+420><thread=5540 (0x15A4)>
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.179+420><thread=5540 (0x15A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.181+420><thread=5540 (0x15A4)>
Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.194+420><thread=5540 (0x15A4)>
No SUPs are present $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.199+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.220+420><thread=5540 (0x15A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.224+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.226+420><thread=5540 (0x15A4)>
Trigger event array index 0 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:37.356+420><thread=5540 (0x15A4)>
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.388+420><thread=5540 (0x15A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.493+420><thread=5540 (0x15A4)>
Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.541+420><thread=5540 (0x15A4)>
Changes in active SUP list detected. New active SUP List is:~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.543+420><thread=5540 (0x15A4)>
SUP0: SCCM2012.MORTONGENERAL.ORG, group = , nlb = ~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.546+420><thread=5540 (0x15A4)>
Updating active SUP groups...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.550+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.553+420><thread=5540 (0x15A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.559+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.562+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.593+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.596+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.611+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.614+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.617+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.620+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:52.634+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:52.637+420><thread=5540 (0x15A4)>
Trigger event array index 0 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:52.640+420><thread=5540 (0x15A4)>
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.761+420><thread=5540 (0x15A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.798+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.813+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.823+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.826+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.840+420><thread=5540 (0x15A4)>
Waiting for changes for 23 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.843+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.846+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.849+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:07.863+420><thread=5540 (0x15A4)>
Waiting for changes for 23 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:07.866+420><thread=5540 (0x15A4)>
Wait timed out after 23 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:30.913+420><thread=5540 (0x15A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:40.917+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:40.920+420><thread=5540 (0x15A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:40.923+420><thread=5540 (0x15A4)>
Wait timed out after 60 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:31.041+420><thread=5540 (0x15A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:41.045+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:41.048+420><thread=5540 (0x15A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:41.051+420><thread=5540 (0x15A4)>
Randall

Lync 2013 x64 silent client deployment via SCCM 2012 SP1

Greetings everyone!
I ran into a problem with Lync 2013 x64 silent deployment.
I need to provide every workstation with Lync 2013 client, so i decided to use deployment via SCCM 2012 sp1.
I created 2 msp files with OCT, one based on x86 Office 2013 Proplus, and other based on x64 Office 2013 Proplus.
Added them as applications to sccm software library.
Deployment of Lync 2013 x86 application was a success with over than 80% compliance.
But all Lync 2013 x64 automatic installations finish with different errors.
I created special device collection for workstations with office 2010 x64 and 2013 x64, because i can't install other architecture products once it has x64 product installed.
My membership query-rules for this collection:
Office 2013 x64
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
= SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90150000-0011-0000-1000-0000000FF1CE}"
Office 2010 x64
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
= SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90140000-0011-0000-1000-0000000FF1CE}"
My application deployment type points to setup.exe in office 2013 x64 installation folder, where i created msp file in updates folder via OCT and edited config.xml file in proplus.ww folder.
So my installation program looks like this setup.exe /adminfile updates\1lync.msp /config proplus.ww\config.xml
The same configuration works with Lync 2013 x86 deployment, except other setup folders.
When i try running installation program setup.exe with /adminfile and /config parameters locally, it installs successfully without errors or warnings.
I'm trying to find out problem source, does anyone have ideas what I am doing wrong?
Also i'm trying to reduce office 2013 installation folder size, what subfolders are necessary for Office 2013 proplus installation (still installing only lync with common files and tools)? Because now 3.5 GB package is quite hard to distribute to sccm secondary
sites with deployment point.
Thanks in advance.

Hi,
Here are some tips and tricks for your reference.
Tips and Tricks: Deploying Lync 2013 client using SCCM 2012 | Lync 2013 Client Customization for SCCM 2012 Deployment Package
http://zahirshahblog.com/2014/01/08/tips-and-tricks-deploying-lync-2013-client-using-sccm-2012-lync-2013-client-customization-for-sccm-2012-deployment-package/
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.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

WSUS SP2; SCCM 2012 SP1; Sync failed: WSUS update source not found

Hi,
I have installed the Fresh SCCM 2012 SP1 and WSUS 3.0 SP2 + KB2720211 + KB2734608. However, still the Sync is getting failed. This is what I am getting in the wsyncmgr and WCM logs:
wsyncmgr:
Sync failed: WSUS update source not found on site PR1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=3668 GMTDATE=Fri Jan 09 18:00:00.537 2015 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found
on site PR1. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
1/9/2015 12:00:00 PM 3668 (0x0E54)
WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.489 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Remote configuration failed on WSUS Server.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.515 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
I have used the default port numbers 80 and 443 still the sync is failing. Please provide your advise to fix this issue.
Regards,
Malwinder

WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
It's not only a matter of installing the console, but also those hotfixes on a remote server ...
Torsten Meringer | http://www.mssccmfaq.de

SCCM 2012 SP1 + WSUS + Server 2012 + SQL Server 2012

Hi all;
I installed SCCM 2012 with Sp1 for my site server and everything is going well.. And than i installed the WSUS role on my Windows Server 2012 and SCCM 2012 SP1 it gave an error message which is "Fatal Error: The schema version of the database is from a newer
version of WSUS than currently installed. You must either patch your WSUS server to at least that version or drop the database." My database server is SQL Server 2012... Do you know any pathc for WSUS or SQL Server 2012 doesnt support WSUS yet???
Thank You...
MCT

Normally if you are going to install SCCM 2012 SP1 +Windows 2012 with SQL 2012, Then you better use the SQL 2012 sp1.
also when you are installing the WSUS version 6.2 which come with server 2012 make sure you leave the default settings as it is. it shows in the below article.
also when you are giving the path to save the WSUS contents make sure the drive you going to create the wsus folder and the place where you going to download the updates is having free disk space and its formatted with the NTFS volume. Also the service account
you are using for this configuration should have the admin rights to the location of the wsus folder you going to create,
Thanks
Hasitha

Management Point fails after installing SCCM 2012 SP1

I'm carrying out an install of SCCM 2012 SP1 with the following hardware (fresh install not an upgrade from 2007)
1. Newly built Windows Server 2012 box
2. Site database located on a remote SQL 2012 cluster, both nodes Windows Server 2012, with CU5
The install went fine but when checking the Site Server Components the Management Point isn't installing. The following both show errors;
SMS_MP_CONTROL_MANAGER - MP.msi could not install. Checked the MP.msi log file which shows the following errors;
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\CcmExec_Global.mof' (Phase: 3, Object: 5, Lines: 76 - 83, Error: 80041002)
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\PolicyDefaults.mof' (Phase: 3, Object: 4, Lines: 49 - 57, Error: 80041002)
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\StateMsgSchema.mof' (Phase: 3, Object: 6, Lines: 89 - 94, Error: 80041002)
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\DataTransferService.mof' (Phase: 3, Object: 5, Lines: 318 - 323, Error: 80041002)
[19:53:19] Failed to compile 'C:\Program Files\SMS_CCM\CcmExec_MP.mof' (Phase: 3, Object: 1, Lines: 31 - 36, Error: 80041002)
MSI (s) (0C!94) [19:53:20:862]: Product: ConfigMgr Management Point -- Error 25140. Setup was unable to compile the file CcmExec_Global.mof
The error code is 80041002
Error 25140. Setup was unable to compile the file CcmExec_Global.mof
The error code is 80041002
CustomAction CcmRegisterWmiMofFile returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
SMS_NOTIFICATION_SERVER - bgbisapi.msi could not install. Extract from log below;
[19:53:38] IGNORE: Failed to delete extension 'C:\Program Files\SMS_CCM\bgbisapi.dll'. Return Code = 0x80020009 (The extension might not be registered)
[19:53:39] WARNING: Failed to remove PerfLib entries for performance application SmsBgb (2)
[19:53:39] WARNING: Failed to remove configuration for performance application SmsBgb (80070057)
MSI (s) (0C!80) [19:53:39:540]: Product: BGB http proxy -- Internal Error 25001. 80070057
Internal Error 25001. 80070057
CustomAction CcmRegisterPerfCounters returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
I've tried uninstalling MP and reinstalling, triple checked all the right pre-reqs in Roles and Features are enabled, even rebuilt the server from scratch and tried again but same result.
Would really appreciate some help if anyone's fixed this issue

I'm still struggling, I've uninstalled MP
<04/16/14 08:06:59> SMSMP Setup Started....
<04/16/14 08:06:59> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /deinstall /siteserver:EICSC001 SMSMP 0
<04/16/14 08:06:59> Deinstalling the SMSMP
<04/16/14 08:06:59> No versions of SMSMP are installed. Returning Success.
<04/16/14 08:06:59> ~RoleSetup().
Ran the command, Invoke-Command {gwmi -query "SELECT * FROM __Namespace WHERE Name='CCM'" -Namespace "root" | Remove-WmiObject}
Checked Namespace Instances to ensure '= ccm' is not longer there.
Rebooted Server and re-installed MP but it still fails
<04/16/14 08:37:26> ====================================================================
<04/16/14 08:37:26> SMSMP Setup Started....
<04/16/14 08:37:26> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:EICSC001 SMSMP 0
<04/16/14 08:37:26> Installing Pre Reqs for SMSMP
<04/16/14 08:37:26> ======== Installing Pre Reqs for Role SMSMP ========
<04/16/14 08:37:26> Found 2 Pre Reqs for Role SMSMP
<04/16/14 08:37:26> Pre Req MSXML60 found.
<04/16/14 08:37:26> No versions of MSXML60 are installed. Would install new MSXML60.
<04/16/14 08:37:26> Enabling MSI logging. msxml6_x64.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\msxml6_x64MSI.log
<04/16/14 08:37:26> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi
<04/16/14 08:37:26> msxml6_x64.msi exited with return code: 0
<04/16/14 08:37:26> msxml6_x64.msi Installation was successful.
<04/16/14 08:37:26> Pre Req SqlNativeClient found.
<04/16/14 08:37:26> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<04/16/14 08:37:26> Pre Req SqlNativeClient is already installed. Skipping it.
<04/16/14 08:37:26> ======== Completed Installation of Pre Reqs for Role SMSMP ========
<04/16/14 08:37:26> Installing the SMSMP
<04/16/14 08:37:26> Passed OS version check.
<04/16/14 08:37:26> IIS Service is installed.
<04/16/14 08:37:26> No versions of SMSMP are installed. Installing new SMSMP.
<04/16/14 08:37:26> Enabling MSI logging. mp.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
<04/16/14 08:37:26> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE
SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<04/16/14 08:37:26> mp.msi exited with return code: 1603
<04/16/14 08:37:26> Backing up D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<04/16/14 08:37:26> Fatal MSI Error - mp.msi could not be installed.
<04/16/14 08:37:26> ~RoleSetup().
On checking I don't seem to have anything in IIS, no default web site.
I've tried reinstalling IIS and reinstalling SCCM 2012 but what ever I do I still hit the same issue with the Management Point.
Any assistance would be greatly appreciated.
Thanks

Windows 8.1 system with new Office 2013 install not pulling down any Office 2013 updates from my SCCM 2012 SP1 server

Hi,
I've just setup a new Windows 8.1 system and added to my SCCM 2012 SP1 server and all is good and it pulled down all the correct Windows updates and pulls down automatically the FEP updates that are distributed from SCCM 2012 daily.
I just installed Office 2013 on this system and have activated it as necessary. The problem is that the system doesn't seem to be pulling down any of the Office 2013 updates that have distributed thru SCCM. I have other systems with
Office 2013 installed and they have pulled down Office 2013 updates in the past when I published them.
If I look at the Office 2013 updates in the SCCM console software section, I can see that for example it shows that Office 2013 SP1 (x86) is needed by one system and installed on 8 other systems and shows as downloaded and deployed.
I've restarted the new system multiple times and also tried to force a software update check from the Configuration Manager applet but nothing seems to happen.
What can I check to try and determine what the problem is?
Thanks in advance,
Nick

Yes, the 8.1 system is a member of collection where the update deployment is targeted.
Are there any specific logs I should check in the client? If I check the WindowsUpdate.log I can see messages about the machine pulling down the FEP updates but that's all it appears to be doing.
in CCM\logs, focus on the updatehandler and updatedeployment, to begin with
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

SCCM 2012 SP1 WSUS/Software Update Point Synchronization error on CAS.

Hi All,
Good day to all you.
I would like to seek all your help on this issue that i have encountering.
My SCCM 2012 SP1 CAS are having a synchronization error in WSUS/Software update point. The CAS have intergrated WSUS role in it. The last good synchronization was on July 16, 2014. No error log found on WCM.log and WSUSctrl.log
Error:
Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall).
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
Sync failed. Will retry in 60 minutes
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
below are wsyncmgr.log:
Setting sync alert to active state on site C01 SMS_WSUS_SYNC_MANAGER (0x1690)
Sync time: 0d00h01m14s SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Wakeup for a polling cycle SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Starting Sync SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Read SUPs from SCF for MYHQKUL990707S.sdb.com SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
Found 1 SUPs SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Found active SUP MYHQKUL990707S.sdb.com from SCF File.
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:20.750 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:20 PM
5776 (0x1690)
Synchronizing WSUS server MYHQKUL990707S.sdb.com SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:21.763 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:21 PM
5776 (0x1690)
Using account sdb\SCCM-Admin to connect to WSUS Server
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
Synchronizing WSUS server myhqkul990707s.sdb.com ...
SMS_WSUS_SYNC_MANAGER 440 (0x01B8)
sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER
440 (0x01B8)
Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall). Source:
Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
5776 (0x1690)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
5776 (0x1690)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
All response is much appreciated
Thank You

Hi,
I recommend you look at the IIS log. Maybe it can give us some clues.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCCM 2012 Client agent not installing

Hi,
We have some client machines which has Client as "No" in the SCCM console. The ccmsetup.log file of these machines shows repeated entries like:
Download Update: 56283664 out of 66797088 bytes transferred.
ccmsetup.log file of another machine shows entries as below:
Download Update: Copy job has been queued.
I repaired a client machine using "Install Client" and monitored the ccmsetup.log file but it does not show any entries for repair or re-installed as it is downloading updates for a long time.
Also found the below error messages in ccmetup log file:
File 'C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi' doesn't exist.
File 'C:\Windows\ccmsetup\WindowsFirewallConfigurationProvider.msi' doesn't exist.File
'C:\Windows\ccmsetup\SCEPInstall.exe' doesn't exist.
File 'C:\Windows\ccmsetup\client.msi' doesn't exist.
Please guide on how to troubleshoot this client issue.
Thanks & Regards,
Lorin
Regards, Lorin Davis

This issue can be related with BITS settings. It can occurs if the BITS throttling is enabled on the client machines.
https://abdujalil.wordpress.com/2014/03/22/configmgr-client-push-installation-issue-download-transfer-take-long-time/
http://www.windows-noob.com/forums/index.php?/topic/7473-configuration-manager-2012-sp1-client-install-taking-hours-to-install/
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

Cannot install SCCM 2012 SP1 CU4

Hi,
I just tried to apply CU4 over one of my SCCM 2012 SP1 CU3 deployments and I receive the following message during the initial verification phase:
Server update status: This update applies to product version 5.0.7804. The installed version on this computer is 5.0.7958.1000. This update is not applicable to this computer.
Console update status: No serviceable configuration manager role was found on the local system.
If I engage the verification phase on this installation for CU2 and CU3 there is no problem at all, so this must be a CU4 package specific error.
Anybody experiencing the same behavior ?

The latest CU that I see for SCCM 2012 SP1 is SP1 Cumulative Update 3, are you sure you are working with the proper file? .
CU4 was released this week:
http://blogs.technet.com/b/configurationmgr/archive/2014/01/29/now-available-cumulative-update-4-for-system-center-2012-configuration-manager-service-pack-1.aspx
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

SCCM 2012 SP1 fails to install OSD of Captured Image

I installed Windows Server 2012, Visual Studio Pro 2008, 2010, 2012 and SQL Server 2012 onto a machine. Configured the settings on Windows Server 2012 and SQL 2012 to how the Developers requested to be configured. Ran the Capture Media from SCCM 2012 SP1,
saved to the designated network share. Capture was successful.
I create a TS to deploy the image to the other Dev Servers but it reboots to say no valid operating system found. I checked Monitoring for the Deployment I see the Task sequence but has the following error: Device - Unknown, MessageID - 11170, Description
- The task sequence manager could not successfully complete execution of the task sequence.
I see in the Apply Operation System from a captured image shows 1-1, 2-2, or 3-3. Does it matter which one I select and if so what does the numbers mean?
Any help is greatly appreciated, thanks!!

Hi Blacksuit,
Those numbers of the captured image stand for the indexes that are part of your WIM. And yes, it does matter which one you select. In the ConfigMgr console, go to your Software Library > Operating Systems > Operating System Images and select
the image you imported into ConfigMgr. Then at the bottom, click the Details tab to display your indexes. The index that contains your OS will have an OS Version and a description. The other indexes will be data images and not contain any
information in the Details tab. You'll need to choose the index (number) that contains the OS for the Apply OS step. To apply the data image indexes, use the Apply Data Image task sequence step and specify the partitions to apply the images
too before the Apply OS step.
Good luck!
-Matt

[Forum FAQ] Management Point fails after installing SCCM 2012 SP1

Symptom:
The Management Point might fail to be installed after you install SCCM 2012 sp1 on Windows Server 2012, either fresh install or others.
You might see some errors in mpMSI.log like listed below.
“Setup was unable to compile the file CcmExec_Global.mof”
“The error code is 80041002”
Cause:
Reinstall Management Point cannot work. This is because CCM Namespace remains in WMI which prevents SCCM from installing MP. You need clear CCM Namespace from WMI.
Resolution:
1. Uninstall Management Point from the console, then wait for the uninstallation to finish in MPSetup.log.
2. Open Wbemtest -> Connect to root -> Click Enum Classes and choose Recursive -> Double click _NAMESPACE in Query Result dialog -> Click Instances -> Delete _NAMESPACE.Name=”ccm”
3. Install Management Point.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Symptom:
The Management Point might fail to be installed after you install SCCM 2012 sp1 on Windows Server 2012, either fresh install or others.
You might see some errors in mpMSI.log like listed below.
“Setup was unable to compile the file CcmExec_Global.mof”
“The error code is 80041002”
Cause:
Reinstall Management Point cannot work. This is because CCM Namespace remains in WMI which prevents SCCM from installing MP. You need clear CCM Namespace from WMI.
Resolution:
1. Uninstall Management Point from the console, then wait for the uninstallation to finish in MPSetup.log.
2. Open Wbemtest -> Connect to root -> Click Enum Classes and choose Recursive -> Double click _NAMESPACE in Query Result dialog -> Click Instances -> Delete _NAMESPACE.Name=”ccm”
3. Install Management Point.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Error installing SCCM 2012 SP1 client

Hi All,
I am getting the following error, detailed in the client.msi.log, when trying to install the SCCM 2012 SP1 client on a couple of windows 2008 R2 servers.
Error 1904. Module C:\Windows\CCM\StatusAgentProxy.dll failed to register. HRESULT -2147010895
The ccmsetup.log details the same message without Error 1904 indicated.
I am installing the client using the SUP method, which has worked without any problems on all 180 other windows servers I have done. ccmsetup starts and downloads all pre reqs required for the client rollout, but it then hits this error and does not
finish the installation.
Any help would be much appreciated?
Regards PowerShell90

Hi,
I've seen this issue a couple of times and usually it's related to incorrect Versions of C++ Library installed on the system you try to install the Client. Try and remove any existing installations, reboot and install this version;
http://www.microsoft.com/en-us/download/details.aspx?id=26368
Let me know how it goes.

SCCM 2012 SP1 agent install via WSUS

Similar Messages

Maybe you are looking for