Unable to connect to wmi root ccm on remote machine error 0x8004100e

Unable to connect to wmi root ccm on remote machine error 0x8004100e

Question

I have SCCM 2012 but I can’t install Cleints on Server 2003. I have not problem to install client on XP,Win7, server 2008.

Cleint doesn’t have firewall

My CCM log is saying

======>Begin Processing request: «2097152351», machine name: «SERVER-1» SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

Execute query exec [sp_IsMPAvailable] N’SYD’ SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> Trying the ‘best-shot’ account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> Attempting to connect to administrative share ‘\SERVER-1admin$’ using account ‘npssccmadministrator’ SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> The ‘best-shot’ account has now succeeded 36 times and failed 0 times. SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> Connected to administrative share on machine SERVER-1 using account ‘npssccmadministrator’ SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> Attempting to make IPC connection to share SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> Searching for SMSClientInstall.* under ‘\SERVER-1admin$’ SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> System OS version string «5.2.3790» converted to 5.20 SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> Service Pack version from machine «SERVER-1» is 2 SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

CWmi::Connect(): ConnectServer(Namespace) failed. — 0x8004100e SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> Unable to connect to WMI (rootccm) on remote machine «SERVER-1», error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> Creating VerifyingCopying exsistance of destination directory \SERVER-1admin$ccmsetup. SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> Copying client files to \SERVER-1admin$ccmsetup. SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> Copying file «E:Program FilesMicrosoft Configuration ManagerbinI386MobileClient.tcf» to «MobileClient.tcf» SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> Copying file «E:Program FilesMicrosoft Configuration ManagerbinI386ccmsetup.exe» to «ccmsetup.exe» SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> Updated service «ccmsetup» on machine «SERVER-1». SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> Started service «ccmsetup» on machine «SERVER-1». SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> Deleting SMS Client Install Lock File ‘\SERVER-1admin$SMSClientInstall.SYD’ SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

Execute query exec [sp_CP_SetLastErrorCode] 2097152351, 0 SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

—> Completed request «2097152351», machine name «SERVER-1». SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

Deleted request «2097152351», machine name «SERVER-1» SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152351, 4 SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

Execute query exec [sp_CP_SetLatest] 2097152351, N’07/11/2013 02:09:37′, 10 SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

SMS_CLIENT_CONFIG_MANAGER 11/07/2013 12:09:37 PM 5712 (0x1650)

Источник

Unable to connect to wmi root ccm on remote machine error 0x8004100e

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

All info posted here is from a testing environment so I’m ok with all security incorrectness — I’m just learning and want see things work

I’m receiving the following while trying to push sccm client:

—> Unable to connect to WMI (rootccm) on remote machine «Client01.ad.tpn.com», error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 5/9/2017 9:47:41 AM 10320 (0x2850)

• I have the firewall off on all 3 network types on both the client and SCCM Server.
• I do get correct feedback from client after issuing:

• I do get correct feedback from client after issuing:

• I’ve double checked my 1 and only boundary it is of type «Active Directory site» and references the Default-First-Site-Name and I’ve verified does match the default site name in ADSAS on the DC.
• Created a boundary group with the following:

* Linked to «Default-First-Site-Name» Boundary

* ticked «Use this boundary for site assignment» chose my 1 and only site

* Chose my 1 and only CM server as the «Site System Server»

I have no idea where to go from here. Please advise where else I can look for clues to the client push failing.

• Moved by Jason Sandys [MSFT] MVP Wednesday, May 10, 2017 7:50 PM

Answers

Is there a reason why you want HTTPS?

Particularly if you are learning don’t setup a HTTPS site. IT has it own set of headaches.

• Marked as answer by Gerry Hampson MVP Sunday, August 27, 2017 6:35 PM

That’s the easiest way to get PKI certs, yes. But as Garth notes, why are you trying to implement HTTPS client communication for an initial lab and learning experience? I’d highly recommend that you start without HTTPS client communication.

The complete requirements for the certs are at https://docs.microsoft.com/en-us/sccm/core/plan-design/network/pki-certificate-requirements

Jason | http://blog.configmgrftw.com | @jasonsandys

• Proposed as answer by Frank Dong Thursday, May 11, 2017 3:46 PM
• Marked as answer by Gerry Hampson MVP Sunday, August 27, 2017 6:35 PM

That is completely normal and expected. It is simply a check to see whether the client is installed or not yet.

rootccm is the namespace that the client agent creates so if it’s there already, that means the system already has the client agent installed. If it’s not there, then great, no client agent installed.

There’s no where to go because that’s normal.

Jason | http://blog.configmgrftw.com | @jasonsandys

Thanks Jason, that makes perfect sense. I couldn’t figure out the purpose of the wmi/ccm query prior to installing the ccm classes.

With that said I was definitely barking up the wrong tree. the coon is up the IIS tree I think. I’m getting permission errors while trying to contact the MP.

When I try to manually browse to https:\CM01sms_mp.sms_aut?mplist I’m receiving a 403 forbidden error. On the CM Server I checked the Application Pool identity for the SMS_MP application in iis and found it to be LocalService. I then check the physical location of the SMS_MP application and found it under C:Program FilesSMS_CCMSMS_MP. I then checked to ensure that the LocalService account had permission to this physical location and it had listFolderContents only so I added ReadAndExecute which also added Read. All of the same is true for the IUSR account (what it had and what I granted). Restarted IIS but these additional permissions had no affect on client accessing bold URL above. Other notes: 1) the physical path of C:Program FilesSMS_CCMSMS_MP I notice is completely empty when I navigate to it on the CM server and 2) I get a 403.7 forbidden message when trying to browse via IE to the bold URL from the CM server.

Источник

Unable to connect to wmi root ccm on remote machine error 0x8004100e

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

All info posted here is from a testing environment so I’m ok with all security incorrectness — I’m just learning and want see things work

I’m receiving the following while trying to push sccm client:

—> Unable to connect to WMI (rootccm) on remote machine «Client01.ad.tpn.com», error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 5/9/2017 9:47:41 AM 10320 (0x2850)

• I have the firewall off on all 3 network types on both the client and SCCM Server.
• I do get correct feedback from client after issuing:

• I do get correct feedback from client after issuing:

• I’ve double checked my 1 and only boundary it is of type «Active Directory site» and references the Default-First-Site-Name and I’ve verified does match the default site name in ADSAS on the DC.
• Created a boundary group with the following:

* Linked to «Default-First-Site-Name» Boundary

* ticked «Use this boundary for site assignment» chose my 1 and only site

* Chose my 1 and only CM server as the «Site System Server»

I have no idea where to go from here. Please advise where else I can look for clues to the client push failing.

• Moved by Jason Sandys [MSFT] MVP Wednesday, May 10, 2017 7:50 PM

Answers

Is there a reason why you want HTTPS?

Particularly if you are learning don’t setup a HTTPS site. IT has it own set of headaches.

• Marked as answer by Gerry Hampson MVP Sunday, August 27, 2017 6:35 PM

That’s the easiest way to get PKI certs, yes. But as Garth notes, why are you trying to implement HTTPS client communication for an initial lab and learning experience? I’d highly recommend that you start without HTTPS client communication.

The complete requirements for the certs are at https://docs.microsoft.com/en-us/sccm/core/plan-design/network/pki-certificate-requirements

Jason | http://blog.configmgrftw.com | @jasonsandys

• Proposed as answer by Frank Dong Thursday, May 11, 2017 3:46 PM
• Marked as answer by Gerry Hampson MVP Sunday, August 27, 2017 6:35 PM

That is completely normal and expected. It is simply a check to see whether the client is installed or not yet.

rootccm is the namespace that the client agent creates so if it’s there already, that means the system already has the client agent installed. If it’s not there, then great, no client agent installed.

There’s no where to go because that’s normal.

Jason | http://blog.configmgrftw.com | @jasonsandys

Thanks Jason, that makes perfect sense. I couldn’t figure out the purpose of the wmi/ccm query prior to installing the ccm classes.

With that said I was definitely barking up the wrong tree. the coon is up the IIS tree I think. I’m getting permission errors while trying to contact the MP.

When I try to manually browse to https:\CM01sms_mp.sms_aut?mplist I’m receiving a 403 forbidden error. On the CM Server I checked the Application Pool identity for the SMS_MP application in iis and found it to be LocalService. I then check the physical location of the SMS_MP application and found it under C:Program FilesSMS_CCMSMS_MP. I then checked to ensure that the LocalService account had permission to this physical location and it had listFolderContents only so I added ReadAndExecute which also added Read. All of the same is true for the IUSR account (what it had and what I granted). Restarted IIS but these additional permissions had no affect on client accessing bold URL above. Other notes: 1) the physical path of C:Program FilesSMS_CCMSMS_MP I notice is completely empty when I navigate to it on the CM server and 2) I get a 403.7 forbidden message when trying to browse via IE to the bold URL from the CM server.

Источник

Unable to connect to wmi root ccm on remote machine error 0x8004100e

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

All info posted here is from a testing environment so I’m ok with all security incorrectness — I’m just learning and want see things work

I’m receiving the following while trying to push sccm client:

—> Unable to connect to WMI (rootccm) on remote machine «Client01.ad.tpn.com», error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 5/9/2017 9:47:41 AM 10320 (0x2850)

• I have the firewall off on all 3 network types on both the client and SCCM Server.
• I do get correct feedback from client after issuing:

• I do get correct feedback from client after issuing:

• I’ve double checked my 1 and only boundary it is of type «Active Directory site» and references the Default-First-Site-Name and I’ve verified does match the default site name in ADSAS on the DC.
• Created a boundary group with the following:

* Linked to «Default-First-Site-Name» Boundary

* ticked «Use this boundary for site assignment» chose my 1 and only site

* Chose my 1 and only CM server as the «Site System Server»

I have no idea where to go from here. Please advise where else I can look for clues to the client push failing.

• Moved by Jason Sandys [MSFT] MVP Wednesday, May 10, 2017 7:50 PM

Answers

Is there a reason why you want HTTPS?

Particularly if you are learning don’t setup a HTTPS site. IT has it own set of headaches.

• Marked as answer by Gerry Hampson MVP Sunday, August 27, 2017 6:35 PM

That’s the easiest way to get PKI certs, yes. But as Garth notes, why are you trying to implement HTTPS client communication for an initial lab and learning experience? I’d highly recommend that you start without HTTPS client communication.

The complete requirements for the certs are at https://docs.microsoft.com/en-us/sccm/core/plan-design/network/pki-certificate-requirements

Jason | http://blog.configmgrftw.com | @jasonsandys

• Proposed as answer by Frank Dong Thursday, May 11, 2017 3:46 PM
• Marked as answer by Gerry Hampson MVP Sunday, August 27, 2017 6:35 PM

That is completely normal and expected. It is simply a check to see whether the client is installed or not yet.

rootccm is the namespace that the client agent creates so if it’s there already, that means the system already has the client agent installed. If it’s not there, then great, no client agent installed.

There’s no where to go because that’s normal.

Jason | http://blog.configmgrftw.com | @jasonsandys

Thanks Jason, that makes perfect sense. I couldn’t figure out the purpose of the wmi/ccm query prior to installing the ccm classes.

With that said I was definitely barking up the wrong tree. the coon is up the IIS tree I think. I’m getting permission errors while trying to contact the MP.

When I try to manually browse to https:\CM01sms_mp.sms_aut?mplist I’m receiving a 403 forbidden error. On the CM Server I checked the Application Pool identity for the SMS_MP application in iis and found it to be LocalService. I then check the physical location of the SMS_MP application and found it under C:Program FilesSMS_CCMSMS_MP. I then checked to ensure that the LocalService account had permission to this physical location and it had listFolderContents only so I added ReadAndExecute which also added Read. All of the same is true for the IUSR account (what it had and what I granted). Restarted IIS but these additional permissions had no affect on client accessing bold URL above. Other notes: 1) the physical path of C:Program FilesSMS_CCMSMS_MP I notice is completely empty when I navigate to it on the CM server and 2) I get a 403.7 forbidden message when trying to browse via IE to the bold URL from the CM server.

Источник

Posted by gmaleev 2018-05-07T10:45:08Z

Hello!

I’ve installed SCCM 1702.

All components are green

I’ve created in Active Directory User for Client Deployment, added user to Domain Admins and Built-InAdministartors.

I try to deploy client via Push Installation from server on my workstation with Windows 10 Pro.

It doesn’t deploy and I see error in log:

—> Unable to connect to WMI (rootccm) on remote machine «MY_MACHINE_NAME», error = 0x8004100e.

Here is screenshot:

https://yadi.sk/i/cjlfqTlt3VUN4g Opens a new window

How can I fix it?

3 Replies

• https://community.spiceworks.com/topic/457790-sccm-2012-r2-unable-to-install-client

  To fix the WMI error, you can try one of these steps :-

  1) Disable the firewall or type in a command prompt with elevated privileges:

  netsh firewall set service remoteadmin enable

  2) Start > Run > services.msc > Windows Management Instrumentation service >right-click it and press Stop.

  Use Windows Explorer to delete all the files in the %SystemRoot%System32WbemRepository folder and restart your computer.

  The Windows Management Instrumentation service will start and the files will be re-created

  https://prajwaldesai.com/community/threads/unable-to-connect-to-wmi-root-ccm-on-remote-machine-error… Opens a new window

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  firewall is disabled.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  were you able to find a fix?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

After going through the install client steps for a device I am getting these errors in my log:

---> Unable to connect to WMI (rootccm) on remote machine "[MACHINE NAME]", error = 0x8004100e.

Execute query exec [sp_CP_SetLastErrorCode] 2097152005, 0

Despite these, on the client machine I see that «ccmsetup» has started under Services.msc. Also, since this is a lab environment and the only advice online points to Windows Firewall, I disabled Windows Firewall on the SCCM Server and Client and did an install again, with the same results.

EDIT: Full Log:

======>Begin Processing request: «2097152005», machine name: «[MACHINE NAME]» SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:11:58 PM 2276 (0x08E4)

Execute query exec [sp_IsMPAvailable] N’100′ SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:11:58 PM 2276 (0x08E4)

—> Trying the ‘best-shot’ account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:11:58 PM 2276 (0x08E4)

—> Attempting to connect to administrative share ‘\[SPECIFIED SITE]admin$’ using account ‘DomainAdministrator’ SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:11:58 PM 2276 (0x08E4)

—> The ‘best-shot’ account has now succeeded 10 times and failed 0 times. SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:11:58 PM 2276 (0x08E4)

—> Connected to administrative share on machine [SPECIFIED SITE] using account ‘DomainAdministrator’ SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:11:58 PM 2276 (0x08E4)

—> Attempting to make IPC connection to share <\[SPECIFIED SITE]IPC$> SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:11:58 PM 2276 (0x08E4)

—> Searching for SMSClientInstall.* under ‘\[SPECIFIED SITE]admin$’ SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:11:58 PM 2276 (0x08E4)

—> System OS version string «10.0.14393» converted to 10.00 SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:11:58 PM 2276 (0x08E4)

—> Unable to connect to WMI (rootccm) on remote machine «[SPECIFIED SITE]», error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:11:58 PM 2276 (0x08E4)

—> Creating VerifyingCopying existence of destination directory \[SPECIFIED SITE]admin$ccmsetup. SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:11:58 PM 2276 (0x08E4)

—> Copying client files to \[SPECIFIED SITE]admin$ccmsetup. SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:11:58 PM 2276 (0x08E4)

—> Copying file «C:Program FilesMicrosoft Configuration ManagerbinI386MobileClient.tcf» to «MobileClient.tcf» SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:11:58 PM 2276 (0x08E4)

—> Copying file «C:Program FilesMicrosoft Configuration ManagerbinI386ccmsetup.exe» to «ccmsetup.exe» SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:12:00 PM 2276 (0x08E4)

Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:12:00 PM 5564 (0x15BC)

Getting a new request from queue «Incoming» after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:12:00 PM 5564 (0x15BC)

Waiting for change in directory «C:Program FilesMicrosoft Configuration Managerinboxesccr.box» for queue «Incoming», (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:12:00 PM 5564 (0x15BC)

—> Updated service «ccmsetup» on machine «[SPECIFIED SITE]». SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:12:15 PM 2276 (0x08E4)

—> Started service «ccmsetup» on machine «[SPECIFIED SITE]». SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:12:15 PM 2276 (0x08E4)

—> Deleting SMS Client Install Lock File ‘\[SPECIFIED SITE]admin$SMSClientInstall.100’ SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:12:15 PM 2276 (0x08E4)

Execute query exec [sp_CP_SetLastErrorCode] 2097152005, 0 SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:12:15 PM 2276 (0x08E4)

—> Completed request «2097152005», machine name «[MACHINE NAME]». SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:12:15 PM 2276 (0x08E4)

Deleted request «2097152005», machine name «[MACHINE NAME]» SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:12:15 PM 2276 (0x08E4)

Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152005, 4 SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:12:15 PM 2276 (0x08E4)

Execute query exec [sp_CP_SetLatest] 2097152005, N’02/19/2019 22:12:15′, 20 SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:12:15 PM 2276 (0x08E4)

<======End request: «2097152005», machine name: «[MACHINE NAME]». SMS_CLIENT_CONFIG_MANAGER 2/19/2019 2:12:15 PM 2276 (0x08E4)

Обновлено 2023 января: перестаньте получать сообщения об ошибках и замедлите работу вашей системы с помощью нашего инструмента оптимизации. Получить сейчас в эту ссылку

1. Скачайте и установите инструмент для ремонта здесь.
2. Пусть он просканирует ваш компьютер.
3. Затем инструмент почини свой компьютер.

Ошибка 8004100e — это ошибка WMI, также называемая WBEM_E_INVALID_NAMESPACE.

Основной причиной является хранилище WMI. Это означает, что WMI поврежден. Что такое хранилище WMI? Это база данных, в которой хранится метаинформация и определения классов WMI.

Другой возможной причиной является то, что диспетчер распространения требует установки базовых компонентов IIS на локальном сервере сайта диспетчера конфигурации для создания виртуального каталога. Диспетчер распространения также требует, чтобы на сервере точки распространения были установлены веб-службы IIS, которые должны поддерживать интеллектуальную службу фоновой передачи (BITS).

Убедитесь, что базовые компоненты IIS установлены на локальном сервере сайта Configuration Manager, а веб-службы IIS установлены на сервере точки распространения.

Сообщение об ошибке может выглядеть так:

cWmi :: Connect () не удалось подключиться к \ DP.domainname.com root MicrosoftIISv2.2. Ошибка = 0x8004100E

или что-то типа того:

ОШИБКА DPConnection :: ConnectRemoteIISManagementWMI () — Не удалось подключиться к DP.domainname.com ошибка = 0x8004100e

Чтобы исправить ошибку 0X8004100E, используйте следующие методы:

Отключение брандмауэра

1. Откройте панель управления — это можно сделать несколькими способами, но самый простой — через меню опытного пользователя или меню «Пуск» Windows 7.
2. Выберите ссылку Система и безопасность.
3. Выберите Брандмауэр Защитника Windows.
4. В левой части экрана брандмауэра Windows выберите Включить или отключить брандмауэр Windows.
5. Выберите пузырь рядом с Отключить брандмауэр Windows (не рекомендуется).
6. Нажмите или нажмите кнопку ОК, чтобы сохранить изменения.

Удаление папок из хранилища

Пуск> Выполнить> Services.msc> Служба инструментария управления Windows> щелкните его правой кнопкой мыши и нажмите Стоп.

С помощью проводника Windows удалите все файлы в папке% SystemRoot% System32 Wbem Repository и перезагрузите компьютер.

Установка IIS 7.0 WMI

Установите поставщик WMI IIS 7.0 на каждом целевом компьютере и на машине Query Engine (или 11.0 CCS Manager), создающей отчеты на целевых компьютерах. Выполните следующие действия, чтобы включить «Сценарии и инструменты управления IIS» на сервере Windows 2008:

Нажмите Пуск -> Панель управления -> Инструменты администрирования -> Диспетчер сервера -> Роли.
Прокрутите вниз до списка ролей IIS под названием «Ролевые службы ## установлены».
Выберите Добавить службы ролей
Прокрутите и выберите Сценарии и инструменты управления IIS.
Нажмите на кнопку Установить
Снова выполните запрос bv-control для Windows.

Перекомпилировать репозитории WMI

Вы также можете решить эту проблему, перекомпилировав полные репозитории WMI для Microsoft Windows и Citrix. Выполните следующие команды, чтобы восстановить эти файлы:

Перекомпилируйте файлы Microsoft Windows.MOF:

Чистая остановка WinMgmt
c:
cd% systemroot% system32 wbem
RD / S / Q хранилище

regsvr32 / s% systemroot% system32 scecli.dll
regsvr32 / s% systemroot% system32 userenv.dll

mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
для / f% s в (‘dir / b / s * .dll’) сделать regsvr32 / s% s
для / f% s в (‘dir / b * .mof’) do mofcomp% s
для / f% s в (‘dir / b * .mfl’) do mofcomp% s

Перекомпилируйте файлы Citrix .MOF:

Сообщение Просмотров: 258

Hi everyone.

I am making crazy. I have problems installing the agent of Configuration Manager on the computers.

On DC and the only SCCM server I have no problem to install the client.

I have tried a lot of solutions:

— Firewall disabled at computer and SCCM Server.

— My account is local administrator account.

— I have connection to \computeradmin$ with the account.

— Checked with WBEMTEST i have connection to the computer and to the server.

This is the ccm.log from the server:

======>Begin Processing request: «2097152005», machine name: «MITECO3» | SMS_CLIENT_CONFIG_MANAGER Execute query exec [sp_IsMPAvailable] N’MIT’ | SMS_CLIENT_CONFIG_MANAGER | 22/02/20—> Trying each entry in the SMS Client Remote
Installation account list | SMS_CLIENT_CONFIG_MANAGE—> Attempting to connect to administrative share ‘\MITECO3.test.localadmin$’ using account ‘TEST—> SspiEncodeStringsAsAuthIdentity succeeded! | SMS_CLIENT_CONFIG_MANAGER | 22/02/20—> SspiExcludePackage
succeeded! | SMS_CLIENT_CONFIG_MANAGER | 22/02/20—> SspiMarshalAuthIdentity succeeded! | SMS_CLIENT_CONFIG_MANAGER | 22/02/20—> NetUseAdd succeeded! | SMS_CLIENT_CONFIG_MANAGER | 22/02/20—> Connected to administrative share on machine MITECO3.test.local
using account ‘TESTadmin_sccm—> Trying the ‘best-shot’ account which worked for previous CCRs (index = 0xFFFF) | SMS_CLIENT_CON—> Attempting to make IPC connection to share <\MITECO3.test.localIPC$> with Kerberos authentica—> SspiEncodeStringsAsAuthIdentity
succeeded for IPC$ authentication! | SMS_CLIENT_CONFIG_MANAGER —> SspiExcludePackage succeeded for IPC$ authentication! | SMS_CLIENT_CONFIG_MANAGER | 22—> SspiMarshalAuthIdentity succeeded for IPC$ authentication! | SMS_CLIENT_CONFIG_MANAGER | —>
NetUseAdd succeeded for IPC$ authentication! | SMS_CLIENT_CONFIG_MANAGER | 22/02/20—> Searching for SMSClientInstall.* under ‘\MITECO3.test.localadmin$’ | SMS_CLIENT_CONFIG_MANAG—> Unable to connect to remote machine «MITECO3.test.local»
using Kerberos with alternate account—> NTLM fallback is enabled, remote machine «MITECO3.test.local» is continuing with client push. | —> System OS version string «10.0.19044» converted to 10,00 | SMS_CLIENT_CONFIG_MANAGER | —>
Unable to connect to WMI (rootccm) on remote machine «MITECO3.test.local», error = 0x8004100e—> Creating VerifyingCopying existence of destination directory \MITECO3.test.localadmin$ccm—> Copying client files to \MITECO3.test.localadmin$ccmsetup.
| SMS_CLIENT_CONFIG_MANAGER —> Copying file «C:Program FilesMicrosoft Configuration ManagerbinI386MobileClient.tcf» to «M—> Copying file «C:Program FilesMicrosoft Configuration ManagerbinI386ccmsetup.exe» to «ccmse—>
Updated service «ccmsetup» on machine «MITECO3.test.local». | SMS_CLIENT_CONFIG_MANAGER | —> Deleting SMS Client Install Lock File ‘\MITECO3.test.localadmin$SMSClientInstall.MIT’ | SMS_Execute query exec [sp_CP_SetLastErrorCode]
2097152005, 0 | SMS_CLIENT_CONFIG_MANAGER | 22/—> Completed request «2097152005», machine name «MITECO3». | SMS_CLIENT_CONFIG_MANAGER | Deleted request «2097152005», machine name «MITECO3» | SMS_CLIENT_CONFIG_MANAGER
| 22/02/20Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152005, 4 | SMS_CLIENT_CONFIG_MANAGER Execute query exec [sp_CP_SetLatest] 2097152005, N’02/22/2022 12:22:39′, 20 | SMS_CLIENT_CONFIG_MANA<======End request: «2097152005», machine
name: «MITECO3». | SMS_CLIENT_CONFIG_MANAGER | 22

Please help me, I have checked a lot os thing.

An easy way to install SCCM 2012 client on domain machines is the client push installation. You can enable this method from console under Administration->Site Configuration-> Sites->R-Click Site Name-> Client Installation Settings-> Client Push Installation

Or from the ribbon:

You Can then Monitor What’s going on through the following log files:

Server log file:

C:Program FilesMicrosoft Configuration ManagerLogsccm.log

Client log files:

C:WindowsccmsetupLogsccmsetup.log

C:WindowsccmsetupLogsclient.msi.log 

————————————————————————————————-

Last week, i’ve faced the following issue when trying to install the client using this method:

ISSUE:

Clients appear with no agent on console.

Errors:

i got the following errors on logs

ccm.log

Unable to connect to WMI (rootccm) on remote machine “MachineName”, error = 0x8004100e.

Client.msi.log

ERROR: RegisterTaskDefinition failed with error 0x800700b7

CustomAction CcmRegisterWinTask returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Action ended 7:17:39: InstallFinalize. Return value 3.

WARNING: Failed to delete setup in progress time-stamp with error 0x80070002

Solution ‘1’:

Disable the firewall or type in a command prompt with elevated privileges:

netsh firewall set service remoteadmin enable

Solution ‘2’:

1. Use the Start menu to right-click My Computer.

2. Press the Manage item.

3. Double-click Services and Applications in the left-hand pane.

4. Press Services to expand it.

5. Scroll to Windows Management Instrumentation in the right-hand pane and right-click it.

6. Press Stop.

7. Use Windows Explorer to delete all the files in the %SystemRoot%System32WbemRepository folder.

8. and restart your computer.

The Windows Management Instrumentation service will start and the files will be re-created

Note: CCM.log on server reads information from CCMSETUP.log on client. So, to get updated information with updated error codes ‘if found’, you should stop service “SMS Agent Host” on client machine and delete this ccmsetup.log file then try pushing the agent again.

—————————————————————————————–

Thanks

M.Zakaria