fly
MemberContent Type
Profiles
Forums
Events
Everything posted by fly
-
[GUIDE] Creating WIM images of Windows XP for system deployment using
fly replied to IcemanND's topic in Windows PE
FWIW, changing the SID isn't necessary. Also, using anything other than sysprep to change the SID is unsupported by MS. -
[GUIDE] Creating WIM images of Windows XP for system deployment using
fly replied to IcemanND's topic in Windows PE
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...) -
[GUIDE] Creating WIM images of Windows XP for system deployment using
fly replied to IcemanND's topic in Windows PE
Wow, this is quality work. **** am I glad that I know about this place. -
Hmmm... After some more reading, it seems the task sequencer doesn't even come into play unless you are capturing an image. Can anyone confirm this?
-
If it matters, I'm doing unattended installs and not doing any image captures...
-
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???
-
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: http://www.goodells.net/dellutility/index.htm The BIOS has code that "intercept" the F12 and "recognizes" setting it active, the "DE" partition. jaclaz 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...
-
Im sure you know this but the update doesn't work.
-
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)
-
Does this work if joined to a domain? If so, its WAAAY easier than what I'm doing.
-
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... That's what I have in the first post, except for the CAD, which I've also tried. Thanks tho.
-
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.
-
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...
-
Bump?
-
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...
-
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...
-
I can't believe this place is failing me, as it never has before.
-
I hit cancel on the XP logon screen, then CAD, and suddenly the autologin works... its very odd.
-
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
-
No replies?
-
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] "DefaultUserName"="USERNAME" "DefaultPassword"="PASSWORD" "DefaultDomainName"="DOMAIN" "AutoLogonCount"=dword:00000001 "AutoAdminLogon"="1" 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] "DefaultUserName"="USERNAME" "DefaultPassword"="PASSWORD" "DefaultDomainName"="DOMAIN" "AltDefaultDomainName"="DOMAIN" "CachePrimaryDomain"="DOMAIN" "AutoLogonCount"=dword:00000002 "AutoAdminLogon"="1" 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...
-
Bump... Can I use relative paths in the OCT? Anyone know before I waste time on it?
-
Ahhh!!! Sweet. Thank you!
-
Even though they are essentially the same thing, I did try the web client. It too needed to install something from the original source.