SCCM Site Component Status not updating
we are in the middle of production deployment of SCCM infrastrucure. the infrastrucure is designed as below. ---Central Site -----Primary Site x 4 (one for each region) ---------Secondary Site (secondary site reporting to primary site in its region) so far we have deployed central site, 2 primary site and 20 secondary site server. Central site and Primary Site is virtual machines. all sites were in healthy state till yesterday. Server infrastrucure had organized an outage to upgrade the hardware on ESX server where SCCM central and Primary servers are hosted which didnt go according to plan and Central and two primary were shutdown prematurely. the servers were back up in couple of hours time and rebooted. since then all the secondary sites under both primary site server have error on their LAN senders component stating that it couldnt connect to Primary site XXX at specified time. that is fine as the primary sites were down during that period but the component status has not updated since. i have checked the sender.log and replmgr.log and there is no errors in the log. shows successfully sent data to site XXX since the site is up. why the site status is not updating automatically? to test if the data is flowing up from secondary site to primary site i manually stopped WDS service on one of the secondary site to see if the componenet status gets updated on Primary site. checked below files on secondary site to see if Status message gets generated and sent to Primary site XXX - statmgr.log - replmgr.log - schedule.log -sender.log all goes through ok without any issues. checked the replmgr.log, schedule.log and statmgr.log on primary site and can see data being received from secondary site. i needed to wait about two hours and then component status got updated after 2 hours to error state. is it normal? there is 10 MBPS link between primary and secondary site. it is weekend and link is hardly utilized. one of the secondary site is completely down at the moment (server turned off) and site status shows all ok on Primary site. i feel something has went wrong during premature shtudown of SCCM VM's. any help on this issue will be greatly appreciated. let me know if you need more info. thanks. Jay
June 18th, 2011 8:32am

there is no backlog in CompSumm.Box Yes status message filtering is enabled.Jay
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2011 12:54pm

all sites are running config manger R3 i have applied hotfix 982399 as sccm services were stopping randomly on primary site server after back up runs. i havent applied hotfix 981640 as it is not applicable in my instance. we are not using any third party VSS provider. i have learnt that LAN_Senders status will remain in error or warning state until the next threshold period kicks in (generally 12 AM everyday) so if the component is back to its normal health it will still remain in warning state until next threshold period kicks in. in normal scenario you would expect component status to update to green automatically when the error is resolved but you have to wait until next threhold period. but still two questions remains unanswered. 1. when the WDS service is disabled why it takes about 2 Hrs for the component status to get updated to warning status? may be there is some setting to change component status schedule that i need to update and i am not aware about? 2. one of the secondary site is completely turned off (since last 2 days) for maintenance why the site status shows as Green and no errors? thanks. Jay
June 19th, 2011 5:41am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics