Zero

Hey All, Currently trying to create boot media from my task sequence using sccm 2007 R2 on windows 2008 R2 in mixed mode. For some reason, when i try to create boot media from my task sequence, i receive the following errors in my CreateTsMedia.log: Boot image architecture is i386 CreateTsMedia 8/06/2011 4:27:37 PM 5160 (0x1428) StageBaseFiles::SetTsmVariables() CreateTsMedia 8/06/2011 4:27:37 PM 5160 (0x1428) Could not retrieve MP certificates CreateTsMedia 8/06/2011 4:27:37 PM 5160 (0x1428) MediaGenerator::~MediaGenerator() CreateTsMedia 8/06/2011 4:27:37 PM 5160 (0x1428) Failed to create media generator (0x80040002) CreateTsMedia 8/06/2011 4:27:37 PM 5160 (0x1428) CreateTsMedia failed with error 0x80040002, details="" CreateTsMedia 8/06/2011 4:27:37 PM 5160 (0x1428) Looking into it.. i dont actually have a certificate in my boot media certificate section of SCCM - what do i need to do to get this working, i was under the impression a cert is not needed when running in a mixed mode?

hey all, just a quick one. i noticed that the intel turbo memory disabling tool from lenovo (its a .inf file that is a placeholder, to get rid of the "unknown device" ibm0068 device in device mgr) when manually installed brings up a "unable to verify if this is the correct driver, are you sure you want to install this driver?" kind of message. because of this message, sccm doesnt install the driver during an OSD task sequence, but once past this message the driver works as intended. my question i guess is, is there a way to add a variable or script it to accept this warning and continue? its my last step in my puzzle..

hey, So i recaptured my build and capture without that registry value modified, and now my sccm injection works. So in summary: Dont use Nlite driver injection if you're going to use sccm for deployment that includes some form of driver injection via sccm.

So i've figured it out i think, capturing overnight so i can apply and view my changes but here's an explanation it seems that it grabs a list of drivers from the registry. nlite edits this devicepath registry entry to include and integrate drivers you have slipstreamed into the bootable media. once installed, that directory remains filled out. it can be found under hklm\software\microsoft\windows\devicepath, it populates %systemroot% with a directory called nldrv and populates that subdirectory. i have reset that value to its default %systemroot%\inf and will re-try the TS tomorrow. UGH!

Ok i rebuilt my image in vmware, and i got a bit more of a useful log with the error. it is statign in smsts.log "Loading offline registry hive "C:\WINDOWS\system32\config\software" into HKLM\OfflineRegistry1 OSDDriverClient 16/08/2010 2:44:27 PM 1436 (0x059C) Loading offline registry hive "C:\WINDOWS\system32\config\system" into HKLM\OfflineRegistry2 OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) CurrentControlSet is mapped to ControlSet001 OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) Driver Cache Index = C:\WINDOWS\inf\drvindex.inf OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) Driver Cache = C:\WINDOWS\Driver Cache\i386 OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) Device Search Path = C:\WINDOWS\NLDRV\290;C:\WINDOWS\NLDRV\289;C:\WINDOWS\NLDRV\288;C:\WINDOWS\NLDRV\287;C:\WINDOWS\NLDRV\286;C:\WINDOWS\NLDRV\285;C:\WINDOWS\NLDRV\284;C:\WINDOWS\NLDRV\283;C:\WINDOWS\NLDRV\282;C:\WINDOWS\NLDRV\281;C:\WINDOWS\NLDRV\280;C:\WINDOWS\NLDRV\279;C:\WINDOWS\NLDRV\278;C:\WINDOWS\NLDRV\277;C:\WINDOWS\NLDRV\276;C:\WINDOWS\NLDRV\275;C:\WINDOWS\NLDRV\274;C:\WINDOWS\NLDRV\273;C:\WINDOWS\NLDRV\272;C:\WINDOWS\NLDRV\271;C:\WINDOWS\NLDRV\270;C:\WINDOWS\NLDRV\269;C:\WINDOWS\NLDRV\268;C:\WINDOWS\NLDRV\267;C:\WINDOWS\NLDRV\266;C:\WINDOWS\NLDRV\265;C:\WINDOWS\NLDRV\264;C:\WINDOWS\NLDRV\263;C:\WINDOWS\NLDRV\262;C:\WINDOWS\NLDRV\261;C:\WINDOWS\NLDRV\260;C:\WINDOWS\NLDRV\259;C:\WINDOWS\NLDRV\258;C:\WINDOWS\NLDRV\257;C:\WINDOWS\NLDRV\256;C:\WINDOWS\NLDRV\255;C:\WINDOWS\NLDRV\254;C:\WINDOWS\NLDRV\253;C:\WINDOWS\NLDRV\252;C:\WINDOWS\NLDRV\251;C:\WINDOWS\NLDRV\250;C:\WINDOWS\NLDRV\249;C:\WINDOWS\NLDRV\248;C:\WINDOWS\NLDRV\247;C:\WINDOWS\NLDRV\246;C:\WINDOWS\NLDRV\245;C:\WINDOWS\NLDRV\244;C:\WINDOWS\NLDRV\243;C:\WINDOWS\NLDRV\242;C:\WINDOWS\NLDRV\241;C:\WINDOWS\NLDRV\240;C:\WINDOWS\NLDRV\239;C:\WINDOWS\NLDRV\238;C:\WINDOWS\NLDRV\237;C:\WINDOWS\NLDRV\236;C:\WINDOWS\NLDRV\235;C:\WINDOWS\NLDRV\234;C:\WINDOWS\NLDRV\233;C:\WINDOWS\NLDRV\232;C:\WINDOWS\NLDRV\231;C:\WINDOWS\NLDRV\230;C:\WINDOWS\NLDRV\229;C:\WINDOWS\NLDRV\228;C:\WINDOWS\NLDRV\227;C:\WINDOWS\NLDRV\226;C:\WINDOWS\NLDRV\225;C:\WINDOWS\NLDRV\224;C:\WINDOWS\NLDRV\223;C:\WINDOWS\NLDRV\222;C:\WINDOWS\NLDRV\221;C:\WINDOWS\NLDRV\220;C:\WINDOWS\NLDRV\219;C:\WINDOWS\NLDRV\218;C:\WINDOWS\NLDRV\217;C:\WINDOWS\NLDRV\216;C:\WINDOWS\NLDRV\215;C:\WINDOWS\NLDRV\214;C:\WINDOWS\NLDRV\213;C:\WINDOWS\NLDRV\212;C:\WINDOWS\NLDRV\211;C:\WINDOWS\NLDRV\210;C:\WINDOWS\NLDRV\209;C:\WINDOWS\NLDRV\208;C:\WINDOWS\NLDRV\207;C:\WINDOWS\NLDRV\206;C:\WINDOWS\NLDRV\205;C:\WINDOWS\NLDRV\204;C:\WINDOWS\NLDRV\203;C:\WINDOWS\NLDRV\202;C:\WINDOWS\NLDRV\201;C:\WINDOWS\NLDRV\200;C:\WINDOWS\NLDRV\199;C:\WINDOWS\NLDRV\198;C:\WINDOWS\NLDRV\197;C:\WINDOWS\NLDRV\196;C:\WINDOWS\NLDRV\195;C:\WINDOWS\NLDRV\194;C:\WINDOWS\NLDRV\193;C:\WINDOWS\NLDRV\192;C:\WINDOWS\NLDRV\191;C:\WINDOWS\NLDRV\190;C:\WINDOWS\NLDRV\189;C:\WINDOWS\NLDRV\188;C:\WINDOWS\NLDRV\187;C:\WINDOWS\NLDRV\186;C:\WINDOWS\NLDRV\185;C:\WINDOWS\NLDRV\184;C:\WINDOWS\NLDRV\183;C:\WINDOWS\NLDRV\182;C:\WINDOWS\NLDRV\181;C:\WINDOWS\NLDRV\180;C:\WINDOWS\NLDRV\179;C:\WINDOWS\NLDRV\178;C:\WINDOWS\NLDRV\177;C:\WINDOWS\NLDRV\176;C:\WINDOWS\NLDRV\175;C:\WINDOWS\NLDRV\174;C:\WINDOWS\NLDRV\173;C:\WINDOWS\NLDRV\172;C:\WINDOWS\NLDRV\171;C:\WINDOWS\NLDRV\170;C:\WINDOWS\NLDRV\169;C:\WINDOWS\NLDRV\168;C:\WINDOWS\NLDRV\167;C:\WINDOWS\NLDRV\166;C:\WINDOWS\NLDRV\165;C:\WINDOWS\NLDRV\164;C:\WINDOWS\NLDRV\163;C:\WINDOWS\NLDRV\162;C:\WINDOWS\NLDRV\161;C:\WINDOWS\NLDRV\160;C:\WINDOWS\NLDRV\159;C:\WINDOWS\NLDRV\158;C:\WINDOWS\NLDRV\157;C:\WINDOWS\NLDRV\156;C:\WINDOWS\NLDRV\155;C:\WINDOWS\NLDRV\154;C:\WINDOWS\NLDRV\153;C:\WINDOWS\NLDRV\152;C:\WINDOWS\NLDRV\151;C:\WINDOWS\NLDRV\150;C:\WINDOWS\NLDRV\149;C:\WINDOWS\NLDRV\148;C:\WINDOWS\NLDRV\147;C:\WINDOWS\NLDRV\146;C:\WINDOWS\NLDRV\145;C:\WINDOWS\NLDRV\144;C:\WINDOWS\NLDRV\143;C:\WINDOWS\NLDRV\142;C:\WINDOWS\NLDRV\141;C:\WINDOWS\NLDRV\140;C:\WINDOWS\NLDRV\139;C:\WINDOWS\NLDRV\138;C:\WINDOWS\NLDRV\137;C:\WINDOWS\NLDRV\136;C:\WINDOWS\NLDRV\135;C:\WINDOWS\NLDRV\134;C:\WINDOWS\NLDRV\133;C:\WINDOWS\NLDRV\132;C:\WINDOWS\NLDRV\131;C:\WINDOWS\NLDRV\130;C:\WINDOWS\NLDRV\129;C:\WINDOWS\NLDRV\128;C:\WINDOWS\NLDRV\127;C:\WINDOWS\NLDRV\126;C:\WINDOWS\NLDRV\125;C:\WINDOWS\NLDRV\124;C:\WINDOWS\NLDRV\123;C:\WINDOWS\NLDRV\122;C:\WINDOWS\NLDRV\121;C:\WINDOWS\NLDRV\120;C:\WINDOWS\NLDRV\119;C:\WINDOWS\NLDRV\118;C:\WINDOWS\NLDRV\117;C:\WINDOWS\NLDRV\116;C:\WINDOWS\NLDRV\115;C:\WINDOWS\NLDRV\114;C:\WINDOWS\NLDRV\113;C:\WINDOWS\NLDRV\112;C:\WINDOWS\NLDRV\111;C:\WINDOWS\NLDRV\110;C:\WINDOWS\NLDRV\109;C:\WINDOWS\NLDRV\108;C:\WINDOWS\NLDRV\107;C:\WINDOWS\NLDRV\106;C:\WINDOWS\NLDRV\105;C:\WINDOWS\NLDRV\104;C:\WINDOWS\NLDRV\103;C:\WINDOWS\NLDRV\102;C:\WINDOWS\NLDRV\101;C:\WINDOWS\NLDRV\100;C:\WINDOWS\NLDRV\099;C:\WINDOWS\NLDRV\098;C:\WINDOWS\NLDRV\097;C OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) Adding C:\drivers\1 to plug-and-play search path. OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) sDevicePath.length() < XP_MAX_DEVICEPATH, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,246) OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) Maximum DevicePath length (4096) exceeded. OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) AddPnPDriverDirsToDevicePath( sTargetPath ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,714) OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) Failed to update device path in offline registry. Code 0x80004005 OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) InstallDriver( iInstallParams->sContentId, iInstallParams->sSource, iInstallParams->pBootCriticalInfo ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,557) OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) Entering ReleaseSource() for D:\SMS\PKG\VI100070 OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) The user tries to release a source directory D:\SMS\PKG\VI100070 that is either already released or we have not connected to it OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,409) OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) Failed to provision driver. Code 0x80004005 OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) Unloading offline SOFTWARE registry hive OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) Unloading offline SYSTEM registry hive OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) Exiting with return code 0x80004005 OSDDriverClient 16/08/2010 2:44:28 PM 1436 (0x059C) Process completed with exit code 2147500037 TSManager 16/08/2010 2:44:28 PM 1208 (0x04B8) !--------------------------------------------------------------------------------------------! TSManager 16/08/2010 2:44:28 PM 1208 (0x04B8) Failed to run the action: Intel(R) ICH8M-E/M SATA AHCI. Unspecified error (Error: 80004005; Source: Windows) TSManager 16/08/2010 2:44:28 PM 1208 (0x04B8) Sending status message . . . TSManager 16/08/2010 2:44:28 PM 1208 (0x04B8) Do not send status message in full media case TSManager 16/08/2010 2:44:28 PM 1208 (0x04B8) Set a global environment variable _SMSTSLastActionRetCode=-2147467259 TSManager 16/08/2010 2:44:28 PM 1208 (0x04B8) Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 16/08/2010 2:44:28 PM 1208 (0x04B8) Clear local default environment TSManager 16/08/2010 2:44:28 PM 1208 (0x04B8) The execution engine ignored the failure of the action (Intel(R) ICH8M-E/M SATA AHCI) and continues execution TSManager 16/08/2010 2:44:29 PM 1208 (0x04B8) Sending status message . . . TSManager 16/08/2010 2:44:29 PM 1208 (0x04B8) " it seems it is matching a driver and then failing to install it! - any help?

Hey, Thanks for the prompt reply! the 80004005 error is found in the smsts.log "0, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\encryptablevolume.cpp,368) OSDDiskPart 12/08/2010 5:28:22 PM 1336 (0x0538)" Volume 'C:' is not an encryptable volume OSDDiskPart 12/08/2010 5:28:22 PM 1336 (0x0538) i havent got bitlocker set anywhere... and its windows xp. in the meantime, im going to rebuild the base image in vmware, and see how i go..

Bump.. i really need help with this. i've tried an alternative today. i created a custom sysprep.inf file and popped it into the c:\sysprep directory. Created in the entry a BuildmassstorageSection=No and then manually added my drivers. Created an automated build and capture disk, captured that version of my OS Created a Task sequence with the .wim, burnt THAT to dvd moved to another model. doesnt work. still gettingthe 7b error. edit: i pretty much followed this guide. http://kongkuba1.spaces.live.com/blog/cns!EEFF1607E296E5AB!146.entry edit: originally i followed this guide for sccm driver injection, but i was just getting error 80004005 with it http://myitforum.com/cs2/blogs/rzander/archive/2009/08/07/apply-xp-massstorage-drivers-from-sccm-osd-task-sequence.aspx

Ok i've hit brick wall. with my stand-alone media, it does the following formats the hdd applies the windows xp wim matches the vendor ID to a driver (Description: Apply Intel® ICH8R/DH/DO SATA AHCI Controller TSManager 12/08/2010 5:28:21 PM 1192 (0x04A8)) crashes with error 80004005 while installing the device drivers here is my attached smsts.log file from the install. can someone please go through it with me and see if they notice anything weird? i really cant see anything atm! smsts.log

Sounds like you need to inject NIC drivers into the boot image. This means you need to import drivers into SCCM, and then attach it to the win pe boot image.

Ok so i've gone one step further and created WMI filters in my task sequence that relate to a driver to be installed. So far, it picks up the driver and says "preparing to install". on reboot, i still get a blue screen with a 7b stop error. what am i doing wrong?

Hi All, Quick one for you all. I am currently deploying XP via SCCM OSD, and i have created a slipstream version of XP using Nlite. i have injected all the drivers for all of our lenovo fleet, and the media itself works a treat. then it gets tricky. we have around 6-7 lenovo models of drivers this cd is built for. i installed xp using this slipstream media, and then used the SCCM capture cd to capture a wim. funnily enough, the image is around 500mb, where the slipstream media is about 1gb. that rang warning bells. so i tried that newly captured image on the same model, and it works. trying it on another model, and it installs the OS, but apon reboot to install the SCCM client, xp bluescreens with 000007b error, which implies my AHCI driver for that model is no longer on the image (where on the slipstream media, it works regardless because the driver has been injected) so my question is as follows 1) during my initial installation of windows xp, obviously the driver needed was there. does XP drop/not carrying across un-needed drivers that are on the CD, for a cleaner install? 2) if the above answer is yes, what do i need to do to get those drivers either embedded onto the image, or installed? edit: just wanted to say that i dont get the blue screen until AFTER its applied the xp.wim. this implies that the WinPE from sccm sp2 has the driver able to write to the disk, but the actual OS that is installed doesnt....

hey all, im about to install SP2 using the guide provided here, but i need to also update the multiple secondary sites that exist. i noticed there is a checkbox in the tutorial that states "upgrade" and a check box also saying "all secondary sites". if i select that option, will it install sp2 onto both primary and secondary sites? Thanks in advance.

Dell do a fantastic service of providing pre-packaged .cab files for every single model, for every single windows OS, specifically for SCCM 2007 http://www.delltechcenter.com/page/Dell+Business+Client+Operating+System+Deployment+-+The+.CAB+Files the above link has helped me to no end with a dell roll out i did recently.it also gives a guide on how to add them etc.

nevermind, i was lazy and didnt read through the many guides that are also available.. there are some good links in the article i posted, right down the bottom.

Hi all, In the middle of planning out an upgrade of SCCM 2007 SP1 to SP2 - there are multiple servers on this national site, i was thinking of using the same procedure as seen in "http://www.windows-noob.com/forums/index.php?/topic/474-how-to-update-sccm-2007-to-sccm-2007-sp1/", but i wanted to know a few things first 1) any recommended prerequisites? the primary server at hq is running the software updates component as well as the OSD component of SCCM 2) how do i upgrade the secondary sites? do i just right click and choose "upgrade" once the sp2 installation is done? 3) do i need to repackage and send out the SCCM client to all desktops, or will this do it itself? Thanks, i know these are nooby questions but i need to know as we rely on it for every day support use.