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/

Thought I'd throw out my solution in case anyone else ever runs into the same issue. I ended up having to put 2 explicit ipconfig /renew statments in my batch file to try to get the ip address. Only once wasn't enough it would still time out. added the second one and it picked it up

It appears my problem is DHCP related. It doesn't get an address fast enough and the command just bombs out. I took out the command for BartPE and used the Factory -winpe command to start the network. It seems to be a little faster but not fast enough. I think I'll just have to get a realy copy of WinPE. I never had a problem with that taking so long in the past. any idea why it would take 20-30 seconds to get an ip address from a windows server?

Plenty OF DHCP scope, it will pull an address, just takes a while. I am actually using BartPE so i didn't have to configure the winbom file. I could try using that instead. What i sould do is have my boss find the copy of WinPE he lost

Even if i break the batch file and try net use multiple times it just goes after something behind the scenes finally happens. I could try it 20 times and it just decides to finally go. The only part I had specifically hidden was the output of the ping so it wouldn't just fill up the screen. I can maximize the command window that is initializing the card and services. I assume the interface would be up otherwise tcpip, dhcp, and NLA wouldn't start. Although taking another look at it, it seems as if maybe my problem is DHCP. I just looked at the ipconfig after the batch breaks, the ip goes from 0.0.0.0 to a 169.x.x.x address before it finally pulls a dhcp ip address. I have noticed other PCs on the network are slow getting addresses sometimes. Is this a server issue or can I speed it up somehow?

I am actually doing that already. I thought it may have been a timing issue so i put in a ping to my localhost for about 30 hops which takes 30ish seconds (probably a bit less). I am outputting the results to >NUL so its not visible. I can try taking that out, but i don't think it will solve it. I may be able to the diskpart and format before the drive map to buy me a little time, but i think I may have already tried it.

I am setting up BartPE to kick off an Unattended network install of XP. My problem is that when I try to map a drive, it can't find the connection for about another 30 seconds or so after the services have started. I have tried putting a delay in my batch file with a ping for a bout 30 seconds or so, still no dice. If the batch file terminates and I wait, I manually keep trying and eventually the command will map the drive. But that kind of defeats the purpose of an automated install. Any ideas why it takes so long to "find the network" or what I can do to get my drive mapped other than pinging my local host for a couple minutes to stall?