Lab Geek

(Originally posted 3/12/2014. Reposting for reference)   Issue: Upon installing a new ConfigMgr 2012 R2 site, the component status for the SMS_NOTIFICATION_SERVER component shows the following error: Site Component Manager failed to install this component, because the Microsoft Installer File for this component (bgbisapi.msi) could not install. Refer to the BgbSetup.log, the bgbisapimsi.log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information. Upon examining the BgbSetup.log file, the following errors are seen:  CTool::RegisterComPlusService: Failed to…

Read More Read More

(Originally posted 12/16/2013. Reposting for reference) A situation developed recently where a client help desk was being hammered with calls during a rollout from users who were seeing the system tray popup notifications telling them that a new application was available from ConfigMgr.  As this behavior was not expected (end user notifications being considered very disruptive), the question became which applications were generating this prompt.  Against calls to disable ALL notifications for new software in the Client Settings policy, we instead…

Read More Read More

(Originally posted 10/1/2013. Reposting for reference) Microsoft System Center 2012 Configuration Manager includes built-in migration tools, and one of the key features of the migration tools is the ability to use Shared Distribution Points.  This allows for a smoother transition between environments by allowing the new ConfigMgr 2012 site to use existing Distribution Points in the old site (ConfigMgr 2012 or SCCM 2007) as content locations while clients in the old site continue to function normally.  Moreover, once the clients…

Read More Read More