crashball

I was able to remote reg in it after it failed to login. It seems to be applying DefaultPassword and AutoLogonCount, but i dont see autoadminlogon and the DefaultUserName is still Administrator. It seems like it is applying some of it, there's no where else it could be getting the password If i log in and apply the autolog.reg and reboot it will work.

I am having some trouble getting autologon to work properly. i am using BDD/OSD to create, sysprep, and capture an image. We have a GPO that renames our administrator account so specifiying autologon in Sysprep.inf doesn't want to work becuase it will always use "administrator" as the user name. What I have done previously was have a .reg file with the autoreg entries and then call it from cmdlines.txt during the install. That doesn't seem to be working anymore. here's my files cmdlines.txt [Commands] "\sysprep\sysprep.exe -clean -quiet" "regedit.exe /s AutoLogon.reg" autologon.reg Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "DefaultUserName"="LocalAdmin" "AutoAdminLogon"="1" "DefaultPassword"="pa$$word" "autologoncount"="1" sysprep.inf [GuiUnattended] AdminPassword="pa$$word" OEMSkipWelcome=1 OEMSkipRegional=1 TimeZone=008 AutoLogon="Yes" AutoLogonCount=1 i have also tried to take the autologon entries out of sysprep.inf to no avail. This has worked for me before, but now it just has the logon screen waiting for a login.

bump

I had a working sysprep image for a bunch of Dell PCs. I made some changes cleaning up my OEM drivers, now I can't seem to get an Intel Pro1000/MT NIC to install on Dell GX260s and GX270s. they actually use the same driver, but dell has them on different versions. I have the correct drivers in the OEM folders on my image. c:\Drivers\* *GX260\NIC *GX270\NIC My OEPnPDriversPath includes this path, ihave doubles checked the registry after the install and it appears to be OK. I tried the drivers from Intel's website. I have even tried their corrected INFs for RIS installs but that does nothing. When XP boots, i can log in locally and it detects new hardware. It even knows that it is an Intel Pro1000/MT, but the driver is not isntalled. If i point it to either directory with the driver, it's happy and installs fine. What I can't figure out is why won't it find it during PNP detection. It worked before, and the changes I made were not major...mainly just cleaning up duplicate and old drivers. Anything i should be look at in particular? this is driving me crazy.

I'm just curious, what the "!" in the "/qb-!" switch means? The ! disables the cancel button. The user can not see it.

I am working on USMT, but it looks like it is going to take a lot of configuring those multiple INF files to get it working the way i need. There is a tool from Altiris called PC Transplant that works really well and it has a nice GUI. It is not free though. http://www.altiris.com/products/pctransplantpro/