Site Status components are at least 51 or more than that are available. And here below of some mentioned may need to come as read / warning in your day to day operations SMS_LAN_SENDER SMS_EXECUTIVE SMS_HIERARCHY_MANAGER SMS_DISTRIBUTION_MANAGER SMS_DESPOOLER SMS_DISCOVERY_DATA_MANAGER SMS_INBOX_MANAGER SMS_MP_CONTROL_MANAGER SMS_MP_FILE_DISPATCH_MANAGER SMS_INVENTORY_PROCESSOR SMS_INBOX_MONITOR SMS_INVENTORY_DATA_LOADER SMS_DATABASE_NOTIFICATION_MONITOR SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT SMS_AI_KB_MANAGER SMS_AMT_PROXY_COMPONENT SMS_SITE_SQL_BACKUP_AUPERPSPSS01 SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT SMS_AD_SYSTEM_DISCOVERY_AGENT SMS_COMPONENT_MONITOR SMS_COMPONENT_STATUS_SUMMARIZER SMS_CLIENT_CONFIG_MANAGER SMS_COLLECTION_EVALUATOR SMS_WSUS_CONFIGURATION_MANAGER SMS_WSUS_CONTROL_MANAGER SMS_SOFTWARE_METERING_PROCESSOR SMS_STATE_SYSTEM SMS_STATUS_MANAGER SMS_MP_FILE_DISPATCH_MANAGER SMS_OUTBOX_MONITOR SMS_PXE_SERVICE_POINT SMS_WSUS_SYNC_MANAGER SMS_COMPONENT_MONITOR SMS_EXECUTIVE SMS_SOFTWARE_INVENTORY_PROCESSOR SMS_OUTBOX_MONITOR SMS_POLICY_PROVIDER SMS_REPLICATION_MANAGER SMS_OBJECT_REPLICATION_MANAGER SMS_OFFER_MANAGER SMS_SITE_BACKUP SMS_SITE_COMPONENT_MANAGER And out of the regular ones in my case I am seeing these many times in the hierarchy SMS_LAN_SENDER==================> in the error mentioned site systems are offline or network connectivity problem SMS_DISTRIBUTION_MANAGER========> Targeted packages are not reached the DP or very frequently updated by some one SMS_MP_CONTROL_MANAGER==========> Mpcert http://sccmserverName/sms_mp/.sms_aut?mpcert MPlist http://sccmserverName/sms_mp/.sms_aut?mplist For MP function mpcontrol.log file.. You may get 401,403 or 500 errors mostly with IIS & SQL issues. If you see error 200 that means MP working Fine. clip_image002 Log files location for a server with the sitecode of DC1 clip_image004 SMS_COLLECTION_EVALUATOR========> at this stage we can ignore this error SMS_WSUS_SYNC_MANAGER===========> Solution: – open the wsyncmgr.log file check for errors and do a more sync if required from below given screenshot clip_image006 clip_image008 Sample Error:- SMS WSUS Configuration Manager failed to configure proxy settings on WSUS Server “USDC1PSPSS02”. Possible cause: WSUS Server version 3.0 SP1 and above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP1 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.You can receive failure because proxy is set but proxy name is not specified or proxy server port is invalid. SMS_OUTBOX_MONITOR============> You need to connect to the Configmgr Service Manager and stop the inbox_monitor component and start it same applies to below one. SMS_Inboxe_MONITOR=============> clip_image010 SMS_PXE_SERVICE_POINT===========> Check the WDS Service in Services.msc console if the service is stopped raise a P-4 incident to start the service. MAKE SURE IF THE SERVICE IS IN STARTED STATE AND YOU ARE TRYING TO STOP IT MAY CHANGE THE STATUS TO STOPPING STATUS AND IT NEVER CHANGES IT STATUS TO RUNIING OR STOPPED STATE, AND It will not allow you to even kill the pid The solution is reboot the system (This also happens to SMS executive service also)

 

Leave a Reply

Your email address will not be published. Required fields are marked *