Jump to content


Search the Community

Showing results for tags 'driver package'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 5 results

  1. Helloy guys, I'm experiencing a very strange behaviour in SCCM OS deployment... my task sequence seems to work fine for all laptops, desktops, tablets etc. except for one laptop model (Deployment for Lenovo E570 - Win 7 OS). I assume that there is a driver issue ,but I simply can't solve it.. During the task sequence the join to the domain "fails". The log claims that no adapters are found. Funny thing is, that during the TS the drivers are installed and after the TS completes, the NIC is present in the device manager. So WTF!? All other models are working fine... I've removed the complete NIC drivers from the package and re-added them. And I added different driver versions. Even added the driver to the boot-image. No success... *UPDATE* I figured out that, after the driver has been installed the adapter is not loaded. When u open a cmd and run ipconfig only the WiFi adapter is present... HEEELP!!
  2. 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) -------------------------------
  3. SCCM 2012 I am creating driver packages and installing/targeting them in the task sequence using WMI queries for machine model. My issue is that the driver packages have to be successfully replicated to ALL distribution points before the task sequence will start. If the new package is not distributed to all distribution points the task sequence will not start until I disable the step. Is this by design? I would like to distribute the package to a single distribution point in my boundary so that I can test before replicating to all DPs. Any help? Thanks, Joel
  4. Hi, I have a really odd problem that I’ve never seen before when deploying an OSD TS to an HP ProBook 6560b. I’m deploying Windows 7 Enterprise 64bit using Confg Manager 2012 SP1. I have the latest driver pack for this model from HP (sp61783.exe), and the correct driver pack is selected in the TS using a WMI query. The driver package is installed OK, however the wrong NIC driver is installed. The NIC is an Intel 82579V (PCI\VEN_8086&DEV_1503), however the driver for the 82579LM (PCI\VEN_8086&DEV_1502) gets installed. Checking the setupapi.dev.log I can see that in the first boot session (i.e. after SCCM has copied the drivers to the driverstore and the laptop reboots to install the drivers) the hardware is detected as DEV_1502. The 82579LM driver is selected and installed, however the device fails to start. After the next reboot in the TS the setupapi.dev.log shows that it has detected DEV_1503 and the 82579V driver is installed and the device starts. Things I’ve tested so far: A driver package with only the NIC driver in case another driver was causing the issue. Installing no drivers at all – the device is still detected as the 82579LM. Creating a new driver package. Several different versions of the driver including the latest from Intel rather than HP. A different install.wim (the original just has IE9 slipstreamed, but I get the same result from the install.wim from the Win7 ISO). Running the TS using standalone media. A couple of interesting things: It’s not a hardware problem as it build correctly in our SCCM 2007 environment – using the same drivers. The same TS works correctly on a ProBook 6570b and this has the same 82579V NIC. If I install manually using the Windows 7 DVD the device is detected correctly as the 82579V. Any help VERY much appreciated! first_boot_dev_1502.txt second_boot_dev_1503.txt
  5. Still working on the SCCM 2012 test lab, and recently I added a driver package to the an OSD TS; I'd like to know if these drivers got properly installed and I don't know which logs to look into. Looks like during the OS deployment job the task sequence that is supposed to load the drivers (mainly DELL Optiplex drivers) runs properly, since I don't see any errors, but I just want to make sure since one set of drivers isn't getting installed. I'm assuming the client logs under windows\CCM\logs, but which file? Thanks!
×
×
  • Create New...