Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by fly

  1. That is one method, but you can also use PEIMG to put the drivers in the boot WIM. Remember, the PE is actually an operating system, and you can service it (ie install packages, programs and drivers) when it is offline/not booted. If you end up having a lot of different drivers to load, it may reduce boot time.

    As far as XP images go, it depends on your licensing. You can sysprep the images before capture OR you may just be able to run the SID Changer on the machine instead. You'd have to test which option is best for you because sometimes SID Changer can break some account related functions like Task Scheduler and IIS for example. I create XP images (not too much anymore) and keep hardware specific images just to be safe from possible problems. My control criteria for XP images are the motherboard, video card (if no onboard video), HAL, Service Pack and BIOS version.

    Lastly, I hope your Broadcom drivers work, some Broadcom NICs do not work in WinPE.

    FWIW, changing the SID isn't necessary. Also, using anything other than sysprep to change the SID is unsupported by MS.

  2. @IcemanND

    Ok, so with Windows Deployment Service I can't made a Hardware independent image only with third party tools like *Universal Imaging Utility*, ok thank you very much for helping me!

    Namaste and have a nice day!


    XP images are hardware (HAL, Mass Storage) dependent, but Vista are not. For Vista, generalizing will only remove the display adapter (and unsigned drivers) if redeployed to like hardware.

    Probably a little offtopic here, but its relatively easy to swap HALs with DEVCON and VBScript. (I'm sure there are even easier ways, but thats what I used long ago...)

  3. I've just started playing with BDD 2007 and I must say that I'm overwhelmed. My goal is to start deploying XP with it, which I've done. Now I want to start adding in my own configurations. Can someone explain the task sequence? I can't find any good docs on it.

    Here's what I'd like to accomplish:

    1) Reboot the PC

    2) Login as a domain user

    3) Use RunOnceEx to configure some stuff

    Where the heck would these scripts go in the task sequence???

  4. If the machine is a Dell, you can use the Dell utility partition to do this, then you just have to press F12 and select it... (I breezed through this thread, sorry if it was mentioned)

    Yep :), but that is a "peculiarity" of DELL Bioses, the idea of the thread was to use the MBR or a bootloader/bootmanager (independently from any BIOS make/brand/code).

    More (GOOD) info on the DELL partition utility is here:


    The BIOS has code that "intercept" the F12 and "recognizes" setting it active, the "DE" partition.


    Yeah, I used just that site to learn how to setup a Dell utility partition to boot and reinstall an OS. I'll save all that for another thread tho...

  5. I've never used that before but I have seen it used when I'm on RDP sometimes. I would think it should translate the domain prefix regardless of the DefaultDomainName setting.

    Yeah, thats what I'm hoping is that it will be impossible for it to attempt to use the local computer name. We'll see...





    Try adding these:



    You can also try "DisableCAD" set it to 1

    That's what I have in the first post, except for the CAD, which I've also tried. Thanks tho.

  6. Right, forgot my timeline there. When this does fail is the domain name listed in the "logon to" field or is it the computername? I'm wondering if the cmdlines.txt command is not being set or the value is being reset afterwards for some reason, but you need to find out what that registry value is when it fails.

    I've used remote registry and all the values seem to be correct. On a new google search, I saw someone mention setting the username as 'DOMAIN\USERNAME', I'm wondering if that will help me.

  7. Sorry, I forgot to get back to you. Seems that the DefaultDomainName key is being set to the computername during setup. I forget if that's the default action, but I think so. You may want to use something like GuiRunOnce to run a req add and set the value of DefaultDomainName to your domain.

    I'm setting those values now using cmdlines.txt. I don't think GUIRunOnce will work, as I can't log on. And I can't remember if I left this (key) piece of info out, but this login error doesn't happen every time.

    I really wish I could just go back to logging on with a non-domain account, as this is a PITA...

  8. Gotcha, sorry I didn't read carefully enough. I thought you just wanted to autologon. So the logon prompt is coming up and if you cancel that and hit CAD again it steps thru just fine. When you have the logon prompt up, exactly what values are listed for each field?

    The "problem" that I see is that it appears to be trying to log on to the local PC, rather than the domain. But like I said, after I hit okay and CAD again, it logs in. Im so confused...

  9. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]


    Your problem is this value. The rest of the first section is spot on, but just drop AutoLogonCount and you should be OK. Just make sure you're not using autologon after mini-setup b/c it'll get disabled when setup decrements the counter specified in unattend/sysprep, just like it does with this registry value.

    But if I take out that value, won't it autologon forever? I just want to do it once, and I'm not setting it via unattend.txt or sysprep because I can't use either of those to logon to a domain account...

  10. What are you hitting cancel to exactly? maybe post a screenshot? I've never setup an auto login after install on my builds, but maybe I'd learn something and be able to help you out a bit better. Is it an option to disable CTRL+ALT+DEL on logon screen via AD GPO?

    I hit cancel on the XP logon screen, then CAD, and suddenly the autologin works... its very odd.

  11. Now if only I could adapt this setupldr.bin to change the hal on a syspreped machine!

    You can script the HAL change using RunOnce...

    edit: I posted how to do it before, but can't remember the tool I used, and the search here sucks. I'll look around though if you're interested.

    edit2: You can hot swap the HAL with devcon: http://msdn2.microsoft.com/en-us/library/m...60-aaeb017e5fc7

  12. I need to autologin to the domain once, as part of my PC build process, but it seems to default to logging into the local PC rather than the domain. What am I doing wrong? Here is what I've tried so far...

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

    I've also tried a more complex version I found on the internets:

    [code]Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

    This 2nd code works MOST of the time. On the times it doesn't work, if I hit cancel then hit CTRL ALT DEL, it automatically logs in without me typing anything...

  • Create New...