MrJinje

Gotcha, was editing my message while you were replying, here is the easiest thing to try. What I would do is use WDS to create another boot.wim (clean no drivers), then integrate all the drivers except the wireless nic(s) and see if that doesn't solve the problem. (thinking is that if no driver is found, it does not cause error). Which is pretty much what arwidmark is saying.

Dumb question, does the default boot.wim that WDS creates even support Wireless, or is lack of wireless support in boot.wim the cause ? i.e. missing wlaninst.dll Can you elaborate if you are booting the boot.wim locally (CD/USB) or via PXE. Normally laptops cannot PXE over their Wireless so my guess you are using sneaker-net (USB). Can you try it with an RJ-45 connected, maybe it will default to the wired nic drivers. Failing that, what I would do is use WDS to create another boot.wim (clean no drivers), then integrate all the drivers except the wireless nic(s) and see if that doesn't solve the problem. (thinking is that if no driver is found, it does not cause error)

+1 vote for boycotting all Seagate products until our "statistical unimportance" affects their bottom line. Don't know what to tell you about your situation, it definitely sux. Here is a merged thread on the issue

Since you mention freezing during performance check. Please try to re-install into a .VHD file so that the performance check is skipped. (boot from VHD does not run performance check - disabled by M$) There is a sticky in the "Windows 7" forum on how to do this. This will determine if the performance check or something else freezing up.

Mount the .wim file. (HINT: Use DISM) Go into the "MountPoint\Windows\System32\OEM" folder and grab the .XRM-MS file. That is your "OEM Certificate". Then restore that WIM image (using the recovery disk) onto one of the machines and run a product key checker to obtain your OEM product key. Once you have both of those items, the it becomes very easy to build your DVD. Place the Product key in your Autounattend.xml, and place the XRM-MS file in this folder on your DVD. DVD\Sources\$OEM$\$$\System32\OEM FYI, if you really want to get good with deploying Windows 7 in your office, you should learn everything you can about DISM.

I gave it a once over using the "keep list", but didn't see anything, maybe your eyes will see something I missed.

%0 is the batch file itself, so that line is used for cleanup. It is not required, but some people like to delete their scripts after they run.

on the main forums page, scroll to the very bottom, look for "Today's active content" I don't know about the other stuff, I think it is limited to a "static" 24 hour period.

go here

Yes.

If you pop over to Max's thread (see sticky) you will find some good examples. Place it in the oobesystem pass during the Microsoft-Windows-Shell-Setup component <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <Order>1</Order> <Description>making the magic happen</Description> <CommandLine>cmd /C wmic useraccount where "name='Bob'" set PasswordExpires=FALSE</CommandLine> </SynchronousCommand> </FirstLogonCommands>

Yes, mount your default user profile and make the change there. REG LOAD HKU\Hive "C:\Documents and Settings\Default User\NTUSER.DAT" REG ADD HKU\Hive\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced /v HideFileExt /t REG_DWORD /d 0 /f REG UNLOAD HKU\Hive If you want to build this into your nLite, you should run it at the T-12 cmdlines.txt stage so that is integrated before any user accounts are created.

Yes, as long as you are logged in using a different account. (so the folder is not in use)

n/m

I would try creating a few copies of the VBS snippet and running them like this. One VBS per SFX. runwait("2.vbs") RunWait("4.vbs") RunWait("wrar39b5.vbs") And each of the VBS files will be slightly different. CreateObject("Wscript.Shell").Run """" & ".\2.exe" & """", 0, False CreateObject("Wscript.Shell").Run """" & ".\4.exe" & """", 0, False CreateObject("Wscript.Shell").Run """" & ".\wrar39b5.exe" & """", 0, False But it's probably a better idea (considering 10 bad SFX files) that you try to repackage each of them so that they are invisible. Add the VBS file to your archive, and edit the VBS to run your internal batch file. Then set the SFX to call the VBS instead of the batch. This way the batch is invisible and you don't need to change your auto-it script.

Gotcha, what I would try is to integrate this setting during the T-12 stage (cmdlines.txt) and using an altered security template that changes the Adminstrator name. http://www.msfn.org/board/password-complexity-automatic-t139929-pid-895560.html/page__p__895560__hl__secedited__fromsearch__1#entry895560 In that example I advised the user to use the runonceex. But in your case you need to run it before first login (and before Administrator is created), so that you can login using your desired name on first boot. FYI, the way to accomplish that on a live machine, is to 1) change "Administrator" name to "laffin" via secpol.msc or other method. 2) create a second admin account "Tom" 3) login with that new "Tom" account 4) delete the existing "Administrator" folder. 5) log out, and log back in with new "laffin" name. Thus creating a "laffin" folder 6) Finally Delete the "Tom" account, it is no longer needed.

Call your problematic batch from VBS like this, it should run the command without showing any cmd window. Run_Batch_Invisible.vbs CreateObject("Wscript.Shell").Run """" & ".\MyBatch.cmd" & """", 0, False Call that VBS from setupcomplete.cmd (or first login commands) using cscript with nologo switch. cscript.exe //nologo Run_Batch_Invisible.vbs Also, without seeing your codes I have no way of knowing if it is a nesting issue or not. Even with this invisible tweak, nested scripts can still create a secondary or tertiary cmd window and we might need to do some minor re-writes to avoid that. Another simpler method might be CMDOW.exe, but that shows a CMD window for a fraction of a second. You are on your own with the image stuff, but hiding the window is actually very simple.

Online Resources http://developers.facebook.com/docs/ http://wiki.developers.facebook.com/index.php/Main_Page

Secpol.msc > Local Policies > Security Options > Rename Administrator Account

Since you mention big oil, maybe you'd like my first few posts in this thread. XOM - Short at $80

Then buy some long term PUT options and profit from the downfall. Better yet, why don't you short sell apple and pray that they don't split again.

Bad news, that section of the GUI is a combined page, it is all or none. You cannot separate them, this is a limitation of the windows 7 installation GUI. Your best bet is to fully automate both settings with your unattend.xml, then run a VBS script during SetupComplete.cmd using the old InputBox to enter a computer name. Rename.vbs strRename = InputBox("Enter new computer name") strComputer = "." Set objWMIService = GetObject("winmgmts:" _ & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") Set colComputers = objWMIService.ExecQuery _ ("Select * from Win32_ComputerSystem") For Each objComputer in colComputers err = objComputer.Rename(strRename) Next You also need to schedule a reboot before it will take effect.

Just to be sure, are you talking about this page. Or is it a different page you see from WDS

Did you try this one. My link If the installer is limited to Windows 7, then try to run it in compatibility mode. That should trick it into working on W2K8-R2