cluberti

I think that might be part of your problem. From where was this original image captured?

With those specifications, you will probably find XP to be a better performer than Windows 7 on that machine in most scenarios.

Correct - there are hints in there on how to do it. You can set it in the registry or in group policy/local policy as well.

Clive, this has been discussed before. Don't forget that you can try a search before posting a question just in case; we've got 9 years of history to search through .

If it was replying/forwarding/etc, I'd guess you have an add-in in IE that's crashing (spawning a new window in IE8 can spawn a new process, which means reloading all add-ins, and this is the most common location for an IE8 add-in crash). What happens if you start IE from a command line of iexplore.exe -extoff and then try the site? Does it still crash?

For the ComputerName question, it's not available because the ComputerName variable is only valid in the Specialize pass. As for the rest: Microsoft-Windows-LUA-Settings in offlineServicing - EnableLUA = false Can't be done from a setting in the Unattend.xml itself, but that's where running something like this comes in handy from a Run command. Again, not gonna be found in the XML settings itself (you can configure the StartPanelLinks under Windows-Shell-Setup, but you won't find anything beyond that. You can always use preference policies in a domain to do that though, otherwise you'll be making a default profile. Nope See #2 See #3 Nope You can use the Networking-MPSSVC-Svc to set some of the service and group defaults, but not any rules. You will have to script those with netsh. Nope, although you *can* copy local security policies from one machine to another. Nope You can probably do all of the Nopes with powershell or vbscripts running from Run commands in the XML, but a lot of what you're looking to do is considered advanced configuration and is meant to be handled by group policy or the user themselves, so there's no unattend settings directly for them (again, everything can be done, it just matters how much scripting you want to delve into on a Run command on FirstLogon to do these things).

You can use bcdedit to edit the bcd file in \boot on the CD, but you can only change the location boot.wim is loaded from. Setup.exe is still going to look in \sources for installation .wim files to display installation options for, and I am fairly certain this is hard-coded and cannot be changed. I would also have to ask the question of why you would want to do this, as it (on it's surface) seems like a silly thing to do.

It's not listed simply because the article hasn't been updated to list the newer OSes, but watch a procmon - the reg value gets checked. It should work. You can use the value of 10002 (hex, that's 65538 decimal) if you'd like, but you have to make sure you reboot the server after adding the reg value for it to take effect.

I would simply uninstall and reinstall the Win7 WAIK. That should be sufficient to fix it.

I haven't looked at these yet, but I think Standard can do WMC mode. My guess is the default shell registry is changed to point to the Media Center binary ehshell.exe so as to launch it, but I'd have to dig deep to see exactly what it's doing.

If you enable userenv logging and then try to log in with that user (you probably want to do it during off hours, because it will generate a lot of data), you should see a bit more. You can also check for login failure events in the event log, but those aren't as useful as userenv logging. You probably want to set the UserEnvDebugLevel reg value to 0x00030002.

DSIM replaces imagex for almost everything (and for things it doesn't, it acts like a wrapper on imagex commands). Using Imagex/PEimg and DSIM to inject drivers to an offline image ultimately do the same thing - add drivers to the root Windows CD so that they can be discovered and installed during hardware detection.

No, not values, but subkeys. Do you see any subkeys under ProfileList other than Administrator? (These will be sorted by SID...)

I've moved your post to nLite, as this is where it should start. If you could, please attach (not paste) your lastsession.ini file, as well as the winnt.sif file created on your XP CD by nLite so we can have a look at what's going on.

You might want to look in the registry on the machine in HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList before capture to make sure there are zero users listed here that will not exist on the captured image. Anything here will cause that failure specifically, and it sounds like this might at least be something you want to look into.

Is the user unable to log on to the server, or is the profile just not getting created and the user is logging on with a temporary profile? More info is going to be needed to help you, as your problem description isn't 100% covering all of the bases of what's happening here I believe.

No, it's more akin to hiring the company that built your car to be your mechanic. It's a good engine, and I'd bet it'd be a part of the OS if they wouldn't get sued to oblivion for doing it.

Another +1 for migrating off of .cmd scripts, and while using .js/.vbs is much more of a preferred method, powershell is where you want to do any sort of console scripting in today's day and age. For things you want GUI-based, HTAs with vbscript/jscript are still the easiest place to go (you could go .net + powershell, but at that point it's an app, not just an admin script ).

In fact I've migrated all of my projects from previous versions to 2010, and only one of them (C++ 6.0 app) required any tweaking (needed to review some code and follow this). My .NET apps came over without any problems at all. The thing to watch for when coming from VC++ 6.0 to 2008 or 2010 is that there were pretty big breaking changes in 2005 (I think mostly for ISO compliance). Once your code is in 2008, you should be able to migrate to 2010 without issues, although I can't guarantee that v.Next won't have issues if there are breaking changes. This would really not matter much for migrating forward from any version though, for what it's worth.

You need to run adplus BEFORE explorer crashes - otherwise, it's too late. Adplus spawns cdb.exe, which attaches to a running process and monitors it for crashes. If you're running the command AFTER the dialog stating the process needs to close, you're too late.

What happens if you use align=16065? If it works, you'll have 16 to 32MB of space unused on the disk, but you'll know you're absolutely running into 931760.

NP . I'd still quarter the devs...

http://www.nytimes.com/2010/06/29/technology/29dell.html?pagewanted=2&ref=technology

According to this, explorer.exe didn't crash (didn't even get a 1st chance exception). What was this of?