MrJinje

Try netsh interface teredo set state disabled

If you removed the autounattend and used a clean install.wim, then likely you do not have an untouched source. Who sold you the DVD, or is this one of those bit-torrent specials ???

Let's build one then.If the machines are already imaged when you get them from lenovo, you will likely have to boot up one machine, manually make your changes, sysprep, reseal and capture that as a new WIM. Then you could lay that Sysprep image on all the other machines, and your customers would get the OOBE and working keyboard while fulfilling all M$ re-distribution requirements. NOTED: If any of these keyboard settings are user-based or HKCU based, instead make the changes in the default user profile, as sysprep will delete your user account when it generalizes the machine. (but not default user settings)

Here is where to make the setting. Whether or not that will work, your guess is as good as mine, WDS does not seem to be very straightforward.

Can we set aside your current W7 setup, and re-copy your W7 DVD (clean install) so we can try this with a fresh Install.wim. Then we should be able to use the XML (after making changes #1 and #4) and see if that new wim doesn't fix problems #2 and #3. My guess is something ran DISM /TIME-ZONE and force installed your Time Zone preventing the pop-up. Fresh copy of Install.WIM should resolve these kind of issues.

Try this (only for Firefox). Then reload that page, mine is completely blank. https://addons.mozilla.org/en-US/firefox/addon/6623 Have mine set to delete all LSO's when I close Firefox.

Yes At times Explorer.exe is known to do that. EDIT: But not for prolonged periods.

Can you export your OS to a WIM and create an ISO, and see how that ISO installs in a VM. Then we can narrow down if it is the WIM itself or a WDS/MDT settings issue. If that doesn't help, maybe we need more details, is this a vanilla RTM image, or a customized sysprep job, or some kind a vlite special. What exactly are we working with ?

Arlesterc, open secpol.msc and go here to make the change. You need to "Enable" that setting. (it should be disabled by default)

MacGyver method is still the best. Just need a car battery, 100' copper wire coiled around an iron rod, and some jumper cables. Instant electro-magnet. Caution, may cause irreparable HDD damage, 80's theme music, and a propensity for hockey hair.

Hadn't heard of that before, can you go into greater detail ?

Did you do any language modifications using DISM. What does you lang.ini say ? DVD\sources\lang.ini

You just need to modify/recreate your DVD with the new boot.wim and it should work (test ISO in VM before burning).

In WDS, have you both enabled unattended installations and associated the XML file with WDS for that (x64) architecture Open WDS, Right Click on your Server, select properties, go to "Client" tab.

OK, next test is to re-mount the boot.wim image #2 and using explorer, navigate to C:\Mount\Windows (inside the mounted WIM), and try to drill down to System32. I'm hoping it throws an error saying you do not have permissions to read inside the directory. (based on the second clause in the listed error) Otherwise, is there any way you can replace that boot.wim with one from an untouched DVD source just to rule out anything henke going on with it. Try it with a different boot.wim, its possible yours got corrupted somehow. Yet another issue may be that you are not running it from an "Administrative" context. Did you open CMD with Run-As Administrator

Assuming he is not mistyping his error, there might be a command line fix using NET USER (if you can get some alternative local admin rights). NET USER username /EXPIRES:NEVER Run NET HELP USER for greater details.

I think easy transfer will require some small user interaction (no silent options are known), if you are corporate minded you should be using USMT from the WAIK. It should allow you full automation. Check the WAIK documentation (usmt.chm) for greater details. $OEM$ folder is just a structure to import files to your image without "mounting/editing" your WIM. If you are more comfortable editing your WIM and placing the files directly inside it, you should be able to script to it's location just the same. (it's all about knowing where the file is when you need to call it from script). Another alternative if you have network access during the install, is to map a drive to your server and run the .MIG from the share. [just-a-thought]The network option is the best if you have a corporate network, you can point a first login command to a script on your network share, and could update your scripts on the server side without needing to edit your images. Very future proof. [just-a-thought]

Maybe you should tell me which things you need that are not working. Username/Password and Timezone are not configured in the XML (as they should not be), so you should be getting prompted during installation already. Tell me if this is not the case. For now I'll assume those two are already working correctly and try to help fix the other two that are actual problems. #4 is configured in your XML. Delete this entire line to re-enable the Network Location prompt. <NetworkLocation>Home</NetworkLocation> I think #1 is configured here, delete this part and it should go back to asking what language you want during the install.

He already answered this question. He created the ISO from the original. Enough witch-hunting for now, he is not doing anything wrong (except for slip streaming SP3 from W7), which as he stated in his final post, he will simply not integrate SP 3 (since he only has access to W7). That should solve all his problems allowing his COA to activate properly when installing.

Check here. http://www.msfn.org/board/index.php?showtopic=128393 To find the link, go to the KB Article for each update, follow the link "for it professionals", scroll to section listing affected OS'es, follow the individual links to the download pages for each OS (W7x86, W7x64, W2K8-R2x64 etc) from there, click the "Download" button. On the next page, find the "start download" and right click it to get the direct path.

if he purchased it at a computer store with {insert any small piece of hardware}, it is likely a full install CD with COA. Usually the Key issue with nLite is related to slip-streaming SP3, so you will have to re slip-stream SP3 from XP-Mode or any other XP machine he can find. It cannot be slip-streamed properly from anything but XP. Windows 7 and Vista simply do not do it correctly.

Mostly because you need to delete those sections from inside your unattend.xml or simply do not use an unattend.xml The entire point of being "unattended" is to not require a person to be at the computer "attending" to pop-up windows. Simple answer is delete your unattend.xml and run a normal install, or attach, (do not paste) your XML, and maybe someone can tell you which sections to delete. (probably the entire OOBE section)

Go into AD User and Computers, right click user-name > goto accounts tab > and check "Never" EDIT: LOL, read closer dummy, the OP said Local.....

Another way to capture your user profile before sysprep'ing is to use the Windows Easy Transfer on your DVD, run a capture, then make restoring your profile settings part of your unattend process. It doesn't even need to be done on the same machine, you can create your profile on a different machine and use your existing install.wim and modify it to install the .mig (windows easy transfer migration file) on first logon via your $OEM$ folder. (or if you have access to USMT that could work too). Assuming you don't mind having to make an additional reboot after installing, this could be a fix that doesn't require capturing a new sysprep image.

Try the internal method. Open WDS drill down to "Boot Images" right click, select "Create Capture Image" and follow the prompts. When I PXE booted, I picked my new Capture image and here is the screen I get. It was 100% wizard driven, so maybe not the "best" method, but certainly the easiest/quickest as opposed to manually creating your own PE image and fully scripting IMAGEX by hand. It can only capture "sysprep" machines, so if you are not sysprepping, an alternative would be needed.