SCCM을 활용하기 위해서는 Domain에 가입된 PC 들에 Agent 프로그램을 배포해야합니다.
아래와 같이 진행하였습니다.
<SCCM Agent1 User를 Domain Join>
Administration - Sites 이동
우클릭 - Client Installation Settings - Client Push Installation
Enable 설정
관리자 계정 추가 (Domain Admins 소속그룹)
Assets and Compliance 메뉴로 이동 - 설치 대상을 우클릭 - Install Client
Next
Next
Next
Close
해당 Client 에서 설치가 되고 있지 않는 것으로 확인
리서치시 로그의 경로는 다음과 같습니다.
C:\Program Files\Microsoft Configuration Manager\Logs\ccm.log
아래와 같이 실패 로그를 확인할 수 있습니다.
|
======>Begin Processing request: "2097152006", machine name: "AGENT1" $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:05.290-540><thread=7364 (0x1CC4)> Getting a new request from queue "Incoming" after 100 millisecond delay. $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:05.290-540><thread=3608 (0xE18)> Waiting for change in directory "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:05.291-540><thread=3608 (0xE18)> Execute query exec [sp_IsMPAvailable] N'PEP'~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:05.295-540><thread=7364 (0x1CC4)> ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:05.296-540><thread=7364 (0x1CC4)> ---> Attempting to connect to administrative share '\\Agent1.limcmfz.com\admin$' using account 'limcmfz\sccm-admin'~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:05.297-540><thread=7364 (0x1CC4)> ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account limcmfz\sccm-admin (00000035) $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:30.945-540><thread=7364 (0x1CC4)> ---> The device Agent1.limcmfz.com does not exist on the network. Giving up~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:30.947-540><thread=7364 (0x1CC4)> ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:30.947-540><thread=7364 (0x1CC4)> ---> Attempting to connect to administrative share '\\AGENT1\admin$' using account 'limcmfz\sccm-admin'~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:30.947-540><thread=7364 (0x1CC4)> ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account limcmfz\sccm-admin (00000035) $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:52.011-540><thread=7364 (0x1CC4)> ---> The device AGENT1 does not exist on the network. Giving up~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:52.012-540><thread=7364 (0x1CC4)> ---> ERROR: Unable to access target machine for request: "2097152006", machine name: "AGENT1", access denied or invalid network path. $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:52.013-540><thread=7364 (0x1CC4)> Execute query exec [sp_CP_SetLastErrorCode] 2097152006, 53~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:52.015-540><thread=7364 (0x1CC4)> Stored request "2097152006", machine name "AGENT1", in queue "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:52.020-540><thread=7364 (0x1CC4)> Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152006, 2~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:52.022-540><thread=7364 (0x1CC4)> Execute query exec [sp_CP_SetLatest] 2097152006, N'06/20/2017 05:32:52', 31~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:52.026-540><thread=7364 (0x1CC4)> <======End request: "2097152006", machine name: "AGENT1". $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 14:32:52.029-540><thread=7364 (0x1CC4)> |
오류를 근거로 Research를 진행 아래의 MSDN Blog 자료를 확인할 수 있습니다.
How to identify SCCM Client installation blocked by Windows firewall on client side
Client PC에서 다음 작업을 진행
네트워크 고급 공유 설정에서 파일 및 프린터 공유 켜기를 진행
제어판 - 시스템 및 보안 - Windows 방화벽 - 고급 설정 이동
WMI 목록 중 도메인 관련 항목만 더블 클릭
사용함으로 설정
Install Client 진행 후 이전과 동일하게 로그 확인
|
======>Begin Processing request: "2097152006", machine name: "AGENT1" $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:00.602-540><thread=4332 (0x10EC)> Execute query exec [sp_IsMPAvailable] N'PEP'~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:00.604-540><thread=4332 (0x10EC)> ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:00.605-540><thread=4332 (0x10EC)> ---> Attempting to connect to administrative share '\\Agent1.limcmfz.com\admin$' using account 'limcmfz\sccm-admin'~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:00.606-540><thread=4332 (0x10EC)> Getting a new request from queue "Incoming" after 100 millisecond delay. $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:00.602-540><thread=3608 (0xE18)> Waiting for change in directory "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:00.624-540><thread=3608 (0xE18)> ---> The 'best-shot' account has now succeeded 4 times and failed 0 times. $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:00.708-540><thread=4332 (0x10EC)> ---> Connected to administrative share on machine Agent1.limcmfz.com using account 'limcmfz\sccm-admin'~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:00.709-540><thread=4332 (0x10EC)> ---> Attempting to make IPC connection to share <\\Agent1.limcmfz.com\IPC$> ~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:00.709-540><thread=4332 (0x10EC)> ---> Searching for SMSClientInstall.* under '\\Agent1.limcmfz.com\admin$\'~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:00.713-540><thread=4332 (0x10EC)> ---> System OS version string "10.0.15063" converted to 10.00 $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:01.229-540><thread=4332 (0x10EC)> ---> Unable to connect to WMI (root\ccm) on remote machine "Agent1.limcmfz.com", error = 0x8004100e. $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:01.262-540><thread=4332 (0x10EC)> ---> Creating \ VerifyingCopying existence of destination directory \\Agent1.limcmfz.com\admin$\ccmsetup.~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:01.263-540><thread=4332 (0x10EC)> ---> Copying client files to \\Agent1.limcmfz.com\admin$\ccmsetup.~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:01.265-540><thread=4332 (0x10EC)> ---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "MobileClient.tcf" $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:01.268-540><thread=4332 (0x10EC)> ---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "ccmsetup.exe" $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:01.302-540><thread=4332 (0x10EC)> ---> Created service "ccmsetup" on machine "Agent1.limcmfz.com". $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:22.590-540><thread=4332 (0x10EC)> ---> Started service "ccmsetup" on machine "Agent1.limcmfz.com". $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:23.125-540><thread=4332 (0x10EC)> ---> Deleting SMS Client Install Lock File '\\Agent1.limcmfz.com\admin$\SMSClientInstall.PEP'~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:23.129-540><thread=4332 (0x10EC)> Execute query exec [sp_CP_SetLastErrorCode] 2097152006, 0~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:23.136-540><thread=4332 (0x10EC)> ---> Completed request "2097152006", machine name "AGENT1". $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:23.140-540><thread=4332 (0x10EC)> Deleted request "2097152006", machine name "AGENT1" $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:23.140-540><thread=4332 (0x10EC)> Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152006, 4~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:23.142-540><thread=4332 (0x10EC)> Execute query exec [sp_CP_SetLatest] 2097152006, N'06/20/2017 06:07:23', 33~ $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:23.147-540><thread=4332 (0x10EC)> <======End request: "2097152006", machine name: "AGENT1". $$<SMS_CLIENT_CONFIG_MANAGER><06-20-2017 15:07:23.151-540><thread=4332 (0x10EC)> |
Agent Test Machine에 설치된 것을 확인할 수 있습니다.
SCCM 상에서 확인 -Active 상태를 확인할 수 있습니다.
'MS 기타제품&Tool > System Center' 카테고리의 다른 글
| System Center 2016: Configuration Manager 설치 (4) | 2017.09.18 |
|---|---|
| SCCM 2016. Software Library 를 통한 Office 365 배포 (0) | 2017.07.07 |
| SCCM 2016. Build Update (0) | 2017.06.13 |
| SCVMM. Hyper-V Host 추가 (0) | 2017.04.21 |
| SCVMM 2016. Hyper-v 호스트 추가시 Error(415), Warning(10444) 나타나는 증상 (0) | 2017.04.16 |