Last month when installing a high available ConfigMgr infrastructure I received an error message. This message came when adding a second SMS Provider. Just have a look at this blogpost first: "How to install a multiple SMS Provider in ConfigMgr 2012". After installing the second SMS Provider everything seems fine, but after rebooting the server there was the error message. "The Status Viewer was unable to retreive the stored queries list from the data base".
Lucky me I found the following blogpost: "Unable to retrieve Configuration Manager 2012 Status Messages".
It mentions: You need to modify the startup type of the SMS Executive and Component Manager Services. Set the startup type to Delayed Start and then reboot the system after the change.
In this particular case the ConfigMgr Site server and SQL server were installed on different systems and the SMS Provider was installed on another remote system (second ConfigMgr Site server). By implementing the delayed start of these services on the Primary Site server everything seems fine again.
Hope it helps!
Showing posts with label SMS Provider. Show all posts
Showing posts with label SMS Provider. Show all posts
Wednesday, March 12, 2014
Thursday, April 18, 2013
How to install a multiple SMS Provider in ConfigMgr 2012 SP1
In ConfigMgr 2012 it's possible to install multiple SMS Providers for High Availability. The SMS Provider is the interface between the ConfigMgr console and the Site database. In an earlier blogpost I have described what to do for installing multiple SMS Providers: How to install a multiple SMS Provider in ConfigMgr 2012. Just follow the steps and you are fine!
Last week I installed an additional SMS Provider in ConfigMgr 2012 SP1. An error message followed because Windows ADK wasn't installed (oops). Because ConfigMgr 2012 SP1 uses Windows ADK, this is needed also on the site server where an additional SMS Provider is installed.
Before you run Setup, you must download and install Windows ADK on the site server and on each computer that runs an instance of the SMS Provider. That's mentioned HERE.
The error messages are:
After installing "Windows Deployment Tools" and "Windows PE" (both Windows ADK) setup was running fine again. Hope it helps!
Last week I installed an additional SMS Provider in ConfigMgr 2012 SP1. An error message followed because Windows ADK wasn't installed (oops). Because ConfigMgr 2012 SP1 uses Windows ADK, this is needed also on the site server where an additional SMS Provider is installed.
The error messages are:
- CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e
- INFO: WMI namespace root\MSCluster not exists on <server>
- CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\WOW6432Node\Microsoft\Windows Kits\Installed Products on <server>
- CWmiRegistry::WmiOpen: Failed to get values from SOFTWARE\WOW6432Node\Microsoft\Windows Kits\Installed Products
- CWmiRegistry::WmiOpen: Failed to connect to registry on machine <server>. Error code: 2
- ERROR: Failed to query registry values. 'Windows Deployment Tools' component of ADK not found.
- ERROR: Failed to query registry values. 'Windows PE' component of ADK not found.
- Failed to install SDK
After installing "Windows Deployment Tools" and "Windows PE" (both Windows ADK) setup was running fine again. Hope it helps!
Monday, November 5, 2012
How to install a multiple SMS Provider in ConfigMgr 2012
In ConfigMgr the SMS Provider is installed during installation. The SMS Provider is the interface between the ConfigMgr console and the Site database. In ConfigMgr 2007 there can be only one SMS Provider installed per ConfigMgr Site. In ConfigMgr 2012 however multiple installations of the SMS Provider are supported. Just remember: It
cannot be installed on a clustered SQL server database server or on the same
computer as the SMS Provider for another site.
For example: ConfigMgr 2012 is installed already and the SMS Provider is installed on your Primary Site server. Now you want to install another one on your SQL server, which isn't installed on a clustered SQL server database server. Here are the steps which must be followed:
1) Open the Start Menu on the ConfigMgr server and select Microsoft System Center 2012 > Configuration Manager > Configuration Manager Setup
2) Getting Started > Select "Perform site maintenance or reset this Site" and click Next
3) Site Maintenance > Select "Modify SMS Provider configuration" and click Next
4) Manage SMS Providers > Select "Add a new SMS provider" and "Enter the FQDN of the server where the SMS Provider is to be installed" and click Next
5) Configuration > After a few minutes the SMS Provider will be installed on another server
Good news that the SMS Provider can be installed multiple times now, and isn't a Single-point-of-failure anymore! With above steps multiple SMS Providers can be installed or uninstalled. Just choose to divide ConfigMgr roles also to have a High Available ConfigMgr environment.
Good luck with your installation!
For example: ConfigMgr 2012 is installed already and the SMS Provider is installed on your Primary Site server. Now you want to install another one on your SQL server, which isn't installed on a clustered SQL server database server. Here are the steps which must be followed:
1) Open the Start Menu on the ConfigMgr server and select Microsoft System Center 2012 > Configuration Manager > Configuration Manager Setup
2) Getting Started > Select "Perform site maintenance or reset this Site" and click Next
3) Site Maintenance > Select "Modify SMS Provider configuration" and click Next
4) Manage SMS Providers > Select "Add a new SMS provider" and "Enter the FQDN of the server where the SMS Provider is to be installed" and click Next
5) Configuration > After a few minutes the SMS Provider will be installed on another server
Good news that the SMS Provider can be installed multiple times now, and isn't a Single-point-of-failure anymore! With above steps multiple SMS Providers can be installed or uninstalled. Just choose to divide ConfigMgr roles also to have a High Available ConfigMgr environment.
Good luck with your installation!
Subscribe to:
Posts (Atom)



