cluberti

There's no way to disable bitlocker, but if your users are already running as non-administrators they cannot enable it anyway. One trick you could try is to set up in GP the configuration to store keys in AD, but don't extend your AD schema and don't configure it for storing bitlocker keys (it'll fail if someone does manage to run it on a domain machine). But no, there are no inbox options for actually *disabling* bitlocker entirely.

You don't - you'll have to hack it. If you've got a Windows 7 Pro machine, is there any reason you aren't just using the XP Mode VM download of XP Pro you're already licensed to use?

I've actually had that happen to me a few times with MDT - if you look in WSIM or notepad at the task sequence's unattend.xml in the control folder, it'll show en-us (0409), but when you load the image from MDT, it'll be GB instead of US. In those situations, I've had to completely demo the *entire* MDT install, shares, folders, files and all (short of my app package source files and OS WIM files) and reinstall. Once it starts, it will continue. You literally have to rip MDT out - recreating just the task sequences or bootstrap/custom.ini files won't fix it, for some reason. It sucks completely, but I've run into it at least twice and once it's broken, that install of MDT is *always* broken (and it's always only en-us to en-GB - other languages continue to work just fine).

I'd have to see proof (not a one-off "it happened on Vista!" post by some random user), because it's easily, readily repro'ed on XP (again, even in a VM) by myself, at least 2 - 3 times a day of normal use. It never happens under Vista or Win7 during the same usage, so while it's *possible*, it's just not *probable*. It's possible I might win the lottery too, but the probability is likely just as low .

You've already done something bad - you ran an nLite'd source (the SP3 source) through nLite again, and usually that can be problematic. What I would suggest is go back to your SP2 source and integrate SP3 manually using the /integrate switch, *without* nLite. Then run that source (after making a copy, of course) through nLite and see what happens.

Moving from Windows XP section as per the nice big red bolded block of text above your original post which you neglected to read: "If you have questions about customizing Windows XP that are nLite-specific, please post them in the nLite forum, not here."

At this point, I think it's probably beneficial for you to post your unattend file, just to make sure. As to your questions, I'm assuming your OemPnpDriversPath points to \Drivers on the boot volume, so you should be placing the uncompressed disk drivers in the $1\Drivers\ folder structure in $OEM$.

Fantastic .

I can't really answer #1, as I don't do a lot of the office hacking for size that some folks do - however, just removing all of the language binaries and folders other than the one you're actually installing can (depending on the language(s) you keep) sometimes be enough to get down under 700MB - the updates are what causes it to grow, however. As to #2, I'm not sure about that either - the features in the Office disc are licensed for the version they came with, so I'm not sure you can easily put them onto the same disc and use the same installer for both. I'm assuming you're licensed for both and just want both on the same machine, but short of making the Office 2007 components from a non-Enterprise CD into a self-extracting and installing executable, I'm not sure it can easily be done. I'll leave that to others who do more installation modification than I - all of my installs are from enterprise media for those features, and usually from SCCM.

First, welcome to MSFN . Second, a little more info is helpful - obviously this is an XP OEM key, but what disc was used to make the nLite'd CD? Also, what platform did you run nLite on (another XP machine? Vista/Win7, etc?), and what machine are you trying to install this CD on specifically where you get the error?

What you might want to do is give them an XP SP3 slipstreamed disc without a key, and download/slipstream all of the WGA fixes from your (legitimate) installation. That way you have one specific XP recovery CD you've made, and they can enter their key, timezone, etc. during the GUI installation.

The clipboard and OLE/COM are pretty different underneath between XP and Vista or Win7, and given it affects multiple IE versions across multiple OSes (right up until the underlying OS design was changed), and that it repros on generic VM hardware, I don't actually think it's specifically an IE bug, I think it's actually a clipboard / OLE bug that IE is invoking due to whatever happens between copy/paste in IE. And no, you cannot run IE6 on Vista or Win7 (at least in a supported way) without a Virtual Machine.

If it's local, that won't help. And, if you didn't create a second local account with admin privileges or the machine isn't on a domain with a domain admin account you can use to log in, resetting the password offline is about the only option (and it has to be done with a tool that understands how to reset the password timer too, which a good number of reset tools out there do not (at least not that I've seen - I haven't used any others in about a year or so in favor of the MSDaRT locksmith tool, which can do this properly offline). It was a change in Vista and Win7 that even local accounts require password changes every <x> days (I think the default is 45) by default. The error isn't that the account itself has expired, it's saying the password validity has expired. Depending on how long it's been since it expired, you should still be getting prompted for the old password so that you can change the password itself. If not, and I'm missing the point, you might want to post a screenshot of the error, because accounts don't expire by default (unless you configure them to), but passwords do.

Again:

A 2019 will cause a 333, because nonpaged pool is required to do the map for the disk write. The registry is memory mapped in sections, so when a section needs to be flushed it will fail, but the 2019 indicates you're out of nonpaged pool memory to satisfy requests (and once you hit this, it will *always* fail until the reboot, even if NPP frees up to satisfy a future request). Poolmon will catch this, but it's not always easy to use. I've got a tool that you can use to catch this, linked at the end of this post. Extract the linked file to C:\Poolmon3 Double click C:\Poolmon3\_LogPool-as-a-service.cmd to start the actual logging This will install poolmon as a service on the machine (obviously this should be run as an administrator on the machine) via srvany, and generate data in a folder called Poolmon-OUTPUT inside the C:\Poolmon3 folder. Let it run until you start seeing the 2019 events again, and then run the _RemovePoolmon3Service.cmd file to stop the service (and thus the logging) after you've let it capture ~5 minutes of 2019s. Once you've done that, compress the Poolmon-OUTPUT folder and attach it to a new post here, and we can tell you what's causing the 2019s (also, feel free to reboot the server once you've gathered the 5 or so minutes of 2019 data, to get yourself back up and running). Please note this is probably a driver issue, but it isn't a disk issue - the 333 error is actually caused by the 2019, due to the way the registry is mapped and the fact that it requires NPP (which you've exausted on the server) to complete the registry flush to disk. If you want to know what nonpaged pool is (above and beyond it's a kernel memory pool that drivers use), you can find more in the Windows Internals' books by Mark Russinovich. Tool download.

Actually, Trip - his command is just fine. If you pass the path to a folder, DISM will parse the entire contents of the folder for .inf files. The command itself is fine, however Mr Jinje is probably onto something with the folder containing the image. Assuming it was mounted and is being accessed via the tool, it may be a sharing violation or some other. To the OP, You might want to try and mount the WIM outside of Mr Jinje's tool and use the DISM commands manually (and using a folder other than C:\Mount is also a potentially good idea) to try and add the drivers.

I'm not sure it's as big a deal as you're making it out to be (maybe it is, but I don't see a huge outpouring of grief over the 2D subsystem anywhere). While I agree there are some issues, I don't think it's affecting most people. For example, I didn't notice it until it was mentioned in this thread - and it seemed to be video-driver specific too, *AND* specific to Nvidia drivers and newer Radeon 5xxx series cards (which seem to lack almost all 2D features in the driver), meaning it could be poor driver ports from WDDM 1.0 to 1.1 causing it, or just video driver vendor issues. I tried this on my wife's Dell laptop with an Intel integrated 4500 POS, and I couldn't repro any of it there either, for what it's worth.

It's called reading the documentation. Specifically, the <CopyProfile> parameter of your unattended file. If you ran sysprep /generalize (and if you're at least following the sysprep documentation to create a proper image, you did) then it's doing what you told it to do . Also, you've still not answered MrJinje's question...

I've actually seen the "odd text in the seaarchbar" paste issue as well in the past, and it was only on XP. After upgrading to Vista back in 2006, the problem went away (still IE7), and I've never had it happen with Win7 either. However, I can confirm I've had it happen in a virtual XP machine, so I don't think it's driver-related in any way either.

Only other question before we see the .ini - was this source "clean" before it was run through nlite, or had it already been run through nlite before slipstreaming the SP and update pack?

We're in the middle of an upgrade, and weird things are happening with the old (current) board. Hopefully once we migrate this will all be resolved, but for right now it's just going to be ........ weird .

Usually a BSOD right after install is complaining about the lack of a bootable device.

Given the bent of the way MS is designing their GUI nowadays, I don't think you'll ever be upgrading with that stance, honestly.

Hmmm - a fixed drive, set to automount, with no filesystem (at least not to WMI, anyway). The second question - if you boot from a recovery disc or WinPE disc, does the partition show up in diskpart or any other disk management tools there? It almost sounds like some recovery or tools partition that the BIOS has set up.

It seems like this has been flagged as a virus by some engines, but not all, we'll all have to hold off to make sure we know for sure if the file is, or is not, infected with a virus or if a false positive is possible. By the way, anyone can submit samples to most A/V vendors (there are usually instructions for each on their respective pages) and get a response within about 24 - 48 hours, depending on vendor. The file has been submitted to AVG, McAfee, Symantec, and Microsoft for analysis, and from there we'll see.