Hello,
I did a client push to one machine:
- Verified boundary, boundary group.
the machine got stuck on:
==========[ ccmsetup started in process 57904 ]========== ccmsetup 5/10/2018 1:54:47 PM 82176 (0x14100)
Running on platform X64 ccmsetup 5/10/2018 1:54:47 PM 82176 (0x14100)
Updated security on object C:\Windows\ccmsetup\cache\. ccmsetup 5/10/2018 1:54:47 PM 82176 (0x14100)
Launch from folder C:\Windows\ccmsetup\ ccmsetup 5/10/2018 1:54:47 PM 82176 (0x14100)
CcmSetup version: 5.0.8577.1115 ccmsetup 5/10/2018 1:54:47 PM 82176 (0x14100)
Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 5/10/2018 1:54:47 PM 82176 (0x14100)
Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 5/10/2018 1:54:47 PM 82176 (0x14100)
In ServiceMain ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
[PATHUICSQLAMIR] Running on 'Microsoft Windows Server 2012 R2 Standard' (6.3.9600). Service Pack (0.0). SuiteMask = 272. Product Type = 18 ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /ForceInstall /ignoreskipupgrade /config:MobileClient.tcf ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /ForceInstall /ignoreskipupgrade /config:MobileClient.tcf ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
SslState value: 224 ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
CCMHTTPPORT: 80 ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
CCMHTTPSPORT: 443 ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
CCMHTTPSSTATE: 448 ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
CCMHTTPSCERTNAME: ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Lookup MP: VRPSCCMPR01.ad ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
FSP: VRPSCCMRS01.ad. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
CCMCERTISSUERS: CN=ad-VRCA-CA; DC=ad; ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
CCMFIRSTCERT: 1 ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
CCMPKICERTOPTIONS: 1 ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
MANAGEDINSTALLER: 0 ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Client is set to use HTTPS when available. The current state is 448. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Begin searching client certificates based on Certificate Issuers ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Certificate Issuer 1 [CN=ad-VRCA-CA; DC=ad; ] ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Analyzing 1 Chain(s) found ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Chain has Certificate [Thumbprint x] issued to [PATHUICSQLAMIR.ad] issued by [CN=ad-VMCASUB-CA; DC=ad] ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Chain has Certificate [Thumbprint x] issued to [ad-VMCASUB-CA] issued by [CN=ad-VRCA-CA; DC=ad] ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Chain has Certificate [Thumbprint x] issued to [ad-VRCA-CA] issued by [CN=ad-VRCA-CA; DC=ad] ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Based on Certificate Issuer 'ad-VRCA-CA' found Certificate [Thumbprint x] issued to 'PATHUICSQLAMIR.ad' ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Begin validation of Certificate [Thumbprint x] issued to 'PATHUICSQLAMIR.ad' ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
CRL check enabled. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Verification of Certificate chain returned 00000000 ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Completed validation of Certificate [Thumbprint x] issued to 'PATHUICSQLAMIR.ad' ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Analyzing 1 Chain(s) found ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Chain has Certificate [Thumbprint x] issued to [PowerShellWebAccessTestWebSite] issued by [CN=PowerShellWebAccessTestWebSite] ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Skipping Certificate [Thumbprint x] issued to 'PowerShellWebAccessTestWebSite' as root is '' ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Completed searching client certificates based on Certificate Issuers ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Begin to select client certificate ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
The 'Certificate Selection Criteria' was not specified, counting number of certificates present in 'MY' store of 'Local Computer'. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
1 certificate(s) found in the 'MY' certificate store. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Only one certificate present in the certificate store. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Begin validation of Certificate [Thumbprint x] issued to 'PATHUICSQLAMIR.ad' ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Allowing usage of CNG key storage. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
The Certificate [Thumbprint x] issued to 'PATHUICSQLAMIR.ad' has 'Client Authentication' capability. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Completed validation of Certificate [Thumbprint x] issued to 'PATHUICSQLAMIR.ad' ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
>>> Client selected the PKI Certificate [Thumbprint x] issued to 'PATHUICSQLAMIR.ad' ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Raising pending event:
instance of CCM_ServiceHost_CertRetrieval_Status
{
ClientID = "GUID:1B144088-ED90-46E3-BDCD-490F4A90DE5F";
DateTime = "20180510205447.751000+000";
HRESULT = "0x00000000";
ProcessID = 57904;
ThreadID = 28064;
};
ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Successfully submitted pending event to WMI. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
CCMCERTID: MY;x ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Config file: C:\Windows\ccmsetup\MobileClientUnicode.tcf ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Retry time: 10 minute(s) ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
MSI log file: C:\Windows\ccmsetup\Logs\client.msi.log ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
MSI properties: CCMCERTID="MY;x" CCMCERTISSUERS="CN=ad-VRCA-CA; DC=ad" CCMFIRSTCERT="1" CCMHOSTNAME="SCCMinternet.ad" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="448" CCMPKICERTOPTIONS="1" DNSSUFFIX="ad" FSP="VRPSCCMRS01.ad" INSTALL="ALL" MANAGEDINSTALLER="0" SMSMP="VRPSCCMPR01.ad" SMSSITECODE="UCP" SMSSLP="VRPSCCMPR01.ad" ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Source List: ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
\\VRPSCCMIBCM01.ad\SMSClient ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
\\VRPSCCMMS03.ad\SMSClient ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
\\VRPSCCMPR01.ad\SMSClient ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
\\VRPSCCMIBCM01.AD\SMSClient ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
\\VRPSCCMMS03.AD\SMSClient ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
\\VRPSCCMPR01.AD\SMSClient ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
MPs: ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
HTTPS://VRPSCCMMS03.ad ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
HTTPS://VRPSCCMPR01.ad ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Detected client version 5.00.8577.1005 from WMI. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Task 'Configuration Manager Client Retry Task' does not exist ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Updated security on object C:\Windows\ccmsetup\. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
[5.00.8577.1005] Params to send '5.0.8577.1115 Deployment Error: 0x0, ' ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
<ClientDeploymentMessage ErrorCode="0"><Client Baseline="1" BaselineCookie="" Platform="2" Langs=""/></ClientDeploymentMessage> ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Raised pending client deployment state message. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Vista or above. No need to check BITS 2.5 ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Detected 189265 MB free disk space on system drive. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Client OS Version 6.2 Service Pack 0.0 ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Running as user "SYSTEM" ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
Checking Write Filter Status. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 5/10/2018 1:54:47 PM 28064 (0x6DA0)
And it stays on this line three days for the first try and now 30 minutes already !!! what is the cause of this block?
Thanks,
Dom
Security / System Center Configuration Manager Current Branch / SQL
