Search the Community
Showing results for tags 'SMS Provider'.
-
Hello, After importing drivers to create a driver package, I checked the Applicability tab under properties and found that Windows 10 was unchecked. When I went to add checkboxes (Since my image is Windows 10) I received "The SMS Provider reported an error." This only happens if I check the boxes for Windows 10, all other OS checkboxes work just fine. When I choose the first option "This driver can be run on any platform" it lets me apply the changes but when I initiated the Task Sequence on the computer it would download the drivers and for a brief moment go to installing drivers and then skip onto the next step. Once the OS booted up I checked device manager and there are missing drivers. Any help would be greatly appreciated. Note: I upgraded SCCM last month to: System Center 2012 R2 Configuration Manager SP1 Console Version: 5.0.8239.1000 Site Version: 5.00.8239.1000 The Error Message Details ConfigMgr Error Object: instance of SMS_ExtendedStatus { Description = "The digest is not valid"; ErrorCode = 1078462235; File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspconfigurationitem.cpp"; Line = 2142; Operation = "PutInstance"; ParameterInfo = ""; ProviderName = "ExtnProv"; StatusCode = 2147749889; }; ------------------------------- Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException The SMS Provider reported an error. Stack Trace: at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put() at Microsoft.ConfigurationManagement.AdminConsole.DesiredConfigurationManagement.ConsoleDcmConnection.Microsoft.ConfigurationManagement.DesiredConfigurationManagement.IDcmStoreConnection.UpdateExistingItem(ConfigurationItem item, Object existingItem) at Microsoft.ConfigurationManagement.DesiredConfigurationManagement.ConfigurationItem.Persist(Object existingStoreItem) at Microsoft.ConfigurationManagement.AdminConsole.DesiredConfigurationManagement.DcmObjectWrapper.Microsoft.ConfigurationManagement.ManagementProvider.IResultObject.Put() at Microsoft.ConfigurationManagement.AdminConsole.SmsDialogData.Put(Boolean retainLock) at Microsoft.ConfigurationManagement.AdminConsole.DialogFramework.Forms.SmsPropertySheet.Put(ActionTrigger trigger) ------------------------------- System.Management.ManagementException Generic failure Stack Trace: at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put() at Microsoft.ConfigurationManagement.AdminConsole.DesiredConfigurationManagement.ConsoleDcmConnection.Microsoft.ConfigurationManagement.DesiredConfigurationManagement.IDcmStoreConnection.UpdateExistingItem(ConfigurationItem item, Object existingItem) at Microsoft.ConfigurationManagement.DesiredConfigurationManagement.ConfigurationItem.Persist(Object existingStoreItem) at Microsoft.ConfigurationManagement.AdminConsole.DesiredConfigurationManagement.DcmObjectWrapper.Microsoft.ConfigurationManagement.ManagementProvider.IResultObject.Put() at Microsoft.ConfigurationManagement.AdminConsole.SmsDialogData.Put(Boolean retainLock) at Microsoft.ConfigurationManagement.AdminConsole.DialogFramework.Forms.SmsPropertySheet.Put(ActionTrigger trigger) -------------------------------
- 4 replies
-
- Driver Package
- SMS Provider
-
(and 1 more)
Tagged with:
-
Hi I have installed SCCM 2012 r2 as a Standalone primary site running the Site server on Win2012 and the SQL DB on a separate 2012VM. I have the site server setup with the following roles: Application Catalogue Service point Application catalogue website point Component server Distribution server Endpoint Protection point Management Point Site Server System Server Software update point I also have WSUS installed on the same VM. The problem I am facing is when I try to download Windows updates from Microsoft, it will pull the meta data, but I can't get the actual updates to download, and I get the error, "The sms provider encountered and error, (Update number...)" I have checked the Patch downloader log and it shows no errors, the wsyncmgr.log show the updates synchronizing, and skipping superseded updates, when I create a software download group, no problems, but when I try to deploy, I follow the wizard all the way to the end, then I get error all selected updates cannot be downloaded, followed by: Success: Updates Targeted: and a whole big list of updates, the another list of all the updates that will be downloaded from the internet and they match. I have no proxy in place, so does not need configured. SCCM and it's DB where previously running on one VM but performance was a nightmare, so we stripped it out and I rebuilt on to two machines. Do I need to do something with the clients? As the problem seems to be between the WSUS and the Site server, I figured not. Any advice welcome. Cheers Paul
-
Hi all. Attempting to install 2012 SP1 and it appears the pre-req checks for the Deployment Tools and PE are performed on the server that is specified for the SMS provider, rather than the SCCM server itself. Please refer screenshot below where the ADK tests are being undertaken on the DB server for some reason. SCCM Server: ADL-SCCM02.ourdomain.com (Win 2k8 R2) DB Server: ADL-SCDB01.ourdomain.com (SQL 2012 with cU2) The deployment kit has been installed on ADL-SCCM02 (including WinPE, Deployment Kit, etc), however the pre-req check is testing the database server (ADL-SCDB01). We opted to install the SMS provider on the database server (ADL-SCDB01) so suspected this could be related. As a troubleshooting step, I switched the SMS provider to ADL-SCCM02 and the pre-req's passed, presumably as the pre-req tests were correctly undertaken on the SCCM server instead of the DB server. The log file from a failed check is below. Extract: <01-09-2013 20:13:00> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>> <01-09-2013 20:13:00> ADL-SCDB01.mydomain.com; Windows Deployment Tools installed; Error; The Windows Deployment Tools component of the Assessment and Deployment Kit (ADK) is required and must be installed before Setup can continue. See http://go.microsoft.com/fwlink/?LinkID=252874 <01-09-2013 20:13:00> INFO: CheckAdkWinPeInstalled on ADL-SCDB01.mydomain.com. <01-09-2013 20:13:01> ADL-SCDB01.mydomain.com; Windows Preinstallation Environment installed; Error; The Windows Preinstallation Environment component of the Assessment and Deployment Kit (ADK) is required and must be installed before Setup can continue. See http://go.microsoft.com/fwlink/?LinkID=252874 <01-09-2013 20:13:01> ADL-SCDB01.mydomain.com; SMS Provider machine has same domain as site server; Passed I'm not aware of any link or dependancy between the SMS provider and the ADK, so assume this is a bug in the pre-req checker where a variable is not updated from the SMS or DB check and is passed to the ADK check. I'm about to try again after removing the other warnings, which shouldn't be critical (just windows auth on sql box) but could possible cause a logic error in the wizard. BTW I recall back in 2007 that the pre-req checker didn't correctly check permissions on the System container when applying via security group (with machine account a member) rather than the machine account itself - looks like this is still the case (hence one of our warnings)? Any other suggestions? We could of course install the SMS provider on the SCCM box and be done with it, however we're going to have a number of console installed across our support staff etc, and so it seems more efficient to install the provider on the DB to prevent the double hop and optimise performance.. Thanks in advance.