TROUBLESHOOTING MISSING ACTION ITEMS IN MECM CLIENT... PROBABILITIES OF SOLUTION
Previous scenario where site code is missing observed device was not having right boundary
Observation: Device will not receiving Site code too.
Previous Video tutorial link: • MECM CLIENT INSTALLATION TROUBLESHOOTING
New scenario is device is having site code but still Action items are missing.
3 logs in client computer gives an idea if client is properly registered & receiving policies.
1. ClientIDManager.log
2. ClientLocation.log
3. LocationServices.log
ClientIDManager we see Client is not registered.
LocationServices we see AD Site info
ClientLocation we see assigned MP
Reviewing logs from MP side: MP_RegistrationManager.log
Located in C:\SMS_CCM\Logs\
Get GUID from Client computer LocationServices
Search GUID in MP_RegistrationManager, here we see similar entry of client not registered
Error Code: 0x87d00238 :: Public key not found
Another Log file: mpfdm.log
C:\SMS\Logs\mpfdm.log
Error reported is 5 i.e. Access Denied
Here it is reporting cannot create file in (path name)
What is mpfdm.log:
It records the actions of the management point component that moves client files to the corresponding INBOXES folder on the site server.
Microsoft doc link: https://docs.microsoft.com/en-us/mem/...
Review permission on given path, enable access if not enough permission.
Monitor on client : ClientIDManagerStartup.log
On Server: mpfdm.log
If permission issue is fixed, Check Action items on MECM Client computer.
OTHER PROBABILITIES OF SOLUTION:
1. Check if device is in provisioning mode:
During an OS deployment task sequence, Configuration Manager places the client in provisioning mode. In this state, the client doesn't process policy from the site. This behavior allows the task sequence to run without risk of additional deployments running on the client. When the task sequence completes, either success or handled failure, it exits client provisioning mode.
If the task sequence unexpectedly fails, the client can be left in provisioning mode. For example, if the device restarts in the middle of task sequence processing, and it's unable to recover. An administrator must manually identify and fix clients in this state.
Powershell Command: Invoke-WmiMethod -Namespace root\CCM -Class SMS_Client -Name SetClientProvisioningMode -ArgumentList $false
Registry check on client computer:
HKLM\Software\Microsoft\CCM\CcmExec
Provisioning Mode is false
Microsoft link : https://docs.microsoft.com/en-us/mem/...
2. Reinstalling Client
3. Restarting SMS Agent Host service
4. Check if Duplicate devices with same hostname present in Console
5. Review SMSCFG.ini located in C:\Windows
----------------------------------------------------------------------------------------------------------------------
Follow Below platforms to get updates:
Blog Website: https://yagneshmalaviya.com/
Twitter : / yagneshmalaviya
LinkedIn : / yagnesh-malaviya
Facebook: / mecmworld
Instagram : / mecm_world
Email ID: [email protected]
If you would like to share your troubleshooting fix or knowledge on MECM, you are most welcome to share your interest in email. Will look forward to collaborate & share knowledge. Thank You :)
Смотрите видео TROUBLESHOOTING MISSING ACTION ITEMS IN MECM CLIENT... PROBABILITIES OF SOLUTION онлайн без регистрации, длительностью часов минут секунд в хорошем качестве. Это видео добавил пользователь MECM WORLD 22 Май 2022, не забудьте поделиться им ссылкой с друзьями и знакомыми, на нашем сайте его посмотрели 5,787 раз и оно понравилось 118 людям.