Hi All, We are in a need of deployment of a registry key through SCCM before Drivers are being installed. I have tried in the following ways : i) Created a package with a program as "regedit.exe /s xxx.reg" and included it in "Install Software" step of Task sequence. ii) Created a package without a program and included it in "Run command line" step of T.S with command "regedit.exe /s xxx.reg" iii) Created a batch file in following way and ran through "Run Command line" : @echo off SETLOCAL Set THISDIR="%~dp0*.*" regedit.exe /s "%THISDIR%xxx.reg" This was working in Winpe phase.i.e it was importing registry key. But, when deployment is done reg key is not seen in registry. I am missing something here ? Can some one please reply regarding this ? Thanks

This was working in Winpe phase.i.e it was importing registry key. But, when deployment is done reg key is not seen in registry. WinPE is only used before the final OS is installed on the disk. All settings will not remain. You have to run that step in the final OS.Torsten Meringer | http://www.mssccmfaq.de

If that key is crucial and the driver in question needs to be installed via the apply driver step, you could also implement the regkey in your image... Or would it be possible to exclude the driver and install it in a later (install software) step ? This way you can set the regkey first (run commandline).Miguel Rodriguez

Hi, "We are in a need of deployment of a registry key through SCCM before Drivers are being installed." If it must be present before the Windows installation step itself you should consider including it in your build process for the image. Regards, Jörgen-- My System center blog ccmexec.com --

Torsten, My Task sequence looks like this : i) Restart in WinPE ii) Partition disk iii) Apply OS iv) Apply Network settings v) Run Command line(Registry Install) vi) Apply drivers by package vii) setup and configmgr If i run command line (registry key install) at the end of setup and configmgr setup, where registry key will be imported - final OS or winpe?

Setup Windows and ConfigMgr Client includes a reboot to final OS. So the key would be imported in the final OS, but that's after the driver installation!?Miguel Rodriguez

Miguel, So, is there a way doing before drivers installation ?

To my knowledge - no. See my other reply for your options on this (image or seperate step in TS to install just this one driver).Miguel Rodriguez

What issue are we talking about exactly? Why do you have to create a regkey before applying a driver? What should it do? Please add some details as it's usually not necessary to modify the registry before "installing" drivers.Torsten Meringer | http://www.mssccmfaq.de

We are having a issue with one of drivers. Driver vendor had missed providing a registry key which is used to create logging information about the driver and correct working of driver in the target system. So,They came back and provided a registry key(xxx.reg) and asked us to install before drivers are being applied through SCCM. I have tried applying it through T.S as mentioned in my earlier post. Manoj

What driver is the reg key for and what function does it perform -- more info is always better when asking a question of folks who have no idea what you're doing. The Apply drivers task does not actually install any drivers. It merely copies them to the hard drive and makes them available to Windows setup which occurs during the Setup Windows And ConfigMgr task -- in Vista+ it also adds them to the offline image using DISM but it is still up to Windows setup to actually install them in the OS. Thus, adding the reg key after the Setup Windows and ConfigMgr task is the appropriate place for this edit.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

The reg key just enables the logging information for a graphics driver in the target system. From MSDN Forum - Manoj

Hi All, I created a package with source files and create a T.S step to run command line with command line "reg import xxx.reg" .I am getting a error in T.S - 0x8007052E which says bad username/password in smsts.log. I am providing Administrator account settings to run this step. Nothing seems to work. Has anyone deployed registry key through SCCM successfully? If yes what is the procedure for it. Manoj

Yes, I use it all times for setting a default domain as last step in Task Sequence. That way the domain is displayed after reboot ,and not the local device. I create a new package for that with the regkey file in it. Then create a step in the Task Sequence (in Windows mode) for "Run Command Line" with command "regedit.exe /s <filename>" At package (in the same screen) select the package with the regkey file in it. Eventually you can set account information, but it must working without that also. That way it must be working. My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

Hi Manoj, I do this all the time but like others have said, it needs to be run in the OS environment and not in the WinPE environment. If you need the key to be there before the Drivers installation then make it part of your base image (build and capture sequence) and then install the driver during your Deployment phase where the key will already be there. You can use either a REG file or VBS to write the keys during the build of your core image. You shouldn't need to specify an account... It should import the key(s) just fine running under Local System. What is the registry key path you are importing to? -Jeff

registry key path which i was importing to is Local Machine(HKLM) hive. Manoj

Hi All, Finally , I was successful in installing registry key through SCCM. But when i tried to build and capture the image(registry key applied) through Task sequence i am getting '0x00000004' error in prepare OS step of T.S. Any help would be appreciated. From MSDN Forum - Manoj

You should open up a new thread for that problem, as it is not related to the original problem. If you do so post the contents of your Tasksequence, the last smsts.log and the os version you try to deploy.Miguel Rodriguez