Jump to content


Zero

Established Members
  • Content Count

    29
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Zero

  1. 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?
  2. 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..
  3. Zero

    Querky AHCI issue

    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.
  4. Zero

    Querky AHCI issue

    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!
  5. Zero

    Querky AHCI issue

    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?
  6. Zero

    Querky AHCI issue

    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..
  7. Zero

    Querky AHCI issue

    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
  8. Zero

    Querky AHCI issue

    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
  9. 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.
  10. Zero

    Querky AHCI issue

    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?
  11. Zero

    Querky AHCI issue

    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....
  12. 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.
  13. 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.
  14. 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.
  15. 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.
  16. oh god i could hug you so much right now. windows-noob indeed.
  17. hey all, just wondering if anyone knows a way to convert a stand-alone dvd created by SCCM 2007 r2 to a bootable USB without receiving the HAL32.DLL error warning? The issue is, our SCCM server is a virtual machine using vsphere, and therefore has no usb passthrough support. so for me to get a bootable usb key, i have to extract it onto a usb key. so what i've done so far is created a stand-alone DVD which is tested and works, and then followed the steps for formatting a usb key to fat32, making it active and then copying the contents of the dvd onto the USB key - the issue i have is that while this allows me to boot off of the USB key successfully, apon a reboot the client machine gives me an error of being unable to find hal32.dll i checked out the web and it stated something about using a ts variable called SMSTSLaunchMode equals UDF+FORMAT, but it doesnt really mention in what step to add this etc? has anyone else been in a similiar situation? surely im not the first to use a sccm that was virtual and needing to do stand alone usb drives?
  18. Hi All, we're Currently running SCCM 2007 R2 SP2 and we've just started to deploy secondary sites at all of our branch offices. I have setup a secondary site and a branch distribution point. pushing software itself seems to work currently and over time the software successfully installs, but when pushing boot images to the BDP, i get stuck on "Install Pending" and the following error OVER and OVER and over in the logs(to get to the logs, i right click on the install pending and select "show all messages") SMS Server SMS_DISTRIBUTION_MANAGER THREAD ID: 1272 PROCESS ID: 1980 MESSAGE ID: 2342 SMS Distribution Manager is starting to distribute package "Boot image (x64)" to distribution point "["Display=\\vic-UTILITY-02\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=GIF"]\\NSW-UTILITY-02\SMSPXEIMAGES$\". looking into the distmgr.log file on the server i get the following ~Updating package info for package BUR00002 $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:06.541 2010 AUS Eastern Daylight Time><thread=3920 (0xF50)> ~Package BUR00002 does not have a preferred sender. $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:06.546 2010 AUS Eastern Daylight Time><thread=3920 (0xF50)> ~Sent package server list to parent site BUR for package BUR00002 $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:06.548 2010 AUS Eastern Daylight Time><thread=3920 (0xF50)> ~StoredPkgVersion (1) of package BUR00002. StoredPkgVersion in database is 1. $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:06.548 2010 AUS Eastern Daylight Time><thread=3920 (0xF50)> ~SourceVersion (4) of package BUR00002. SourceVersion in database is 4. $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:06.548 2010 AUS Eastern Daylight Time><thread=3920 (0xF50)> STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=VIC-UTILITY-02 SITE=HRD PID=1596 TID=3920 GMTDATE=Wed Mar 31 05:20:06.549 2010 ISTR0="Boot image (x64)" ISTR1="BUR00002" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="BUR00002" $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:06.549 2010 AUS Eastern Daylight Time><thread=3920 (0xF50)> ~Exiting package processing thread. $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:06.549 2010 AUS Eastern Daylight Time><thread=3920 (0xF50)> ~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.224 2010 AUS Eastern Daylight Time><thread=2896 (0xB50)> ~Starting package processing thread,thread ID = 6E0 $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.224 2010 AUS Eastern Daylight Time><thread=2896 (0xB50)> ~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.225 2010 AUS Eastern Daylight Time><thread=2896 (0xB50)> STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=VIC-UTILITY-02 SITE=HRD PID=1596 TID=1760 GMTDATE=Wed Mar 31 05:20:11.225 2010 ISTR0="Boot image (x64)" ISTR1="BUR00002" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="BUR00002" $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.225 2010 AUS Eastern Daylight Time><thread=1760 (0x6E0)> No action specified for the package BUR00002. $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.225 2010 AUS Eastern Daylight Time><thread=1760 (0x6E0)> No action specified for the package on server ["Display=\\VIC-UTILITY-02\"]MSWNET:["SMS_SITE=HRD"]\\VIC-UTILITY-02\. $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.225 2010 AUS Eastern Daylight Time><thread=1760 (0x6E0)> Start adding package to server ["Display=\\VIC-UTILITY-02\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=HRD"]\\VIC-UTILITY-02\SMSPXEIMAGES$\... $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.226 2010 AUS Eastern Daylight Time><thread=1760 (0x6E0)> Will wait for 1 threads to end. $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.226 2010 AUS Eastern Daylight Time><thread=1760 (0x6E0)> Thread Handle = 3012 $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.226 2010 AUS Eastern Daylight Time><thread=1760 (0x6E0)> Attempting to add or update a package on a distribution point. $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.226 2010 AUS Eastern Daylight Time><thread=4504 (0x1198)> for ["Display=\\VIC-UTILITY-02\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=HRD"]\\VIC-UTILITY-02\SMSPXEIMAGES$\, machine account is to be used~ $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.227 2010 AUS Eastern Daylight Time><thread=4504 (0x1198)> STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=VIC-UTILITY-02 SITE=HRD PID=1596 TID=4504 GMTDATE=Wed Mar 31 05:20:11.228 2010 ISTR0="Boot image (x64)" ISTR1="["Display=\\VIC-UTILITY-02\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=HRD"]\\VIC-UTILITY-02\SMSPXEIMAGES$\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="BUR00002" AID1=404 AVAL1="["Display=\\VIC-UTILITY-02\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=HRD"]\\VIC-UTILITY-02\SMSPXEIMAGES$\" $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.228 2010 AUS Eastern Daylight Time><thread=4504 (0x1198)> ~RDC:This is a Share Type DP. Will use the Share Name SMSPXEIMAGES$ for RDC signature $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.228 2010 AUS Eastern Daylight Time><thread=4504 (0x1198)> ~Established connection to ["Display=\\VIC-UTILITY-02\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=HRD"]\\VIC-UTILITY-02\SMSPXEIMAGES$\ $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.237 2010 AUS Eastern Daylight Time><thread=4504 (0x1198)> ~Signature share exists on distribution point path MSWNET:["SMS_SITE=HRD"]\\VIC-UTILITY-02\SMSSIG$\ $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.244 2010 AUS Eastern Daylight Time><thread=4504 (0x1198)> ~Validating the compressed file C:\SMSPKG\BUR00002.PCK for package BUR00002 $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:11.245 2010 AUS Eastern Daylight Time><thread=4504 (0x1198)> ~The package file requires a NTFS drive to decompress to. $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:12.389 2010 AUS Eastern Daylight Time><thread=4504 (0x1198)> ~Decompressing package C:\SMSPKG\BUR00002.PCK to C:\_S M29ef.TMP $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:12.389 2010 AUS Eastern Daylight Time><thread=4504 (0x1198)> ~Used 1 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:16.231 2010 AUS Eastern Daylight Time><thread=2896 (0xB50)> ~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><Wed Mar 31 16:20:16.231 2010 AUS Eastern Daylight Time><thread=2896 (0xB50)> Looking into the logs as i wait again, i get the following over and over and over now.. Severity Type Site code Date / Time System Component Message ID Description Information Milestone GIF 31/03/2010 4:27:17 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2342 SMS Distribution Manager is starting to distribute package "Boot image (x64)" to distribution point "["Display=\\VIC-UTILITY-02\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=GIF"]\\VIC-UTILITY-02\SMSPXEIMAGES$\". Information Milestone GIF 31/03/2010 4:26:17 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2300 SMS Distribution Manager is beginning to process package "Boot image (x64)" (package ID = BUR00002). Information Milestone GIF 31/03/2010 4:26:12 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2301 SMS Distribution Manager successfully processed package "Boot image (x64)" (package ID = BUR00002). Information Milestone GIF 31/03/2010 4:26:12 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2322 SMS Distribution Manager decompressed package "BUR00002" from "C:\SMSPKG\BUR00002.PCK" to "C:\_S Mtslp.TMP". Information Milestone GIF 31/03/2010 4:24:56 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2342 SMS Distribution Manager is starting to distribute package "Boot image (x64)" to distribution point "["Display=\\VIC-UTILITY-02\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=GIF"]\\VIC-UTILITY-02\SMSPXEIMAGES$\". Information Milestone GIF 31/03/2010 4:23:56 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2300 SMS Distribution Manager is beginning to process package "Boot image (x64)" (package ID = BUR00002). Information Milestone GIF 31/03/2010 4:23:51 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2301 SMS Distribution Manager successfully processed package "Boot image (x64)" (package ID = BUR00002). Information Milestone GIF 31/03/2010 4:23:51 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2322 SMS Distribution Manager decompressed package "BUR00002" from "C:\SMSPKG\BUR00002.PCK" to "C:\_S Mugtv.TMP". Information Milestone GIF 31/03/2010 4:22:36 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2342 SMS Distribution Manager is starting to distribute package "Boot image (x64)" to distribution point "["Display=\\VIC-UTILITY-02\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=GIF"]\\VIC-UTILITY-02\SMSPXEIMAGES$\". Information Milestone GIF 31/03/2010 4:21:35 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2300 SMS Distribution Manager is beginning to process package "Boot image (x64)" (package ID = BUR00002). Information Milestone GIF 31/03/2010 4:21:30 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2301 SMS Distribution Manager successfully processed package "Boot image (x64)" (package ID = BUR00002). Information Milestone GIF 31/03/2010 4:21:30 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2322 SMS Distribution Manager decompressed package "BUR00002" from "C:\SMSPKG\BUR00002.PCK" to "C:\_S M3joy.TMP". Information Milestone GIF 31/03/2010 4:20:14 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2342 SMS Distribution Manager is starting to distribute package "Boot image (x64)" to distribution point "["Display=\\VIC-UTILITY-02\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=GIF"]\\VIC-UTILITY-02\SMSPXEIMAGES$\". Information Milestone GIF 31/03/2010 4:19:14 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2300 SMS Distribution Manager is beginning to process package "Boot image (x64)" (package ID = BUR00002). Information Milestone GIF 31/03/2010 4:19:10 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2301 SMS Distribution Manager successfully processed package "Boot image (x64)" (package ID = BUR00002). Information Milestone GIF 31/03/2010 4:19:09 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2322 SMS Distribution Manager decompressed package "BUR00002" from "C:\SMSPKG\BUR00002.PCK" to "C:\_S Mkyqc.TMP". Information Milestone GIF 31/03/2010 4:17:54 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2342 SMS Distribution Manager is starting to distribute package "Boot image (x64)" to distribution point "["Display=\\VIC-UTILITY-02\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=GIF"]\\VIC-UTILITY-02\SMSPXEIMAGES$\". Information Milestone GIF 31/03/2010 4:16:53 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2300 SMS Distribution Manager is beginning to process package "Boot image (x64)" (package ID = BUR00002). Information Milestone GIF 31/03/2010 4:16:48 PM VIC-UTILITY-02 SMS_DISTRIBUTION_MANAGER 2301 SMS Distribution Manager successfully processed package "Boot image (x64)" (package ID = BUR00002). this error is occuring every 3 minutes on the dot, and the package never finishes installing. any idea on how to fix this?
  19. Hi All, Im currently in the middle of a project where i am deploying sccm to multiple sites in a primary->secondary configuration. at the moment, the primary site is working as intended, clients are being discovered and instaling the client, but on secondary sites the clients are being discovered via AD system discovery but the client is not installing. Is there a good blog post or a good summary on how to do this? i cant really see any guides for secondary sites that have a step by step process of the above. any help at all would be great. things i have tried so far: 1)configuring the client installation push settings per site to reflect the site name, and checked all boxes in the client settings. 2)configured an AD Admin account as the account to be used during installation
  20. Hi All, Got a few questions and a little bit of background info to cover my question. first of all, i run a network with 5 subnets. currently, the HQ has config manager installed (2007 sp2 r2) and its working successfully, clients are pushed, software is working, deployment is working well (thanks to you guys!) and all is well. but now its time to push this software to all other sites, which sit under a different subnet. So, a few questions. I have configured a secondary site via the push available from the console. this has worked successfully, but what do i need to do from this point to get the client push installation working on offsite? Please tell me if I've missed something here: i have enabled discovery for the secondary site's subnet, and this has successfully discovered all the client machines, but has not installed the agent. im guessing i need to 1) add the secondary site distribution point to the client installation push package?
  21. ok a restart of the server seemed to make it work OK. also, the reason why it was sitting on "contacting server" was actually due to me not loading the correct boot image. for some reason, it wanted a x64 boot image. cant complain, it seems to be working now.
  22. Ok i got it working further. i reinstalled wds, didnt goto the UI, went to the config manager console, installed the psp role, and then added a new distrubution store for the x86 boot image reminstall$ or something to those lines. i now get past that error, and im now stuck on the pxe client waiting for the server to respond. so it picks up a dhcp address, but is waiting there, ie; "contacting server 192.168.x.x ..... ....... ......"
  23. when you say add the boot image to my distribution point, do you mean the existing ones that i have been using for agent-based o/s installs?this is where im getting confused. my environment is already deploying operating systems to machines with the cfgmgr agent installed and running, there are boot images that already exist for that task sequence to use. when it comes to baremetal installations for unknown machines, it returns an error on pxe booted machines saying no boot image found. what is the procedure i need to follow to install a boot image, where do i define or create this boot image?
  24. ok, are you talking about the boot images node in sccm or wds? in wds, its empty. in sccm, the two boot images which are used for non-bare metal deployments are there, yes.
  25. Hi All, I'm currently running SCCM 2007 sp1 R2 with successful deployments of windows 7 from the desktop provided they already have an o/s installed. i am interested in configuring the server as a PXE answer point to replace our existing WDS Server so i am able to do bare metal deployments. i have followed various instructions on how to install this.. 1) install wds onto the server. do not configure it, simply install the service in 2008 server. 2) add the PSP roll to the WDS server (which is the same server as the sccm server) a) ticked the respond to unknown computers option 3) i've created a task sequence and assigned it to the unknown computer group, and ensured that i ticked the "make available to pxe boots" option 4) when booting a pc into pxe mode, it returns the error of "no boot image found" basically, it appears that sccm 2007 isnt injecting a boot image for the wds server to use (which on a traditional wds server installation, is done post installation of the service.). am i missing a step? should i be adding the standard x86 bootimage from sccm via the wds console to get around this? i just dont seem to be able to find a solid answer for this on the internet, at all. all the guides skim over the wds configuration part.
×
×
  • Create New...