Post install SP1 of SCCM 2012, as usual typical
admin task was to check all components logs to find how was site doing. To my
surprise there are few logs that weren’t observed in any of previous version of
SMS or SCCM. Going through these logs dint reveal much info on what they are
all about, but could see it is a new role installed thru and by SCCM only (rolesetup.exe
/install /siteserver:MYSERVER SMSBGB 0) .
16-01-2013 17:13 310,868 bgbisapiMSI.log.LastError
16-01-2013 21:38 955,927 bgbmgr.log
16-01-2013 12:12 2,621,583 bgbmgr.lo_
16-01-2013 21:34 55,694 BgbServer.log
16-01-2013 18:14 318,539 BgbSetup.log
Ok, I took longer breaths to calm down and to simplify my search with log snippets, msi names etc and finally cracked it……and would like to share with you that this is the new game changing component introduced for the first time in SMS/SCCM versions with SCCM 2012 SP1, that allow us to push notifications (policies as we know them) to SCCM Client with objective of assigning them immediate actions to perform , instead of waiting till its policy interval usually, such push may help fasten tasks like OOB patch etc. This new feature called “Client Notification” is interesting compared to Pull mechanism that SMS/SCCM clients use traditionally and comprises of Notification Server, Notification Manager (on Server) and Notification agent (on Client) components to function. More info and credits to Randy XU’s blog below. Also write up on Client Notification by Randy is one the best articles that I have seen for its quality despite being quantitative. BTW, I still need to explore this feature and will share more from the floor when I do so
C:\Program Files\Microsoft Configuration
Manager\Logs>dir *bgb*
16-01-2013
18:14 325,900
bgbisapiMSI.log16-01-2013 17:13 310,868 bgbisapiMSI.log.LastError
16-01-2013 21:38 955,927 bgbmgr.log
16-01-2013 12:12 2,621,583 bgbmgr.lo_
16-01-2013 21:34 55,694 BgbServer.log
16-01-2013 18:14 318,539 BgbSetup.log
I could see from snippet of logs mentioning install
of BGB components hence I did try to install it those msi ("C:\Program
Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi) myself, hoping I
will get clue on these app/program, but it started a program with “BGB http
Proxy” which I have never heard, guess so is Google. I quit that program as
safety measure, please don’t tell anyone J
Ok, I took longer breaths to calm down and to simplify my search with log snippets, msi names etc and finally cracked it……and would like to share with you that this is the new game changing component introduced for the first time in SMS/SCCM versions with SCCM 2012 SP1, that allow us to push notifications (policies as we know them) to SCCM Client with objective of assigning them immediate actions to perform , instead of waiting till its policy interval usually, such push may help fasten tasks like OOB patch etc. This new feature called “Client Notification” is interesting compared to Pull mechanism that SMS/SCCM clients use traditionally and comprises of Notification Server, Notification Manager (on Server) and Notification agent (on Client) components to function. More info and credits to Randy XU’s blog below. Also write up on Client Notification by Randy is one the best articles that I have seen for its quality despite being quantitative. BTW, I still need to explore this feature and will share more from the floor when I do so
--- Thanks, Vasu Miriyala
1455 days later: Fast Channel Notification
ReplyDeletehttps://blogs.technet.microsoft.com/scotts-it-blog/2014/09/29/incorrect-deployment-of-database-replica-in-sccm-2012-may-cause-client-fast-channel-notification-problems/