[SCCM] Failed to resend previous report as an FSP message (CCMEval)

 Failed to resend previous report as an FSP

[Explanation]

Previous report failed to send as a state message. Attempting to send as an FSP message. CcmEval 8/30/2017 4:56:30 AM 27260 (0x6A7C)
Failed to resend previous report as an FSP message. CcmEval 8/30/2017 4:56:30 AM 27260 (0x6A7C)
Previous send is not complete, need to send report this time. CcmEval 8/30/2017 4:56:30 AM 27260 (0x6A7C)

SCCM Client 평가로그인 ccmeval.log 에서 발생한 메시지로, 확인결과, SCCM SP1으로 업그레이드를 하면서 'Windows Management Framework 3.0'와의 호환성 문제로 발생한 메시지라고 한다. 하지만 아래 링크처럼 SP1에서 발생하지 않는 부분이라고 하는데.. 그렇다면 업그레이드되지 않은 Client 때문일 수도 있을 것 같다. 자세한 해결 방법은 아래 링크를 확인하면 된다. 링크

♔♔♔♔♔♔♔♔♔♔

[Cause]

This issue may occur if Windows Management Framework 3.0 (described in KB 2506143) has been installed in your System Center 2012 Configuration Manager RTM environment. The System Center 2012 Configuration Manager RTM client is incompatible with Windows Management Framework 3.0. During the daily Client Health evaluation, CCMEval.exe mistakenly finds the WMI repository to be corrupted. Therefore, CCMEval.exe requests a rebuild and then reinstalls the client. The rebuild of the repository by CCMEval causes loss of management point-specific information, methods, and more from WMI. This causes the management point to fail.
System Center 2012 Configuration Manager Service Pack 1 (SP1) provides official support for Windows Management Framework 3.0. Therefore, System Center 2012 Configuration Manager SP1 is not affected by this issue.

[Resolution] 

To resolve this issue, apply System Center 2012 Configuration Manager SP1 to your environment. For System Center 2012 Configuration Manager RTM environments, you can work around the issue by setting the following registry value to True on the affected clients:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmEval\NotifyOnly

When this registry value is set to True, the client still runs the evaluation task daily and then incorrectly reports that the WMI repository is corrupted. However, it does not request the repository rebuild or the daily client reinstallation.

If the management point is already failing because of the evaluation that is being run, you must uninstall and then reinstall the management point to make sure that it is back online. To do this, follow these steps: Reinstall MP role

• Under Servers and Site System Roles, select the server that is hosting the failing management point. 
• Right-click the Management Point role, and then select Remove Role.
• Monitor the MPSetup.log on the Management Point server to make sure that the removal is complete. 
• Right-click the same server, and then select Add Site System Roles.
• In the wizard, select the Management Point role, and then monitor the MPSetup.log on the Management Point server to make sure that the reinstallation is complete.

댓글이나 의견은 언제든지 환영합니다.

Your Comments are Always Welcome!