Everything posted by IT-Hilger
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
-
SCCM 2012 OSD Apply Driver Packages without importing them to the Database
Hi Sant, thats different from (exe) package to package. You must try to extract them and then use the .inf, .sys and .cat files. You can try to extract the .exe with 7zip for example. If this doesn't work, run the .exe and wait at the first dialog of the .exe program and don't click next. Then open the %temp% folder on the pc and have a look inside the last modified folder in %temp% folder. I think you should find the extracted driver files there. BR Achim
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
-
SCCM 2012 OSD Apply Driver Packages without importing them to the Database
Hi Dietmar, nice to hear, thanks. Nice idea with OSDisk variable! DISM sometimes gives return code "2" or "50". By default, SCCM TS just takes "0" and "3010" as success codes. When you don't add the return codes 2 and 50 as success codes, the apply drivers works fine, but SCCM thinks that there was an error because it doesn't know that this return codes also mean success.
-
SMS_NOTIFICATION_SERVER-FAILED CRITICAL SCCM SP1 SQL 2012 SP1
We also tried the above solutions but they didn't help. In our system the problem was a corruption in Windows performance counter library. Run this command in an Administrator CMD: cd C:\WINDOWS\system32 lodctr /R You should see a success message after the above command. Then restart SMS_SITE_COMPONENT_MANAGER and see if it works. BR Achim
- SCCM 2012 OSD Apply Driver Packages without importing them to the Database
-
SCCM 2012 OSD Apply Driver Packages without importing them to the Database
Hi Everybody, this thread is for those who want the old SCCM 2007 driver management back. Normally you have to import every driver to the database first, put them into a driver package, and then deploy them during OSD. In SCCM 2007 you could easily create a Driver Package from your Driver Source Folder and apply this Driver Package during OSD. This way of Driver Management was much easier and more reliable than the new way in SCCM 2012. But luckily there is still a method to prevent importing drivers into database and directly distribute driver packages to your clients. Step 1 Download drivers for your brands and models. Put them into seperate folders - one folder for one model - like you did in SCCM 2007 Step 2 Create a Package for each model and operating system. Then distribute this packages to your DP. Step 3 Create a Step "Set Task Sequence Variable" under your Auto Apply Drivers Group (after the Apply Operating System Step) in your Task Sequence. Task Sequence Variable: winrootdir Task Sequence Value: D:\ Condition: If Folder "D:\Windows" exists I created a second step after this with Drive Letter E:\. Because on some Notebooks the Systemroot is E:\ during OSD. Step 4 Create TS Steps for each model to apply the driver package. Type: Run Command Line Command line: DISM.exe /Image:%winrootdir% /Add-Driver /Driver:.\ /Recurse Package: Choose the corresponding package you created in step 2 Success codes: Add 2 and 50 Condition: WMI Query (here an example for Dell Latitude E7240) select * from win32_computersystem where Model like "Latitude E7240%" Repeat the steps above for each computer model you want to image. With this way of applying drivers we have 0 problems in our environment. Very easy and reliable. BR Achim If you have questions - feel free to contact me http://ithilger.de/kontakt
