Ccmsetup failed with error code 0x80070642

Ccmsetup failed with error code 0x80070642

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

Asked by:

Question

I’m currently testing CM2012 agent deployment in a lab where we have CM2007 agent is installed.

Currently using push method to do this and it keeps failing with the following in ccmsetup.log:

MSI: Action 13:19:20: CcmStartService. ccmsetup 14/09/2012 13:19:20 2792 (0x0AE8)
MSI: Action 13:19:20: InstallFinalize. ccmsetup 14/09/2012 13:19:20 2792 (0x0AE8)
MSI: Action 13:19:20: InstallInitialize. ccmsetup 14/09/2012 13:19:20 2792 (0x0AE8)
MSI: Action 13:19:20: CcmStopServiceRollback. ccmsetup 14/09/2012 13:19:20 2792 (0x0AE8)
MSI: Action 13:19:20: SmsClientUninstallSucceeded. Sending status message ccmsetup 14/09/2012 13:19:20 2792 (0x0AE8)
MSI: Action 13:19:26: ProcessComponents. Updating component registration ccmsetup 14/09/2012 13:19:26 2792 (0x0AE8)
MSI: Action 13:19:26: UnpublishFeatures. Unpublishing Product Features ccmsetup 14/09/2012 13:19:26 2792 (0x0AE8)
MSI: Action 13:19:26: CcmStopService. ccmsetup 14/09/2012 13:19:26 2792 (0x0AE8)
MSI: Action 13:19:28: StopServices. Stopping services ccmsetup 14/09/2012 13:19:28 2792 (0x0AE8)
MSI: Action 13:19:28: SmsUninstallPrepDrvrAMD64. Uninstalling Software Metering PREP Driver ccmsetup 14/09/2012 13:19:28 2792 (0x0AE8)
MSI: Action 13:19:28: SmsSwDistCacheDirDelete. ccmsetup 14/09/2012 13:19:28 2792 (0x0AE8)
ccmsetup is shutting down ccmsetup 14/09/2012 13:23:53 2868 (0x0B34)
Shutdown has been requested ccmsetup 14/09/2012 13:23:53 2792 (0x0AE8)
Installation will be cancelled due to shutdown. Windows Installer will return error code 1602. ccmsetup 14/09/2012 13:23:53 2792 (0x0AE8)
MSI: Action 13:37:33: SmsStopUIComponents. Stopping UI Components ccmsetup 14/09/2012 13:37:33 2792 (0x0AE8)
Shutdown has been requested ccmsetup 14/09/2012 13:37:33 2792 (0x0AE8)
Installation will be cancelled due to shutdown. Windows Installer will return error code 1602. ccmsetup 14/09/2012 13:37:33 2792 (0x0AE8)
MSI: Action 13:37:33: Rollback. Rolling back action: ccmsetup 14/09/2012 13:37:33 2792 (0x0AE8)
Shutdown has been requested ccmsetup 14/09/2012 13:37:33 2792 (0x0AE8)
Installation will be cancelled due to shutdown. Windows Installer will return error code 1602. ccmsetup 14/09/2012 13:37:33 2792 (0x0AE8)
Installation was cancelled (1602) ccmsetup 14/09/2012 13:37:34 2792 (0x0AE8)
InstallFromManifest failed 0x80070642 ccmsetup 14/09/2012 13:37:34 2792 (0x0AE8)
A Fallback Status Point has not been specified. Message with STATEID=’313′ will not be sent. ccmsetup 14/09/2012 13:37:34 2792 (0x0AE8)
CcmSetup failed with error code 0x80070642 ccmsetup 14/09/2012 13:37:34 2868 (0x0B34)

Источник

System Center Configuration Manager и как с ним бороться

SCCM, Intune, MDT, EMS, MDM, MAM, Azure AD и другие странные слова

проблемы с установкой клиента через Client Push installation

Заметки на полях.

Сейчас провожу внутреннее обучение для коллег в виде курса по SCCM vNext и в нескольких лабораторных инфраструктурах были встречены следующие ошибки:

Failed to send status 309. Error (87D00215)

Failed to download from DP ‘http://SCCMNEXT.firma.com/SMS_DP_SMSPKG$/TP400002’, error 0x800706d9.

Enumerated all 1 DP locations but none of them is good. Fallback to MP.

Failed to download client files by BITS. Error 0x800706d9

Решение проблемы: сделать исключение на фаерволле для BITS (порт TCP 80) или выключить фаерволл, но не останавливать службу Windows Firewall (если это лабораторная среда).

InstallFromManifest failed 0x80070642

Failed to get client version for sending state messages. Error 0x8004100e

Failed to send status 311. Error (87D00215)

Failed to connect to policy namespace. Error 0x8004100e

CcmSetup failed with error code 0x80070642

Решение проблемы: сделать восстановление WMI — открыть %windir%System32WBEM или SysWOW64WBEM и запустить

GetDPLocations failed with error 0x80072ee7

Failed to get DP locations as the expected version from MP ‘SCCM.contoso.com’. Error 0x80072ee7

Failed to get client version for sending state messages. Error 0x8004100e

Решение проблемы: проверить доступность контроллера домена — настройки IP/DNS/etc.

Источник

Ccmsetup failed with error code 0x80070642

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

Answered by:

Question

Running SCCM 2012 SP1 with hotfix 2801987

The client is failing to install during the task sequence process because of a reboot in the middle of it? Can anyone help determine why from the ccmsetup log?

Answers

what does your client.msi.log file tell you ?

Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I’m on Twitter > ncbrady

are you installing the client using any other method ?

what is causing the reboot is it a step in the task sequence or the setup windows and configmgr step ? (which does reboot the computer and is expected)

Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I’m on Twitter > ncbrady

what does your client.msi.log file tell you ?

Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I’m on Twitter > ncbrady

are you installing the client using any other method ?

what is causing the reboot is it a step in the task sequence or the setup windows and configmgr step ? (which does reboot the computer and is expected)

Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I’m on Twitter > ncbrady

Nick Moseley | http://t3chn1ck.wordpress.com

To clarify, are you installing the client hotfix with the PATCH= command line parameter in the Setup Windows and ConfigMgr step? (And thus not installing it as a swd package)

Nick Moseley | http://t3chn1ck.wordpress.com

No, we’re not doing that. Can you explain that a little further?

Also, the worse part about this is it’s intermittent even on the same exact machine.

You can’t patch the SCCM client like that while it’s actively running the task sequence. In the same place where you are also specifying the SMSMP=»server» and the other parameters, you also have to specify client hotfixes in there with the PATCH= command line parameter. which the instructions are typically outlined in the KB for the hotfix. However, in checking the actual patch you’ve specified above, I thought it was a client side hotfix, but it’s only a server hotfix.

At what stage is your task sequence restarting and then halting? Have you checked the SMSTS.log for more details?

Nick Moseley | http://t3chn1ck.wordpress.com

You can’t patch the SCCM client like that while it’s actively running the task sequence. In the same place where you are also specifying the SMSMP=»server» and the other parameters, you also have to specify client hotfixes in there with the PATCH= command line parameter. which the instructions are typically outlined in the KB for the hotfix. However, in checking the actual patch you’ve specified above, I thought it was a client side hotfix, but it’s only a server hotfix.

At what stage is your task sequence restarting and then halting? Have you checked the SMSTS.log for more details?

Nick Moseley | http://t3chn1ck.wordpress.com

To clarify, are you installing the client hotfix with the PATCH= command line parameter in the Setup Windows and ConfigMgr step? (And thus not installing it as a swd package)

Nick Moseley | http://t3chn1ck.wordpress.com

yannara, are you asking about http://support.microsoft.com/kb/2801987? You don’t have to provide a PATCH= statement after having this patch installed. Just update the ConfigMgr client package on DPs.
s10xtremenlow: have you updated the DPs after having the hotfix installed? (The error message does not indicate that you are running into the issue described in kb2801987 though)

• Edited by TorstenM MVP Monday, January 21, 2013 3:55 PM

yannara, are you asking about http://support.microsoft.com/kb/2801987? You don’t have to provide a PATCH= statement after having this patch installed. Just update the ConfigMgr client package on DPs.
s10xtremenlow: have you updated the DPs after having the hotfix installed? (The error message does not indicate that you are running into the issue described in kb2801987 though)

Here are all of the logs. SMSTS.log, client.msi, ccmsetup.log, etc

The task sequence runs action setup windows and config manager and downloads the files. It then reboots into sysprep, runs sysprep and reboots to windows. It gets to installing the configuration manager client and reboots in the middle of it. Comes back into windows and we’re presented with the logon screen. The client re-installs behind the scenes at while its sitting at the logon screen but no other tasks run that are after the client install in the task sequence.

Pulled this from your SMSTS.log and seems to be source of your problem.

Failed to create certificate store from encoded certificate.. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows)

Are you operating in HTTP or HTTPS? Have you followed the guides in http://technet.microsoft.com/en-us/library/gg699362.aspx?

Nick Moseley | http://t3chn1ck.wordpress.com

Pulled this from your SMSTS.log and seems to be source of your problem.

Failed to create certificate store from encoded certificate.. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows)

Are you operating in HTTP or HTTPS? Have you followed the guides in http://technet.microsoft.com/en-us/library/gg699362.aspx?

Nick Moseley | http://t3chn1ck.wordpress.com

I’m operating on both I believe. I’ll look at that guide now. Why would this be intermittent? I’d rather not use HTTPS.

I believe we figured out what was causing it. What’s really frustrating is the logs don’t reference anything to the issue but I happened to find someone else with a similar issue and this was the fix for him too..

For boundaries we were using subnets that we manually entered and they were part of boundary groups. We imported subnets from sites and services of AD and forgot to put those in boundary groups. Once we did that this issue immediately was cleared.

Basically we had:

192.168.5.0/24 — In a boundary group

192.168.5.1-192.168.5.254 — was not in a boundary group. we put this in a boundary group and it immediately started working.

Источник

проблемы с установкой клиента через Client Push installation

02.12.2015, 23:57

FOR /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
Net stop /y winmgmt
FOR /f %s in ('dir /b *.mof *.mfl') do mofcomp %s
Net start winmgmt

SCCM2012 client install issues.

Posted on 12.10.2013 Updated on 15.10.2013

Общая информация:

При push-установке  клиента отследить происходящее можно по следующим логам: ccm.log на сервере с которого будет начинаться установка, ccmsetup.log в папке C:WindowsccmsetupLogs  конечного клиента. В логе ccm на сервере процесс будет выглядеть так

---> Attempting to connect to administrative share '\TESTPCPCadmin$' using account 'MYDOMAINSCCM2012_push'    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:39    1584 (0x0630)
---> The 'best-shot' account has now succeeded 1565 times and failed 905 times.    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:39    1584 (0x0630)
---> Connected to administrative share on machine TESTPCPC using account 'MYDOMAINSCCM2012_push'    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:39    1584 (0x0630)
---> Attempting to make IPC connection to share <\TESTPCPCIPC$>    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:39    1584 (0x0630)
---> Searching for SMSClientInstall.* under '\TESTPCPCadmin$'    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:39    1584 (0x0630)
---> System OS version string "6.1.7601" converted to 6,10    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:39    1584 (0x0630)
---> Unable to connect to WMI (rootccm) on remote machine "TESTPCPC", error = 0x8004100e.    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:39    1584 (0x0630)
---> Creating  VerifyingCopying exsistance of destination directory \TESTPCPCadmin$ccmsetup.    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:39    1584 (0x0630)
---> Copying client files to \TESTPCPCadmin$ccmsetup.    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:39    1584 (0x0630)
---> Copying file "C:Program FilesMicrosoft Configuration ManagerbinI386MobileClient.tcf" to "MobileClient.tcf"    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:39    1584 (0x0630)
---> Copying file "C:Program FilesMicrosoft Configuration ManagerbinI386ccmsetup.exe" to "ccmsetup.exe"    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:40    1584 (0x0630)
---> Created service "ccmsetup" on machine "TESTPCPC".    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:40    1584 (0x0630)
---> Started service "ccmsetup" on machine "TESTPCPC".    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:40    1584 (0x0630)
---> Deleting SMS Client Install Lock File '\TESTPCPCadmin$SMSClientInstall.MSC'    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:40    1584 (0x0630)
Execute query exec [sp_CP_SetLastErrorCode] 2097163290, 0    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:40    1584 (0x0630)
---> Completed request "2097163290", machine name "TESTPCPC".    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:40    1584 (0x0630)
Deleted request "2097163290", machine name "TESTPCPC"    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:40    1584 (0x0630)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097163290, 4    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:40    1584 (0x0630)
Execute query exec [sp_CP_SetLatest] 2097163290, N'05/17/2013 18:36:40', 3    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:40    1584 (0x0630)
<======End request: "2097163290", machine name: "TESTPCPC".    SMS_CLIENT_CONFIG_MANAGER    17.05.2013 22:36:40    1584 (0x0630)

После чего основные события будут разворачиваться уже в логах на клиенте.

1. Client-certificate: None

Установка клиента проходит успешно, но SCCM не видит клиента, и в свойствах клиента отображается Client-certificate: None.

В логе CertificateMaintenance

Creating Signing Certificate...    CertificateMaintenance    17.05.2013 23:46:42    7660 (0x1DEC)
Crypt acquire context failed with 0x8009000f.    CertificateMaintenance    17.05.2013 23:46:42    7660 (0x1DEC)
Failed to create certificate 8009000f    CertificateMaintenance    17.05.2013 23:46:42    7660 (0x1DEC)
CCMDoCertificateMaintenance() failed (0x8009000f).    CertificateMaintenance    17.05.2013 23:46:42    7660 (0x1DEC)
Raising pending event:
instance of CCM_ServiceHost_CertificateOperationsFailure
{
DateTime = "20130517194642.959000+000";
HRESULT = "0x8009000f";
ProcessID = 9376;
ThreadID = 7660;
};
CertificateMaintenance    17.05.2013 23:46:42    7660 (0x1DEC)
CCMDoCertificateMaintenance() raised CCM_ServiceHost_CertificateOperationsFailure status event.    CertificateMaintenance    17.05.2013 23:46:42    7660 (0x1DEC)

Решение: Необходимо удалить из папки C:UsersAll UsersMicrosoftCryptoRSAMachineKeys ключ, начинающийся с 19c5cf… после чего перезагрузить сервер.

2. Ошибка — не найден класс WMI

CCM.log ругается на отсутствие классов WMI на клиенте.  Установка клиента может падать с кодом ошибки 0x80004004.  Проверяем работу WMI стандартной утилитой wbemtest. Пробуем найти тот класс на который ругается SCCM через Enum Classes — Recursive. Если его нет, и вообще количество классов WMI много меньше чем на рабочем ПК, значит тут проблемы с WMI, и необходимо будет воспользоваться статьей от MS и пересоздать репозиторий WMI. (Может негативно сказаться на работоспособности стороннего ПО) — http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.asp Вот скрипт из этой статьи:

sc config winmgmt start= disabled
net stop winmgmt /y
%systemdrive%
cd %windir%system32wbem
for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s
wmiprvse /regserver
winmgmt /regserver
sc config winmgmt start= auto
net start winmgmt
for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s

3. Неверный код сайта

В случае если клиенту был присвоен неверный код сайта (это может произойти например при миграции с 2007). При этом зачастую в консоли клиент отображается как Inactive. порядок действий следующий

1. Качаем и устанавливаем http://psrightclicktools.codeplex.com/
2. В консоли появится дополнительное меню, доступное по правой кнопке мыши.
3. Client Tools — Assign Client To Another Site  — присваиваем правильный сайт, дожидаемся окна с оповещением что присвоен успешно
4. Client Tools — Restart SMS Host agent Service  — дожидаемся окна с оповещением
5. Client Actions — Discovery Data Collection  & Hardvare Inventory Cycle

Через минут 15  — 20 клиент должен стать активным.

4. 5.0.7804.1000 Deployment Error 0x80070642. Pre-req: MicrosoftPolicyPlatformSetup.msi

Установка заканчивается ошибкой

File C:WINDOWSccmsetupMicrosoftPolicyPlatformSetup.msi installation was cancelled (1602)    ccmsetup
InstallFromManifest failed 0x80070642    ccmsetup
Sending Fallback Status Point message to 'SMR-CM12', STATEID='311'.    ccmsetup
Failed to get client version for sending messages to FSP. Error 0x8004100e    ccmsetup
Params to send FSP message '5.0.7804.1000 Deployment Error 0x80070642. Pre-req: MicrosoftPolicyPlatformSetup.msi'    ccmsetup
State message with TopicType 800 and TopicId {2479B1BC-7D0B-421D-82DE-DB3A2AAAD306} has been sent to the FSP    FSPStateMessage
CcmSetup failed with error code 0x80070642    ccmsetup

Как видно из ошибки — не прохоидт установка необходимого для клиента SCCM MicrosoftPolicyPlatformSetup.msi. Обсуждение данной проблемы тут: http://social.technet.microsoft.com/Forums/en-US/configmanagerdeployment/thread/a73233ab-0f9e-4304-ae2f-1a8aa92619b6

Выпущено исправление KB2801987 Однако есть и ручной Workaround — принудительная установка компоненты с отключением перезагрузки:

msiexec /i c:windowsccmsetupMicrosoftPolicySetup.msi /l* c:windowsmpps.log REBOOT=ReallySupress

5. MSI: Setup was unable to create the WMI namespace CCMSoftwareMeteringAgent  The error code is 8004100F

В логе установки на клиенте ошибки типа

MSI: Setup was unable to create the WMI namespace CCMSoftwareMeteringAgent
The error code is 8004100F    ccmsetup
MSI: Действие 17<:20:44: Rollback. Откат действия:    ccmsetup
File C:Windowsccmsetup{1AF71F68-6089-4211-ADDC-06DF40606141}client.msi installation failed. Error text: ExitCode: 1603
Action: CcmCreateWmiNamespaces.
ErrorMessages:
Setup was unable to create the WMI namespace CCMSoftwareMeteringAgent
The error code is 8004100F
ccmsetup   0x0B14
Next retry in 120 minute(s)...

Это снова проблемы с WMI на клиенте. Необходимо пересоздать репозиторий WMI
1. Останавливаем службу «Инструментарий управления Windows» и все зависимые службы
2. %WinDir%System32WbemRepository — переименовываем данную папку
3. Запускаем службу
4. Устанавливаем клиента SCCM любыми доступными методами

System Center Configuration Manager и как с ним бороться

SCCM, Intune, MDT, EMS, MDM, MAM, Azure AD и другие странные слова

Archive for Декабрь 2015

новые обучающие материалы

Курсы на Microsoft Virtual Academy:

Вчера вышла новая версия MDT — Microsoft Deployment Toolkit (MDT) 2013 Update 2. Очень серьёзных изменения программа не претерпела, а небольшие изменения описаны в блоге разработчиков Aaron Czechowski, из рук которого мы получили предварительную версию (MDT) 2013 Update 2 ещё в начале ноября. 🙂

Обновление 1512 для System Center Configuration Manager Technical Preview

Сегодня вышло обновление 1512 для System Center Configuration Manager TP4, которое вы можете протестировать на своих лабораторных стендах:

• поддержка Windows 10 Device Health Attestation;
• просмотр списка пользователей из консоли ConfigMgr, которые приняли лицензионное соглашение (при условии интеграции с Microsoft Intune).

Подробнее можно прочитать в блоге разработчиков.

System Center Configuration Manager версия 1511

Итак, сегодня System Center Configuration Manager 1511 стал доступен для всех. Каждый может скачать новую версию System Center Configuration Manager и использовать триальную версию 180 дней. Кроме того, ConfigMgr доступен на сайтах MSDN и VLSC.

System Center Configuration Manager 1511

Итак, новая версия System Center Configuration Manager — 1511 — готова к скачиванию и установке! Свершилось! Никаких больше Technical Preview! 🙂

На данный момент скачать могут только обладатели подписки MSDN.

Пришла пора браться за серию видеоуроков по новой версии SCCM.

проблемы с установкой клиента через Client Push installation

Заметки на полях.

Сейчас провожу внутреннее обучение для коллег в виде курса по SCCM vNext и в нескольких лабораторных инфраструктурах были встречены следующие ошибки:

Failed to send status 309. Error (87D00215)

Failed to download from DP ‘http://SCCMNEXT.firma.com/SMS_DP_SMSPKG$/TP400002’, error 0x800706d9.

Enumerated all 1 DP locations but none of them is good. Fallback to MP.

Failed to download client files by BITS. Error 0x800706d9

Решение проблемы: сделать исключение на фаерволле для BITS (порт TCP 80) или выключить фаерволл, но не останавливать службу Windows Firewall (если это лабораторная среда).

InstallFromManifest failed 0x80070642

Failed to get client version for sending state messages. Error 0x8004100e

Failed to send status 311. Error (87D00215)

Failed to connect to policy namespace. Error 0x8004100e

CcmSetup failed with error code 0x80070642

Решение проблемы: сделать восстановление WMI — открыть %windir%System32WBEM или SysWOW64WBEM и запустить

GetDPLocations failed with error 0x80072ee7

Failed to get DP locations as the expected version from MP ‘SCCM.contoso.com’. Error 0x80072ee7

Failed to get client version for sending state messages. Error 0x8004100e

Решение проблемы: проверить доступность контроллера домена — настройки IP/DNS/etc.

ошибка точки управления — Call to HttpSendRequestSync failed for port 80 with status code 500

При установке клиента встретилась ошибка в ccmsetup.log:

Failed to receive ccm message response. Status code = 500

GetDPLocations failed with error 0x80004005

Failed to get DP locations as the expected version from MP ‘http://SCCMNEXT.firma.com’. Error 0x80004005

Failed to find DP locations from MP ‘http://SCCMNEXT.firma.com’ with error 0x80004005, status code 500. Check next MP.

Проблема с точкой управления, которая повторяется каждые 30 секунд, видна в mpcontrol.log:

Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error

Проблема была найдена и заключалась в том, что на сайт-сервере был удалён WSUS, но сайт WSUS Administration остался в IIS. При открытии http://sccmnext.firma.com/sms_mp/.sms_aut?MPlist и http://sccmnext.firma.com/sms_mp/.sms_aut?MPcert была ошибка HTTP 500.19, error code 0x8007007e. Решение было найдено здесь.

Я удалил сайт WSUS Administration и отключил компрессию XPress в WSUS при помощи

Источник

slblogspot

made for memorize

SCCM2012 client install issues.

При push-установке клиента отследить происходящее можно по следующим логам: ccm.log на сервере с которого будет начинаться установка, ccmsetup.log в папке C:WindowsccmsetupLogs конечного клиента. В логе ccm на сервере процесс будет выглядеть так

После чего основные события будут разворачиваться уже в логах на клиенте.

1. Client-certificate: None

Установка клиента проходит успешно, но SCCM не видит клиента, и в свойствах клиента отображается Client-certificate: None.

В логе CertificateMaintenance

Решение: Необходимо удалить из папки C:UsersAll UsersMicrosoftCryptoRSAMachineKeys ключ, начинающийся с 19c5cf… после чего перезагрузить сервер.

2. Ошибка — не найден класс WMI

CCM.log ругается на отсутствие классов WMI на клиенте. Установка клиента может падать с кодом ошибки 0x80004004. Проверяем работу WMI стандартной утилитой wbemtest. Пробуем найти тот класс на который ругается SCCM через Enum Classes — Recursive. Если его нет, и вообще количество классов WMI много меньше чем на рабочем ПК, значит тут проблемы с WMI, и необходимо будет воспользоваться статьей от MS и пересоздать репозиторий WMI. (Может негативно сказаться на работоспособности стороннего ПО) — http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.asp Вот скрипт из этой статьи:

3. Неверный код сайта

В случае если клиенту был присвоен неверный код сайта (это может произойти например при миграции с 2007). При этом зачастую в консоли клиент отображается как Inactive. порядок действий следующий

1. Качаем и устанавливаем http://psrightclicktools.codeplex.com/
2. В консоли появится дополнительное меню, доступное по правой кнопке мыши.
3. Client Tools — Assign Client To Another Site — присваиваем правильный сайт, дожидаемся окна с оповещением что присвоен успешно
4. Client Tools — Restart SMS Host agent Service — дожидаемся окна с оповещением
5. Client Actions — Discovery Data Collection & Hardvare Inventory Cycle

Через минут 15 — 20 клиент должен стать активным.

4. 5.0.7804.1000 Deployment Error 0x80070642. Pre-req: MicrosoftPolicyPlatformSetup.msi

Установка заканчивается ошибкой

Как видно из ошибки — не прохоидт установка необходимого для клиента SCCM MicrosoftPolicyPlatformSetup.msi. Обсуждение данной проблемы тут: http://social.technet.microsoft.com/Forums/en-US/configmanagerdeployment/thread/a73233ab-0f9e-4304-ae2f-1a8aa92619b6

Выпущено исправление KB2801987 Однако есть и ручной Workaround — принудительная установка компоненты с отключением перезагрузки:

5. MSI: Setup was unable to create the WMI namespace CCMSoftwareMeteringAgent The error code is 8004100F

В логе установки на клиенте ошибки типа

Это снова проблемы с WMI на клиенте. Необходимо пересоздать репозиторий WMI
1. Останавливаем службу «Инструментарий управления Windows» и все зависимые службы
2. %WinDir%System32WbemRepository — переименовываем данную папку
3. Запускаем службу
4. Устанавливаем клиента SCCM любыми доступными методами

Понравилось это:

Похожее

This entry was posted in SCCM and tagged SCCM2012.

2 ответ. на » SCCM2012 client install issues. «

Здравствуйте! Являюсь системным администратором одной из крупных организаций. Из главного офиса в Москве поступило распоряжение ставить sccm на все машины. SCCM ставим скриптом. Но вот какая ситуация, на ПК закупленные в последние годы SCCM ставится без проблем. На ПК 2007 года+ ещё пару посвежее никак не получается поставить. Лог.
———
File C:WINDOWSccmsetup<8971b736-fb0a-4d07-ae81-82d40bbcd630>client.msi installation failed. Error text: ExitCode: 1603
Action: CcmRegisterWmiMofFile.
ErrorMessages:
Setup was unable to compile the file SmsClient.mof
The error code is 8004100E
———-

Интересно, что у всех одна ошибка. Обовил систему, пересоздавал wmi, с BITS вроде тоже всё в порядке, сбросил все службы в дефолт, скриптом установил разрешения на запись в реестр, как в новой системе. Все эти системы ранее администрировал другой админ. Может где чего отключил, или ещё чего? Или с правами какими-то намудрено? Заметил, в системах 2 адмиистратора- «Администратор», и «333». Пробовал и под одним, и под другим. Может вы сталкивались с подобным? Вобщем, буду признателен за любую помощь. Ведь переустановка системы, как мне предложили в гл. офисе- это не хороший вариант. Во-первых, машин много, а, во-вторых, куча спец софта, многое уже и не восстановить.

Источник

The Blog

Consulting Services

As an SCCM administrator, it’s important to learn the concept of troubleshooting a Configuration Manager client installation. By targeting the SCCM client installation error codes, you will have a better idea of what is happening during client installation. The error codes are not an exact science, they can defer depending on the situation. For a better understanding of ccmsetup error codes, read this great post from Jason Sandys.

Client installation troubleshooting is probably your first challenge after an SCCM Installation. A better SCCM client installation rate equals better overall management. You want your SCCM non-client count to be as low as possible.

These error codes appear in ccmsetup logs, located on the target machine – C:windowsccmsetuplogs. During the SCCM client installation process, monitor the ccmsetup.log using cmtrace.exe and locate each error code.

There are other logs, to which the SCCM client installation relates. If you don’t find enough information in the ccmsetup.log, scan all related log files in c:windowsccmlogs . Use the command line net helpmsg, for more information about your return error code.

SCCM Console

You can also add the Last Installation Error column in the SCCM console:

• Open the SCCM console and navigate to Assets and Compliance / Devices
• In the devices view, right-click on the header and select Last Installation Error

There are chances that the last error code returns an empty value for a device. Important to understand: an SCCM Client error code of “” is a success.

SCCM Client Installation Error Codes

This post from Technet Forums (Thanks to Charlie Hawkins), has inspired us to prepare a list of all error codes, that can happen during the SCCM client installation. Some errors have been added based on our personal experiences.

Feel free to send us any new error codes, this list will be updated based on your comments.

Don’t forget to put emphasis on the prerequisites of the SCCM client, this will increase your success percentage during client installation. You can also check the list of client commands list, as additional help for troubleshooting your SCCM clients.

SCCM Client Installation Error CodesReporting

Knowing the client installation status from reports reduces the number of devices without SCCM client installed in your IT infrastructure. It also increases your effectiveness, when it’s time to tackle all unhealthy clients.

One of our custom SSRS reports is made especially for the Configuration Manager Client. This report now shows the last SCCM client installation error codes, including the description of the installation deployment state. This report will help you achieve the *near* 100% client installation, that your project manager loves to see.

Источник

Prajwal Desai is a Microsoft MVP in Enterprise Mobility. He writes articles on SCCM, Intune, Configuration Manager, Microsoft Intune, Azure, Windows Server, Windows 11, WordPress and other topics, with the goal of providing people with useful information.

As an SCCM administrator, it’s important to learn the concept of troubleshooting a Configuration Manager client installation. By targeting the SCCM client installation error codes, you will have a better idea of what is happening during client installation. The error codes are not an exact science, they can defer depending on the situation. For a better understanding of ccmsetup error codes, read this great post from Jason Sandys.

Client installation troubleshooting is probably your first challenge after an SCCM Installation. A better SCCM client installation rate equals better overall management. You want your SCCM non-client count to be as low as possible.

These error codes appear in ccmsetup logs, located on the target machine – C:windowsccmsetuplogs. During the SCCM client installation process, monitor the ccmsetup.log using cmtrace.exe and locate each error code.

There are other logs, to which the SCCM client installation relates. If you don’t find enough information in the ccmsetup.log, scan all related log files in c:windowsccmlogs. Use the command line net helpmsg, for more information about your return error code.

SCCM Console

You can also add the Last Installation Error column in the SCCM console:

• Open the SCCM console and navigate to Assets and Compliance / Devices
• In the devices view, right-click on the header and select Last Installation Error

There are chances that the last error code returns an empty value for a device. Important to understand: an SCCM Client error code of “0” is a success.

This post from Technet Forums (Thanks to Charlie Hawkins), has inspired us to prepare a list of all error codes, that can happen during the SCCM client installation. Some errors have been added based on our personal experiences.

Feel free to send us any new error codes, this list will be updated based on your comments.

Don’t forget to put emphasis on the prerequisites of the SCCM client, this will increase your success percentage during client installation. You can also check the list of client commands list, as additional help for troubleshooting your SCCM clients.

SCCM Client Installation Error CodesReporting

Knowing the client installation status from reports reduces the number of devices without SCCM client installed in your IT infrastructure. It also increases your effectiveness, when it’s time to tackle all unhealthy clients.

One of our custom SSRS reports is made especially for the Configuration Manager Client. This report now shows the last SCCM client installation error codes, including the description of the installation deployment state. This report will help you achieve the *near* 100% client installation, that your project manager loves to see.

Environment

• WiX 3.10.2
• Visual Studio 12.0
• Windows 7, 8, 10

I create a MSI and include it in a Bootstrapper
to create an exe file with multi languages (package per user using «HKCU» property).

For each user, the package is installed in «C:Users${username}AppDatalocal${installed_directory}».

The error 0x80070642 has been reported during performing a package ‘repair’ with the following scenario:

Log as ‘user1’

• Install package (pkg windows user) -> OK

Log as ‘user2’

• Install same package -> OK

Log as ‘user1’

• Uninstall package -> OK

Log as ‘user2’

• Repair package -> Setup failed with the error 0x80070642
• Uninstall package -> OK
• Install package -> OK
• Repair package -> OK
• Uninstall package -> OK

Product.wxs used:

<?xml version="1.0" encoding="UTF-8"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"  xmlns:bal="http://schemas.microsoft.com/wix/BalExtension" >

    <!-- =================================================================== -->
    <!-- PRODUCT -->
    <!-- Main definitions -->
    <!-- =================================================================== -->

    <Product Id="$(Some_GUID)" UpgradeCode="$(UpgradeCode)"
             Name="$(ProductName)" Manufacturer="$(Manufacturer)" Language="1033" Version="2.1.3">
        <!-- Required definitions -->

        <Package InstallerVersion="200" Compressed="yes" InstallScope="perUser" InstallPrivileges="limited" ReadOnly="yes" />

        <MajorUpgrade AllowSameVersionUpgrades="yes" DowngradeErrorMessage="A newer version of [ProductName] is already installed." />
        <MediaTemplate EmbedCab="yes" />

        <Feature Id="ProductFeature" Title="Installer" Level="1">
            <ComponentGroupRef Id="ProductComponents" />
            <ComponentRef Id="RegistryEntries" />
        </Feature>

        <Property Id="LOGVERBOSE" Value="1"/>

        <!-- Icon specification -->

        <Icon Id="icon.ico" SourceFile="icon.ico"/>
        <Property Id="ARPPRODUCTICON" Value="icon.ico" />

        <!-- UI definition + action to run the monitor at the end -->

        <WixVariable Id="WixUIBannerBmp" Value="banner-top.bmp" />
        <WixVariable Id="WixUIDialogBmp" Value="banner-dialog.bmp" />
        <WixVariable Id="WixUILicenseRtf" Value="license.rtf" />

        <CustomAction Id="RunApp"
                      Directory="APPFOLDER"
                      ExeCommand="[APPFOLDER]application.exe"
                      Execute="immediate"
                      Impersonate="yes"
                      Return="asyncNoWait"/>

        <!-- Uninstall sequence -->

        <Binary Id='CustomAction' SourceFile='..SomeCustomActionbinReleaseSomeCustomAction.dll'/>
        <CustomAction Id='KillProcesses' BinaryKey='CustomAction' DllEntry='KillProcesses' Execute='immediate' Return='check'/>

        <InstallExecuteSequence>
            <Custom Action="RunApp" After="InstallFinalize">NOT Installed OR REINSTALL</Custom>
            <Custom Action="KillProcesses" Before="InstallValidate">1</Custom>
        </InstallExecuteSequence>
    </Product>


    <!-- =================================================================== -->
    <!-- REGISTRY KEYS -->
    <!-- Used to run the monitor at startup -->
    <!-- =================================================================== -->

    <Fragment>
        <DirectoryRef Id="TARGETDIR">
            <Component Id="RegistryEntries" Guid="$(Some_GUID)">
                <RegistryKey Root="HKCU"
                             Key="SoftwareMicrosoftWindowsCurrentVersionRun">
                    <RegistryValue Type="string" Name="SomeFolder" Value="&quot;[APPFOLDER]application.exe&quot;"/>
                </RegistryKey>
            </Component>
        </DirectoryRef>
    </Fragment>

    <!-- =================================================================== -->
    <!-- COMPONENTS -->
    <!-- Definition of the different files to install -->
    <!-- =================================================================== -->

    <Fragment>
        <Directory Id="TARGETDIR" Name="SourceDir">
            <Directory Id="LocalAppDataFolder">
                <Directory Id="INSTALLFOLDER" Name="Manufacturer">
                    <Directory Id="APPFOLDER" Name="ProductName" />
                </Directory>
            </Directory>
        </Directory>
    </Fragment>

    <Fragment>
        <ComponentGroup Id="ProductComponents" Directory="APPFOLDER">
            <!-- RemoveFolder tags are required to avoid compilation errors -->

            <Component Id="RemoveFolders" Guid="$(Some_GUID)">
                <RemoveFolder Id="APPFOLDER" Directory="APPFOLDER" On="uninstall"/>
                <RemoveFolder Id="INSTALLFOLDER" Directory="INSTALLFOLDER" On="uninstall"/>
                <RemoveFile Id="PurgeAppFolder" Name="config.conf"  On="uninstall"/>
                <RegistryKey Root="HKCU" Key="SoftwareManufacturerProductNameUninstall">
                    <RegistryValue Name="InstallFolder" Value="[APPFOLDER]" Type="string" KeyPath="yes" />
                </RegistryKey>
            </Component>

            <!-- Next are the files to install. Each file must have a registry
            key associated to avoid a compilation error. -->

          <Component Id="id1" Guid="$(Some_GUID)">
            <File Source="datainstall3rdparty-license.txt" />
            <RegistryKey Root="HKCU" Key="SoftwareManufacturerProductNameUninstall">
              <RegistryValue Name="InstallFolder" Value="[APPFOLDER]" Type="string" KeyPath="yes" />
            </RegistryKey>
          </Component>

          <Component Id="id2" Guid="$(Some_GUID)">
            <File Source="datainstallReleaseapplication.exe" />
            <RegistryKey Root="HKCU" Key="SoftwareManufacturerProductNameUninstall">
              <RegistryValue Name="InstallFolder" Value="[APPFOLDER]" Type="string" KeyPath="yes" />
            </RegistryKey>
          </Component>

    </Fragment>

</Wix>

Bundle.wxs used:

<?xml version="1.0" encoding="UTF-8"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:bal="http://schemas.microsoft.com/wix/BalExtension"  xmlns:util="http://schemas.microsoft.com/wix/UtilExtension">

  <Bundle Name="$(ProductName)" Version="$(ProductVersion)" Manufacturer="$(Manufacturer)" UpgradeCode="$(UpgradeCode)">

    <WixVariable Id="WixStdbaThemeXml" Value="layoutlayout.xml"/>

    <BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.RtfLicense">
        <bal:WixStandardBootstrapperApplication LogoFile="layoutWelcome.png" LicenseFile="resources1033licence.rtf" SuppressOptionsUI="yes" />

        <Payload Compressed="yes" Id="thm-de-DE" Name="1031thm.wxl" SourceFile="resources1031thm.wxl" />
        <Payload Compressed="yes" Id="thm-en-US" Name="1033thm.wxl" SourceFile="resources1033thm.wxl" />
        <Payload Compressed="yes" Id="thm-fr-FR" Name="1036thm.wxl" SourceFile="resources1036thm.wxl" />
        <Payload Compressed="yes" Id="thm-nl-NL" Name="1043thm.wxl" SourceFile="resources1043thm.wxl" />

        <Payload Compressed="yes" Id="lic-de-DE" Name="1031license.rtf" SourceFile="resources1031licence.rtf" />
        <Payload Compressed="yes" Id="lic-en-US" Name="1033license.rtf" SourceFile="resources1033licence.rtf" />
        <Payload Compressed="yes" Id="lic-fr-FR" Name="1036license.rtf" SourceFile="resources1036licence.rtf" />
        <Payload Compressed="yes" Id="lic-nl-NL" Name="1043license.rtf" SourceFile="resources1043licence.rtf" />
    </BootstrapperApplicationRef>

    <Chain>
      <MsiPackage DisplayInternalUI="no" Id="Setup" Compressed="yes" SourceFile="resourcesrelease$(MsiName)" Permanent="no" Vital="yes">
      </MsiPackage>

    </Chain>
  </Bundle>

</Wix>