none
Internet Client fails to get sccm client vi SUP RRS feed

  • Question

  •  

    I am having problem pushing out the client vi SUP to remote clients(they are part of AD but Offsite). it downloads the client but the setup fails..  I have firewall forwarding rule setup which points to my primary site server.  I have server.xyz.corp is the intranet base fqdn and server.xyz.us is the internet base fqdn. My public dns has a entry for server.xyz.us.  also my group policy for remote client has wsus server as server.xyz.us.  Also my pki internal infrastructure is around xyz.corp..Also i have done the SAN cert where i have integrated server.xyz.corp and server.xyz.us.  Internally wsus is pushing out the sccm client fine without any issue but for remote clients is not working..following are the logs from the client.. currently i have port 443 and 8531 open on the firewall ..i even tried opening up port 80 but not success..

     

     

    ==========[ ccmsetup started in process 2696 ]========== ccmsetup 8/4/2008 9:53:04 AM 1228 (0x04CC)

    Version: 4.0.6221.1000 ccmsetup 8/4/2008 9:53:04 AM 1228 (0x04CC)

    Found additional ccmsetup.exe parameters through the registry. ccmsetup 8/4/2008 9:53:04 AM 1228 (0x04CC)

    Command line: C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe /mpTongue Tiederver /native SMSSITECODE=KS1 FSP=sql1 CCMHOSTNAME="server.xyz.us" ccmsetup 8/4/2008 9:53:04 AM 1228 (0x04CC)

    User credentials are not required to access installation files. ccmsetup will be executed in service-only mode. ccmsetup 8/4/2008 9:53:04 AM 1228 (0x04CC)

    Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 8/4/2008 9:53:04 AM 1228 (0x04CC)

    A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 8/4/2008 9:53:04 AM 1228 (0x04CC)

    ccmsetup service is stopped. ccmsetup 8/4/2008 9:53:04 AM 1228 (0x04CC)

    Successfully deleted the ccmsetup service ccmsetup 8/4/2008 9:53:09 AM 1228 (0x04CC)

    Ccmsetup is not registered in the Run key ccmsetup 8/4/2008 9:53:09 AM 1228 (0x04CC)

    Successfully deleted existing ccmsetup.exe ccmsetup 8/4/2008 9:53:10 AM 1228 (0x04CC)

    Downloading file C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe ccmsetup 8/4/2008 9:53:10 AM 1228 (0x04CC)

    Downloading C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe to C:\WINDOWS\system32\ccmsetup\ccmsetup.exe ccmsetup 8/4/2008 9:53:10 AM 1228 (0x04CC)

    File download 10% complete (65536 of 602112 bytes). ccmsetup 8/4/2008 9:53:10 AM 1228 (0x04CC)

    File download 21% complete (131072 of 602112 bytes). ccmsetup 8/4/2008 9:53:10 AM 1228 (0x04CC)

    File download 32% complete (196608 of 602112 bytes). ccmsetup 8/4/2008 9:53:10 AM 1228 (0x04CC)

    File download 43% complete (262144 of 602112 bytes). ccmsetup 8/4/2008 9:53:10 AM 1228 (0x04CC)

    File download 54% complete (327680 of 602112 bytes). ccmsetup 8/4/2008 9:53:10 AM 1228 (0x04CC)

    File download 65% complete (393216 of 602112 bytes). ccmsetup 8/4/2008 9:53:10 AM 1228 (0x04CC)

    File download 76% complete (458752 of 602112 bytes). ccmsetup 8/4/2008 9:53:10 AM 1228 (0x04CC)

    File download 87% complete (524288 of 602112 bytes). ccmsetup 8/4/2008 9:53:10 AM 1228 (0x04CC)

    File download 97% complete (589824 of 602112 bytes). ccmsetup 8/4/2008 9:53:10 AM 1228 (0x04CC)

    File download 100% complete (602112 of 602112 bytes). ccmsetup 8/4/2008 9:53:10 AM 1228 (0x04CC)

    Download complete. ccmsetup 8/4/2008 9:53:10 AM 1228 (0x04CC)

    Successfully created the ccmsetup service ccmsetup 8/4/2008 9:53:11 AM 1228 (0x04CC)

    ==========[ ccmsetup started in process 876 ]========== ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    Version: 4.0.6221.1000 ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /mpTongue Tiederver /native SMSSITECODE=KS1 FSP=sql1 CCMHOSTNAME="server.xyz.us" ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    CCMHTTPPORT: 80 ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    CCMHTTPSPORT: 443 ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    CCMHTTPSSTATE: 31 ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    CCMHTTPSCERTNAME: ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    FSP: sql1 ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    Config file: ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    Retry time: 10 minute(s) ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    MSI log file: ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    MSI properties: SMSSITECODE="KS1" FSP="sql1" CCMHOSTNAME="server.xyz.us" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="31" ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    Source List: ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    MPs: ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    server ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    Sending Fallback Status Point message, STATEID='100'. ccmsetup 8/4/2008 9:53:11 AM 2984 (0x0BA8)

    sending with winhttp failed; 80072ee7 FSPStateMessage 8/4/2008 9:53:16 AM 2984 (0x0BA8)

    Successfully started the ccmsetup service ccmsetup 8/4/2008 9:53:16 AM 1228 (0x04CC)

    Deleted file C:\WINDOWS\system32\ccmsetup\ccmsetup.exe.download ccmsetup 8/4/2008 9:53:16 AM 1228 (0x04CC)

    Running as user "SYSTEM" ccmsetup 8/4/2008 9:53:16 AM 2292 (0x08F4)

    Detected 58405 MB free disk space on system drive. ccmsetup 8/4/2008 9:53:16 AM 2292 (0x08F4)

    DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 8/4/2008 9:53:16 AM 2292 (0x08F4)

    Client OS is not Windows XP Embedded ccmsetup 8/4/2008 9:53:16 AM 2292 (0x08F4)

    Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again. ccmsetup 8/4/2008 9:53:16 AM 2292 (0x08F4)

    Successfully ran BITS check. ccmsetup 8/4/2008 9:53:17 AM 2292 (0x08F4)

    The 'Certificate Store' is empty in the registry, using default store name 'MY'. ccmsetup 8/4/2008 9:53:17 AM 2292 (0x08F4)

    The 'Certificate Selection Criteria' was not specified, counting number of certificates present in 'MY' store of 'Local Computer'. ccmsetup 8/4/2008 9:53:17 AM 2292 (0x08F4)

    1 certificate(s) found in the 'MY' certificate store. ccmsetup 8/4/2008 9:53:17 AM 2292 (0x08F4)

    Only one certificate present in the certificate store. ccmsetup 8/4/2008 9:53:17 AM 2292 (0x08F4)

    SSL Registry key Software\Microsoft\CCM not found, assuming Client SSL is disabled. ccmsetup 8/4/2008 9:53:17 AM 2292 (0x08F4)

    The certificate issued to 'ksea-l-992E6094.xyz.corp' has 'Client Authentication' capability. ccmsetup 8/4/2008 9:53:17 AM 2292 (0x08F4)

    Using the certificate issued to 'ksea-l-992E6094.xyz.corp'. ccmsetup 8/4/2008 9:53:17 AM 2292 (0x08F4)

    Failed to send HTTP request. (Error at WinHttpSendRequest: 12007) ccmsetup 8/4/2008 9:53:19 AM 2292 (0x08F4)

    DownloadFileByWinHTTP encountered an unrecoverable error. ccmsetup 8/4/2008 9:53:19 AM 2292 (0x08F4)

    Sending Fallback Status Point message, STATEID='308'. ccmsetup 8/4/2008 9:53:19 AM 2292 (0x08F4)

    sending with winhttp failed; 80072ee7 FSPStateMessage 8/4/2008 9:53:23 AM 2292 (0x08F4)

     

    Tuesday, August 5, 2008 9:24 PM

Answers

  •  Dometh wrote:

     

    I am having problem pushing out the client vi SUP to remote clients(they are part of AD but Offsite). ....Internally wsus is pushing out the sccm client fine without any issue but for remote clients is not working.

     

     

    Are you trying to install clients with the Internet-based software update point while they are on the Internet?  This isn’t supported.  From Decide How to Install Configuration Manager Clients for Internet-Based Client Management:

     

    Note

    Installing a client directly from the Internet-based management point, or from the Internet-based software update point is not supported.

     

    Instead, either install them via a VPN or install them manually and supply all the client installation files locally.

     

     

    - Carol

     

    This posting is provided “AS IS” with no warranties and confers no rights.

     

    Tuesday, August 5, 2008 10:43 PM