cluberti

No, add what you have. It won't delay response from anyone else, and at MSFN we welcome everyone's response.

No, using WDS and WinPE 3.0 is far faster than it was with WinPE 2.0, and transfer speeds seem better to once within the PE. I'm guessing the speed difference may exist in your implementation of deployment, specifically a client OS with a non-native PXE client.

Moved. Please try to put your topics in the right place the first time - this has nothing to do with Unattended Windows directly.

Actually, is there any reason you'd recommend making both AD and DNS redundant, but not DHCP? Install DHCP on both and split the scope at least 80/20.

The admin account itself is enabled in safe mode for obvious reasons, but that's expected.

User banned for vulgarity and violation of rule 7 again. As to your concerns, MSFN tries to police and prohibit warez of any kind to be hosted or directly linked here, but if we prevented every single person's account from creation or use on MSFN that condones or participates in warez, we'd have far fewer users and far less time - this is a hobby, not a job. We do what we can to keep MSFN clean and above board (and take the heat for it when we do, as always happens), but purging a member because they do something that we don't like isn't really wise or necessary. Also, there are countries and regions in the world that do not have IP laws, where things like this aren't technically illegal, so we really can only police MSFN, and not the internet.

The problem with performance issues is, slow compared to what? Was it always slow, or did the laptop work previously and now it doesn't? Can you describe the slowness with some specifics, and then what you're comparing them to? Also, what are the specs of the laptop - perhaps XP is too "heavy" for it? Again, I don't really know how else to answer, because the original post is devoid of anything we can use to actually help you troubleshoot it.

You will not find help with warez here. Use nLite on your own copy of Windows, please do not download Windows from anyone but Microsoft. [Closed].

Assuming you still have the boot.wim in WDS, try booting to it and then pressing shift+F10 when the problem occurs to get a cmd prompt. Then try to ping the server, or net use \\server\DistributionShare$. I've seen MDT installs where the share doesn't get created, or has fairly restrictive permissions (it should have at least read perms for everyone).

Limitations like this are the reason tools like MDT and SCCM exist - this just isn't possible. Thankfully MDT is free, so you should consider it.

If the image is aware, you don't have to do anything - on WOW64 it'll actually have access to all 4GB of VA (there's no kernel VA to share in WOW64). The x64 kernel doesn't handle it (like it would on boot on x86), and WOW64 has no configuration for /3GB because of the way it's designed, anything compiled LARGE_ADDRESS_AWARE will automatically have access to all 4GB of it's VA in it's WOW64 process.

You can get a semblance of the old the classic logon screen via secpol or the registry, but it doesn't behave quite as XP did (you'll get username/password boxes after pressing ctrl+alt+del, but not the old NT4-style logon box). You can either configure Vista or Win7 to use this, or the welcome screen, but not both. Pressing ctrl+alt+del twice does nothing in Vista or Win7.

On an unactivated Win7 box, application functionality is not impacted, but you will get the notification once, wait a four-hour window, and then approximately once an hour after that (and I think there are also reboots that kick in after some time as well, although I don't know if RTM is the same as the RC (once every two hours). I am unsure as to whether or not you can get WU updates, but manual update install would still work. I've not let a machine lapse yet, so I don't know for sure. If you've not used any of your grace re-arms, you could also use slmgr to re-arm the timer for another 30 days (up to 3 times).

No, copyprofile isn't going to overwrite settings that are considered user-specific (they'll be in the default profile if copyprofile worked, but you'll still run into most of the settings re-prompting), and I have never seen UAC disabled after sysprep. This is most likely by design. Again, see above. This seems to be by design - you'll have to run the command to disable UAC during OOBE or on FirstLogon when logging on as admin after sysprep completes. The same is likely true for Security Center getting reset by sysprep as well, regardless of CopyProfile settings. By design. The only thing you can do is force all networks to be considered public (which brings it's own set of issues when even a private local home network is treated as public), otherwise every new network has to be classified, and you will be prompted. This is by design. Incorrect, and this doesn't even really do anything (there are bugs with this, even in Win7) that require some scripting on FirstLogon as admin to bypass. I don't believe that this works if you slipstream IE8 into your install, as I've had this problem as well (dism sets up IE8 once the system is up, which is after the IEWelcomeMsg is applied - thus it gets reset). Importing the registry setting instead into the default user profile does seem to work though. This one I'm not sure on - it works for me in Win7, and I've not imaged Vista in awhile, so I wonder if this is another sysprep victim.

Note that Windows has always been able to run under alternate shells since Win95 and NT4, so if you don't like the non-classic shell/start menu, you've always been free to replace it. I do personally like the new menus, but there are alternatives for the classic lovers out there - ClassicShell is probably the most comprehensive of the free ones, though, and it is pretty good.

I usually use ISO Recorder to make an ISO image of the contents of a folder first, then use it to actually burn DVDs. I use oscdimg when working with anything that needs to be bootable, but ISO Recorder for everything else.

Right - it's a victim of the initial image. We probably won't have this problem with SP2, but SP1 isn't going to work. I know what you're getting at, but I thought I already covered that . We won't get into the D drive issue on new images either - I still haven't figured that one out.

Not a problem. Welcome to MSFN .

1. Download the 3.5 SP1 redist package: http://download.micr.../dotnetfx35.exe 2. Extract the installer: dotnetfx35.exe /x:<folder>(where <folder> is the folder you want to extract the package to) I believe once you run that, the installer for 2.0 SP1 (netfx20a_X86.msi) will be in "<folder>\ext\wcu\dotNetFramework\dotNetFX20\".

It's a victim of the image format. If the install was flat, it'd work; if the SP was able to be made as an MSP, it'd work. Unfortunately, the SP is it's own installable package, and as such you have to load an image, install the SP package, then repackage via sysprep (reverse integration). I wish it weren't so, but unfortunately it is. I guess since I keep a base image in MDT/SCCM and use that to build a base WIM to deploy I don't have the pain others do, but I doubt it'll change anytime soon. Until the SP itself can be made into an MSP package (don't hold your breath), it's going to be this way.

You probably won't be able to "convert" it, as an MSI is just a database of actions that get passed to the MSI engine in Windows. I'm assuming you'd want to do "repackaging", which I would avoid (also, most if not all repackaging tools nowadays are non-free and somewhat expensive) unless you absolutely *must* have an MSI package.

You can also try the Daniel_K drivers if your card is supported by them as well, if Creative leaves you in the lurch.

To the OP, please place nLite-related questions in the nLite forum in the future. Thank you.

As to tdx.sys, let me explain - that driver itself is the inbox Windows 7 driver (tdx.sys is the "front man" for network support, I just assumed it was Broadcom hiding behind it given the chipset). Given that and the kernel are in the pool alloc being double freed, the only (real) possibilities are a misbehaving network driver, or potentially an antivirus/antimalware or firewall driver (if you've got anything third party in there, that would also have potentially an LSP, I'd be suspicious). I can't dig further because !address doesn't work in this dump, but I'd start by upgrading your drivers (all of them) to the latest certified versions for Win7, and then I'd monitor for more issues.

Could it be caused by the same driver? Sure. But they're totally different bugchecks with totally different reasons.